Re: CI github failed : Java 11 or java 17

2022-11-30 Thread Jacques Le Roux
I found the cause. For performance reason, and especially in order to be able to quickly switch from a JDK version to another, I use a batch file to copy over JDKs to a RAM Disk. So java_home is always the same: this RAM Disk. It has been working since Java 8, It now fails with JDK 17 (from

Re: CI github failed : Java 11 or java 17

2022-11-30 Thread Jacques Le Roux
After upgrading non-functional changes at OFBIZ-12400 (Java code, AsciiDoc versions, Groovy from 2.5.18 to 3.0.13), we can focus on Gradle and JDK version. With last Java 17 and still Gradle 6.5,of of course the same error than before: "does not export com.sun.tools.javac.code to unnamed

Re: CI github failed : Java 11 or java 17

2022-11-30 Thread Jacques Le Roux
Hi Eugen, As you know I'm still on Win7 and was able to manage all related issues so far (like the need to use npm 13.14.0 locally in build.gradle) To simplify things I just committed the non functional Java changes unrelated to Gradle and JDK upgrades, not the same than your for CsrfUtil