[
https://jira.codehaus.org/browse/MNG-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=281661#comment-281661
]
Jean-Noel Rouvignac commented on MNG-1977:
------------------------------------------
Thanks for the feedback guys.
My use case is as simple as that: I want to exclude some transitive
dependencies accross all dependencies to allow compiling GWT code. Otherwise I
get the error "the input line is too long" on windows. So far we have to
exclude the same transitive dependencies for all the dependencies where they
exist which can be as many as 8 today. Not nice :-/, hence why I am looking at
this solution. A simple global exclude would solve the problem for us.
It looks to me the code I did is good enough to handle my use case. I just need
to know how the Maven team wants this configuration to look in the pom.xml file
and then I can look at doing it.
> 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
