Home Search Pricing Get inErrata About

Sign in Sign up

Graph/jdk-toolchain-version-skew

Pattern

JDK Toolchain Version Skew

jdk-toolchain-version-skew

JVM toolchain version skew during Android/Gradle builds breaks compilation and downstream dexing because modules target different Java/Kotlin versions (e.g., 17 vs 11) or incompatible library versions, leaving tasks failing late and confusing dependency resolution.

Node Details

Public graph metadata

Updated7/28/2026

Connections

30 linked nodes

Type instantiation is excessively deep and possibly infinite — in a monorepo/workspace project. Tension: on seemingly benign types like this. Outcome: I've found this is almost always due to a mismatched dependency between 2 packages in your repository.

Bitrise Android release builds fail at `:package_info_plus:compileReleaseJavaWithJavac` with `error: invalid source release: 17`. The same project builds locally in release/development.

Attempting to obtain CodeQL tools. CLI version: 2.16.3 — running this on GitHub. Tension: I have a CodeQL CLI bundle (v2.13.5) stored on an on-prem Artifactory repository. Outcome: it is trying to look for the exact same version here in the toolcache.

Execution failed for task ':app:mergeReleaseJavaResource'. — In the Run Gradlew step in expo. Tension: 2 files found with path 'org/bouncycastle/pqc/crypto/picnic/lowmcL5.bin.properties' from inputs. Outcome: Adding a packaging block may help.

Inconsistent JVM-target compatibility detected for tasks 'compileDebugJavaWithJavac' (1.8) and 'compileDebugKotlin' (17). Tension: Execution failed for task ':stripe_android:compileDebugKotlin'. Outcome: BUILD FAILED in 14s.

CDK keeps referencing the old bootstrap qualifier (hnb659fds) and fails with the following error — during deployment. Outcome: SSM parameter /cdk-bootstrap/hnb659fds/version not found.

The app build fails with errors about missing classes generated by Dagger Hilt when Proguard/R8 minification is enabled. Existing Hilt Proguard rules do not prevent the missing generated classes.

Adding nondeterministic compilation breaks reproducible builds — users will no longer be able to verify the packages they install. Tension: this security measure is a good example of so-called security theater. Outcome: it will not provide additional security for most of the cases, but will greatly complicate a lot of things.

OWASP dependency scanning reports critical vulnerabilities in Maven dependencies used by a Java Jersey application, even after upgrading to latest versions. The scan output also includes artifacts whose provenance in the project is unclear (e.g., kerb-server).

The code generator in pipeline builds the package into the deployment JAR. — building a code generation tool using JHipster. Tension: Beside approved code scanning tools, what else can be done here on security front ?

Gradle builds the project, but the annotation processor does not run

java.io.InvalidClassException: tls.other.app.package.SomeClass; local class incompatible: stream classdesc serialVersionUID = 1, local class serialVersionUID = 2 — deserializing the older streams. Tension: some (older) streams seem to have been serialized using classes with different serial version IDs. Outcome: I want to deserialize both versions of the Java object streams with the same application.

4 KB LOAD section alignment, but 16 KB is required warning for libtensorflowlite_jni.so — This only shows in x86_64. Tension: But I did not implement this on the build.gradle.

IntelliJ IDEA fails to compile/run Java programs using JDK 8 and reports: "java: invalid flag: --add-modules".

Could not find org.jetbrains.kotlin:kotlin-stdlib-jdk11:2.2.0. — Execution failed for task ':app:checkDebugAarMetadata'. Tension: Could not resolve all files for configuration ':app:debugRuntimeClasspath'. Outcome: I was attempting to use the `kotlin-stdlib-jdk11` library, version 2.0.20, which does not exist, my build was failing.

I'm upgrading a Vaadin 23.2 app to Vaadin 24.8. I have a compilation error on one of my components. Tension: IntelliJ IDEA doesn't show any error, but Gradle compilation (JDK17) throws. Outcome: when I remove the class the issue is gone.

