Am 06/12/16 um 21:47 schrieb Mirko Friedenhagen: > Hello Christian, > > that I could fix. Although hamcrest is transitive in junit.
It is a 'compile' scope dependency of 'junit' and that is transitive and will become 'test' in case of using 'junit' in 'test' scope. If you manage that dependency to 'test' scope it will no longer be a 'compile' scope dependency of 'junit' but a 'test' scope one. And that is not transitive and will not be available in the classpath. Concerning > https://github.com/1and1/testlink-junit/: > I now invoked the project as 'mvn340 -P '!foss-parent-verification' > clean verify' and get other stack traces. This might be because the > parent pom of the project manages logback as having scope test, that > means probably that the project class path is leaking into the plugin > class path. > When I try to manage the dependencies as scope runtime, the version > number is not picked up from the parent. I think you are running into <https://github.com/gleclaire/findbugs-maven-plugin/pull/35>. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
