I would use a simpler approach: just atomic and complete features. We should stop with the Cap/Req usage that cause too much issues (refresh, dual chain resolution, etc).
Regards J On Fri, May 1, 2026 at 6:18 PM Matt Pavlovich <[email protected]> wrote: > Re-working the Jakarta spec features to be API/Impl separated will go a > long way here. Move from “install these x bundles” to “I need Jakarta REST > spec..” > > DRAFT: https://github.com/apache/karaf/pull/1795 > > > On May 1, 2026, at 11:06 AM, Holger Friedrich via dev < > [email protected]> wrote: > > > > Hi, > >> Thoughts? > > > > Sounds good, lets go for Karaf 4.5! > > > > I have the feeling that getting the transition javax to jakarta > completed is the biggest challenge for now. A few of the dependencies are > old and pull in javax packages; a few like hibernate pull in both and might > be wrapped to drop the old ones. If we do not handle it and start porting > apps on top of Karaf, we end up with two different bundles in parallel > (esp. if we have namespace changes as for fasterxml.jackson). > > > > Regards, Holger > > > > > > > >
