Home Search Pricing Get inErrata About

Sign in Sign up

Graph/spring-boot-starter-mismatch

AntiPattern

Dependency Coordinate Drift

spring-boot-starter-mismatch

Mismatched Spring Boot/Maven coordinates or duplicate starters cause resolution and auto-configuration to diverge (e.g., missing versions, renamed artifacts, competing servlet mappings, classpath logging fights, or inconsistent Jackson ObjectMapper setup), breaking builds and runtime behavior.

Node Details

Public graph metadata

Updated8/6/2026

Connections

30 linked nodes

MATCHESSolution

Aligning the package versions usually fixes the issue — between 2 packages in your repository. Tension: a different version of the "zod" dependency. Outcome: either manually or by using a tool like ncu. You can also move common dependencies into your root package to enforce a common version.

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

webpack config. Tension: These two solutions can both fix this issue.

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

Instead of `io.sentry:sentry-spring` one has to use `io.sentry:sentry-spring-boot-starter` — in the dependencies. Tension: remove the following from the code. Outcome: I've just tested in my actual project, and logged errors are still sent to Sentry correctly.

MATCHESSolution

I found a solution: — spring-boot-maven-plugin. Tension: all the options above are ignored by `maven-surefire-plugin`. Outcome: org.apache.maven.plugins maven-surefire-plugin 60.

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

Spring Boot 4 introduced some major changes where, by default, it uses Jackson 3 instead of Jackson 2. Outcome: making it a more suitable candidate over the no-arg counterpart.

MATCHESSolution

`spring-boot-starter-aop` has been renamed to `spring-boot-starter-aspectj` — Replace that in your pom.xml. Outcome: it will run fine.

MATCHESSolution

Remove `spring-boot-starter-json` and keep `spring-boot-jackson2`, then configure Spring Boot to prefer Jackson 2 via `spring.http.converters.preferred-json-mapper: jackson2` and (if needed) supply an `ObjectMapper` bean built from `Jackson2ObjectMapperBuilder` with the custom module registered.

MATCHESSolution

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

MATCHESSolution

Spring Boot 4. Tension: Spring Boot 4 modularizes the codebase so various things are moved to different modules/dependencies.

MATCHESSolution

But you can try this workaround solution to see if this works: — spring-cloud-gcp-starter-secretmanager 7.3.2. Tension: enforce Spring Cloud GCP 7.x to use Spring Cloud Context 5.0.0. Outcome: which uses Spring Boot 4.0.0 starters.

MATCHESSolution

Replace spring-boot-starter-webmvc with spring-boot-starter-web to include an embedded server and make the H2 console accessible.

MATCHESSolution

If you see 2 versions of JPA — Spring Boot 3.3.x pulling in Spring Data JPA 3.3.x but another library in your project bringing an older Spring Data JPA. Tension: then remove the older version. Outcome: remove the older version.

MATCHESSolution

props.put(ConsumerConfig.AUTO_OFFSET_RESET_CONFIG, "latest"); — You'll have to explicitly set it via:. Tension: Spring Kafka changes that behavior unless you explicitly configure it. Outcome: check these out: Should I set Kafka auto.offset.reset to earliest or latest?

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

you need to add the corresponding repository to your `pom.xml` — To resolve the issue. Tension: it kicks an error saying it can't find the artifact in the jboss-ga-repository. Outcome: After adding this, try running `mvn clean install` again, and it should work.

MATCHESSolution

Use a JAR-in-JAR packaging approach (e.g., Spring Boot’s `spring-boot-maven-plugin` with `repackage`) or another plugin that preserves/merges `META-INF/services/` so Log4j Core can be loaded correctly from the packaged dependencies.

MATCHESSolution

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

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

Remove your `cacheManager` bean and replace it with an `CacheManagerCustomizer` instead. — Make sure that you have both `spring-boot-starter-actuator` and approriate Google Caffeine and Micrometer dependencies. Tension: and that will be all you need to have metrics. Outcome: Spring Boot already configures those metrics.

MATCHESSolution

If you meant to use the Spring Boot support — you can remove the `io.opentelemetry` dependencies, use the actuator starter. Tension: this behavior difference is called out in the Spring Boot docs. Outcome: refer to the Spring Boot docs.

MATCHESSolution

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

MATCHESSolution

Align all Spring Boot/Spring Security/Authorization Server dependency versions (e.g., upgrade the Spring Boot plugin to the same version and remove hardcoded version overrides), and prefer using org.springframework.boot:spring-boot-starter-oauth2-authorization-server so transitive dependencies match.

MATCHESSolution

After remove this row it run perfectly — previously I did specify spring framework as 6.1.14. Tension: conflict between dependency that include in 3.4.x. Outcome: it run perfectly.

MATCHESSolution

Try switching the relationship so that the `Company` is the "owner" — JPA JoinColumn vs mappedBy. Tension: see if that fixes it. Outcome: see if that fixes it.

MATCHESSolution

Update docker-compose to properly configure the Couchbase service and run startup scripts (e.g., setup-couchbase.sh) after the server starts to create the required bucket, scopes, collections, and indexes, ensuring the environment variables align with Spring Boot’s configuration.

MATCHESSolution

You will need to add `maven-processor-plugin` to `the pom.xml` — To ensure the generated classes are created before compilation. Tension: This plugin runs annotation processors like those required for Lombok and Hibernate JPA model generation during the generate-sources phase. Outcome: To ensure the generated classes are created before compilation.

MATCHESSolution

Using the starter — `transaction-jdbc`, `transaction-jms` and `transaction-jta` are automatically imported with `jakarta` as classifier. Tension: Check if you are importing the "no-jakarta" modules. Outcome: try to use the starter, or specify the classifier in pom.xml.

[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

Dependency Coordinate Drift - inErrata Knowledge Graph | Inerrata