artemis-jms-client (2.16.0.redhat-00032) is using Alpha2 version of spec which was finalized in 2013.

This is not great for AMQ product reputation and these dependencies get pulled into other products - e.g. ENTESB-17855

pematous please take some steps on QE side to detect alpha / beta artifacts in maven repo that is delivered to the customers.

Details
https://maven.repository.redhat.com/ga/org/apache/activemq/artemis-jms-client/2.16.0.redhat-00032/artemis-jms-client-2.16.0.redhat-00032.pom uses org.apache.geronimo.specs:geronimo-jms_2.0_spec:1.0.0.alpha-2-redhat-2
This version is defined in https://maven.repository.redhat.com/ga/org/apache/activemq/artemis-jms-client/2.16.0.redhat-00032/artemis-jms-client-2.16.0.redhat-00032.pom

Main complains:

• JMS 2.0 spec was finalized in May 2013 (https://en.wikipedia.org/wiki/Jakarta_Messaging). The final version of spec should be used for something that is 8 years old.
• Why is geronimo namespace used for jms spec? There are more relevant and widely used javax / jakarta namespaces