sbt
Logs the forked standard output at the info level and the forked standard error at the error level.
Configures the forked standard output to be sent to output and the forked standard error
to be sent to the standard error of this process.
Represents a commad that can be forked.
Configures forking.
Configures forking.
The Java installation to use. If not defined, the Java home for the current process is used.
Configures the forked standard output and error streams. If not defined, StdoutOutput is used, which maps the forked output to the output of this process and the forked error to the error stream of the forking process.
The list of jars to put on the forked boot classpath. By default, this is empty.
The directory to use as the working directory for the forked process. By default, this is the working directory of the forking process.
The options to prepend to all user-specified arguments. By default, this is empty.
If true, the standard input of the forked process is connected to the standard input of this process. Otherwise, it is connected to an empty input stream. Connecting input streams can be problematic, especially on versions before Java 7.
The environment variables to provide to the forked process. By default, none are provided.
Logs the forked standard output at the info level and the forked standard error at the error level.
Configures where the standard output and error streams from a forked process go.
(Since version 0.13.0) Use ForkOptions
(Since version 0.13.0) Use ForkOptions
(Since version 0.13.0) Use ForkOptions
This module is an interface to starting the scala interpreter or runner.
Configures the forked standard output to go to standard output of this process and for the forked standard error to go to the standard error of this process.
Provides an approximation to isolated execution within a single JVM.
Provides an approximation to isolated execution within a single JVM. System.exit calls are trapped to prevent the JVM from terminating. This is useful for executing user code that may call System.exit, but actually exiting is undesirable.
Exit is simulated by disposing all top-level windows and interrupting user-started threads. Threads are not stopped and shutdown hooks are not called. It is therefore inappropriate to use this with code that requires shutdown hooks, creates threads that do not terminate, or if concurrent AWT applications are run. This category of code should only be called by forking a new JVM.
Logs the forked standard output at the
infolevel and the forked standard error at theerrorlevel. The output is buffered until the process completes, at which point the logger flushes it (to the screen, for example).