You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org> on 2011/02/15 08:25:22 UTC
[jira] Closed: (SUREFIRE-699) Remove TestNG from system classpath
of forked process
[ http://jira.codehaus.org/browse/SUREFIRE-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Rosenvold closed SUREFIRE-699.
---------------------------------------
Resolution: Fixed
Fix Version/s: 2.7.3
Assignee: Kristian Rosenvold
Fixed in r1070793. Thanks for the issue, thanks for the help!
> Remove TestNG from system classpath of forked process
> -----------------------------------------------------
>
> Key: SUREFIRE-699
> URL: http://jira.codehaus.org/browse/SUREFIRE-699
> Project: Maven Surefire
> Issue Type: Bug
> Components: classloading, TestNG support
> Affects Versions: 2.7.2
> Reporter: Reinhard Nägele
> Assignee: Kristian Rosenvold
> Priority: Critical
> Fix For: 2.7.3
>
>
> 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
--
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