[
https://jira.codehaus.org/browse/MNG-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=281586#comment-281586
]
Joerg Schaible commented on MNG-1977:
-------------------------------------
bq. compile -> compile = runtime
bq. This would make many builds far more robust to changes in child
dependencies.
You can simulate this if you use a global master pom. Then you would not only
set the version in the depMgmt, but also the scope of all deps to runtime.
That will have the same effect, you would have to set compile scope explicitly
everywhere in our project. Been there and reverted it ... you'll see yourself,
if you try ;-)
> 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
