I'm sure some of you have noticed that the surefire-plugin does not respect
the concept that the 'java.class.path' sysvar is a shared variable.
Surefire moves the, well ..., the classpath that all of the resources the
tests need from the common java.class.path to their own
surefire.test.class.path .
I won't go into the philosophical debate as to why this is not a good idea,
but if you have complex code that sometimes needs to traverse file trees
that are in archives, you'll need to know this property to run maven.
String classpath = System.getProperty("surefire.test.class.path");
if(StringUtils.isBlank(classpath))
classpath = System.getProperty("java.class.path");
--
View this message in context:
http://www.nabble.com/java.class.path-and-the-surefire-plugin-tp15861133s177p15861133.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]
