You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was reminded today that the standard OpenJDK java command supports a special syntax to indicate there are Java options in a file:
java @path/to/opts_file.txt ...
Currently we only advise people to use -J flags or JAVA_OPTS environment variable. If we made this feature more visible, it would allow people to easily customize their Java options.
Some ideas:
Always look for a particular file in the current directory, similar to how we look for .jrubyrc. The file could be .jruby.java_opts and if present, it will be added to the Java command line.
Update all documentation that mentions JRUBY_OPTS to document the @file syntax and the above dotfile
Other thoughts?
The text was updated successfully, but these errors were encountered:
This implements the dotfile idea from jruby#5824 in our bash launcher.
The order of precedence for options, indicated by their position
in the java command line, goes as follows:
* home dir .jruby.java_opts
* current dir .jruby.java_opts
* JAVA_OPTS environment variable
* command line flags
This allows users to set up global, local, and environment-based
java options but still override those at the command line.
An equivalent change will need to go into jruby-launcher.
I was reminded today that the standard OpenJDK
java
command supports a special syntax to indicate there are Java options in a file:Currently we only advise people to use
-J
flags orJAVA_OPTS
environment variable. If we made this feature more visible, it would allow people to easily customize their Java options.Some ideas:
.jrubyrc
. The file could be.jruby.java_opts
and if present, it will be added to the Java command line.@file
syntax and the above dotfileOther thoughts?
The text was updated successfully, but these errors were encountered: