struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig McClanahan" <>
Subject Tracing Maven2 Transitive Dependencies
Date Sat, 10 Jun 2006 18:25:57 GMT
I'm working on the Maven2 build for the shale-usecases example (on the
mvn_reorg branch).  Currently, the application buids, but it fails on some
XML parsing errors when you deploy it.  In turn, this happens because
xml-apis-1.0.b2.jar and xercesImpl-2.2.1.jar are getting picked up as
dependencies that need to be included in the war.  Now, the challenge is to
identify where they are coming from so they can be excluded.

I've tried Wendy's suggestion of using -X on the mvn execution, which gives
a pretty copious amount of output ... and still doesn't make it clear from
which POM the dependency is actually getting inherited.  Is there some
mechanism in Maven2 that just lists out the dependency tree, so you can
figure stuff like this out easily?


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message