Hi all, I think requiring Java 17 in the next RAT release is fine for the reasons mentioned on the ticket. It's really time to say goodbye to Java 8 ;) Java 11 is already kind-of EOL, so +1 to skip that version.
If people cannot upgrade to whatever Java version Rat will require, it's still possible to run rat with a different Java toolchain. Robert On Mon, Oct 27, 2025 at 12:02 PM Tilman Hausherr <[email protected]> wrote: > > Hi, > > Everything is outdated somehow. Why not start with jdk11 for the next > release because jdk17 could mean that many more people would have to > change their build scripts? And then after the release and maybe angry > feedback of people who don't read here, move to jdk17 for the next next > release. > > Tilman > > Am 26.10.2025 um 11:34 schrieb P. Ottlinger: > > Dear RAT-users, > > > > as part of the upcoming 1.0.0-release we want to get rid of > > -deprecated stuff in RAT (you may have run into some of these warnings > > while migrating to 0.17) and > > -update to a newer JDK version (as our reliance on JDK8 forces us to > > stay with many discontinued versions of libraries and dependencies). > > > > > > In the related task (created during development of 0.17) > > https://issues.apache.org/jira/browse/RAT-478 I mentioned upgrading to > > JDK11, BUT this seems to be outdated as well, therefore I'd like to > > start the discussion if JDK17 would be a better starting point. > > > > JDK17 would allow us to use newer versions of libraries (e.g. > > https://docs.junit.org/6.0.0/release-notes/). > > > > Looking forward to your opinion & preferences. > > > > Thanks > > Phil > >
