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/16 23:21:22 UTC
[jira] Commented: (SUREFIRE-700) Surefire is not isolated from
itself
[ http://jira.codehaus.org/browse/SUREFIRE-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=256442#action_256442 ]
Kristian Rosenvold commented on SUREFIRE-700:
---------------------------------------------
The format of the properties files is also pretty constrained when it comes to that.
> Surefire is not isolated from itself
> ------------------------------------
>
> Key: SUREFIRE-700
> URL: http://jira.codehaus.org/browse/SUREFIRE-700
> Project: Maven Surefire
> Issue Type: Improvement
> Affects Versions: 2.4.1, 2.4.2, 2.4.3, 2.5, 2.6, 2.7, 2.7.1, 2.7.2
> Reporter: Kristian Rosenvold
> Assignee: Kristian Rosenvold
> Fix For: 2.7.3
>
>
> The current classloader structure in surefire does not isolate surefire from changes to surefire in itself. This means an interface change in *most* private interfaces and classes can break the build of surefire itself.
> This is due to the classloader structure systemclassloader<-testclassloader<-providerclassloader, where a modified surefire immediately becomes effective by being loaded in testclassloader.
> This issue will be fixed by making the following structure:
> systemclassloader<-testframeworkclassloader<-testclassloader
> systemclassloader<-testframeworkclassloader<-surefireclassloader
> Pardon the ascii graphics but it seems like jira does not allow me to draw systemclassloader<-testframeworkclassloader as one common root ;)
--
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