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:46:22 UTC

[jira] Commented: (SUREFIRE-699) Remove TestNG from system classpath of forked process

    [ http://jira.codehaus.org/browse/SUREFIRE-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=256091#action_256091 ] 

Kristian Rosenvold commented on SUREFIRE-699:
---------------------------------------------

Btw, the change I removed was was introduced in  r541168 from the collab2 surefire branch. In software terms that is after the dinosaurs ruled the earth, but before the vikings pillaged Scotland.

> 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