+1 for JDK 17 as minimum version. Some tools we are using do not support JDK 17 for now, e.g. JBoss bridge, jarjar, etc. Maybe we have to find alternatives or maintain them by ourselves.
Apart from new features and bugfix, performance improvement should gain more concerns. Our CI does not trigger performance test for now, it's hard for us to find performance issue in time. Cheers, Daniel Sun On 2025/08/24 10:43:03 Paul King wrote: > Hi folks, > > Now that 5 is out, I created a GROOVY_5_0_X branch, and master has become > Groovy 6. > > We should discuss a minimum JDK version we plan to support for Groovy 6. > > My current thinking is that since we are typically very conservative with > the minimum version, we should bump to JDK17. I am hoping Groovy 6 will be > delivered with a quicker window than Groovy 5, but there hasn't been any > discussion about features as yet, so it's a little hard to predict. I think > JDK17 gives us a nice increment where we can make numerous advances, and if > the release is taking longer than we expected, we can always adjust our > decision. But, I'm interested in what others think ... > > > > Cheers, Paul. >
