That sounds like a good plan to me. CI is now ok on main. I will enable CI on 4.4.x branch too.
For the release trend, I would prefer to have Karaf 5 dedicated for big changes. So, let's focus on 4.5.x with JDK24+ support. I will also include the flat resolver and Karaf services (URL, logging, web, as alternative to Pax) on the 4.x series. I already started a bunch of improvements for 4.5.x (I will create the PRs). Regards JB JB On Thu, Aug 28, 2025 at 9:23 PM Matt Pavlovich <[email protected]> wrote: > > Karaf had a user chime in on the users list asking about JDK 24 support— and > get confused that Karaf 5 wouldn’t be the next-gen based on what was > previously announced. I know JDK 25 is out now, so the questions will start > rolling in. > > I think we need to make a decision on this soon, and be able to start making > changes to main branch b/c we’ll need to set to JDK 21. > > Proposal: > > 1. Update main to karaf 4.5.0-SNAPSHOT (already done) > 2. Update main to source/target/release JDK 21 > 3. Make JAAS API conversions > 4. Update a document for anyone extending karaf with JAAS API that their code > needs to change. > 5. Target a karaf-4.5.x release before end of year w/ new pax-web and JAAS > API in place > > Thanks, > Matt > > PS. I’d welcome an invite as a Karaf committer/PMC to help get this going > sooner =) > > > > On Aug 25, 2025, at 2:07 PM, Romain Manni-Bucau <[email protected]> > > wrote: > > > > Hi all, > > > > Can mean next gen never happens in that product line if you go with semver > > so 6 can be used for LTS.next which will break other stuff (not an issue > > but something to assume before switching to semver). > > > > Romain Manni-Bucau > > @rmannibucau <https://x.com/rmannibucau> | .NET Blog > > <https://dotnetbirdie.github.io/> | Blog <https://rmannibucau.github.io/> | > > Old > > Blog <http://rmannibucau.wordpress.com> | Github > > <https://github.com/rmannibucau> | LinkedIn > > <https://www.linkedin.com/in/rmannibucau> | Book > > <https://www.packtpub.com/en-us/product/java-ee-8-high-performance-9781788473064> > > Javaccino founder (Java/.NET service - contact via linkedin) > > > > > > Le lun. 25 août 2025 à 19:44, Matt Pavlovich <[email protected]> a écrit : > > > >> Thanks, JB. One thing other thing I was thinking about over the weekend > >> is that the JAAS change is breaking for anyone that does security modules. > >> We may need to consider SEMVER with all this. > >> > >> Example: > >> > >> karaf-4.4.x: JDK 11, 17, 21 (JDK 25 won’t work) > >> karaf-5.0.x: JDK 21, 25 (based on karaf 4.x stuff) > >> karaf-6.0.x: JDK (next-gen stuff minho / simplified services, etc) > >> > >> Thanks, > >> Matt > >> > >>> On Aug 25, 2025, at 1:41 AM, Jean-Baptiste Onofré <[email protected]> > >> wrote: > >>> > >>> Hi > >>> > >>> It looks good to me. Before making this change, I propose to have CI > >>> with JDK11/17/21 on the 4.4.x branch (I will do that). For now, with > >>> GitHub migration, the CI is running only on main (with JDK17 for now). > >>> > >>> If there are no objections, I will prepare this. > >>> > >>> Regards > >>> JB > >>> > >>> On Wed, Aug 20, 2025 at 3:03 PM Matt Pavlovich <[email protected]> > >> wrote: > >>>> > >>>> While researching approaches for addressing the JAAS API changes (and > >> coming deprecation in JDK 25), there is not a clean approach to: > >>>> > >>>> 1. Support both JAAS API styles > >>>> 2. Support multiple JDK release less than JDK 18 (non-LTS) > >>>> 3. Support JDK 25 on karaf-4.4.x due to removal of deprecated JAAS API > >> style > >>>> > >>>> ref: https://issues.apache.org/jira/browse/KARAF-7977 > >>>> > >>>> I propose a big jump in JDK baseline to help modernize going forward. > >> With Spring 5 and Jetty 9 no longer doing releases, there is little the > >> Karaf team can do to continue to support JDK 11 runtimes. Those using older > >> releases must accept “as-is” for major framework dependencies. > >>>> > >>>> karaf-4.4.x: JDK 11, 17, 21 (JDK 25 won’t work) > >>>> karaf-4.5.x: JDK 21, 25 > >>>> > >>>> Benefits: > >>>> > >>>> 1. Provides a wide range of JDK in v4.4.x > >>>> 2. Allows advanced users to start testing with JDK 25 on a release > >>>> > >>>> Thoughts? > >>>> > >>>> Matt Pavlovich > >>>> > >>>> > >> > >> >
