jira-importer opened a new issue, #200:
URL: https://github.com/apache/maven-war-plugin/issues/200

   **[Steven 
Coco](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=steevcoco)** 
opened 
**[MWAR-34](https://issues.apache.org/jira/browse/MWAR-34?redirect=false)** and 
commented
   
   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.
   
   
   ---
   
   **Attachments:**
   - [Maven War Manifest 
Tester.zip](https://issues.apache.org/jira/secure/attachment/12720610/Maven+War+Manifest+Tester.zip)
 (_1.90 kB_)
   
   **Issue Links:**
   - [MJAR-38](https://issues.apache.org/jira/browse/MJAR-38) Maven Puts 
Arbitrary Extension Definition in JAR Manifest by Default.
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to