Exclude jakarta.validation-api #179
Merged
Conversation
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
jnc74743
merged commit 6f6b8d4
into
stfc:dependabot/maven/org.hibernate.validator-hibernate-validator-9.0.0.Final
1 check passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Version Incompatibility
You're using:
validation-api:2.0.1.Final (Jakarta Bean Validation 2.0)
hibernate-validator:9.0.0.Final
However, Hibernate Validator 9.0.0.Final is based on Jakarta Bean Validation 3.0, which uses the jakarta.validation package (not javax.validation).
This mismatch is likely causing the ConfigurationImpl class to fail during initialization.
One solution is: Upgrade to Jakarta Validation 3.0. But unfortunately that is not working. So I am excluding the other dependency which is coming with hibernate-validator.