Improve handling of -J arguments and jvm options
#769
Merged
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
This new flag can be passed in by the user whenever it doesn't want the interpretation of arguments starting with `-J`. This can happen when an application being run uses these arguments and forwards them to another application.
jvican
added
enhancement
cli
install
ergonomics
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.
Information in the commit messages. In a nutshell:
-Jfor test and run as normal app arguments.-Jarguments in thebloop serverinvocations and document them..jvmoptsfile in the bloop installation directory by default.Fixes #761
Fixes #565