maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reinhard Nägele (JIRA) <>
Subject [jira] Created: (SUREFIRE-699) Remove TestNG from system classpath of forked process
Date Mon, 14 Feb 2011 13:13:22 GMT
Remove TestNG from system classpath of forked process

                 Key: SUREFIRE-699
             Project: Maven Surefire
          Issue Type: Bug
          Components: classloading, TestNG support
    Affects Versions: 2.7.2
            Reporter: Reinhard Nägele
            Priority: Critical

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:

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message