[
https://jira.codehaus.org/browse/MNG-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=277686#comment-277686
]
Pierre-Antoine Grégoire commented on MNG-1977:
----------------------------------------------
Hello,
BTW the <scope>excluded</scope> solution doesn't really helps in any way to
deal easily with excludes.
It looks like a hard-wired work-around.
Adding a <transitive>true|false</transitive> or a
<handling>transitive|simple</handling> (maybe better to allow further
unforeseen improvements) both at the level of all <dependencies></dependencies>
or at the level of a single <dependency></dependency> wouldn't be hard to deal
with (just a test to trigger the transitive search of the underlying tree) and
would achieve the expected result.
I thought that the pom model was supposed to evolve from version 3.0.x on?
Regards.
Pierre-Antoine.
> Global dependency exclusions
> ----------------------------
>
> Key: MNG-1977
> URL: https://jira.codehaus.org/browse/MNG-1977
> Project: Maven 2 & 3
> Issue Type: New Feature
> Components: POM
> Reporter: Kees de Kooter
> Fix For: 3.1
>
> Attachments: global_excls_it-test_v2.patch,
> global_excls_maven3_v2.patch
>
>
> I depend on some libraries, which in turn depend on something
> (which in turn depend on something) that I don't want, because I declare
> some other artifact in my pom.xml.
> A concrete example: I don't want that the artifact "xerces" is imported in
> my project because I declare to depend on "xercesImpl" which ships newer
> libraries but with the same namespaces.
> I guess I would need an "exclude transitive dependency at all", either
> globally or from this and that artifact. I saw the <exclusions> tag, but it
> forces me to be very verbose and have exact control on what is required by a
> dependency.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
