[ 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
