Remove use of parent classloader in surefirebooter but keep TestNG support
working
----------------------------------------------------------------------------------
Key: SUREFIRE-54
URL: http://jira.codehaus.org/browse/SUREFIRE-54
Project: surefire
Issue Type: Bug
Affects Versions: 2.1
Reporter: fabrizio giustina
Priority: Critical
The removal of the parent system classloader while running tests in surefire
booter totally broke testNG support.
I am going to revert the commit:
http://svn.apache.org/viewvc/maven/surefire/trunk/surefire-booter/src/main/java/org/apache/maven/surefire/booter/SurefireBooter.java?r1=427040&r2=438999&diff_format=h
... in order to keep testng working for now, but we should find a way to solve
both problems soon.
The removal of the parent classloader is needed, according to Kenney for the
following reason:
If this is not done, the System classloader is added, in this case an
AppClassloader containing everything in the root classpath. For instance, in
maven, everything in core/ is available.This can cause clashes with the
plexus-utils used in maven itself.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
