Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-5168

Follow OSGi standard version naming for artemis-native artifacts

    XMLWordPrintable

Details

    • False
    • False
    • Undefined

    Description

      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?

      Attachments

        Issue Links

          is duplicated by

          Task - Represents a small unit of work that is not end-user facing. ENTMQBR-5297 Rebuild activemq-artemis-native-linux library with standard naming

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-21948 (7.4.z) libartemis-native artifacts versions don't follow OSGi standard

          • Critical - To be worked on immediately following BLOCKER issues.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-18459 Incorrect version of libartemis-native artifacts in EAP 7.3 Maven repo

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-16606 (7.2.z) Upgrade Artemis from 2.6.3.redhat-00020 to 2.7.0.redhat-00057

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified
          mentioned in

          Page Loading...

          Activity

            People

              dbruscin Domenico Francesco Bruscino
              jstourac@redhat.com Jan Stourac
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: