Re: [PROPOSAL] Jakarta approach for ActiveMQ 5.x broker

2023-03-30 Thread Christopher Shannon
Thanks Matt for bringing this up. We definitely need to figure out a path forward as there is a lot of confusion about this still and users are getting bit by it when trying to upgrade to Spring 6 and Spring boot 3. Ultimately I think we will need to support both javax and jakarta for quite a

Re: [PROPOSAL] Jakarta approach for ActiveMQ 5.x broker

2023-03-30 Thread Endre Stølsvik
>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é wrote: > Hi,

Re: [PROPOSAL] Jakarta approach for ActiveMQ 5.x broker

2023-03-30 Thread Jean-Baptiste Onofré
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 wrote: > > Hello All- > > I started building a jakarta-based broker for

[PROPOSAL] Jakarta approach for ActiveMQ 5.x broker

2023-03-30 Thread Matt Pavlovich
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