Now there's a 2.3.24-SNAPSHOT in the Apache snapshot Maven repo: https://repository.apache.org/content/repositories/snapshots/org/freemarker/freemarker/2.3.34-SNAPSHOT/
This uses "JEP 238: Multi-Release JAR Files", so hopefully now no tools will choke on it. (Actually, as far as I know some older tools fail when seeing class files inside META-INF, so now those will fail instead, but that's hopefully a more rare, and more manageable situation.) This change is form this PR, which is already merged: https://github.com/apache/freemarker/pull/110 Note that building FreeMarker (not using it) now requires Java 17 instead of 16, because 17 is needed for the fresh enough version of bnd (the tool used during build to add OSGi meta info). I wonder if we should just say that Java record support is only available starting from Java 17, instead of from 16. Support was only added in 2.3.33, and because 16 is not LTS, and 17 is, and both are relatively old, 16 is pretty exotic, and it might not worth the pain to have it for the build. On Mon, Jun 3, 2024 at 5:50 AM Olivier Lamy <ol...@apache.org> wrote: > > Hi, > Last release of freemarker [1] mentions " the minimum required Java > version was increased from Java 7 to Java 8" but Maven enforcer rule > fail with max byte code 1.8. > > Try this simple pom [2] with mvn validate and this will show the problem. > > would it be possible to package the java16 using https://openjdk.org/jeps/238 > ? > > Thanks. > Olivier > [1] https://freemarker.apache.org/docs/versions_2_3_33.html > [2] https://gist.github.com/olamy/aeeb0abd3ec41ee0496fa640ce38af5e -- Best regards, Daniel Dekany
