Doesn't work on Java 16
See original GitHub issueCaused by: java.lang.IllegalAccessError: class com.github.bsideup.jabel.JabelCompilerPlugin (in unnamed module @0x7f3097e8) cannot access class com.sun.tools.javac.code.Source$Feature (in module jdk.compiler) because module jdk.compiler does not export com.sun.tools.javac.code to unnamed module @0x7f3097e8
This is likely due to JEP 396.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Jenkins does not support Java 16 [duplicate] - Stack Overflow
This reads like Jenkins needs a long-term support version to run but you should be able to provide additional Java versions for your...
Read more >Why and How to Upgrade to Java 16 or 17 - InfoQ
Class file major version 61 is used for Java 17, 60 was used for Java 16. This basically means that the plugin or...
Read more >FST doesn't work on Java 16 · Issue #312 - GitHub
Temporary workaround: add --illegal-access=permit argument as a command-line argument for your java.exe . Yes, to java.exe , not to javac or ...
Read more >[MCL-18306] Newer versions of Java are blocked - Jira - Mojang
Bug - A problem which impairs or prevents the functions of the product. MCL-18740 Unable to launch Minecraft versions before 1.17 with Java...
Read more >Java 16 and IntelliJ IDEA - The JetBrains Blog
If you are still working with Java 8, you might have mixed feelings about the ... For your information, a compact constructor doesn't...
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
To use 0.3.0 with java 16 you can add the following flags: “–add-opens=jdk.compiler/com.sun.tools.javac.code=ALL-UNNAMED”, “–add-opens=jdk.compiler/com.sun.tools.javac.parser=ALL-UNNAMED” to the forkOptions.jvmArgs variable of JavaCompile tasks, set isFork to true and update byte-buddy and byte-buddy-agent to the 1.10.22 version by excluding them and re-adding them to the annotationProcessor configuration
@Treehopper I’m not really familiar with maven but I think it should probably work, or maybe you could try replacing --add-opens with --add-exports since you’re using compiler arguments and not forking the jvm