http://openjdk.java.net/jtreg/vmoptions.html
is still written as if shell tests were common, but y'all have been replacing them with ProcessTools and related libraries.
I see:
"""
Running a new Java virtual machine from within Java code
This is not common. You should only consider doing this when you need to change the characteristics (JVM options) of the JVM that is currently in use. If you do need to start a child JVM, you may need to use the sun.boot.class.path property, so that the child JVM can inherit the bootclasspath you are using, including any additions to the bootclasspath specified by the user with the -Xbootclasspath/p: or -Xbootclasspath/a: options.
"""
BUT:
- This is not common ... NOT!
- sun.boot.class.path has gone away
-Xbootclasspath/p: has gone away
is still written as if shell tests were common, but y'all have been replacing them with ProcessTools and related libraries.
I see:
"""
Running a new Java virtual machine from within Java code
This is not common. You should only consider doing this when you need to change the characteristics (JVM options) of the JVM that is currently in use. If you do need to start a child JVM, you may need to use the sun.boot.class.path property, so that the child JVM can inherit the bootclasspath you are using, including any additions to the bootclasspath specified by the user with the -Xbootclasspath/p: or -Xbootclasspath/a: options.
"""
BUT:
- This is not common ... NOT!
- sun.boot.class.path has gone away
-Xbootclasspath/p: has gone away