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 <mattr...@apache.org> 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é <j...@nanthrax.net> > 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 <mattr...@apache.org> > 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 > >> > >> > >
