[MJAR-38] Maven Puts Arbitrary Extension Definition in JAR Manifest by Default.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0
• Fix Version/s: 2.1
• Environment: Maven version: 2.0.4; Microsoft Windows XP [Version 5.1.2600]
• Assignee: Brett Porter
• Reporter: Steven Coco
• Created: 28/Apr/06 09:33
• Updated: 06/Apr/15 01:49
• Resolved: 21/Jun/06 00:48

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!

Issue Links

• is related to: MWAR-34 Maven Puts Arbitrary Extension Definition in WAR Manifest by Default.
• is related to: MJAR-39 Maven Sets Manifest Attribute Values to Multi-Line Strings