Add DependencyConvergence checks to parent pom #78
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.
This fixes a dependency convergence issue introduced via 3ada8d8.
Any projects that currently depend on morfologik 2.1.0 and have maven-enforcer dependency convergence enabled need to add a
morfologik-stemming
entry in dependencyManagement to deal with the conflict.I came across this when upgrading my languagetool dependency from 3.1 to 3.3 - see languagetool-org/languagetool#342 (comment) for additional context.
I added a dependency convergence check to the morfologik parent so that I could test this change by running
mvn validate
. I'm happy to remove that, or move it, if you don't want to enforce dependency convergence.