You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dan Fabulich (JIRA)" <ji...@codehaus.org> on 2007/12/09 07:23:57 UTC
[jira] Closed: (SUREFIRE-347) regression: plexus is not properly
isolated
[ http://jira.codehaus.org/browse/SUREFIRE-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Fabulich closed SUREFIRE-347.
---------------------------------
Resolution: Cannot Reproduce
Fix Version/s: (was: 2.3.1)
Using the plexus-conflict test checked into surefire trunk, I was unable to reproduce this issue with either Surefire 2.3 or the latest trunk. I was able to reproduce the related bug SUREFIRE-334 in trunk when useSystemClassLoader=true, but not in Surefire 2.3, where I found that useSystemClassLoader=true was just broken.
> regression: plexus is not properly isolated
> -------------------------------------------
>
> Key: SUREFIRE-347
> URL: http://jira.codehaus.org/browse/SUREFIRE-347
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.3
> Reporter: Brett Porter
>
> Currently, if you use 2.3.1-SNAPSHOT on doxia-site-renderer, you get a test error due to a class incompatibility in Plexus.
> The same issue occurs if you use forkMode=never under 2.3 or earlier.
> this could be related to, or caused by SUREFIRE-334. Fix that first and see if this is still an issue. However, note that it works under 2.3 with forkMode=once and useSystemClassLoader=true.
--
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