Missed comment<http://jira.codehaus.org/browse/MNG-1977?focusedCommentId=194430&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_194430>in global dependency exclusions issue discussion, it points to related exlcusion replacements issue <http://jira.codehaus.org/browse/MNG-4391>.
Regards, Stevo. On Thu, Oct 15, 2009 at 12:55 PM, Stevo Slavić <[email protected]> wrote: > Hello Maven users, > > In Maven 3 it will hopefully be possible to define global dependency > exclusions <http://jira.codehaus.org/browse/MNG-1977>. Question is will it > be possible to specify transitive dependency exclusion replacements, local > and/or global? > > Here is one example case where I think this would be useful: > spring-security-core v2.0.x module is built against spring framework 2.0.x > and depends on its artifacts, some of which have been reorganized and/or > renamed in 2.5.x. If then application depends on both spring framework 2.5.x > and spring security 2.0.x, duplicate modules (backwards compatible, yet with > different maven artifactId) will unnecessarily be present. > > With Maven 2 one can in dependencyManagement section specify dependency > exclusion (for spring-security's transitive dependencies to spring 2.0.x), > but can not specify their effective replacements at same place - if I'm not > mistaken, instead I have to spread that dependency replacement info all over > the multi-module project pom's. For a non-reporting plugin one can specify > exclusions and add dependencies but not for a dependency. > > Regards, > Stevo. >
