You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Kees de Kooter (JIRA)" <ji...@codehaus.org> on 2014/03/14 15:53:04 UTC

[jira] (MNG-1977) Global dependency exclusions

    [ https://jira.codehaus.org/browse/MNG-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=342902#comment-342902 ] 

Kees de Kooter commented on MNG-1977:
-------------------------------------

8 years, 155 votes, 5 duplicates and 4 patches later I wonder: should I be proud or embarrassed that the issue is still unresolved?

> 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: Issues to be reviewed for 4.x
>
>         Attachments: global_excls_it-test_v2.patch, global_excls_it-test_v3.patch, global_excls_maven3_v2.patch, global_excls_maven3_v3.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 was sent by Atlassian JIRA
(v6.1.6#6162)