[
http://jira.codehaus.org/browse/SUREFIRE-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Rosenvold updated SUREFIRE-700:
----------------------------------------
Attachment: stage2.patch
Added "shade" based solution in r1075071.
Please note that this will not be effective until after we have released a
version with this patch in it,
at which time we can apply this subsequent patch, stage2.patch. Make sure the
version numbers (in shaderfire pom.xml) file are correct when applying this
patch. I just add this patch to in case I get run over by a truck
> 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
>
> Attachments: stage2.patch
>
>
> 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
