Closed Ellen-Wittingen closed 1 year ago
It seems mill prioritizes resolving the java version from JAVA_HOME
, perhaps you have an older version there? If not, I'd be interested in the supported values listed in javac --help
.
I do not have JAVA_HOME
set to any value. However, javac --version
showed I was using javac 20.
I now installed and put as default javac 17, and this solved the issue. It compiles fine now.
For javac 20, it does show that it supports compiling for java 17, so that is interesting
-profile <profile>
Check that API used is available in the specified profile.
This option is deprecated and may be removed in a future release.
--release <release>
Compile for the specified Java SE release. Supported releases: 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20
-s <directory> Specify where to place generated source files
--source <release>, -source <release>
Provide source compatibility with the specified Java SE release. Supported releases: 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20
--source-path <path>, -sourcepath <path>
Specify where to find input source files
--system <jdk>|none Override location of system modules
--target <release>, -target <release>
Generate class files suitable for the specified Java SE release. Supported releases: 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20
Hmm, strange. I don't think it's very fruitful to debug this further over github comments. Feel free to re-open the issue if it occurs again or you have more information.
Starting at commit 33212b626a842b2369404b2efbbf5a8efaafddc5 and onwards, building the project with
gives the following build error:
It has the same behaviour on a fresh clone from respository, so it does not seem an IntelliJ issue. I am building this on Fedora with OpenJDK 17.0.6 on the path
Full stack trace: