You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Steven Coco (JIRA)" <ji...@codehaus.org> on 2006/04/28 16:33:19 UTC
[jira] Created: (MJAR-38) Maven Puts Arbitrary Extension Definition
in JAR Manifest by Default.
Maven Puts Arbitrary Extension Definition in JAR Manifest by Default.
---------------------------------------------------------------------
Key: MJAR-38
URL: http://jira.codehaus.org/browse/MJAR-38
Project: Maven 2.x Jar Plugin
Type: Bug
Versions: 2.0
Environment: Maven version: 2.0.4
Microsoft Windows XP [Version 5.1.2600]
Reporter: Steven Coco
Attachments: Jar Extension-Name Tester.zip
I'm using the latest Maven release. When I build my project, the resulting Jar file's manifest contains an Extension-Name attribute along with Specification and Implementation attributes. The POM contains no mention that this project is a Java optional package -- an "extension" (or an extension of any other kind).
I don't know why Maven is doing that.
If Maven is doing this by default for some reason, it absolutely shouldn't. Maven should not identify my Jar as an optional package unless I explicitly say so. Jars are only extensions if explicitly created as such.
The name it uses for the extension name is the POM's <artifactId>. That's not even a UID!
--
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: (MJAR-38) Maven Puts Arbitrary Extension Definition
in JAR Manifest by Default.
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAR-38?page=all ]
Brett Porter closed MJAR-38:
----------------------------
Resolution: Fixed
> Maven Puts Arbitrary Extension Definition in JAR Manifest by Default.
> ---------------------------------------------------------------------
>
> Key: MJAR-38
> URL: http://jira.codehaus.org/browse/MJAR-38
> Project: Maven 2.x Jar Plugin
> Type: Bug
> Versions: 2.0
> Environment: Maven version: 2.0.4
> Microsoft Windows XP [Version 5.1.2600]
> Reporter: Steven Coco
> Assignee: Brett Porter
> Fix For: 2.1
> Attachments: Jar Extension-Name Tester.zip, MJAR-38.patch, MJAR-38.patch
>
>
> I'm using the latest Maven release. When I build my project, the resulting Jar file's manifest contains an Extension-Name attribute along with Specification and Implementation attributes. The POM contains no mention that this project is a Java optional package -- an "extension" (or an extension of any other kind).
> I don't know why Maven is doing that.
> If Maven is doing this by default for some reason, it absolutely shouldn't. Maven should not identify my Jar as an optional package unless I explicitly say so. Jars are only extensions if explicitly created as such.
> The name it uses for the extension name is the POM's <artifactId>. That's not even a UID!
--
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: (MJAR-38) Maven Puts Arbitrary Extension Definition
in JAR Manifest by Default.
Posted by "Mike Perham (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAR-38?page=all ]
Mike Perham updated MJAR-38:
----------------------------
Attachment: (was: MavenArchiver.patch.2)
> Maven Puts Arbitrary Extension Definition in JAR Manifest by Default.
> ---------------------------------------------------------------------
>
> Key: MJAR-38
> URL: http://jira.codehaus.org/browse/MJAR-38
> Project: Maven 2.x Jar Plugin
> Type: Bug
> Versions: 2.0
> Environment: Maven version: 2.0.4
> Microsoft Windows XP [Version 5.1.2600]
> Reporter: Steven Coco
> Assignee: Mike Perham
> Attachments: Jar Extension-Name Tester.zip
>
>
> I'm using the latest Maven release. When I build my project, the resulting Jar file's manifest contains an Extension-Name attribute along with Specification and Implementation attributes. The POM contains no mention that this project is a Java optional package -- an "extension" (or an extension of any other kind).
> I don't know why Maven is doing that.
> If Maven is doing this by default for some reason, it absolutely shouldn't. Maven should not identify my Jar as an optional package unless I explicitly say so. Jars are only extensions if explicitly created as such.
> The name it uses for the extension name is the POM's <artifactId>. That's not even a UID!
--
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: (MJAR-38) Maven Puts Arbitrary Extension
Definition in JAR Manifest by Default.
Posted by "Steven Coco (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAR-38?page=comments#action_64393 ]
Steven Coco commented on MJAR-38:
---------------------------------
I should have marked this as a Blocker since there is no way to prevent Maven from merging these attributes into the final Manifest.
I downloaded SVN in an attempt to make a patch for these issues, but I had problems with the server and cannot afford the needed time to make a fix.
> Maven Puts Arbitrary Extension Definition in JAR Manifest by Default.
> ---------------------------------------------------------------------
>
> Key: MJAR-38
> URL: http://jira.codehaus.org/browse/MJAR-38
> Project: Maven 2.x Jar Plugin
> Type: Bug
> Versions: 2.0
> Environment: Maven version: 2.0.4
> Microsoft Windows XP [Version 5.1.2600]
> Reporter: Steven Coco
> Attachments: Jar Extension-Name Tester.zip
>
>
> I'm using the latest Maven release. When I build my project, the resulting Jar file's manifest contains an Extension-Name attribute along with Specification and Implementation attributes. The POM contains no mention that this project is a Java optional package -- an "extension" (or an extension of any other kind).
> I don't know why Maven is doing that.
> If Maven is doing this by default for some reason, it absolutely shouldn't. Maven should not identify my Jar as an optional package unless I explicitly say so. Jars are only extensions if explicitly created as such.
> The name it uses for the extension name is the POM's <artifactId>. That's not even a UID!
--
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: (MJAR-38) Maven Puts Arbitrary Extension
Definition in JAR Manifest by Default.
Posted by "Steven Coco (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAR-38?page=comments#action_66647 ]
Steven Coco commented on MJAR-38:
---------------------------------
Including empty tags to squelch the attributes should work out well!
Great work.
Thanks again.
PS:
I'm going to file an RFE in the Sun database to have the Jar, Extension mechanism, and Versioning specifications cleared up and synchronized.
> Maven Puts Arbitrary Extension Definition in JAR Manifest by Default.
> ---------------------------------------------------------------------
>
> Key: MJAR-38
> URL: http://jira.codehaus.org/browse/MJAR-38
> Project: Maven 2.x Jar Plugin
> Type: Bug
> Versions: 2.0
> Environment: Maven version: 2.0.4
> Microsoft Windows XP [Version 5.1.2600]
> Reporter: Steven Coco
> Assignee: Mike Perham
> Attachments: Jar Extension-Name Tester.zip, MJAR-38.patch, MavenArchiver.patch.1, MavenArchiver.patch.1, MavenArchiver.patch.2, MavenArchiver.patch.3
>
>
> I'm using the latest Maven release. When I build my project, the resulting Jar file's manifest contains an Extension-Name attribute along with Specification and Implementation attributes. The POM contains no mention that this project is a Java optional package -- an "extension" (or an extension of any other kind).
> I don't know why Maven is doing that.
> If Maven is doing this by default for some reason, it absolutely shouldn't. Maven should not identify my Jar as an optional package unless I explicitly say so. Jars are only extensions if explicitly created as such.
> The name it uses for the extension name is the POM's <artifactId>. That's not even a UID!
--
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: (MJAR-38) Maven Puts Arbitrary Extension
Definition in JAR Manifest by Default.
Posted by "Jochen Wiedmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAR-38?page=comments#action_67569 ]
Jochen Wiedmann commented on MJAR-38:
-------------------------------------
Brett, I have read your quote and my impression is, that the problem report is in essence a duplicate of MJAR-39.
As for your comment on releasing the maven-archiver: I'd recommend that this be done after Mike's patch to this issue is committed, which I cannot do. Perhaps Mike can do this now?
> Maven Puts Arbitrary Extension Definition in JAR Manifest by Default.
> ---------------------------------------------------------------------
>
> Key: MJAR-38
> URL: http://jira.codehaus.org/browse/MJAR-38
> Project: Maven 2.x Jar Plugin
> Type: Bug
> Versions: 2.0
> Environment: Maven version: 2.0.4
> Microsoft Windows XP [Version 5.1.2600]
> Reporter: Steven Coco
> Attachments: Jar Extension-Name Tester.zip, MJAR-38.patch, MJAR-38.patch
>
>
> I'm using the latest Maven release. When I build my project, the resulting Jar file's manifest contains an Extension-Name attribute along with Specification and Implementation attributes. The POM contains no mention that this project is a Java optional package -- an "extension" (or an extension of any other kind).
> I don't know why Maven is doing that.
> If Maven is doing this by default for some reason, it absolutely shouldn't. Maven should not identify my Jar as an optional package unless I explicitly say so. Jars are only extensions if explicitly created as such.
> The name it uses for the extension name is the POM's <artifactId>. That's not even a UID!
--
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: (MJAR-38) Maven Puts Arbitrary Extension
Definition in JAR Manifest by Default.
Posted by "Steven Coco (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAR-38?page=comments#action_64391 ]
Steven Coco commented on MJAR-38:
---------------------------------
This issue is related to MJAR-39 and MWAR-34 in that since it sets the Specification-Title element by default to the POM's <description> element, it easily can create an invalid Manifest.
> Maven Puts Arbitrary Extension Definition in JAR Manifest by Default.
> ---------------------------------------------------------------------
>
> Key: MJAR-38
> URL: http://jira.codehaus.org/browse/MJAR-38
> Project: Maven 2.x Jar Plugin
> Type: Bug
> Versions: 2.0
> Environment: Maven version: 2.0.4
> Microsoft Windows XP [Version 5.1.2600]
> Reporter: Steven Coco
> Attachments: Jar Extension-Name Tester.zip
>
>
> I'm using the latest Maven release. When I build my project, the resulting Jar file's manifest contains an Extension-Name attribute along with Specification and Implementation attributes. The POM contains no mention that this project is a Java optional package -- an "extension" (or an extension of any other kind).
> I don't know why Maven is doing that.
> If Maven is doing this by default for some reason, it absolutely shouldn't. Maven should not identify my Jar as an optional package unless I explicitly say so. Jars are only extensions if explicitly created as such.
> The name it uses for the extension name is the POM's <artifactId>. That's not even a UID!
--
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: (MJAR-38) Maven Puts Arbitrary Extension Definition
in JAR Manifest by Default.
Posted by "Mike Perham (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAR-38?page=all ]
Mike Perham updated MJAR-38:
----------------------------
Attachment: (was: MavenArchiver.patch.1)
> Maven Puts Arbitrary Extension Definition in JAR Manifest by Default.
> ---------------------------------------------------------------------
>
> Key: MJAR-38
> URL: http://jira.codehaus.org/browse/MJAR-38
> Project: Maven 2.x Jar Plugin
> Type: Bug
> Versions: 2.0
> Environment: Maven version: 2.0.4
> Microsoft Windows XP [Version 5.1.2600]
> Reporter: Steven Coco
> Assignee: Mike Perham
> Attachments: Jar Extension-Name Tester.zip
>
>
> I'm using the latest Maven release. When I build my project, the resulting Jar file's manifest contains an Extension-Name attribute along with Specification and Implementation attributes. The POM contains no mention that this project is a Java optional package -- an "extension" (or an extension of any other kind).
> I don't know why Maven is doing that.
> If Maven is doing this by default for some reason, it absolutely shouldn't. Maven should not identify my Jar as an optional package unless I explicitly say so. Jars are only extensions if explicitly created as such.
> The name it uses for the extension name is the POM's <artifactId>. That's not even a UID!
--
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: (MJAR-38) Maven Puts Arbitrary Extension
Definition in JAR Manifest by Default.
Posted by "Steven Coco (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAR-38?page=comments#action_67417 ]
Steven Coco commented on MJAR-38:
---------------------------------
Hello again...
Well, all these comments are going on ( ! ) and I noticed my previous comment here, and I really am more thinking that these should just be turned off by default: if there's any "switch", they should be off by default and something should turn them on.
The reason I feel that way is that the POM is the project's descriptor: it is not the specification's descriptor. -- Maven uses the <description> element as the Specification Title; but this really makes no sense -- What is the plan if the POM element values change???
The description element in particular should really contain something more like "reference implementation xyz...": not something considered a title.
Maven really seems to be attempting to find some solution to how to make every Jar in the world a standard optional package; but it just shouldn't. (That's why ClassLoader is not final!!!) These manifest attributes should be rigidly defined and specified by the Jar author and no "defaults" should exist .
So I have to clarify my opinion and I feel Maven should just not to be doing any of this to begin with. It's highly un-standard; and these attributes in particular have a clearly defined usage.
Anyway, thanks for "your patience" -- appRECIATED...
Steven Coco.
> Maven Puts Arbitrary Extension Definition in JAR Manifest by Default.
> ---------------------------------------------------------------------
>
> Key: MJAR-38
> URL: http://jira.codehaus.org/browse/MJAR-38
> Project: Maven 2.x Jar Plugin
> Type: Bug
> Versions: 2.0
> Environment: Maven version: 2.0.4
> Microsoft Windows XP [Version 5.1.2600]
> Reporter: Steven Coco
> Attachments: Jar Extension-Name Tester.zip, MJAR-38.patch
>
>
> I'm using the latest Maven release. When I build my project, the resulting Jar file's manifest contains an Extension-Name attribute along with Specification and Implementation attributes. The POM contains no mention that this project is a Java optional package -- an "extension" (or an extension of any other kind).
> I don't know why Maven is doing that.
> If Maven is doing this by default for some reason, it absolutely shouldn't. Maven should not identify my Jar as an optional package unless I explicitly say so. Jars are only extensions if explicitly created as such.
> The name it uses for the extension name is the POM's <artifactId>. That's not even a UID!
--
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: (MJAR-38) Maven Puts Arbitrary Extension Definition
in JAR Manifest by Default.
Posted by "Jochen Wiedmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAR-38?page=all ]
Jochen Wiedmann updated MJAR-38:
--------------------------------
Attachment: MJAR-38.patch
> Maven Puts Arbitrary Extension Definition in JAR Manifest by Default.
> ---------------------------------------------------------------------
>
> Key: MJAR-38
> URL: http://jira.codehaus.org/browse/MJAR-38
> Project: Maven 2.x Jar Plugin
> Type: Bug
> Versions: 2.0
> Environment: Maven version: 2.0.4
> Microsoft Windows XP [Version 5.1.2600]
> Reporter: Steven Coco
> Assignee: Mike Perham
> Attachments: Jar Extension-Name Tester.zip, MJAR-38.patch, MavenArchiver.patch.1, MavenArchiver.patch.1, MavenArchiver.patch.2, MavenArchiver.patch.3
>
>
> I'm using the latest Maven release. When I build my project, the resulting Jar file's manifest contains an Extension-Name attribute along with Specification and Implementation attributes. The POM contains no mention that this project is a Java optional package -- an "extension" (or an extension of any other kind).
> I don't know why Maven is doing that.
> If Maven is doing this by default for some reason, it absolutely shouldn't. Maven should not identify my Jar as an optional package unless I explicitly say so. Jars are only extensions if explicitly created as such.
> The name it uses for the extension name is the POM's <artifactId>. That's not even a UID!
--
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: (MJAR-38) Maven Puts Arbitrary Extension Definition
in JAR Manifest by Default.
Posted by "Mike Perham (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAR-38?page=all ]
Mike Perham closed MJAR-38:
---------------------------
Resolution: Fixed
Fix Version: 2.1
Whew. Patch applied to shared/maven-archiver.
> Maven Puts Arbitrary Extension Definition in JAR Manifest by Default.
> ---------------------------------------------------------------------
>
> Key: MJAR-38
> URL: http://jira.codehaus.org/browse/MJAR-38
> Project: Maven 2.x Jar Plugin
> Type: Bug
> Versions: 2.0
> Environment: Maven version: 2.0.4
> Microsoft Windows XP [Version 5.1.2600]
> Reporter: Steven Coco
> Fix For: 2.1
> Attachments: Jar Extension-Name Tester.zip, MJAR-38.patch, MJAR-38.patch
>
>
> I'm using the latest Maven release. When I build my project, the resulting Jar file's manifest contains an Extension-Name attribute along with Specification and Implementation attributes. The POM contains no mention that this project is a Java optional package -- an "extension" (or an extension of any other kind).
> I don't know why Maven is doing that.
> If Maven is doing this by default for some reason, it absolutely shouldn't. Maven should not identify my Jar as an optional package unless I explicitly say so. Jars are only extensions if explicitly created as such.
> The name it uses for the extension name is the POM's <artifactId>. That's not even a UID!
--
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: (MJAR-38) Maven Puts Arbitrary Extension
Definition in JAR Manifest by Default.
Posted by "Mike Perham (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAR-38?page=comments#action_67287 ]
Mike Perham commented on MJAR-38:
---------------------------------
I'm giving up on this because it is simply too difficult to get changes to maven-archiver approved at this point because it is part of maven core and 2.0.x is locked down pretty tight at this point. maven-archiver is moving out of maven core for 2.1 so hopefully it will become a little easier to change and we can get the patch in the 2.1 release.
> Maven Puts Arbitrary Extension Definition in JAR Manifest by Default.
> ---------------------------------------------------------------------
>
> Key: MJAR-38
> URL: http://jira.codehaus.org/browse/MJAR-38
> Project: Maven 2.x Jar Plugin
> Type: Bug
> Versions: 2.0
> Environment: Maven version: 2.0.4
> Microsoft Windows XP [Version 5.1.2600]
> Reporter: Steven Coco
> Attachments: Jar Extension-Name Tester.zip, MJAR-38.patch
>
>
> I'm using the latest Maven release. When I build my project, the resulting Jar file's manifest contains an Extension-Name attribute along with Specification and Implementation attributes. The POM contains no mention that this project is a Java optional package -- an "extension" (or an extension of any other kind).
> I don't know why Maven is doing that.
> If Maven is doing this by default for some reason, it absolutely shouldn't. Maven should not identify my Jar as an optional package unless I explicitly say so. Jars are only extensions if explicitly created as such.
> The name it uses for the extension name is the POM's <artifactId>. That's not even a UID!
--
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: (MJAR-38) Maven Puts Arbitrary Extension Definition
in JAR Manifest by Default.
Posted by "Mike Perham (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAR-38?page=all ]
Mike Perham updated MJAR-38:
----------------------------
Attachment: (was: MavenArchiver.patch.1)
> Maven Puts Arbitrary Extension Definition in JAR Manifest by Default.
> ---------------------------------------------------------------------
>
> Key: MJAR-38
> URL: http://jira.codehaus.org/browse/MJAR-38
> Project: Maven 2.x Jar Plugin
> Type: Bug
> Versions: 2.0
> Environment: Maven version: 2.0.4
> Microsoft Windows XP [Version 5.1.2600]
> Reporter: Steven Coco
> Assignee: Mike Perham
> Attachments: Jar Extension-Name Tester.zip
>
>
> I'm using the latest Maven release. When I build my project, the resulting Jar file's manifest contains an Extension-Name attribute along with Specification and Implementation attributes. The POM contains no mention that this project is a Java optional package -- an "extension" (or an extension of any other kind).
> I don't know why Maven is doing that.
> If Maven is doing this by default for some reason, it absolutely shouldn't. Maven should not identify my Jar as an optional package unless I explicitly say so. Jars are only extensions if explicitly created as such.
> The name it uses for the extension name is the POM's <artifactId>. That's not even a UID!
--
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: (MJAR-38) Maven Puts Arbitrary Extension
Definition in JAR Manifest by Default.
Posted by "Mike Perham (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAR-38?page=comments#action_66581 ]
Mike Perham commented on MJAR-38:
---------------------------------
If the three patches are all for one file, please just supply one patch. There's no real reason to break it up into three pieces. Makes it easier for you and me.
> Maven Puts Arbitrary Extension Definition in JAR Manifest by Default.
> ---------------------------------------------------------------------
>
> Key: MJAR-38
> URL: http://jira.codehaus.org/browse/MJAR-38
> Project: Maven 2.x Jar Plugin
> Type: Bug
> Versions: 2.0
> Environment: Maven version: 2.0.4
> Microsoft Windows XP [Version 5.1.2600]
> Reporter: Steven Coco
> Assignee: Mike Perham
> Attachments: Jar Extension-Name Tester.zip, MavenArchiver.patch.1, MavenArchiver.patch.1, MavenArchiver.patch.2, MavenArchiver.patch.3
>
>
> I'm using the latest Maven release. When I build my project, the resulting Jar file's manifest contains an Extension-Name attribute along with Specification and Implementation attributes. The POM contains no mention that this project is a Java optional package -- an "extension" (or an extension of any other kind).
> I don't know why Maven is doing that.
> If Maven is doing this by default for some reason, it absolutely shouldn't. Maven should not identify my Jar as an optional package unless I explicitly say so. Jars are only extensions if explicitly created as such.
> The name it uses for the extension name is the POM's <artifactId>. That's not even a UID!
--
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: (MJAR-38) Maven Puts Arbitrary Extension Definition
in JAR Manifest by Default.
Posted by "Jochen Wiedmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAR-38?page=all ]
Jochen Wiedmann updated MJAR-38:
--------------------------------
Attachment: MJAR-38.patch
> Maven Puts Arbitrary Extension Definition in JAR Manifest by Default.
> ---------------------------------------------------------------------
>
> Key: MJAR-38
> URL: http://jira.codehaus.org/browse/MJAR-38
> Project: Maven 2.x Jar Plugin
> Type: Bug
> Versions: 2.0
> Environment: Maven version: 2.0.4
> Microsoft Windows XP [Version 5.1.2600]
> Reporter: Steven Coco
> Attachments: Jar Extension-Name Tester.zip, MJAR-38.patch, MJAR-38.patch
>
>
> I'm using the latest Maven release. When I build my project, the resulting Jar file's manifest contains an Extension-Name attribute along with Specification and Implementation attributes. The POM contains no mention that this project is a Java optional package -- an "extension" (or an extension of any other kind).
> I don't know why Maven is doing that.
> If Maven is doing this by default for some reason, it absolutely shouldn't. Maven should not identify my Jar as an optional package unless I explicitly say so. Jars are only extensions if explicitly created as such.
> The name it uses for the extension name is the POM's <artifactId>. That's not even a UID!
--
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: (MJAR-38) Maven Puts Arbitrary Extension
Definition in JAR Manifest by Default.
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAR-38?page=comments#action_67562 ]
Brett Porter commented on MJAR-38:
----------------------------------
I noticed some additional comments to review with regards to the manifest:
http://mail-archives.apache.org/mod_mbox/maven-users/200511.mbox/%3C82533828A9FA7E4292F08A1D132304813FA8A5@itomae2km04.AD.QINTRA.COM%3E
BTW, the archiver is now separate and can be released whenever it is required for the JAR plugin.
> Maven Puts Arbitrary Extension Definition in JAR Manifest by Default.
> ---------------------------------------------------------------------
>
> Key: MJAR-38
> URL: http://jira.codehaus.org/browse/MJAR-38
> Project: Maven 2.x Jar Plugin
> Type: Bug
> Versions: 2.0
> Environment: Maven version: 2.0.4
> Microsoft Windows XP [Version 5.1.2600]
> Reporter: Steven Coco
> Attachments: Jar Extension-Name Tester.zip, MJAR-38.patch, MJAR-38.patch
>
>
> I'm using the latest Maven release. When I build my project, the resulting Jar file's manifest contains an Extension-Name attribute along with Specification and Implementation attributes. The POM contains no mention that this project is a Java optional package -- an "extension" (or an extension of any other kind).
> I don't know why Maven is doing that.
> If Maven is doing this by default for some reason, it absolutely shouldn't. Maven should not identify my Jar as an optional package unless I explicitly say so. Jars are only extensions if explicitly created as such.
> The name it uses for the extension name is the POM's <artifactId>. That's not even a UID!
--
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: (MJAR-38) Maven Puts Arbitrary Extension
Definition in JAR Manifest by Default.
Posted by "Mike Perham (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAR-38?page=comments#action_66531 ]
Mike Perham commented on MJAR-38:
---------------------------------
Jochen, please supply patches which are diff'd off the svn source. Your patches are based off of files with weird names (/tmp/MavenArchiver.java.1???) and can't be applied to SVN.
Couple other comments:
1) There's a one or two places where your code doesn't match the Maven style. Please correct if possible.
2) Collections.EMPTY_MAP is immutable AFAIK. It's not clear to me if this Map will be mutated. Please replace it with new HashMap() if the contents are mutable.
3) in your third patch, you do "if containsKey remove". It'd rather see "if containsKey return" as it minimizes redundant work.
> Maven Puts Arbitrary Extension Definition in JAR Manifest by Default.
> ---------------------------------------------------------------------
>
> Key: MJAR-38
> URL: http://jira.codehaus.org/browse/MJAR-38
> Project: Maven 2.x Jar Plugin
> Type: Bug
> Versions: 2.0
> Environment: Maven version: 2.0.4
> Microsoft Windows XP [Version 5.1.2600]
> Reporter: Steven Coco
> Attachments: Jar Extension-Name Tester.zip, MavenArchiver.patch.1, MavenArchiver.patch.2, MavenArchiver.patch.3
>
>
> I'm using the latest Maven release. When I build my project, the resulting Jar file's manifest contains an Extension-Name attribute along with Specification and Implementation attributes. The POM contains no mention that this project is a Java optional package -- an "extension" (or an extension of any other kind).
> I don't know why Maven is doing that.
> If Maven is doing this by default for some reason, it absolutely shouldn't. Maven should not identify my Jar as an optional package unless I explicitly say so. Jars are only extensions if explicitly created as such.
> The name it uses for the extension name is the POM's <artifactId>. That's not even a UID!
--
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: (MJAR-38) Maven Puts Arbitrary Extension
Definition in JAR Manifest by Default.
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAR-38?page=comments#action_67801 ]
Brett Porter commented on MJAR-38:
----------------------------------
ok, the patch didn't actually remove anything, it just made it possible to override
> Maven Puts Arbitrary Extension Definition in JAR Manifest by Default.
> ---------------------------------------------------------------------
>
> Key: MJAR-38
> URL: http://jira.codehaus.org/browse/MJAR-38
> Project: Maven 2.x Jar Plugin
> Type: Bug
> Versions: 2.0
> Environment: Maven version: 2.0.4
> Microsoft Windows XP [Version 5.1.2600]
> Reporter: Steven Coco
> Assignee: Brett Porter
> Fix For: 2.1
> Attachments: Jar Extension-Name Tester.zip, MJAR-38.patch, MJAR-38.patch
>
>
> I'm using the latest Maven release. When I build my project, the resulting Jar file's manifest contains an Extension-Name attribute along with Specification and Implementation attributes. The POM contains no mention that this project is a Java optional package -- an "extension" (or an extension of any other kind).
> I don't know why Maven is doing that.
> If Maven is doing this by default for some reason, it absolutely shouldn't. Maven should not identify my Jar as an optional package unless I explicitly say so. Jars are only extensions if explicitly created as such.
> The name it uses for the extension name is the POM's <artifactId>. That's not even a UID!
--
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: (MJAR-38) Maven Puts Arbitrary Extension
Definition in JAR Manifest by Default.
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAR-38?page=all ]
Brett Porter reopened MJAR-38:
------------------------------
Assign To: Brett Porter
though this is applied, when I set the jar plugin to use the archiver it still generates the elements
> Maven Puts Arbitrary Extension Definition in JAR Manifest by Default.
> ---------------------------------------------------------------------
>
> Key: MJAR-38
> URL: http://jira.codehaus.org/browse/MJAR-38
> Project: Maven 2.x Jar Plugin
> Type: Bug
> Versions: 2.0
> Environment: Maven version: 2.0.4
> Microsoft Windows XP [Version 5.1.2600]
> Reporter: Steven Coco
> Assignee: Brett Porter
> Fix For: 2.1
> Attachments: Jar Extension-Name Tester.zip, MJAR-38.patch, MJAR-38.patch
>
>
> I'm using the latest Maven release. When I build my project, the resulting Jar file's manifest contains an Extension-Name attribute along with Specification and Implementation attributes. The POM contains no mention that this project is a Java optional package -- an "extension" (or an extension of any other kind).
> I don't know why Maven is doing that.
> If Maven is doing this by default for some reason, it absolutely shouldn't. Maven should not identify my Jar as an optional package unless I explicitly say so. Jars are only extensions if explicitly created as such.
> The name it uses for the extension name is the POM's <artifactId>. That's not even a UID!
--
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: (MJAR-38) Maven Puts Arbitrary Extension Definition
in JAR Manifest by Default.
Posted by "Jochen Wiedmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAR-38?page=all ]
Jochen Wiedmann updated MJAR-38:
--------------------------------
Attachment: MavenArchiver.patch.1
> Maven Puts Arbitrary Extension Definition in JAR Manifest by Default.
> ---------------------------------------------------------------------
>
> Key: MJAR-38
> URL: http://jira.codehaus.org/browse/MJAR-38
> Project: Maven 2.x Jar Plugin
> Type: Bug
> Versions: 2.0
> Environment: Maven version: 2.0.4
> Microsoft Windows XP [Version 5.1.2600]
> Reporter: Steven Coco
> Assignee: Mike Perham
> Attachments: Jar Extension-Name Tester.zip, MavenArchiver.patch.1, MavenArchiver.patch.1, MavenArchiver.patch.2, MavenArchiver.patch.3
>
>
> I'm using the latest Maven release. When I build my project, the resulting Jar file's manifest contains an Extension-Name attribute along with Specification and Implementation attributes. The POM contains no mention that this project is a Java optional package -- an "extension" (or an extension of any other kind).
> I don't know why Maven is doing that.
> If Maven is doing this by default for some reason, it absolutely shouldn't. Maven should not identify my Jar as an optional package unless I explicitly say so. Jars are only extensions if explicitly created as such.
> The name it uses for the extension name is the POM's <artifactId>. That's not even a UID!
--
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: (MJAR-38) Maven Puts Arbitrary Extension Definition
in JAR Manifest by Default.
Posted by "Jochen Wiedmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAR-38?page=all ]
Jochen Wiedmann updated MJAR-38:
--------------------------------
Attachment: MavenArchiver.patch.3
MavenArchiver.patch.2
MavenArchiver.patch.1
> Maven Puts Arbitrary Extension Definition in JAR Manifest by Default.
> ---------------------------------------------------------------------
>
> Key: MJAR-38
> URL: http://jira.codehaus.org/browse/MJAR-38
> Project: Maven 2.x Jar Plugin
> Type: Bug
> Versions: 2.0
> Environment: Maven version: 2.0.4
> Microsoft Windows XP [Version 5.1.2600]
> Reporter: Steven Coco
> Attachments: Jar Extension-Name Tester.zip, MavenArchiver.patch.1, MavenArchiver.patch.2, MavenArchiver.patch.3
>
>
> I'm using the latest Maven release. When I build my project, the resulting Jar file's manifest contains an Extension-Name attribute along with Specification and Implementation attributes. The POM contains no mention that this project is a Java optional package -- an "extension" (or an extension of any other kind).
> I don't know why Maven is doing that.
> If Maven is doing this by default for some reason, it absolutely shouldn't. Maven should not identify my Jar as an optional package unless I explicitly say so. Jars are only extensions if explicitly created as such.
> The name it uses for the extension name is the POM's <artifactId>. That's not even a UID!
--
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: (MJAR-38) Maven Puts Arbitrary Extension
Definition in JAR Manifest by Default.
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAR-38?page=comments#action_66580 ]
Stephane Nicoll commented on MJAR-38:
-------------------------------------
Mike,
Could you please make sure the fix is backported to other plugins generating a MANIFEST entry (Jar, War, Ejb, Ear I guess).
Thanks!
> Maven Puts Arbitrary Extension Definition in JAR Manifest by Default.
> ---------------------------------------------------------------------
>
> Key: MJAR-38
> URL: http://jira.codehaus.org/browse/MJAR-38
> Project: Maven 2.x Jar Plugin
> Type: Bug
> Versions: 2.0
> Environment: Maven version: 2.0.4
> Microsoft Windows XP [Version 5.1.2600]
> Reporter: Steven Coco
> Assignee: Mike Perham
> Attachments: Jar Extension-Name Tester.zip, MavenArchiver.patch.1, MavenArchiver.patch.1, MavenArchiver.patch.2, MavenArchiver.patch.3
>
>
> I'm using the latest Maven release. When I build my project, the resulting Jar file's manifest contains an Extension-Name attribute along with Specification and Implementation attributes. The POM contains no mention that this project is a Java optional package -- an "extension" (or an extension of any other kind).
> I don't know why Maven is doing that.
> If Maven is doing this by default for some reason, it absolutely shouldn't. Maven should not identify my Jar as an optional package unless I explicitly say so. Jars are only extensions if explicitly created as such.
> The name it uses for the extension name is the POM's <artifactId>. That's not even a UID!
--
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: (MJAR-38) Maven Puts Arbitrary Extension
Definition in JAR Manifest by Default.
Posted by "Steven Coco (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAR-38?page=comments#action_66596 ]
Steven Coco commented on MJAR-38:
---------------------------------
Hi folks. Thanks for looking into all this.
I really would like to stress that thes attributes should not be forced into the manifest. They must be defeatable. One can see it make sense liberally re-using these attributes in an enterprise environment. But in any kind of project that does not have and follow an externally-defined specification, these do not make any sense. For instance, in a standalone application, these attributes are their own kind of ludacris.
A new user will also be confounded to find a specification for providing appropriate values for these does not exist. And here comes JSR-277 (http://jcp.org/en/jsr/detail?id=277), which is defining a module and versioning specification for Java
You might also note that you can include a Main-Class attribute in the mainfest and still be forced into having the extension attributes; and in such a manifest configuration, the main class is supposed to be the extension's installer program. And in general, who knows what the plugin (the Java browser plugin) or Java Web Start might do with these Jars with extension specifications: which are not well-defined by the Jar author.
For myself: these are going to fully cripple Maven's Jar packaging. I have to twiddle every manifest into shape before putting any Jar in service.
And I would extend these comments to the War plugin.
And on the subject of making a patch:
I got a ways into dropping the needed sources from SVN. But AbstractJarMojo is importing org.codehaus.plexus.archiver.jar.JarArchiver which does not appear to get resolved by any of the dependencies declared in the POMs. I couldn't figure out how the classpath was supposed to be set up.
Thanks again!
> Maven Puts Arbitrary Extension Definition in JAR Manifest by Default.
> ---------------------------------------------------------------------
>
> Key: MJAR-38
> URL: http://jira.codehaus.org/browse/MJAR-38
> Project: Maven 2.x Jar Plugin
> Type: Bug
> Versions: 2.0
> Environment: Maven version: 2.0.4
> Microsoft Windows XP [Version 5.1.2600]
> Reporter: Steven Coco
> Assignee: Mike Perham
> Attachments: Jar Extension-Name Tester.zip, MavenArchiver.patch.1, MavenArchiver.patch.1, MavenArchiver.patch.2, MavenArchiver.patch.3
>
>
> I'm using the latest Maven release. When I build my project, the resulting Jar file's manifest contains an Extension-Name attribute along with Specification and Implementation attributes. The POM contains no mention that this project is a Java optional package -- an "extension" (or an extension of any other kind).
> I don't know why Maven is doing that.
> If Maven is doing this by default for some reason, it absolutely shouldn't. Maven should not identify my Jar as an optional package unless I explicitly say so. Jars are only extensions if explicitly created as such.
> The name it uses for the extension name is the POM's <artifactId>. That's not even a UID!
--
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: (MJAR-38) Maven Puts Arbitrary Extension
Definition in JAR Manifest by Default.
Posted by "Jochen Wiedmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAR-38?page=comments#action_66642 ]
Jochen Wiedmann commented on MJAR-38:
-------------------------------------
@Stephane: The propsed patch is against the Maven Archiver, which is shared by the jar, war, ... plugins. In other words, your concern should be fulfilled automatically.
> Maven Puts Arbitrary Extension Definition in JAR Manifest by Default.
> ---------------------------------------------------------------------
>
> Key: MJAR-38
> URL: http://jira.codehaus.org/browse/MJAR-38
> Project: Maven 2.x Jar Plugin
> Type: Bug
> Versions: 2.0
> Environment: Maven version: 2.0.4
> Microsoft Windows XP [Version 5.1.2600]
> Reporter: Steven Coco
> Assignee: Mike Perham
> Attachments: Jar Extension-Name Tester.zip, MJAR-38.patch, MavenArchiver.patch.1, MavenArchiver.patch.1, MavenArchiver.patch.2, MavenArchiver.patch.3
>
>
> I'm using the latest Maven release. When I build my project, the resulting Jar file's manifest contains an Extension-Name attribute along with Specification and Implementation attributes. The POM contains no mention that this project is a Java optional package -- an "extension" (or an extension of any other kind).
> I don't know why Maven is doing that.
> If Maven is doing this by default for some reason, it absolutely shouldn't. Maven should not identify my Jar as an optional package unless I explicitly say so. Jars are only extensions if explicitly created as such.
> The name it uses for the extension name is the POM's <artifactId>. That's not even a UID!
--
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: (MJAR-38) Maven Puts Arbitrary Extension Definition
in JAR Manifest by Default.
Posted by "Mike Perham (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAR-38?page=all ]
Mike Perham updated MJAR-38:
----------------------------
Attachment: (was: MJAR-38.patch)
> Maven Puts Arbitrary Extension Definition in JAR Manifest by Default.
> ---------------------------------------------------------------------
>
> Key: MJAR-38
> URL: http://jira.codehaus.org/browse/MJAR-38
> Project: Maven 2.x Jar Plugin
> Type: Bug
> Versions: 2.0
> Environment: Maven version: 2.0.4
> Microsoft Windows XP [Version 5.1.2600]
> Reporter: Steven Coco
> Assignee: Mike Perham
> Attachments: Jar Extension-Name Tester.zip
>
>
> I'm using the latest Maven release. When I build my project, the resulting Jar file's manifest contains an Extension-Name attribute along with Specification and Implementation attributes. The POM contains no mention that this project is a Java optional package -- an "extension" (or an extension of any other kind).
> I don't know why Maven is doing that.
> If Maven is doing this by default for some reason, it absolutely shouldn't. Maven should not identify my Jar as an optional package unless I explicitly say so. Jars are only extensions if explicitly created as such.
> The name it uses for the extension name is the POM's <artifactId>. That's not even a UID!
--
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: (MJAR-38) Maven Puts Arbitrary Extension Definition
in JAR Manifest by Default.
Posted by "Mike Perham (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAR-38?page=all ]
Mike Perham updated MJAR-38:
----------------------------
Attachment: MJAR-38.patch
> Maven Puts Arbitrary Extension Definition in JAR Manifest by Default.
> ---------------------------------------------------------------------
>
> Key: MJAR-38
> URL: http://jira.codehaus.org/browse/MJAR-38
> Project: Maven 2.x Jar Plugin
> Type: Bug
> Versions: 2.0
> Environment: Maven version: 2.0.4
> Microsoft Windows XP [Version 5.1.2600]
> Reporter: Steven Coco
> Assignee: Mike Perham
> Attachments: Jar Extension-Name Tester.zip, MJAR-38.patch
>
>
> I'm using the latest Maven release. When I build my project, the resulting Jar file's manifest contains an Extension-Name attribute along with Specification and Implementation attributes. The POM contains no mention that this project is a Java optional package -- an "extension" (or an extension of any other kind).
> I don't know why Maven is doing that.
> If Maven is doing this by default for some reason, it absolutely shouldn't. Maven should not identify my Jar as an optional package unless I explicitly say so. Jars are only extensions if explicitly created as such.
> The name it uses for the extension name is the POM's <artifactId>. That's not even a UID!
--
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: (MJAR-38) Maven Puts Arbitrary Extension Definition
in JAR Manifest by Default.
Posted by "Mike Perham (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAR-38?page=all ]
Mike Perham updated MJAR-38:
----------------------------
Attachment: (was: MavenArchiver.patch.3)
> Maven Puts Arbitrary Extension Definition in JAR Manifest by Default.
> ---------------------------------------------------------------------
>
> Key: MJAR-38
> URL: http://jira.codehaus.org/browse/MJAR-38
> Project: Maven 2.x Jar Plugin
> Type: Bug
> Versions: 2.0
> Environment: Maven version: 2.0.4
> Microsoft Windows XP [Version 5.1.2600]
> Reporter: Steven Coco
> Assignee: Mike Perham
> Attachments: Jar Extension-Name Tester.zip
>
>
> I'm using the latest Maven release. When I build my project, the resulting Jar file's manifest contains an Extension-Name attribute along with Specification and Implementation attributes. The POM contains no mention that this project is a Java optional package -- an "extension" (or an extension of any other kind).
> I don't know why Maven is doing that.
> If Maven is doing this by default for some reason, it absolutely shouldn't. Maven should not identify my Jar as an optional package unless I explicitly say so. Jars are only extensions if explicitly created as such.
> The name it uses for the extension name is the POM's <artifactId>. That's not even a UID!
--
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