Yes moving to Eclipse provided API jars would be nice :) Emmanuel
Le 09/03/2021 à 22:59, Clebert Suconic a écrit : > I see, My personal opinion is +1000... make sure you update the > distribution scripts when you do it. > > > Also, make sure you update artemis-core-client-all. Perhaps > artemis-core-client-osgi. > > The compatibility tests will be a good tool to validate it. > > > Also, make sure you don't see any reference to the geronimo library on > the codebase other than compatibility tests. > > > On Tue, Mar 9, 2021 at 4:53 PM Domenico Francesco Bruscino > <[email protected]> wrote: >> Yes, I'm proposing to move to the eclipse provided jars. >> They are already available on maven central. >> >> Il giorno mar 9 mar 2021 alle ore 22:45 Clebert Suconic < >> [email protected]> ha scritto: >> >>> What you are proposing? to move to the eclipse provided jars? >>> >>> if eclipse is providing the jars EE, it would be a good move. >>> >>> In the past the only reason why geronimo created the JARs was because >>> of Oracle (even before Oracle, as Sun) did not allow the >>> redistribution of the ee jars. >>> >>> I think it would be a good move. >>> >>> >>> Is that available on maven central? >>> >>> On Tue, Mar 9, 2021 at 4:42 PM Domenico Francesco Bruscino >>> <[email protected]> wrote: >>>> Hi, >>>> >>>> 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]. >>>> Do you have any concern on migrating to Jakarta EE 8 artifacts? >>>> >>>> [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 >>>> >>>> Thanks, >>>> Domenico >>> >>> >>> -- >>> Clebert Suconic >>> > >
