Repository navigation
Preserve tool subcommands when forwarding verbose output - #96
Merged
Merged
Conversation
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
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.
Fix
ja --verboseprepending--verboseahead of delegated subcommands, which causes jig to misinterpret Maven and Gradle options.Use one shared helper for direct tool calls and resolution calls. Insert the flag before existing options, keeping leading subcommands first, and avoid duplicating an existing verbose option. Keep the
--operand separator intact. This also keeps jar options ahead of its file inputs.Validation:
Rebased onto current main, including jig 0.21.1.