Build fails on undertow example with an error related to Multi-release module
See original GitHub issueBuilding the project fails with following error:
Error: jboss-logging-3.2.1.Final.jar is a multi-release jar file but --multi-release option is not set
while boss-logging is not a multi-release module.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Compilation error in undertow - java - Stack Overflow
I am developing a webapp using undertow and am fairly new to java. I get an error while running ... Error: [ERROR] Failed...
Read more >spring-projects/spring-boot - Gitter
Failed to build body from content. Serializable class not available to broker. Reason: java.lang.ClassNotFoundException: Forbidden class demo.
Read more >Release Notes - Red Hat Issue Tracker
performRuntime method; [WFLY-9910] - CustomUndertowFilterTestCase fails to reload ... [WFLY-10252] - Upgrade Weld-related modules to JBoss Modules 1.8 ...
Read more >Java – Schneide Blog
It is therefore important that no errors or warnings are output, ... -q \ --multi-release 17 \ --print-module-deps \ --class-path build/lib/* ...
Read more >Unable to build from source code (similar error... - JBoss.org
When trying to build from source I get the following error - a similar ... [ERROR] Failed to execute goal on project switchyard-as7-modules: ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
There is a bug in jdeps which prevents it from running with a mixture of MR JARs and non-MR JARs.
We run into this when adding module descriptors to existing JARs (typically dependencies you’d like to use in a jlink image). After adding a descriptor under META-INF/versions/9 to the first dependency, the jdeps call to subsequent ones (for creating the candidate descriptor) failse due to that. As I learned, this has been fixed in JDK 12 and also be backported to the upcoming 11.0.2 release, i.e. then things can be made working by passing the
--multi-release=xyz
option to the jdeps call.Nevermind. Setting jvmVersion to 9 works.