Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Does not support Java 16+

See original GitHub issue

Using parallel-consumer with Java 17 fails with the following exception at compile time:

[INFO] Compiling 4 source files to /builds/backend/access-logs-injector/target/classes
An exception has occurred in the compiler (17.0.2). Please file a bug against the Java compiler via the Java bug reporting page ( after checking the Bug Database ( for duplicates. Include your program, the following diagnostic, and the parameters passed to the Java compiler in your report. Thank you.
java.util.ServiceConfigurationError: com.sun.source.util.Plugin: Provider com.github.bsideup.jabel.JabelCompilerPlugin could not be instantiated
	at java.base/
	at java.base/java.util.ServiceLoader$ProviderImpl.newInstance(
	at java.base/java.util.ServiceLoader$ProviderImpl.get(
	at java.base/java.util.ServiceLoader$
	at jdk.compiler/
	at jdk.compiler/
	at jdk.compiler/$doCall$0(
	at jdk.compiler/
	at jdk.compiler/
	at jdk.compiler/
	at org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(
	at org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile(
	at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(
	at org.apache.maven.plugin.compiler.CompilerMojo.execute(
	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(
	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(
	at org.apache.maven.DefaultMaven.doExecute(
	at org.apache.maven.DefaultMaven.doExecute(
	at org.apache.maven.DefaultMaven.execute(
	at org.apache.maven.cli.MavenCli.execute(
	at org.apache.maven.cli.MavenCli.doMain(
	at org.apache.maven.cli.MavenCli.main(
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(
	at java.base/java.lang.reflect.Method.invoke(
	at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(
	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(
	at org.codehaus.plexus.classworlds.launcher.Launcher.main(
Caused by: java.lang.IllegalAccessError: class com.github.bsideup.jabel.JabelCompilerPlugin (in unnamed module @0x3fbe503c) cannot access class$Feature (in module jdk.compiler) because module jdk.compiler does not export to unnamed module @0x3fbe503c
	at com.github.bsideup.jabel.JabelCompilerPlugin.<clinit>(
	at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(
	at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(
	at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(
	at java.base/java.lang.reflect.Constructor.newInstance(
	at java.base/java.util.ServiceLoader$ProviderImpl.newInstance(
	... 34 more

This is because parallel-consumer uses an old jabel version which doesn’t support Java 16+. 0.4.0 seems to fix the issue, see

Could you bump jabel version? Six months after Java 17 GA, it would be nice to not have to sprinkle --add-open everywhere 😉

Issue Analytics

  • State:closed
  • Created a year ago
  • Reactions:4
  • Comments:19 (13 by maintainers)

github_iconTop GitHub Comments

lopezzlauracommented, Apr 26, 2022

Hi, Thanks for publishing snapshots so promptly, unfortunately using it fails as io.stubbs.truth.truth-generator-api is missing but required. Could you publish this lib as well ? Excluding the lib does work but just to let you know, as we’d rather avoid that.

cyklcommented, Apr 19, 2022

I did notice #225 and the 1.0, but scope and ETA were unclear to me.

Can you try it with master?

I will (I want to give the new batching feature a try anyway).

Read more comments on GitHub >

github_iconTop 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 >
Oracle Java SE Support Roadmap
Oracle provides this Oracle Java SE Support Roadmap, to help you understand maintenance and support options and related timelines.
Read more >
Why and How to Upgrade to Java 16 or 17 - InfoQ
This basically means that the plugin or dependency doesn't work on that version of Java. Most of the time upgrading to the latest...
Read more >
Java 16 and IntelliJ IDEA - The JetBrains Blog
Java 16 features are supported in IntelliJ IDEA 2021.1, which is scheduled to be released this March. The early access versions of 2021.1 ......
Read more >
Java 16 support - [Deprecated] Suggest new features
While eclipse JDT now supports Java 16, it's still not yet part of their latest official JDT release (available through their marketplace, not ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found