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 16:35:22 UTC
[jira] Created: (SUREFIRE-700) Surefire is not isolated from itself
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.7.2, 2.7.1, 2.7, 2.6, 2.5, 2.4.3, 2.4.2, 2.4.1
Reporter: Kristian Rosenvold
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
^------surefireclassloader
--
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
[jira] Updated: (SUREFIRE-700) Surefire is not isolated from itself
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Rosenvold updated SUREFIRE-700:
----------------------------------------
Fix Version/s: (was: 2.8)
2.8.1
> Surefire is not isolated from itself
> ------------------------------------
>
> Key: SUREFIRE-700
> URL: http://jira.codehaus.org/browse/SUREFIRE-700
> Project: Maven Surefire
> Issue Type: Improvement
> Components: classloading
> 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.8.1
>
> 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
[jira] Closed: (SUREFIRE-700) Surefire is not isolated from itself
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Rosenvold closed SUREFIRE-700.
---------------------------------------
Resolution: Fixed
Fix Version/s: (was: 2.8.1)
2.8
I'm marking this issue as fixed for 2.8, since we can start using it immediately afterwards (on 2.8.1-SNAPSHOT).
> Surefire is not isolated from itself
> ------------------------------------
>
> Key: SUREFIRE-700
> URL: http://jira.codehaus.org/browse/SUREFIRE-700
> Project: Maven Surefire
> Issue Type: Improvement
> Components: classloading
> 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.8
>
> 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
[jira] Updated: (SUREFIRE-700) Surefire is not isolated from itself
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Rosenvold updated SUREFIRE-700:
----------------------------------------
Fix Version/s: (was: 2.7.3)
2.8
> 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.8
>
> 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
[jira] Issue Comment Edited: (SUREFIRE-700) Surefire is not
isolated from itself
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=257899#action_257899 ]
Kristian Rosenvold edited comment on SUREFIRE-700 at 2/27/11 9:39 AM:
----------------------------------------------------------------------
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 JIRA in case I get run over by a truck
"shadedVersion" in root pom should be the version of surefire you will be building with, and should be N-1.
was (Author: krosenvold):
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
[jira] Commented: (SUREFIRE-700) Surefire is not isolated from
itself
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=259517#action_259517 ]
Kristian Rosenvold commented on SUREFIRE-700:
---------------------------------------------
And, as can be seen from /src/site/apt/developingSurefire.apt this solution is shade based and not classloader based, giving 100% isolation.
> Surefire is not isolated from itself
> ------------------------------------
>
> Key: SUREFIRE-700
> URL: http://jira.codehaus.org/browse/SUREFIRE-700
> Project: Maven Surefire
> Issue Type: Improvement
> Components: classloading
> 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.8
>
> 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
[jira] Work started: (SUREFIRE-700) Surefire is not isolated from
itself
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on SUREFIRE-700 started by Kristian Rosenvold.
> 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
>
> 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
[jira] Closed: (SUREFIRE-700) Surefire is not isolated from itself
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Rosenvold closed SUREFIRE-700.
---------------------------------------
Resolution: Fixed
Fix Version/s: 2.7.3
Fixed in r1071421
Please note that the "api" modules and the "booter" module will have to stay backward compatible with the version of surefire that is running the tests. This is a significant improvement since most implementation classes also had to stay backward compatible before this change.
The core of the change is in ClasspathConfiguration, the rest is just cleaning up classpaths and stuff.
> 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
[jira] Reopened: (SUREFIRE-700) Surefire is not isolated from
itself
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Rosenvold reopened SUREFIRE-700:
-----------------------------------------
Reverted commit and reopened because it broke the build on windows
> 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
[jira] Updated: (SUREFIRE-700) Surefire is not isolated from itself
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Rosenvold updated SUREFIRE-700:
----------------------------------------
Component/s: classloading
> Surefire is not isolated from itself
> ------------------------------------
>
> Key: SUREFIRE-700
> URL: http://jira.codehaus.org/browse/SUREFIRE-700
> Project: Maven Surefire
> Issue Type: Improvement
> Components: classloading
> 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.8
>
> 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
[jira] Updated: (SUREFIRE-700) Surefire is not isolated from itself
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (SUREFIRE-700) Surefire is not isolated from
itself
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (SUREFIRE-700) Surefire is not isolated from itself
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Rosenvold updated SUREFIRE-700:
----------------------------------------
Description:
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 ;)
was:
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
^------surefireclassloader
> 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
>
> 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