[jdt] Remove the overrides for jdt as version ranges no longer being … #920
Conversation
This file contains 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
…used since 2022 Since https://repo1.maven.org/maven2/org/eclipse/jdt/org.eclipse.jdt.junit.core/3.11.500/org.eclipse.jdt.junit.core-3.11.500.pom, version ranges are no longer used. Moving to remove this logic as no longer necessary.
|
This is a nice simplification. Glad upstream fixed their POM creation. |
|
Yes much better for us to not support that any longer. |
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.
…used since 2022
Since https://repo1.maven.org/maven2/org/eclipse/jdt/org.eclipse.jdt.junit.core/3.11.500/org.eclipse.jdt.junit.core-3.11.500.pom, version ranges are no longer used. Moving to remove this logic as no longer necessary.