Use the dependencies report. It gives you exactly which dependency
comes from where. I think it also generates which dependencies are
dupes.
mvn site should create such a report iirc. Maybe you also need to
specify the report, but I'm a bit rusty on that part.
Another goldmine is: mvn help:effective-pom
I also suggest using the dependencyManagement part to specify the
versions of each dependency, and just use the dependency bit to
specify groupId and artifactId.
Martijn
On 9/21/07, mchack [EMAIL PROTECTED] wrote:
I have a fairly large project working that users Spring/Hibernate with Wicket
Spring annotations but was built using eclipse ide with manual specified
dependencies. We want to move to Maven but I am having a hell of a time at
it. The generate war contains many duplicate jars (different versions) and
am not sure how to figure out where they are coming from.
I assume that I have to specify proper exclusions. Does anyone have hints,
advice, etc. that would point me in the right direction. I can see the
future benefits of Maven but need to get over the inital hump.
-Mike
--
View this message in context:
http://www.nabble.com/Maven-advice-appreciated-tf4497248.html#a12825376
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.0-beta3 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta3/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
