Closed ruedigerk closed 9 months ago
same here
This is probably a duplicate of #69 and a fix documented here.
I followed the documentation and encountered a missing setting
[ERROR] import: Entry[import from realm ClassRealm[maven.api, parent: null]]
[ERROR]
[ERROR] -----------------------------------------------------
[ERROR] : module java.base does not open java.nio to unnamed module @3ce4eb42
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginContainerException
@DirkMahler I think you should add --add-opens java.base/java.nio=ALL-UNNAMED
to the jvm options. It fixed at least my build.
Bug Description
When running the jQAssistant Maven plugin in version 2.0.1 (all prior versions are also affected but produce different errors) on JDK17, the build fails with the following error:
Your Environment
How can we reproduce the bug?
Run the plugin with JDK17.
Definition of Done for the Implementers
Remove this hint: these checkboxes can be checked like this: [x]