With further analyzing I found that in case of the error (ClassNotFound) the corresponding JAR file is really missing in the compiler class path while the test classes are compiled. On some build runs, the junit jar was not in the compiler classpath, on some other build runs, the mockito jar file was not in the classpath. Sometimes both are missing. But sometimes a project which faild on a build, runs ok when I try it again and it fails later on a different project - but always with the same classpath problems. I found this problems only on compiling test-classes, never on non test classes.
In the meantime someone opened a bug at codehouse which seems to describe the same (or nearly the same) problem: http://jira.codehaus.org/browse/MNG-4996?focusedCommentId=253613#action_253613 Thanks for your help, Frank -- View this message in context: http://maven.40175.n5.nabble.com/surefire-classpath-problems-with-maven-3-parallel-tp3346469p3364711.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
