[
https://jira.codehaus.org/browse/MNG-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=277621#comment-277621
]
Arnaud Heritier commented on MNG-1977:
--------------------------------------
Hi, I didn't review your patch thus I won't judge about it.
I really dislike this idea to continue to play with the lake of control in old
maven versions which will ignore things they don't know in the POM.
For me such change must be done only in a new POM version and with all
mechanisms to be used with previous and future maven versions.
Did you test such POM with Maven 3.0.x ? I think it at least display a warning
if there is a scope it doesn't know (I don't remember but perhaps it breaks the
build).
And when a maven version ignores it, what does it do ? It uses the compile
scope ? #fail in that case, instead of excluding it, you explicitely add it
(transitively)
Cheers
> 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
