Re: Starting ActiveMQ 5.18.x preparation/update

2023-01-09 Thread Matt Pavlovich
Hey JB- Thoughts on consolidating the pre-jakarta work into a quick v5.18.x and then doing a v5.19.x for jakarta? My thought is that we could consolidate v5.16.x and v5.17.x support work into a v5.18.x for all javax.* supported build going forward and then start 5.19.x w/ the jakarta namespace

Re: Starting ActiveMQ 5.18.x preparation/update

2023-01-09 Thread Jean-Baptiste Onofré
Hi Matt, It sounds good to me, as soon as we move forward on 5.19.x soon after 5.18.x. Jakarta namespace could be quickly expected by users as some frameworks already switched to it (spring boot, camel, ...), so client libs will have to move fast. For Spring 6, it's not very difficult, I already d