larry-cable commented on issue #321:
URL:
https://github.com/apache/maven-compiler-plugin/issues/321#issuecomment-2777236755
the mystery deepens, so I strace(1) mvn and located the execve of javac:
`execve("/usr/java/jdk-24-oracle-x64//bin/javac", ["javac", "--release",
"24", "--module-version", "1", "--patch-module",
"java.base=/home/lpgc/src/git/jpscompatibility/src/main/java/java.base/share/classes",
"--source-path", "/home/lpgc/src/git/jpscompatibility/src/main/java", "-s",
"/home/lpgc/src/git/jpscompatibility/target/generated-sources/annotations",
"-d", "/home/lpgc/src/git/jpscompatibility/target/classes",
"src/main/java/java.base/share/classes/java/lang/String.java"]...`
I extracted this and created a a shell file and experimented with this to
determine what was the difference between this and
a simple command line that appeared to work
you will be glad to hear that it does not appear to be a plugin bug but in
fact the presence of a --release option that appears
to affect the configuration of the javac compiler!
I'll ask internally why this is so ...
@desruisseaux many thanks for your help today! **very very much
appreciated**!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
