Not as far as I know, though improvements seem to be planned:
http://jira.codehaus.org/browse/MNG-2315
http://jira.codehaus.org/browse/MNG-3832
http://stackoverflow.com/questions/547805/how-to-exclude-all-transitive-d...
--
Jess Sightler
Red Hat Consulting
Mobile:704-916-9383
http://www.redhat.com
----- Original Message -----
From: "Jason T. Greene" <jason.greene(a)redhat.com>
To: jboss-as7-dev(a)lists.jboss.org, "Paul Gier" <pgier(a)redhat.com>
Sent: Monday, May 14, 2012 1:42:35 PM
Subject: Re: [jboss-as7-dev] Reminder about pom.xml exclusions
On 5/14/12 12:05 PM, David M. Lloyd wrote:
Just a reminder that when you add a new Maven dependency to AS7,
before
submitting the pull request, be SURE to thoroughly audit the output of
"mvn dependency:tree" and make sure that all transitive dependencies are
excluded in the main "pom.xml" - even if they look harmless! If you
don't, we can run into a problem where different versions of Maven or
different JDKs give different dependency graphs, resulting in builds
that work for some people but not others, which sucks for everyone involved.
If there is a transitive dependency that you need, then add it in as a
first-level dependency in the main pom.xml and specify the version directly.
I think this is what is underlying
https://issues.jboss.org/browse/AS7-4782 and I'm sure others will run
into similar issues as well.
Paul,
Does maven have a no-transitive feature? :)
--
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev