You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Paul Benedict (JIRA)" <ji...@codehaus.org> on 2014/07/02 15:45:19 UTC
[jira] (MNG-3564) alternative and higher level configuration option
to
[ https://jira.codehaus.org/browse/MNG-3564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Benedict updated MNG-3564:
-------------------------------
Fix Version/s: (was: Issues to be reviewed for 3.x)
> alternative and higher level configuration option to <exlusions>
> ----------------------------------------------------------------
>
> Key: MNG-3564
> URL: https://jira.codehaus.org/browse/MNG-3564
> Project: Maven
> Issue Type: New Feature
> Components: General
> Affects Versions: 2.0.9
> Reporter: manuel aldana
>
> maven provides scope (test, runtime etc.) to filter certain dependencies.
> never the less sometimes it is quite helpful to have a another configuration option, where you decide what to include transitively or what kind of dependency-set is relevant to your current project. using <exclusions> configuration to accomplish this is often very verbose, non-standard and is difficult to read (it is often not obvious what is meant with all these exclusions).
>
> as an example ivy includes such configuration meta-info approach (see http://ant.apache.org/ivy/m2comparison.html). this feature would be nice because when building releases one is more flexible.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)