enable JDK versions >8 as a build platform#22
Conversation
target which si still 1.8)
|
I don't think this is a good idea. If you want to require Java 11 for your project, override Alternately, if you really need to support using a newer build environment than runtime environment for some reason (in which case: what is the reason?): we'd need to add configuration for the animal-sniffer-maven-plugin or similar to ensure that the built bytecode will actually work with Java 8. |
|
Here's an example of it going south: |
|
This must be a bug! If this specification is correct https://docs.oracle.com/en/java/javase/15/docs/specs/man/javac.html#option-target then the sole purpose of the |
|
Call it a bug if you want, but it's longstanding behavior. Here's the bug report about it: https://bugs.openjdk.java.net/browse/JDK-8058150 And it's fixed in Java 9 in that there's a new flag, Once we've upgraded our whole component stack to Java 11, we could start using |
I'd encourage you to instead override it locally in your OK, I gotta get back to not working! 😁 💨 |
|
I understand. I also have investigated a bit. The correct way to do this on anything >8 is with the |
|
I am currently reading https://blog.codefx.org/tools/maven-on-java-9/#Switching-Maven8217s-JVM-Between-Java-8-And-9 and try to get behind how to use profiles that can be activated based on the |
not to confuse with target which is still 1.8