This is a tracking issue for ENTMQBR-2178, because it causes issues in EAP tests and we cannot track it otherwise.
Following artifacts do not contain Implementation-Version attribute in their MANIFEST.MF file in the jar archive:
artemis-hornetq-protocol-1.5.5.016-redhat-00001.jar /home/hudson/hudson_workspace/workspace/eap-71x-acceptance-tattletale/manu/out/UnzipEap/workspace/jboss-eap-7.1/modules/system/layers/base/org/apache/activemq/artemis/protocol/hornetq/main/artemis-hornetq-protocol-1.5.5.016-redhat-00001.jar Not listed artemis-hqclient-protocol-1.5.5.016-redhat-00001.jar /home/hudson/hudson_workspace/workspace/eap-71x-acceptance-tattletale/manu/out/UnzipEap/workspace/jboss-eap-7.1/modules/system/layers/base/org/apache/activemq/artemis/main/artemis-hqclient-protocol-1.5.5.016-redhat-00001.jar Not listed artemis-native-1.5.5.016-redhat-00001.jar /home/hudson/hudson_workspace/workspace/eap-71x-acceptance-tattletale/manu/out/UnzipEap/workspace/jboss-eap-7.1/modules/system/layers/base/org/apache/activemq/artemis/journal/main/artemis-native-1.5.5.016-redhat-00001.jar
I can see that there is available Bundle-Version which can be utilized instead:
Bundle-Version: 1.5.5.016-redhat-00001
Although, in other artifacts we have Implementation-Version specified. Thus I believe that we should be consistent and have it specified also in these two packages.
- clones
-
JBEAP-16092 (7.2.z) Missing Implementation-Version attribute in MANIFEST.MF
-
- Closed
-
- links to