Set JAVA_TOOL_OPTIONS environment variable instead of nonstandard JAVA_OPTS #1013
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.
The JAVA_TOOL_OPTIONS environment variable is passed to all Java processes.
This is useful for Java processes that somehow miss the flags passed in via command line. In particular, the JVM launched by initialization of the SBT thin client for some reason. only sees flags passed in by JAVA_TOOL_OPTIONS.
https://docs.oracle.com/javase/8/docs/technotes/guides/troubleshoot/envvars002.html
The adjusted Makefile passes in the Java flags through both command line, and through the JAVA_TOOL_OPTIONS environment variable. This should not cause problems, and should minimize risk.
Type of change: other enhancement
Impact: software change | API change
Release Notes
JAVA_OPTS Makefile variable has been changed to the standard JAVA_TOOL_OPTIONS variable.