On Fri, Feb 19, 2010 at 9:10 AM, Aaron Birkland <[email protected]> wrote: > >> I think the biggest hang-up in the whole process was figuring out >> which exclusions had to be done in the root pom for which libraries, >> so that the real log4j and commons-logging libraries wouldn't be >> accidentially transitively included. I found "mvn dependency:tree" >> helpful along the way. > > Is this something we would need to watch out for in the future? i.e. if > we need to add a new library hosted in mvn central (or wherever) as a > dependency, do we need to be careful in the case that it depends on > log4j or commons logging and be sure to put in the appropriate > exclusions?
Yes, unfortunately maven doesn't (yet) support global exclusions: http://jira.codehaus.org/browse/MNG-1977 It's probably a ways down the road on the maven roadmap. Until then, it would be nice to have an automated way to catch the use of unwanted libraries, though. I wonder if there's a maven-friendly way of failing the build if dependency:tree includes commons-logging (or log4j)...hmmm. A shell script could do it, of course: mvn dependency:tree|grep unwanted-lib - Chris ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Fedora-commons-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers
