Hello,
It makes a ton of sense to mark jakarta version a 5.0, just like
ActiveMQ 6 which started to officially support jakarta.jms.
This also gives us a new major release to announce and shake things a
bit! :-)
Cheers,
Łukasz
On 5/6/26 17:36, Jean-Baptiste Onofré wrote:
Hi Robert,
Yes, the full resolver will still be available (in the corresponding
distribution).
If I don't expect much trouble migrating from Karaf 4.4 to 4.5, it's true
that we made/make many changes in Karaf 4.5 (JDK bump, remove the specs
bundle, etc).
Maybe worth bumping to Karaf 5.
Others?
Regards
JB
On Wed, May 6, 2026 at 12:30 PM Robert Varga <[email protected]> wrote:
On 06/05/2026 11.24 am, Jean-Baptiste Onofré wrote:
That's a good call.
If we agree to use the Karaf distribution powered by simple resolver and
Karaf services by default (see the other thread), then, I think it makes
sense to use Karaf 5.0.0.
What are the others thinking?
So as long as the full resolver is still available for custom
distributions, I do not really have a preference.
I will note that it is completely normal in the ecosystem to raise
required Java version with a minor bump.
Jakarta namespace changes are typically done across a major version
bump, but I can't think of a non-library that has done so.
I guess we should be guesstimating the migration effort inflicted on
downstreams: is it going to be on the scale of karaf3 -> karaf4 or
karaf4.1 -> karaf4.2?
Regards,
Robert
