Just discovered the reporting thanks. I will also try the effective pom report. Sounds cool.
-Mike Martijn Dashorst wrote: > > 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 > >> > > > -- > 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] > > > -- View this message in context: http://www.nabble.com/Maven-advice-appreciated-tf4497248.html#a12827577 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
