Hi Endre- Thanks, this might be a way to bring 5.18.x forward on Jetty version 12 w/o converting 5.18.x to jakarta and Spring 6.
-Matt Pavlovich > On Mar 30, 2023, at 3:06 PM, Endre Stølsvik <en...@stolsvik.com> wrote: > > From a lurker position here, I just wanted to point out that Jetty is > evidently making a version 12 which will support both javax. and jakarta. > in the same server. > https://www.eclipse.org/jetty/download.php > > Kind regards, > Endre > > > On Thu, Mar 30, 2023 at 9:54 PM Jean-Baptiste Onofré <j...@nanthrax.net> > wrote: > >> Hi, >> >> I agree with the plan but why not keep 5.19.0-SNAPSHOT on main ? >> We have the activemq-5.18.x branch already that could be LTS where we >> keep javax namespace. >> >> Regards >> JB >> >> On Thu, Mar 30, 2023 at 7:54 PM Matt Pavlovich <mattr...@gmail.com> wrote: >>> >>> Hello All- >>> >>> I started building a jakarta-based broker for ActiveMQ 5.x and propose >> the following steps to manage the change. >>> >>> Background: >>> >>> Jakarta support in ActiveMQ 5.x is going to pull in JDK 17, Spring 6, >> Jakarta EE 9, Servlet 5.x, and Jetty 11. That is quite a bit of change, and >> I suggest we leave a ‘gap version’ in case we need to make any incremental >> updates to 5.18.x series along the way. >>> >>> 1. Rename main to 5.20.0-SNAPSHOT >>> 2. Commit broker-related jakarta, servlet, jetty, spring, etc changes to >> main >>> 3. Create new ‘-javax’ broker modules to support a >> apache-activemq-javax-5.20.0-bin.tar.gz package using re-packaging of the >> jakarta artifacts. >>> 4. Leave 5.19.x as a ‘gap version’ in case it is needed for 5.18.x >> changes >>> >>> Thanks, >>> Matt Pavlovich >>
