-
Bug
-
Resolution: Done
-
Major
-
None
-
False
-
False
-
Undefined
-
Not sure whether I set correct component or maybe even a project - feel free to alternate then, thank you.
During testing of JBoss EAP 7.4.0.GA-CRx release, we bumped into a naming issue of libartemis-native-linux artifacts, see JBEAP-21948. Based on what I was able to find out, similar issue was reported also during JBoss EAP 7.3.0.GA-CR1 testing in JBEAP-18459, so it's a repetitive issue. Whole thing was discussed quite thoroughly in JBEAP-16606. Based on the comments there, I got impression that the final agreement is to follow OSGi versioning standard even for these artifacts. But it looks like this doesn't happen always.
Could we please either follow this agreement or in case there are reasons we don't want to do so to get some other agreement so we are all on the same page?
- is duplicated by
-
ENTMQBR-5297 Rebuild activemq-artemis-native-linux library with standard naming
- Closed
- is related to
-
JBEAP-21948 (7.4.z) libartemis-native artifacts versions don't follow OSGi standard
- Closed
-
JBEAP-18459 Incorrect version of libartemis-native artifacts in EAP 7.3 Maven repo
- Closed
-
JBEAP-16606 (7.2.z) Upgrade Artemis from 2.6.3.redhat-00020 to 2.7.0.redhat-00057
- Closed
- mentioned in
-
Page Loading...