From 5cdf4f9bbd36f6611ae6e1579c524b78f6c69cf4 Mon Sep 17 00:00:00 2001 From: Mark Harrah Date: Wed, 10 Oct 2012 08:10:25 -0400 Subject: [PATCH] fix Forking links --- src/sphinx/Detailed-Topics/Running-Project-Code.rst | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/src/sphinx/Detailed-Topics/Running-Project-Code.rst b/src/sphinx/Detailed-Topics/Running-Project-Code.rst index 9682df04d..d734252b6 100644 --- a/src/sphinx/Detailed-Topics/Running-Project-Code.rst +++ b/src/sphinx/Detailed-Topics/Running-Project-Code.rst @@ -5,9 +5,8 @@ Running Project Code The ``run`` and ``console`` actions provide a means for running user code in the same virtual machine as sbt. This page describes the problems with doing so, how sbt handles these problems, what types of -code can use this feature, and what types of code must use a [[forked -jvm\|Forking]]. Skip to User Code if you just want to see when you -should use a [[forked jvm\|Forking]]. +code can use this feature, and what types of code must use a :doc:`forked jvm `. +Skip to User Code if you just want to see when you should use a :doc:`forked jvm `. Problems ======== @@ -91,10 +90,9 @@ following situations must apply for user code to run in the same JVM: The requirements on threading and shutdown hooks are required because the JVM does not actually shut down. So, shutdown hooks cannot be run and threads are not terminated unless they stop when interrupted. If -these requirements are not met, code must run in a [[forked -jvm\|Forking]]. +these requirements are not met, code must run in a :doc:`forked jvm `. The feature of allowing ``System.exit`` and multiple threads to be used cannot completely emulate the situation of running in a separate JVM and is intended for development. Program execution should be checked in a -[[forked jvm\|Forking]] when using multiple threads or ``System.exit``. +:doc:`forked jvm ` when using multiple threads or ``System.exit``.