I have observed this also, and as you, I also was thinking about a potential test-runtime scope :)
At my project I have included the dependency analyze in our CI build like this: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-dependency-plugin</artifactId> <version>2.0</version> <executions> <execution> <id>analyze</id> <phase>verify</phase> <goals> <goal>analyze-only</goal> </goals> <configuration> <failOnWarning>true</failOnWarning> <ignoreNonCompile>true</ignoreNonCompile> </configuration> </execution> </executions> </plugin> The build will fail on dependency problem warnings, but ignore warnings on non-compile scope warnings (e.g. test scope). So it will emit some warnings on unused test-scope dependencies which are required for runtime of the tests, not compile-time, though the build does not fail because of those. - Rune > From: Barrie Treloar [EMAIL PROTECTED] > Sent: 2008-11-10 02:01:39 CET > To: Maven Users List [EMAIL PROTECTED] > Subject: Need for a test-runtime scope? > > I'm just going through my projects with dependency:analyze and noticed > that there is no equivalent of a runtime scope for test. > And therefore I am getting warning for Unused declared dependencies. > > [WARNING] Unused declared dependencies found: > [WARNING] commons-dbcp:commons-dbcp:jar:1.2.2:test > > I don't see much need for a test-runtime, except that this would > remove these warnings. > Alternatively dependency:analyze should avoid providing a warning for > unused dependencies if the scope is test. > > Thoughts? > > --------------------------------------------------------------------- > 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]
