[ http://jira.codehaus.org/browse/MNG-2326?page=all ]
Carlos Sanchez closed MNG-2326:
-------------------------------
Resolution: Duplicate
This is a duplicate, the exclusions affect all dependencies.
Still you should NOT exclude a dependency if you need it in any version. You
have to add it to your pom and that dependency will always win the transitive
ones.
From:
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
Dependency mediation - this determines what version of a dependency will be
used when multiple versions of an artifact are encountered. Currently, Maven
2.0 only supports using the "nearest definition" - so you can always guarantee
a version by declaring it explicitly in your project's POM.
> 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
