Following "Maven Compiler Plugin 3.12.0 Released" [1] I'm trying it out
in a small project of mine [2]. After updating the
maven-compiler-plugin 3.11.0 -> 3.12.0 I've noticed the following error
occurring in my dirty(!) working copy:
> mvn -V package
Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
Maven home: ...\apache-maven-3.9.6
Java version: 21.0.1, vendor: Eclipse Adoptium, runtime: ...\jdk-21
Default locale: en_US, platform encoding: UTF-8
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
...
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.12.0:compile
(java9-compile) on project xbrz-core: Fatal error compiling: basedir
C:\...\xbrz-java\xbrz-core\target\generated-sources\annotations does not
exist -> [Help 1]
that doesn't occur with the compiler plugin 3.11.0. The local change
that appears to trigger the error with the compiler plugin 3.12.0 is
I've deleted "module-info.java" sources:
del /s module-info.java # or with bash
find -name module-info.java -print -delete
Funny enough, if I restore "xbrz-core/src/main/java9/module-info.java"
both of "xbrz-core" and "xbrz-awt" get built successfully, then
"xbrz-tool" fails the same.
Does this behavior appear a regression? I've found a similar symptom
fixed long time ago:
* https://issues.apache.org/jira/browse/MCOMPILER-379
[1] https://lists.apache.org/thread/9x7p7k5n7vptopqrt55o7c2pg7pnznh2
[2] https://github.com/stanio/xbrz-java
Note, "xbrz-java" currently requires JDK 21 for building just for
the javadoc generation. One may edit .mvn/enforcer-extension.xml to
relax this requirement for the purpose of `mvn package` alone.
--
Stanimir
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
