Details
-
Dependency upgrade
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
ActiveMQ Artemis depends on some Apache Geronimo Specs artifacts [1] and Javax artifacts [2] for the Java EE APIs. Most of them could be migrated to their respective Jakarta EE artifacts, given that Jakarta EE 8 provides backwards compatibility within the javax* namespace.
The license of Jakarta EE artifacts is Eclipse Public License 2.0 [3] so they may be included in binary form within an Apache product, see ASF 3RD PARTY LICENSE POLICY [4].
Following the discussion on the dev list[5], I would migrate to Jakarta EE 8 artifacts having the artemis-pom pointing to the EE 8 versions, and override those in modules needing the EE 9 versions instead.
[1]
org/apache/geronimo/specs/geronimo-annotation_1.2_spec/1.0
org/apache/geronimo/specs/geronimo-ejb_3.0_spec/1.0.1
org/apache/geronimo/specs/geronimo-j2ee-connector_1.5_spec/2.0.0
org/apache/geronimo/specs/geronimo-jaspic_1.0_spec/1.0 [5]
org/apache/geronimo/specs/geronimo-jaxrs_2.1_spec/1.1
org/apache/geronimo/specs/geronimo-jms_1.1_spec/1.1 [6]
org/apache/geronimo/specs/geronimo-jms_2.0_spec/1.0-alpha-2 [5]
org/apache/geronimo/specs/geronimo-json_1.0_spec/1.0-alpha-1 [5]
org/apache/geronimo/specs/geronimo-jta_1.1_spec/1.1.1 [5]
org/apache/geronimo/specs/geronimo-servlet_3.0_spec/1.0 [6]
[2]
javax/activation/activation/1.1.1 [5]
javax/annotation/javax.annotation-api/1.3.2
javax/enterprise/cdi-api/1.2 [6]
javax/inject/javax.inject/1 [5]
javax/management/j2ee/javax.management.j2ee-api/1.1.1
javax/xml/bind/jaxb-api/2.3.1 [5]
[3] https://www.eclipse.org/legal/epl-2.0/
[4] https://www.apache.org/legal/resolved.html
[5] this artifact is included in the release package
[6] no jakarta artifact with a matching version exits
Attachments
Issue Links
- fixes
-
ARTEMIS-3077 Package 'javax.jms' is declared in module with an invalid name ('geronimo.jms.2.0.spec')
- Resolved
- links to