Fix UpdateSdkManTest to use current SDKMAN Java versions#991
Merged
Conversation
Update test fixtures to use Java versions available in the current sdkman-java.csv after the automated update removed 17.0.17-tem and 11.0.29-amzn.
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
1 participant
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.
Summary
Fixes CI failures caused by the automated SDKMAN Java candidates update (commit 7c8b223) which removed Java versions that two tests were expecting.
The tests
updateVersionExact()andupdateDistributionOnly()were failing because they referenced17.0.17-temand11.0.29-amznrespectively, which no longer exist in the CSV. Updated test fixtures to use17.0.18-temand11.0.30-amznwhich are available in the current CSV.Test plan
./gradlew test --tests "org.openrewrite.java.migrate.UpdateSdkManTest"- all tests pass