Find which Java version is in use

org.openrewrite.java.migrate.search.AboutJavaVersion

A diagnostic for studying the distribution of Java language version levels (both source and target compatibility across files and source sets).

Recipe source

GitHub, Issue Tracker, Maven Central

  • groupId: org.openrewrite.recipe

  • artifactId: rewrite-migrate-java

  • version: 2.12.0

Options

TypeNameDescriptionExample

String

whenUsesType

Optional. Only mark the Java version when this type is in use.

lombok.val

Data Tables (Only available on the Moderne platform)

Java versions by source set

A per-source set view of Java version in use.

Column NameDescription

Project name

The module name (useful especially for multi-module repositories).

Source set name

The source set, e.g. main or test.

Created by

The JDK release that was used to compile the source file.

VM vendor

The vendor of the JVM that was used to compile the source file.

Source compatibility

The source compatibility of the source file.

Major version source compatibility

The major version.

Target compatibility

The target compatibility or --release version of the source file.

Usage

This recipe has no required configuration options. It can be activated by adding a dependency on org.openrewrite.recipe:rewrite-migrate-java:2.12.0 in your build file or by running a shell command (in which case no build changes are needed):

  1. Add the following to your build.gradle file:

build.gradle
plugins {
    id("org.openrewrite.rewrite") version("6.12.0")
}

rewrite {
    activeRecipe("org.openrewrite.java.migrate.search.AboutJavaVersion")
}

repositories {
    mavenCentral()
}

dependencies {
    rewrite("org.openrewrite.recipe:rewrite-migrate-java:2.12.0")
}
  1. Run gradle rewriteRun to run the recipe.

See how this recipe works across multiple open-source repositories

The community edition of the Moderne platform enables you to easily run recipes across thousands of open-source repositories.

Please contact Moderne for more information about safely running the recipes on your own codebase in a private SaaS.

Contributors

Jonathan Schneider, Sam Snyder, Tim te Beek

Last updated