On Thu, 2024-05-23 at 09:10 +0000, Stefan Seifert wrote: > konrad provided this wiki page with hints for update to parent 60+: > https://cwiki.apache.org/confluence/x/SI75E > > you have to remove java 11 from .sling-module.json during the update, > or add one like this if it does not exist: > https://github.com/apache/sling-org-apache-sling-testing-sling-mock/blob/master/.sling-module.json
I wonder if we could/should do some magic here and automatically remove Java 11 from the JDKs if we find parent pom >= 60 Robert > > stefan > > > -----Original Message----- > > From: Jörg Hoh <jhoh...@googlemail.com.INVALID> > > Sent: Thursday, May 23, 2024 11:04 AM > > To: Sling Developers List <dev@sling.apache.org> > > Subject: parent pom 60 & requirement to use java17 for builds > > > > Hi, > > > > While updating the sling engine to use the latest parent, I found > > that it > > enforces Java 17 or newer to build: > > > > https://ci- > > builds.apache.org/blue/organizations/jenkins/Sling%2Fmodules%2Fslin > > g-org- > > apache-sling-engine/detail/PR-46/1/pipeline > > > > Rule 0: org.apache.maven.enforcer.rules.version.RequireJavaVersion > > failed with message: > > > > <https://ci- > > builds.apache.org/blue/organizations/jenkins/Sling%2Fmodules%2Fslin > > g-org- > > apache-sling-engine/detail/PR-46/1/pipeline#step-49-log- > > 153>Detected > > JDK version 11.0.16-1 > > (JAVA_HOME=/usr/local/asfpackages/java/adoptium-jdk-11.0.16.1+1) is > > not in the allowed range [17,). > > > > > > I checked and found that the resulting bytecode is version 55.0 > > (Java > > SE 11), so it should be okay. > > > > But: How do we adjust the CI builds in a way, that it des not try > > to > > build them with Java 11 anymore? > > > > Jörg > > > > -- > > https://cqdump.joerghoh.de
