Permalink
Browse files

various fixes

  • Loading branch information...
1 parent 25719cd commit 47f625a6603a293c67e893dec04334fcd2500d21 @harrah harrah committed Oct 10, 2012
View
2 0.12.1/docs/Community/Community-Plugins.html
@@ -104,7 +104,7 @@
</pre></div>
</div>
<p>Where <tt class="docutils literal"><span class="pre">&#64;my</span> <span class="pre">encrypted</span> <span class="pre">password&#64;</span></tt> is actually obtained using the following <a class="reference external" href="http://wiki.jfrog.org/confluence/display/RTF/Centrally+Secure+Passwords">instructions</a>.</p>
-<p><em>Note: Your code must abide by the</em> <a class="reference external" href="repository-rules">repository polices</a>.</p>
+<p><em>Note: Your code must abide by the</em> <a class="reference external" href="Repository-Rules">repository polices</a>.</p>
<p>To automatically deploy snapshot/release versions of your plugin use the following configuration:</p>
<div class="highlight-scala"><div class="highlight"><pre><span class="n">publishTo</span> <span class="o">&lt;&lt;=</span> <span class="o">(</span><span class="n">version</span><span class="o">)</span> <span class="o">{</span> <span class="n">version</span><span class="k">:</span> <span class="kt">String</span> <span class="o">=&gt;</span>
<span class="k">val</span> <span class="n">scalasbt</span> <span class="k">=</span> <span class="s">&quot;http://scalasbt.artifactoryonline.com/scalasbt/&quot;</span>
View
2 0.12.1/docs/Community/Repository-Rules.html
@@ -82,7 +82,7 @@
<p>The community repository has the following guideline for artifacts
published to it:</p>
<ol class="arabic simple">
-<li>All pubished artifacts are the authors own work or have an
+<li>All published artifacts are the authors own work or have an
appropriate license which grants distribution rights.</li>
<li>All published artifacts come from open source projects, that have an
open patch acceptance policy.</li>
View
10 0.12.1/docs/Detailed-Topics/Running-Project-Code.html
@@ -85,9 +85,8 @@
<p>The <tt class="docutils literal"><span class="pre">run</span></tt> and <tt class="docutils literal"><span class="pre">console</span></tt> 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]].</p>
+code can use this feature, and what types of code must use a <a class="reference internal" href="Forking.html"><em>forked jvm</em></a>.
+Skip to User Code if you just want to see when you should use a <a class="reference internal" href="Forking.html"><em>forked jvm</em></a>.</p>
<div class="section" id="problems">
<h2>Problems<a class="headerlink" href="#problems" title="Permalink to this headline">¶</a></h2>
<div class="section" id="system-exit">
@@ -162,12 +161,11 @@
<p>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]].</p>
+these requirements are not met, code must run in a <a class="reference internal" href="Forking.html"><em>forked jvm</em></a>.</p>
<p>The feature of allowing <tt class="docutils literal"><span class="pre">System.exit</span></tt> 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 <tt class="docutils literal"><span class="pre">System.exit</span></tt>.</p>
+<a class="reference internal" href="Forking.html"><em>forked jvm</em></a> when using multiple threads or <tt class="docutils literal"><span class="pre">System.exit</span></tt>.</p>
</div>
</div>
View
2 0.12.1/docs/_sources/Community/Community-Plugins.txt
@@ -32,7 +32,7 @@ You'll also need to add your credentials somewhere. For example, you might use
Where ``@my encrypted password@`` is actually obtained using the following `instructions <http://wiki.jfrog.org/confluence/display/RTF/Centrally+Secure+Passwords>`_.
-*Note: Your code must abide by the* `repository polices <repository-rules>`_.
+*Note: Your code must abide by the* `repository polices <Repository-Rules>`_.
To automatically deploy snapshot/release versions of your plugin use the following configuration:
View
2 0.12.1/docs/_sources/Community/Repository-Rules.txt
@@ -5,7 +5,7 @@
The community repository has the following guideline for artifacts
published to it:
-1. All pubished artifacts are the authors own work or have an
+1. All published artifacts are the authors own work or have an
appropriate license which grants distribution rights.
2. All published artifacts come from open source projects, that have an
View
10 0.12.1/docs/_sources/Detailed-Topics/Running-Project-Code.txt
@@ -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 <Forking>`.
+Skip to User Code if you just want to see when you should use a :doc:`forked jvm <Forking>`.
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 <Forking>`.
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 <Forking>` when using multiple threads or ``System.exit``.
View
2 0.12.1/docs/searchindex.js
1 addition, 1 deletion not shown because the diff is too large. Please use a local Git client to view these changes.
View
2 0.13.0-SNAPSHOT/docs/Community/Community-Plugins.html
@@ -104,7 +104,7 @@
</pre></div>
</div>
<p>Where <tt class="docutils literal"><span class="pre">&#64;my</span> <span class="pre">encrypted</span> <span class="pre">password&#64;</span></tt> is actually obtained using the following <a class="reference external" href="http://wiki.jfrog.org/confluence/display/RTF/Centrally+Secure+Passwords">instructions</a>.</p>
-<p><em>Note: Your code must abide by the</em> <a class="reference external" href="repository-rules">repository polices</a>.</p>
+<p><em>Note: Your code must abide by the</em> <a class="reference external" href="Repository-Rules">repository polices</a>.</p>
<p>To automatically deploy snapshot/release versions of your plugin use the following configuration:</p>
<div class="highlight-scala"><div class="highlight"><pre><span class="n">publishTo</span> <span class="o">&lt;&lt;=</span> <span class="o">(</span><span class="n">version</span><span class="o">)</span> <span class="o">{</span> <span class="n">version</span><span class="k">:</span> <span class="kt">String</span> <span class="o">=&gt;</span>
<span class="k">val</span> <span class="n">scalasbt</span> <span class="k">=</span> <span class="s">&quot;http://scalasbt.artifactoryonline.com/scalasbt/&quot;</span>
View
2 0.13.0-SNAPSHOT/docs/Community/Repository-Rules.html
@@ -82,7 +82,7 @@
<p>The community repository has the following guideline for artifacts
published to it:</p>
<ol class="arabic simple">
-<li>All pubished artifacts are the authors own work or have an
+<li>All published artifacts are the authors own work or have an
appropriate license which grants distribution rights.</li>
<li>All published artifacts come from open source projects, that have an
open patch acceptance policy.</li>
View
10 0.13.0-SNAPSHOT/docs/Detailed-Topics/Running-Project-Code.html
@@ -85,9 +85,8 @@
<p>The <tt class="docutils literal"><span class="pre">run</span></tt> and <tt class="docutils literal"><span class="pre">console</span></tt> 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]].</p>
+code can use this feature, and what types of code must use a <a class="reference internal" href="Forking.html"><em>forked jvm</em></a>.
+Skip to User Code if you just want to see when you should use a <a class="reference internal" href="Forking.html"><em>forked jvm</em></a>.</p>
<div class="section" id="problems">
<h2>Problems<a class="headerlink" href="#problems" title="Permalink to this headline">¶</a></h2>
<div class="section" id="system-exit">
@@ -162,12 +161,11 @@
<p>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]].</p>
+these requirements are not met, code must run in a <a class="reference internal" href="Forking.html"><em>forked jvm</em></a>.</p>
<p>The feature of allowing <tt class="docutils literal"><span class="pre">System.exit</span></tt> 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 <tt class="docutils literal"><span class="pre">System.exit</span></tt>.</p>
+<a class="reference internal" href="Forking.html"><em>forked jvm</em></a> when using multiple threads or <tt class="docutils literal"><span class="pre">System.exit</span></tt>.</p>
</div>
</div>
View
9 0.13.0-SNAPSHOT/docs/Getting-Started/Setup.html
@@ -132,16 +132,11 @@
<h3>Apt<a class="headerlink" href="#apt" title="Permalink to this headline">¶</a></h3>
<p>The sbt package is available from the <a class="reference external" href="http://apt.typesafe.com">Typesafe Debian Repository</a>. Please install <a class="reference external" href="http://apt.typesafe.com/repo-deb-build-0002.deb">this deb</a> to add the
typesafe debian repository to your list of approved sources. Then run:</p>
-<div class="highlight-console"><div class="highlight"><pre><span class="go">apt-get update</span>
-<span class="go">apt-get install sbt</span>
-</pre></div>
-</div>
-<p>to grab the latest typesafe stack release of sbt.
-If sbt cannot be found, dont forget to update your list of repositories.
-To do so, run:</p>
<div class="highlight-console"><div class="highlight"><pre><span class="gp">$</span> apt-get update
+<span class="gp">$</span> apt-get install sbt
</pre></div>
</div>
+<p>to grab the latest typesafe stack release of sbt.</p>
<div class="admonition note">
<p class="first admonition-title">Note</p>
<p class="last">Please make sure to report any issues you may find to the <a class="reference external" href="https://github.com/sbt/sbt-launcher-package/issues">launcher package project</a>.</p>
View
2 0.13.0-SNAPSHOT/docs/_sources/Community/Community-Plugins.txt
@@ -32,7 +32,7 @@ You'll also need to add your credentials somewhere. For example, you might use
Where ``@my encrypted password@`` is actually obtained using the following `instructions <http://wiki.jfrog.org/confluence/display/RTF/Centrally+Secure+Passwords>`_.
-*Note: Your code must abide by the* `repository polices <repository-rules>`_.
+*Note: Your code must abide by the* `repository polices <Repository-Rules>`_.
To automatically deploy snapshot/release versions of your plugin use the following configuration:
View
2 0.13.0-SNAPSHOT/docs/_sources/Community/Repository-Rules.txt
@@ -5,7 +5,7 @@
The community repository has the following guideline for artifacts
published to it:
-1. All pubished artifacts are the authors own work or have an
+1. All published artifacts are the authors own work or have an
appropriate license which grants distribution rights.
2. All published artifacts come from open source projects, that have an
View
10 0.13.0-SNAPSHOT/docs/_sources/Detailed-Topics/Running-Project-Code.txt
@@ -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 <Forking>`.
+Skip to User Code if you just want to see when you should use a :doc:`forked jvm <Forking>`.
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 <Forking>`.
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 <Forking>` when using multiple threads or ``System.exit``.
View
10 0.13.0-SNAPSHOT/docs/_sources/Getting-Started/Setup.txt
@@ -61,16 +61,10 @@ typesafe debian repository to your list of approved sources. Then run:
.. code-block:: console
- apt-get update
- apt-get install sbt
+ $ apt-get update
+ $ apt-get install sbt
to grab the latest typesafe stack release of sbt.
-If sbt cannot be found, dont forget to update your list of repositories.
-To do so, run:
-
-.. code-block:: console
-
- $ apt-get update
.. note::
View
2 0.13.0-SNAPSHOT/docs/searchindex.js
1 addition, 1 deletion not shown because the diff is too large. Please use a local Git client to view these changes.

0 comments on commit 47f625a

Please sign in to comment.