The following comment has been added to this issue:

     Author: Stephen McConnell
    Created: Fri, 16 Apr 2004 11:51 AM
       Body:
Under Maven RC2 the jar plugin manifest entries have been changed in such a way that 
can result in runtime failure based on the assigned specification version.

The change is the inclusion of the following line in the manifest:

        <ant:attribute name="Specification-Version" value="${pom.currentVersion}"/>

Firstly - the "Specification-Version" is not the same as the implementation version 
(impl version is correctly assigned as ${pom.currentVersion).  Secondly the jar 
optional extensions spec requires that the specification version is a dewey decimal.  
RC2 generated jars will fail if the current version of the jar contains alphanumeric 
characters (e.g. 1.2-dev) or any string value that cannot be converted to a dewey 
decimal.
---------------------------------------------------------------------
View this comment:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPJAR-7&page=comments#action_18692

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPJAR-7

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MPJAR-7
    Summary: Specification-Version and Implementation-Vendor-Id not being set
       Type: Improvement

     Status: Unassigned
   Priority: Trivial

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven-jar-plugin

   Assignee: 
   Reporter: Lynn Richards

    Created: Wed, 15 Oct 2003 2:29 PM
    Updated: Fri, 16 Apr 2004 11:51 AM
Environment: XP

Description:
Please make the jar manifests consistent.

1. Specification-Version not being set.  pom.specifiationVersion not defined in 
project schema.

- maven.jar.plugin uses:

<ant:attribute 
 name="Specification-Version" 
 value="${pom.specificationVersion}"/>

- maven.ejb.plugin uses:

<ant:attribute 
 name="Specification-Version" 
 value="${pom.currentVersion}"/>


2. Implementation-Vendor-Id not being set.  pom.organization.identifier not defined in 
project schema.

- maven.jar.plugin uses:

<ant:attribute 
 name="Implementation-Vendor-Id"
 value="${pom.organization.identifier}"/>

- maven.ejb.plugin uses (title rather than vendor-id):

<ant:attribute 
 name="Implementation-Title" 
 value="${pom.package}"/>


Thanks,



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to