Skip to content
Jabel - unlock Javac 9+ syntax when targeting Java 8
Branch: master
Clone or download
Latest commit 9c9f1c6 Oct 22, 2019

Jabel - use Javac 12+ syntax when targeting Java 8

Because life is too short to wait for your users to upgrade their Java!


While Java is evolving and introduces new language features, the majority of OSS libraries are still using Java 8 as their target because it still dominates.

But, since most of features after Java 8 did not require a change in the bytecode, javac could emit Java 8 bytecode even when compiling Java 12 sources.

How Jabel works

Although Jabel is an annotation processor, it does not run any processing, but instruments the java compiler classes and makes it treat some new Java 9+ languages features as they were supported in Java 8.

The result is a valid Java 8 bytecode for your switch expressions, var declarations, and other features unavailable in Java 8.

Why it works

The JVM has evolved a lot for the past years. However, most language features that were added are simply a syntatic sugar. They do not require new bytecode, hence can be compiled to the Java 8.

But, since the Java language was always bound to the JVM development, new language features require the same target as the JVM because they get released altogether.

As was previously described, Jabel makes the compiler think that certain features were developed for Java 8, and removes the checks that otherwise will report them as invalid for the target.

It is important to understand that it will use the same code as for Java 12 and won't change the result's classfile version, because the compilation phase will be done with Java 8 target.

How to use

The plugin is distributed with Jitpack


Make sure you have Jitpack added to the repositories list:


Jabel has to be added as an annotation processor to your maven-compiler-plugin:


                <!-- Make sure we're not using Java 9+ APIs -->

Compile your project and verify that Jabel is installed and successfully reports:

[INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ tester.thirteen ---
[INFO] Changes detected - recompiling the module!
Jabel: initialized. Enabled features:


First, you need to add Jitpack to your repository list:

repositories {
    maven { url '' }

Then, add Jabel as any other annotation processor:

dependencies {
    annotationProcessor 'com.github.bsideup.jabel:jabel-javac-plugin:0.2.0'

Now, even if you set source/target/release to 8, the compiler will let you use some new language features. The full list of features will be printed during the compilation.

sourceCompatibility = 12 // for the IDE support

compileJava {
    options.compilerArgs = [
            "--release", "8" // Avoid using Java 12 APIs

Compile your project and verify that the result is still a valid Java 8 bytecode (52.0):

$ ./gradlew --no-daemon clean :example:test

> Task :example:compileJava
Jabel: initialized. Enabled features:
        - SWITCH_RULE

8 actionable tasks: 8 executed

$ javap -v example/build/classes/java/main/com/example/JabelExample.class
Classfile /Users/bsideup/Work/bsideup/jabel/example/build/classes/java/main/com/example/JabelExample.class
  Last modified 31 Aug 2019; size 1463 bytes
  MD5 checksum d98fb6c3bc1b4046fe745983340b7295
  Compiled from ""
public class com.example.JabelExample
  minor version: 0
  major version: 52

IDE support

IntelliJ IDEA

How to avoid using Java 9+ APIs in IntelliJ IDEA

If you set --release=8 flag, the compiler will report usages of APIs that were not in Java 8 (e.g. StackWalker). But if you wish to see such usages while editing the code, you can make IDEA highlight them for you:

  • Open Preferences
  • Choose "Editor -> Inspection"
  • Find "Usages of API which isn't available at the configured language level"
  • Click "Higher than", and select "9 - Modules, private method in interfaces etc" from dropdown

IntelliJ IDEA Language Level Inspection

You can’t perform that action at this time.