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

Reply via email to