Add explicit jakarta.annotation-api dependency to fix version conflict#7972
Merged
JinwooHwang merged 2 commits intoapache:developfrom Dec 13, 2025
Merged
Conversation
jakarta.resource-api:2.1.0 declares a transitive dependency on jakarta.annotation-api:2.1.0, but Spring Boot 3.3.4 (used by geode-gfsh) requires jakarta.annotation-api:2.1.1. This causes Maven enforcer to fail with a version conflict error. By explicitly declaring jakarta.annotation-api as an api dependency in geode-core, the published POM will include it with version 2.1.1 (from DependencyConstraints), which takes precedence over the transitive 2.1.0 dependency from jakarta.resource-api. Reported-by: Leon Finker
Contributor
Author
|
Hi @sboorlagadda and @leonfin . I would appreciate your review. Thank you. |
sboorlagadda
approved these changes
Dec 12, 2025
Contributor
Author
|
Thank you so much for your review and approval, @sboorlagadda !! |
JinwooHwang
added a commit
that referenced
this pull request
Dec 13, 2025
#7972) * Add explicit jakarta.annotation-api dependency to fix version conflict jakarta.resource-api:2.1.0 declares a transitive dependency on jakarta.annotation-api:2.1.0, but Spring Boot 3.3.4 (used by geode-gfsh) requires jakarta.annotation-api:2.1.1. This causes Maven enforcer to fail with a version conflict error. By explicitly declaring jakarta.annotation-api as an api dependency in geode-core, the published POM will include it with version 2.1.1 (from DependencyConstraints), which takes precedence over the transitive 2.1.0 dependency from jakarta.resource-api. Reported-by: Leon Finker * Update expected POM to include jakarta.annotation-api dependency
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
jakarta.resource-api:2.1.0 declares a transitive dependency on jakarta.annotation-api:2.1.0, but Spring Boot 3.3.4 (used by geode-gfsh) requires jakarta.annotation-api:2.1.1. This causes Maven enforcer to fail with a version conflict error.
By explicitly declaring jakarta.annotation-api as an api dependency in geode-core, the published POM will include it with version 2.1.1 (from DependencyConstraints), which takes precedence over the transitive 2.1.0 dependency from jakarta.resource-api.
Reported-by: Leon Finker
For all changes, please confirm:
develop)?gradlew buildrun cleanly?