[MWAR-34] Maven Puts Arbitrary Extension Definition in WAR Manifest by Default.

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 2.0.1
• Environment: Maven version: 2.0.4; Microsoft Windows XP [Version 5.1.2600]
• Assignee: Brett Porter
• Reporter: Steven Coco
• Created: 29/Apr/06 15:15
• Updated: 21/Jun/06 00:48
• Resolved: 21/Jun/06 00:48

Description

I'm using the latest Maven release. When I build my project, the resulting War 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); nor any specification or implementation information. What's more: it is not in fact possible to define such an optional package using a War archive.

Maven should not do any of this by default. Maven should not include any of these Manifest asttributes unless they are explicitly declared. It appears as if there is a misunderstanding on the meaning of these Manifest attributes. This is the same issue as reported in MJAR-38; and as in that issue, the name Maven uses for the extension name is the POM's <artifactId> which is not even a UID.

This is also related to the issue reported in MJAR-39 in that Maven uses the value of the POM's <description> element as the value for the Specification-Title attribute; and if this is a multi-line value, Maven winds up creating an invalid Manifest.

I have marked this issue as a Blocker since there is no way to prevent Maven from merging these attributes into the final Manifest.

Issue Links

• relates to: MJAR-38 Maven Puts Arbitrary Extension Definition in JAR Manifest by Default.