Yes currently the idea is just to produce those new artefacts. I'd like to avoid duplication until the new API becomes incompatible (with the remove of JMS 1.1 style API). Cheers, Emmanuel
Le 22/09/2020 à 20:40, Arthur Naseef a écrit : > To clarify, the subject says "move to" which sounds at first like "remove > and replace" - but that's not the intent, right? Just talking about adding > the JakartaEE API and keeping JMS 2.0, correct? > > If it's just adding a new API, I have no strong feelings either way. > > Art > > > On Tue, Sep 22, 2020 at 10:02 AM Emmanuel Hugonnet <[email protected]> > wrote: > >> Hello, >> Currently Artemis is exposing a JMS 2.0 API but Java EE has moved toward >> JakartaEE. >> For JakartaEE 9 there is only a namespace switch( with more coming on with >> JakartaEE 10). >> Shouldn't we propose new artefacts that expose Jakarta Messaging API too ? >> Do yo have any idea on how to create and provide those artefacts ? >> >> Cheers, >> Emmanuel >> >>
signature.asc
Description: OpenPGP digital signature
