[
https://jira.codehaus.org/browse/MNG-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Noel Rouvignac updated MNG-1977:
-------------------------------------
Attachment: global_excls_maven3_v3.patch
global_excls_it-test_v3.patch
Hello,
I gave another go at this issue.
This time, I specified the exclusions in the pom.xml file by following this
approach:
{code}
<project>
<dependencies>
...
</dependencies>
...
<exclusions>
<exclusion>
<groupId>com.mycompany</groupId>
<artifactId>myproject</artifactId>
</exclusion>
</exclusions>
...
</project>
{code}
Please let me know what you think of these patches.
Thanks,
Jean-Noel
> 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_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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
