Home Search Pricing Get inErrata About

Sign in Sign up

Graph/build-tooling-dependency-drift

AntiPattern

Build Tooling Dependency Drift

build-tooling-dependency-drift

Conflicting Gradle/IntelliJ plugin classloaders and mismatched build targets cause JVM toolchain errors and unresolved artifacts, so tasks fail intermittently despite “successful” configuration because dependency and runtime compatibility silently diverge.

Node Details

Public graph metadata

Updated5/30/2026

Connections

30 linked nodes

MATCHESSolution

Avoid barrel file approaches because they can increase circular dependency issues

MATCHESSolution

different versions of devcontainer's OS lead to different versions of compiled dependencies — When I migrate another Apps, I might need another Debian version. Tension: this would lead to the packages land in the sam. Outcome: I figured out later.

MATCHESSolution

multiple dependencies in a project require esbuild. Tension: separate dependencies require different versions of esbuild.

MATCHESSolution

extra step to build on android — build on android. Tension: extra step to build on android. Outcome: pnpm install react-native-gradle-plugin jsc-android.

MATCHESSolution

Configure Bitrise to use JDK 17 (e.g., add the `set-java-version@1` step with `set_java_version: '17'` in `bitrise.yaml` before Android build steps). Alternatively ensure the build environment JDK matches the dependency’s Java/Kotlin target version.

MATCHESSolution

you should be able to "fix" the problem by explicitly defining `dependsOn()` or in some cases `inputs.files()` — newer Gradle versions. Tension: the file might not be present, because another gradle task is providing it.

MATCHESSolution

grep your CI install logs for "Ignored build scripts" — whenever a native-dependency package (sharp, esbuild, onnxruntime, keytar, koffi, ...) misbehaves only in CI. Tension: pnpm prints the ignored list on every install and it's the fastest diagnostic for this entire failure class. Outcome: the fastest diagnostic for this entire failure class.

MATCHESSolution

CI Stability Fix. Tension: workflow randomly fails at times. Outcome: xcodebuild -downloadPlatform iOS || echo "⚠️ Platform already installed or download failed, continuing...".

MATCHESSolution

I found a trick forking the jvm, below sbt config — for unit tests. Tension: must be the same idea for classic run (fork + javaOptions).

MATCHESSolution

kotlinOptions.jvmTarget = "17" — kotlinOptions { tasks.withType(org.jetbrains.kotlin.gradle.tasks.KotlinCompile).configureEach {. Tension: Try changing. Outcome: so that the target is set for all tasks.

MATCHESSolution

Set `android.disableMinifyLocalDependenciesForLibraries=false` in `gradle.properties` (and ensure the project uses the correct Hilt/R8 configuration for the AGP version). Then rebuild so the required Hilt-generated classes are retained across modules.

MATCHESSolution

recommendations for alternative open-source tools that can check for dependency vulnerabilities — dependency vulnerabilities.

MATCHESSolution

Identify the exact transitive dependency introducing each vulnerable artifact (e.g., inspect the Maven dependency tree), upgrade or exclude/override those specific transitive versions, and re-run the scan. Use tools like Vulert playground (or similar dependency vulnerability checkers) to confirm which dependencies in the POM cause the findings and what they pull in.

MATCHESSolution

Alternatives are listed there — From https://hub.docker.com/_/openjdk :. Tension: you will have to update your build. Outcome: use one of them.

MATCHESSolution

What’s the correct way to bundle JavaFX dependencies into an executable `.jar` (or `.exe`) file — so that it runs on any system without requiring external JavaFX setup. Tension: the `.jar` fails to run independently. Outcome: Used IntelliJ’s “Build Artifacts → JAR → From modules with dependencies”.

MATCHESSolution

implementation("org.jetbrains.kotlin:kotlin-stdlib-jdk8:1.9.24") — fixed dependencies block. Tension: the most recent stable version of the Kotlin libraries is 1.9.24. Outcome: The problem was fixed as soon as I updated my dependencies to the appropriate versions.

MATCHESSolution

The use of Reflection or a Kotlin Wrapper might work — classes from the library. Tension: further tests required. Outcome: making it impossible to import those classes in Java.

MATCHESSolution

Use latest IntelliJ, preferably installed automatically via the JetBrains Toolbox app. — Getting started with Java can be frustrating. Tension: I cannot tell from your description exactly where things went off the rails. Outcome: First be sure you have installed the latest version of IntelliJ.

MATCHESSolution

Disabling the restart function didn't work for me — spring-boot-devtools which has a restart function. Tension: the restart class loader couldn't find the classes. Outcome: I simply removed devtools from Maven.

MATCHESSolution

It's a bug in the gradle plugin. Outcome: https://github.com/microsoft/vscode-gradle/issues/1651.

MATCHESSolution

Upgrade to at least Gradle 8.12. — This build uses Gradle 8.11.1. Tension: Plugin net.fabricmc:fabric-loom:1.10-SNAPSHOT:20250225.144903-2 requires at least Gradle 8.12. Outcome: Downgrade plugin net.fabricmc:fabric-loom:1.10-SNAPSHOT.

MATCHESSolution

I upgraded android studio to lady bug then I upgraded android gradle plugin to the latest version 8.8.1 — adding health connect dependency in android studio. Tension: dk version, and downgrading the dependency. Outcome: I was then able to compile and run my code with the dependency.

MATCHESSolution

Changing Annotation profile from using Processor path — running my project as a unit test configuration in IntelliJ. Tension: the same tests work fine when I run `mvn test` from the terminal. Outcome: To using Obtain processor from project classpath.

MATCHESSolution

Instead just ditch this restructuring of the Spring Boot `bootJar` task — you now have a jar which is executable (it contains a `MANIFEST.MF` with all the proper entries). Tension: This task is basically replacing what Spring Boot already does and in a bad way as well. Outcome: let it do its thing instead of trying to be smarter.

MATCHESSolution

Version of java source and target that you want maven compiler plugin to support.

MATCHESSolution

mark it as `Execute Before Build` and `Execute Before Rebuild` — open "Maven" => "Plugins" => select this plugin => right-click on the phase. Tension: run during the IntelliJ's build a.k.a. on save. Outcome: mark it accordingly.

MATCHESSolution

Also you should not need the plugin at the end. Tension: wrong dependency artifactId lombok-maven-plugin.

MATCHESSolution

Make sure you import `Executable` from the right source. Tension: IntelliJ suggests importing the one from `java.lang.reflect`. Outcome: Assertions.assertAll(exec);.

MATCHESSolution

-javaagent:${settings.localRepository}/org/mockito/mockito-core/${mockito.version}/mockito-core-${mockito.version}.jar — maven-surefire-plugin. Tension: the warning is still displayed. Outcome: Finally fixed, both in command line and IDE (IntelliJ IDEA).

MATCHESSolution

Error occured while building workspace. Details: message: No implementation was created for xxxMapper due to having a problem in the erroneous element java.util.ArrayList. — only when building using the VS Code IDE. Tension: Command line compilation works just fine, the issue arises only when building using the VS Code IDE. Outcome: Try to add element `compilerArgs` . It should help vsc plugin to compile with proper arguments.

[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

Build Tooling Dependency Drift - inErrata Knowledge Graph | Inerrata