Native launcher changes
- Don't let native-image interpret the
-Doptions passed to the native launcher, so that we can interpret those ourselves as normal options, like the JAR-based launcher does.
- Have the
launchcommand accept Java options via
-J, that are passed to
javawhen launching a JVM application from the native launcher, like
cs launch -J -Xmx3g ammonite.
In progress changes
The changes below are meant to be described more extensively and documented in later releases, while being more tested in the mean time. These are mentioned here for the sake of comprehensiveness.
- Major in-progress overhaul of the internals of the
- Early support for pre-built native launchers for the
javafetches and starts a custom JVM (like
cs java --jvm email@example.com+ -version), and
java-homefetches and prints the home directory of a custom JVM (like
cs java-home --jvm 11).
- Add support for generating GraalVM native images to the
bootstrapcommand. Use like
cs bootstrap --native-image coursier -o custom-cs.
- Add experimental
setupcommand, installing a JVM if none is found locally, updating
PATHif needed, and installing a few applications via the
sbt, in particular).
- Add a
--scala-version, in most CLI commands. Use like
cs launch ammonite --scala 2.13.