Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Environment:XP
-
Number of attachments :
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="$
"/>
- maven.ejb.plugin uses:
<ant:attribute
name="Specification-Version"
value="$
"/>
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="$
"/>
- maven.ejb.plugin uses (title rather than vendor-id):
<ant:attribute
name="Implementation-Title"
value="$
"/>
Thanks,
Issue Links
- is depended upon by
-
MAVEN-1244
plugin issues to fix for RC3
-
- is related to
-
MJAR-5
no Implementation-Vendor-Id in META-INF/MANIFEST.MF
-
Maybe I'm missing something, but I don't see anywhere in the maven core (including core-bundled plugins) where pom.specificationVersion is set. To prove this to myself, I created a jar of one of my commonjava projects, then checked the MANIFEST.MF. This is what I got:
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.5.3
Created-By: Apache Jakarta Maven
Built-By: jdcasey
Package: org.commonjava.io
Build-Jdk: 1.4.2_01
Extension-Name: commonjava-io
Specification-Version:
^^^^^^^^^^^^^^
Specification-Vendor: CommonJava Open Component Project
Specification-Title:
Implementation-Version: 2.0
Implementation-Vendor: CommonJava Open Component Project
Implementation-Vendor-Id:
As you can see, nothing! Maybe we should be setting Specification-Version to $
{pom.currentVersion}everywhere...