maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephane Nicoll (JIRA)" <>
Subject [jira] Commented: (MWAR-34) Maven Puts Arbitrary Extension Definition in WAR Manifest by Default.
Date Sun, 30 Apr 2006 12:41:19 GMT
    [ ] 

Stephane Nicoll commented on MWAR-34:

That's interesting. We do have maven 1.0 users reporting the same kind of issue. 

I'll try to work on it through all plugins.

Thanks for the report anyway

> Maven Puts Arbitrary Extension Definition in WAR Manifest by Default.
> ---------------------------------------------------------------------
>          Key: MWAR-34
>          URL:
>      Project: Maven 2.x War Plugin
>         Type: Bug

>  Environment: Maven version: 2.0.4
> Microsoft Windows XP [Version 5.1.2600]
>     Reporter: Steven Coco
>     Priority: Blocker
>  Attachments: Maven War Manifest
> 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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message