Hi, The main change is JDK17 required by the update to Spring 6.x, this is actually the update that implies a new version (ActiveMQ is coupled to Spring right now).
About jakarta, even on Artemis, I guess you had an impact for the users as you moved client from javax.jms to jakarta.jms, right ? Broker side, it's transparent for users, but not client side imho. Regards JB On Thu, Sep 14, 2023 at 5:15 PM Justin Bertram <jbert...@apache.org> wrote: > > I don't have a deep familiarity with the internals here so some of the > fundamentals behind the changes aren't clear to me. > > Is the move to JDK 17 prompted by the fact that Spring 6 requires it? How > tightly is "Classic" coupled with Spring? > > Is the coupling with Spring also why the code-base is being moved > whole-sale to Jakarta? It's been a little while now, but when Artemis > implemented Jakarta support back in early 2021 I don't recall any > disruption for current users and no major version change was needed. Both > Java EE and Jakarta EE implementations are based on the same code-base. Is > something like that not possible here? It would simplify maintenance a lot > since fixes/features wouldn't have to be back-ported. > > > Justin > > On Mon, Sep 11, 2023 at 4:22 PM Christopher Shannon < > christopher.l.shan...@gmail.com> wrote: > > > First, I realize that this thread is likely to cause a fight based on past > > history and probably not go anywhere, but with the work being done > > with Jakarta for AMQ 5.x I think it's time to at least bring up the > > ActiveMQ 6.0 discussion. > > > > With all the breaking changes currently targeted for version 5.19.x, such > > as the Jakarta switch from javax, requiring JDK 17, major Spring and Jetty > > upgrades and now potentially major OSGi changes, it makes zero sense to me > > to have this next AMQ version as version 5.19.0 as it's completely > > incompatible with the previous version 5.18.x. Users are likely going to be > > in for a rude awakening when trying to upgrade and will be quite confused > > as to why so much is different. > > > > The Jakarta changes should really be a major version upgrade so that it's > > much more clear to users that it's very different from the previous > > version. Another major benefit of going with version 6.0 is that it frees > > up the previous javax releases to continue on with 5.19 or 5.20 because we > > will likely need to support the older javax releases for quite a while. > > > > Also, from my point of view it seems pretty clear that the original goal > > for Artemis to become AMQ 6.0.0 is never going to happen. Artemis has had > > its own branding and versioning for several years now and will likely > > continue that way and not change so I don't really see that as a reason to > > not bump AMQ 5.x to 6.x with all the major breaking changes. > > > > Anyways, I figure there won't be much agreement here but thought I should > > at least throw it out there before we go and release 5.19.x with such major > > breaking changes. > >
