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...
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...