[ http://jira.codehaus.org/browse/MNG-1797?page=comments#action_68235 ]
Andreas Schildbach commented on MNG-1797: ----------------------------------------- This issue is very annoying. There are several POMs on ibiblio that are missing <scope>provided</scope> from their javax.servlet, servlet-api dependency. I tried to fix this by excluding the dependency from the affected dependency path, and including the dependency in my POM (using the correct scope) again. Due to the behaviour of the exclude-mechanism, this approach does not work (and there does not seem to be any alternative, does it?) > Dependency excludes apply to every subsequent dependency, not just the one it > is declared under. > ------------------------------------------------------------------------------------------------ > > Key: MNG-1797 > URL: http://jira.codehaus.org/browse/MNG-1797 > Project: Maven 2 > Type: Bug > Versions: 2.0.1 > Reporter: David Hawkins > Fix For: 2.1 > Attachments: MNG-1797-maven-project.patch, MNG-1797-unit-test.patch, > it1019.tgz, it1020.tgz > > > If you specify ANY dependency excludes, all dependencies after that one in > the pom will also exclude what you specified. They appear to be cumulative > on every dependency in that they bleed over into sibling dependencies. > It's easy to test if you add an exclusion to a random dependency. This > exclusion should exclude a required transitive dependency that is included by > a dependency lower in the list. You will find that the dependency lower in > the list no longer includes the required dependency because it is using the > filter you declared in the other dependency. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
