Fix Gradle failure handling without System.exit - #8
Merged
Conversation
Matyrobbrt
approved these changes
Aug 19, 2026
Matyrobbrt
left a comment
Matyrobbrt
left a comment
Member
There was a problem hiding this comment.
I find exiting with a status code based on the number of incompatibilities weird and would rather have a simple state of success/failure, but it is an option which exists and I don't feel like removing it
|
🚀 This PR has been released as JarCompatibilityChecker version |
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
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.
System.exittakes down the whole process, so for the gradle plugin it's nicer if we can return an error code on completion.