[ http://jira.codehaus.org/browse/MNG-2326?page=comments#action_66453 ]
Joerg Schaible commented on MNG-2326: ------------------------------------- @Carlos Because a lot of current POMs on ibiblio do not care about proper dependency management (e.g. current commons-lang reference servlet-api) or we have a different use case than the authors (e.g. commons-configuration reference commons-digester, which is only needed if you use the ConfigurationFactory - a functionality we don't use at all). The current dependency implementation implies now, that we don't use servlet-api or digester in none of our projects anymore - which is plain wrong. While you can fix POMs of case 1, you will never be able to handle case 2 since deps are related to use case. > exclusion of transitive dependency is too dominant > -------------------------------------------------- > > Key: MNG-2326 > URL: http://jira.codehaus.org/browse/MNG-2326 > Project: Maven 2 > Type: Bug > Components: Dependencies > Versions: 2.0.4 > Reporter: Andreas Schildbach > Assignee: Carlos Sanchez > Attachments: mng2326.zip > > > Please consider the following structure: I've got a module M that has got the > dependencies D1 and D2. Both D1 and D2 depend on a transitive dependency T. > I have excluded T from D1 per <exclusion> on the M POM in the dependency to > D1. > Now, one would expect that T is still pulled into M, because there is no > exclusion on the D2 path. But this is not the case, "mvn site" on M is > missing T (in the dependency report), and it is missing from the classpath, > too. However "mvn eclipse:eclipse" on M does the job right: T is listed. -- 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
