For what it's worth - I’ve used Java 24 to run our builds with Maven 3, still targetting Java 8 (at least our runtime is now 23).
Works fine, although Jansi is given warnings about accessing deprecated items. Mark -- "Great artists are extremely selfish and arrogant things" — Steven Wilson, Porcupine Tree On 28 Mar 2025 at 9:14:07 AM, Tommy <to...@natusoft.se> wrote: > You should complain to the idiots at Oracle!! They are totally responsible > for shit like this! > > Personally I have never gone above JDK 11 to avoid shit like this! But > that is easy for me to say since I'm retired and only do hobby projects at > GitHub these days. > > Before I stopped working, none of the customers I worked for in Sweden > went above 11. Just imagine the time and cost to verify all code whenever a > new non backwards compatible JDK is released! > > I'm going to update my will and require "BTW, Oracle are idiots!" on my > gravestone when I die! > > /Tommy > > ______________________ > Tommy Svensson > to...@natusoft.se > On 26 Mar 2025 at 16:18 +0100, Davide Perini <perini.dav...@dpsoftware.org>, > wrote: > > > > Hi there, > > > I'm using JDK23 with maven 3 and everything worked well. > > > I also need maven-shade, maven-assembly and javafx-maven plugins... > > Not all plugins supports maven 4 this is why I would like to stick with > > maven 3.9.9 and maven-compiler-plugin 3.14 > > > Can I use JDK24 considering all the maven plugin I need? > > > I would like to use JDK24 but I get an error when compiling my project, > > > [ERROR] Failed to execute goal > > org.apache.maven.plugins:maven-compiler-plugin:3.14.0:compile > > (default-compile) on project fireflyluciferin: Fatal error compiling: > > java.lang.ExceptionInInitializerError: com.sun.tools.javac.code.TypeTag > > :: UNKNOWN -> [Help 1] > > > Any help would be greatly appreciated. > >
