I am thinking about bumping everything which contains sources and is currently set to 11 or 17 to release 21 to consolidate on one number. (thinking: if its still 8 it either hasn't been looked at for a while or its probably for a reason and something would break)
Although I didn't plan on doing this "by hand" anymore, I think there is still value in it since it would avoid extra cycles on PRs which didn't bump the version and contain new code which would benefit from a bump. this would be for NB 33 after the NB 32 release phase is over to avoid conflicts -mbien On 8/23/26 07:05, Michael Bien wrote: > shouldn't be something to worry about. NB 30 bumped the lower bound to > JDK 21, but individual modules can do that incrementally (e.g when they > are updated). Most modules were consolidated to release=17 via cluster > wide updates as part of the work to migrate to the javac release flag*. > > would be nice to have one day a global default property though to > "invert" the situation**. > > -mbien > > * https://github.com/apache/netbeans/issues/8813 > ** e.g https://github.com/apache/netbeans/pull/9323 > > On 8/23/26 06:17, Ernie Rael wrote: >> This may be expected, but it does seem curious. >> >> * org-openide-util-RELEASE310.jar is bytecode 65/JDK-21 >> * org-openide-util-lookup-RELEASE310.jar is bytecode 61/JDK-17. >> >> -ernie >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
