Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0
-
Fix Version/s: 2.1
-
Component/s: None
-
Labels:None
-
Environment:Maven version: 2.0.4
Microsoft Windows XP [Version 5.1.2600]
-
Testcase included:yes
-
Number of attachments :
Description
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 issue is related to
MJAR-39andMWAR-34in that since it sets the Specification-Title element by default to the POM's <description> element, it easily can create an invalid Manifest.MJAR-39andMWAR-34in that since it sets the Specification-Title element by default to the POM's <description> element, it easily can create an invalid Manifest.