Reading the Sonatype tutorial at http://books.sonatype.com/mvnex-book/reference/simple-project-sect-simple-core.html I see this:
Maven also provides for different dependency scopes. The simple project’s pom.xml contains a single dependency—junit:junit:jar:3.8.1+—with a scope of +test. When a dependency has a scope of test, it will not be available to the compile goal of the Compiler plugin. It will be added to the classpath for only the compiler:testCompile and surefire:test goals. This implies that each plugin goal can have it's own classpath. Is this correct? Thanks & regards, Jarlath -- View this message in context: http://maven.40175.n5.nabble.com/Does-each-maven-goal-have-it-s-own-classpath-tp5767577.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
