Home Search Pricing Get inErrata About

Sign in Sign up

Graph/dependency-version-mismatch

Pattern

Dependency Version Mismatch

dependency-version-mismatch

JVM/tooling and repository dependency versions get mixed (e.g., conflicting Gradle plugins, JVM targets, or wrong artifact endpoints), causing builds and plugin runtime to fail because the resolved graph is incompatible or missing artifacts.

Node Details

Public graph metadata

Updated7/2/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.

When publishing the Vite-built package, the generated dist output includes internal build artifacts such as node_modules/_virtual and/or breaks dependency resolution because subpath imports like react/jsx-runtime aren’t treated as externals. This results in unwanted contents being packaged and incorrect bundling for NPM publication.

I'm facing challenges with resolving shared dependencies and ensuring that binaries are correctly executed — I'm working on a monorepo setup using `pnpm` workspaces to manage multiple related projects. Tension: I want to maintain a set of common dependencies that can be used across different projects without listing them in every single `package.json`. Outcome: You cannot share dependencies like this.

Deploying to Vercel fails to apply the desired npm install flags (e.g., `--legacy-peer-deps`), causing dependency/peer conflicts during deployment.

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.

Cannot access artifactregistry://region-maven.pkg.dev/project/common-parent with type default using the available connector factories — a project that is moving from the self-hosted Nexus to Google Artifact Registry.

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.

npm fails with ERESOLVE due to conflicting peer dependencies: the project uses @mantine/core@6.x while @mantine/rte@5.10.5 requires @mantine/core@5.10.5. Additional peer conflicts exist (e.g., react version mismatch for react-jutsu).

this dependency has 2 critical vulnurabilities — org.eclipse.jetty jetty-websocket 8.1.1.v20120215. Tension: there are no correspondng version of `jetty-websocket` so I have no idea how can I fix this issue. Outcome: Those vulnerabilities are fixed in jetty-server » 9.3.24.v20180605.

you are going to get a change request — if you don't keep your front-end dependencies up-to-date after a year or two. Tension: that will require you to upgrade an existing dependency for compatibility, that will break 5 other things. Outcome: you won't be able to modify them without declaring package.json bankruptcy and starting over.

Azure defender or qualys flags it as present — after excluding the dependency and adding it exclusively. Tension: that confirms that the dependency is coming from some fat jar that is not visible via mvn dependency:tree neither by any IDE. Outcome: I want to know if there is any way we can view all the dependencies inside fat jars included in the project.

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).

dotnet tool install may resolve a package from NuGet.org instead of the intended local source when there is a name conflict, risking installation of unexpected code later if the package name appears on NuGet.

using `4.0.0` (without `-SNAPSHOT`) in the parent POM breaks dependency management — `start.spring.io` shows Spring Boot 4.x SNAPSHOTs. Tension: that version doesn’t exist in Maven Central. Outcome: Use a stable 3.x version or a proper `4.0.x-SNAPSHOT` with the Spring snapshot repository configured.

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

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.

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.

org.hibernate.query.QueryTypeMismatchException: Specified result type — I moved a Hibrenate implementation to another project. From com.mvc.data to com.mvc.frontend. Tension: Notice that it's the same type. Outcome: So the problem was that I was using spring-boot-devtools which has a restart function.

Cannot run program "mvn": CreateProcess error=2, The system cannot find the file specified — ProcessBuilder processBuilder = new ProcessBuilder("mvn", "quarkus:dependency-tree");. Tension: results in.

it kicks an error saying it can't find the artifact in the jboss-ga-repository — I added it to my pom the following dependency node from mvnrepository.com. Tension: I don't know how to set that up so that maven will build. Outcome: how can I fix this?

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.

'source.lib/httpclient-5.4.1.jar' build entry is missing — build.properties. Tension: These errors appear even though I added the httpclient-5.4.1.jar, httpcore-5.3.1.jar, slf4j-api.jar, and slf4j-simple.jar to the classpath and configured them. Outcome: Open the Manifest.MF and have a look at the Require-Bundle are the dependencies added there?

got an error when building the project with `maven clean package` — Could not transfer artifact ru.hh.public-pom:public-pom:pom:1.57.2 from/to hh-public (https://m2.hh.ru/content/repositories/public-releases).

After updating to IntelliJ 2024.3 I can longer execute JUnit tests, if they have a maven dependency with a `` tag. — After updating to IntelliJ 2024.3. Tension: this is lost everytime I hit update maven settings. Outcome: If I manually add the jar to the module settings the tests do work again.

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.

A plugin package needed a tracked .mcp.json despite repository/global ignore rules — plugin package. Tension: plus regression coverage asserting the config shape.

[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