I tweaked the CI configuration to use JDK 17 instead of 11, and the royale-compiler and royale-typedefs builds have both passed. royale-asjs is currently running as I write this.
I remember having to tweak the CI to use a different JDK when Infra updated Jenkins once before. I think that we were building with JDK 8 at the time, but Jenkins started requiring JDK 11. -- Josh Tynjala Bowler Hat LLC https://bowlerhat.dev/ On Tue, Mar 10, 2026 at 1:12 PM Josh Tynjala <[email protected]> wrote: > Class file version 61.0 is JDK 17. 55.0 is JDK 11. So it sounds like > something was compiled to run on JDK 17, but is trying to run on JDK 11. > > I'm guessing that it's the newer Jenkins update that requires JDK 17. > > -- > Josh Tynjala > Bowler Hat LLC > https://bowlerhat.dev/ > > > On Tue, Mar 10, 2026 at 12:30 PM Harbs <[email protected]> wrote: > >> Our build has been stalled for two days. I contacted infra and they got >> it unstuck. I believe they’ve updated Jenkins. >> >> Our build is currently failing with: >> >> F:\jenkins\jenkins-home\agent.jar >> f:\jenkins\jenkins-home\712657a4\maven35-interceptor.jar >> f:\jenkins\jenkins-home\712657a4\maven3-interceptor-commons.jar 60055 >> Exception in thread "main" java.lang.UnsupportedClassVersionError: >> hudson/remoting/Launcher has been compiled by a more recent version of the >> Java Runtime (class file version 61.0), this version of the Java Runtime >> only recognizes class file versions up to 55.0 >> >> I don’t know very much about Maven, but does this have to do with the >> fact that the pom is declaring the Java version as 11? >> >> Harbs > >