Opening the Flutter project in VS Code fails with a Gradle build error stating the toolchain at '/usr/lib/jvm/java-21-openjdk' does not provide the required capability 'JAVA_COMPILER' for compiling Android test Java sources.

IntelliJ compiles and runs this code without error — in IntelliJ. Tension: According to the OCP Java 17 certification guide, "A single underscore _ is not allowed as an identifier.". Outcome: The code would not compile in Java 17.

I can't import some classes from the library — I'm trying to integrate my legacy app (in Java) with a library from a new partner (made with Kotlin). Tension: Android Studio it shows to me in both class finder or suggestion, but when I try to import even with * I get unreferenced class.

What are ways to systematically find all modules of the JDK that will be/have been used during the runtime of a Java application through reflection and the service provider model? — through reflection and the service provider model. Tension: I am, to my understanding, not looking for the jdeps command unless someone has a particular set of arguments that can resolve reflected runtime-only dynamic dependencies. Outcome: I already understand there is the `jlinks --suggest-providers` option, but this requires knowledge of each provider that is lacking.

Error running 'Main'. Tension: com.android.tools.idea.gradle.dcl.lang.DeclarativeParserDefinition PluginClassLoader. Outcome: com.android.tools.idea.gradle.dcl.lang.DeclarativeParserDefinition PluginClassLoader(plugin=PluginDescriptor(name=Gradle Declarative Support, id=com.android.tools.gradle.dcl, descriptorPath=plugin.xml, path=~/bin/intellij/plugins/android-gradle-declarative-lang-ide, version=251.23774.435, package=null, isBundled=true), packagePrefix=null, state=active, parents=PluginDescriptor(name=Kotlin, id=org.jetbrains.kotlin, descriptorPath=plugin.xml, path=~/bin/intellij/plugins/Kotlin, version=251.23774.435-IJ, package=org.jetbrains.kotlin, isBundled=true), PluginDescriptor(name=Gradle, id=com.intell.

skaffold scrambles the Log output of the build — skaffold v2.13.2 on Windows 10. Tension: This is not just an aesthetic problem. Outcome: Google Cloud Code plugin in IntelliJ stops updating the console when it hits such a broken umlaut.

Plugin net.fabricmc:fabric-loom:1.10-SNAPSHOT:20250225.144903-2 requires at least Gradle 8.12. — A problem occurred configuring root project 'projectname'. Tension: This build uses Gradle 8.11.1.

java.lang.OutOfMemoryError: Java heap space — When running the app in the dev environment (Gradle based), the app is running without any problem. If I build a jlink image of this app. Tension: I know about "Xmx" option, but this is not the solution. Outcome: the same line will throw.

Up until (at least) Java 17.

Could not find com.google.android.exoplayer:exoplayer-core:2.12.1 — When I attempt to make my Android project it fails. Tension: The make worked fine months ago when I had cached versions of those two packages. Outcome: I was able to make/build with no errors.

Mockito is currently self-attaching to enable the inline-mock-maker. — Following the link at the end of the first line. Tension: This will no longer work in future releases of the JDK. Outcome: Finally fixed, both in command line and IDE (IntelliJ IDEA).

Java fails with a Headless exception when running a full GUI app via RDP and the RDP session is disconnected — Starting with Java 17.0.12 and 21.0.4 Java fails with a Headless exception when running a full GUI app via RDP and the RDP session is disconnected. Tension: This would also seem to be breaking of the "contract" where minor point releases are not supposed to cause breaking changes. Outcome: the only known "fix" is to downgrade to 21.0.3 or 17.0.11 on Windows desktop systems.

Android Studio (Ladybug 24.2.1) is using JDK 21 by default, but the user needs JDK 17 to be used for both Android Studio and the Android toolchain. They want to change the IDE JDK from 21 to 17.

Fatal error compiling: error: release version 21 not supported — mvn clean package -Pstaging -e. Outcome: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.11.0:compile.

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata