To be clear, the focus is on the features we control. For features from third-party projects, they have to create "clean" features.
I favor wrapping in Karaf when necessary (as I did for Hiberbate 6+ support). This way, we can provide clean features. Regards JB On Fri, May 1, 2026 at 6:07 PM 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 > > > >
