Description of problem: List of artifact with missing Implementation-Version at all: modules/system/layers/base/org/apache/xml-resolver/main/xml-resolver-1.2-redhat-3.jar Additional info: see https://bugzilla.redhat.com/show_bug.cgi?id=927238
David, can you investigate please how this may have happened?
The manifest is being replaced at the end of the build thereby overwriting the original manifest which has the Implementation-Version. The fix is to first set the property impl.version with ant so that it is set to the full redhat version, and then to patch the original manifest to combine with this with the other one so as to not overwrite the original. Note that Bundle-Version: 1.2.0.v200806030312 does not match the Implementation-Version, but I am not worrying about this issue for this bug.
Too risky for this stage of 6.1.0
Hi David, how long would it take you to make this change?
The work has been completed in the SCM, so I am estimating one to two more days for the build.
The build has now been converted to MEAD (current version: 1.2.redhat-9). Therefore, the jar should now pick up the correct Implementation-Version information (from ${project.version}) just as any MEAD build would.
Fixed for EAP 6.2.0 ER2. There is 'Implementation-Version: 1.2.redhat-9' in jboss-eap-6.2.0.ER2.zip/jboss-eap-6.2/modules/system/layers/base/org/apache/xml-resolver/main/xml-resolver-1.2.redhat-9.jar/META-INF/MANIFEST.MF