[
http://jira.codehaus.org/browse/MNG-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144971#action_144971
]
David Jencks commented on MNG-1977:
-----------------------------------
It seems to me that the original problem would be solved better by artifact
substitution or aliasing rather than more exclusions. e.g if you want to use
something reasonable such as slf4j to imitate commons logging usage you want to
replace any dependency on commons-logging with one on jcl-over-slf4j.
Similarly you might want to swap spec implementations, say to use the geronimo
ones no matter which copies the original projects were built against, or use
geronimo's activation implementation instead of sun's. This isn't quite the
same as what osgi gives you but is quite powerful.
> Global dependency exclusions
> ----------------------------
>
> Key: MNG-1977
> URL: http://jira.codehaus.org/browse/MNG-1977
> Project: Maven 2
> Issue Type: New Feature
> Components: POM
> Reporter: Kees de Kooter
> Fix For: 3.0
>
>
> 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 contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
