[SUREFIRE-699] Remove TestNG from system classpath of forked process

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.7.2
• Fix Version/s: 2.8
• Component/s: classloading, TestNG support
• Assignee: Kristian Rosenvold
• Reporter: Reinhard Nägele
• Created: 14/Feb/11 07:13
• Updated: 03/Mar/11 15:16
• Resolved: 15/Feb/11 01:25

Description

TestNG is added to the system classloader of the forked test process. Since TestNG has a dependency to Guice 2, projects using Guice 3 run into trouble because Guice 2 wins.

The problem can be fixed by commenting out line 1025 in AbstractSurefireMojo:

public void addProviderArtifactToBootClasspath( Classpath bootclasspath )
throws ArtifactResolutionException, ArtifactNotFoundException
{
// dependencyResolver.addResolvedArtifactToClasspath( bootclasspath, testNgArtifact );
}

Related discussions:
http://maven.40175.n5.nabble.com/Problems-with-Surefire-TestNG-and-Guice-3-td3384082.html
http://groups.google.com/group/testng-users/browse_thread/thread/db58d13ca498bb92