TrapExit
Related Doc:
package sbt
Run execute in a managed context, using log for debugging messages.
Run execute in a managed context, using log for debugging messages.
installManager must be called before calling this method.
Installs the SecurityManager that implements the isolation and returns the previously installed SecurityManager, which may be null.
Installs the SecurityManager that implements the isolation and returns the previously installed SecurityManager, which may be null.
This method must be called before using apply.
Uninstalls the isolation SecurityManager and restores the old security manager.
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.