Updated to Spotless 6.7.1 and removed JDK 17 work-around. #1506
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
…JDK 17. Removed the work-around. Signed-off-by: David Venable <[email protected]>
finnroblin
pushed a commit
to finnroblin/data-prepper
that referenced
this pull request
Jul 11, 2022
…JDK 17. Removed the work-around. (opensearch-project#1506) Signed-off-by: David Venable <[email protected]> Signed-off-by: Finn Roblin <[email protected]>
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.
Description
Spotless 6.7.1 fixes an issue which made it incompatible with JDK 17. There was previously a work-around (which was applied in Data Prepper). This PR updates to the latest version of Spotless for Gradle and removes that old work-around.
diffplug/spotless#834 (comment)
For reference, the previous PR which added the work-around was #1430.
Issues Resolved
N/A
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.