It's controlled by a flag you can turn on and off. The reason it's off by default is because you may have something required to run the tests, but would show up as an unused dependency because it's not compiled in to the tests directly. An example could be hyper sql used to simulate a database. It's referenced via a jdbc connect string, but isn't compiled in, even in the tests.
(The unused dependencies are determined with bytecode analysis) -----Original Message----- From: Rémy Sanlaville [mailto:[EMAIL PROTECTED] Sent: Thursday, August 16, 2007 4:18 AM To: Maven Developers List Subject: Re: [maven-dependency-plugin] Analyze HTML Report Very nice. Brian, I wonder why the analyze goal of the maven-dependency-plugin just take the compile dependencies for the Unused declared dependencies [1] ? Why don't it take the test dependencies even though it also analyzes the test classes ? [1] http://maven.apache.org/plugins/maven-dependency-plugin/xref/org/apache/maven/plugin/dependency/AnalyzeMojo.html#201 Thanks, Rémy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
