The most reliable (and least readable) way is to run with the '-X' option and look at the classpath in the configuration of the compiler or surefire plugin.
Tom On Jan 27, 2008 5:30 PM, EJ Ciramella <[EMAIL PROTECTED]> wrote: > You can try "mvn site" which should give SOME of this, but other > reporting plugins give more accurate info, like: > > http://maven.apache.org/plugins/maven-dependency-plugin/index.html - > look at the "list" option > > or > > http://maven.apache.org/plugins/maven-project-info-reports-plugin/depend > ency-convergence-mojo.html > > -----Original Message----- > From: sebb [mailto:[EMAIL PROTECTED] > Sent: Sunday, January 27, 2008 11:01 AM > To: [email protected] > Subject: How to trace which repository files are used in a build? > > Is there a debug flag or other method which can be used to trace which > files are accessed from the repository during a Maven 2 build? > > One could empty the local repository before starting a build, and look > for the download messages, but hopefully there is an easier method... > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
