Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

various fixes

  • Loading branch information...
commit 47f625a6603a293c67e893dec04334fcd2500d21 1 parent 25719cd
Mark Harrah harrah authored
2  0.12.1/docs/Community/Community-Plugins.html
@@ -104,7 +104,7 @@
104 104 </pre></div>
105 105 </div>
106 106 <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>
107   -<p><em>Note: Your code must abide by the</em> <a class="reference external" href="repository-rules">repository polices</a>.</p>
  107 +<p><em>Note: Your code must abide by the</em> <a class="reference external" href="Repository-Rules">repository polices</a>.</p>
108 108 <p>To automatically deploy snapshot/release versions of your plugin use the following configuration:</p>
109 109 <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>
110 110 <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>
2  0.12.1/docs/Community/Repository-Rules.html
@@ -82,7 +82,7 @@
82 82 <p>The community repository has the following guideline for artifacts
83 83 published to it:</p>
84 84 <ol class="arabic simple">
85   -<li>All pubished artifacts are the authors own work or have an
  85 +<li>All published artifacts are the authors own work or have an
86 86 appropriate license which grants distribution rights.</li>
87 87 <li>All published artifacts come from open source projects, that have an
88 88 open patch acceptance policy.</li>
10 0.12.1/docs/Detailed-Topics/Running-Project-Code.html
@@ -85,9 +85,8 @@
85 85 <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
86 86 code in the same virtual machine as sbt. This page describes the
87 87 problems with doing so, how sbt handles these problems, what types of
88   -code can use this feature, and what types of code must use a [[forked
89   -jvm|Forking]]. Skip to User Code if you just want to see when you
90   -should use a [[forked jvm|Forking]].</p>
  88 +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>.
  89 +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>
91 90 <div class="section" id="problems">
92 91 <h2>Problems<a class="headerlink" href="#problems" title="Permalink to this headline">¶</a></h2>
93 92 <div class="section" id="system-exit">
@@ -162,12 +161,11 @@
162 161 <p>The requirements on threading and shutdown hooks are required because
163 162 the JVM does not actually shut down. So, shutdown hooks cannot be run
164 163 and threads are not terminated unless they stop when interrupted. If
165   -these requirements are not met, code must run in a [[forked
166   -jvm|Forking]].</p>
  164 +these requirements are not met, code must run in a <a class="reference internal" href="Forking.html"><em>forked jvm</em></a>.</p>
167 165 <p>The feature of allowing <tt class="docutils literal"><span class="pre">System.exit</span></tt> and multiple threads to be used
168 166 cannot completely emulate the situation of running in a separate JVM and
169 167 is intended for development. Program execution should be checked in a
170   -[[forked jvm|Forking]] when using multiple threads or <tt class="docutils literal"><span class="pre">System.exit</span></tt>.</p>
  168 +<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>
171 169 </div>
172 170 </div>
173 171
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
32 32
33 33 Where ``@my encrypted password@`` is actually obtained using the following `instructions <http://wiki.jfrog.org/confluence/display/RTF/Centrally+Secure+Passwords>`_.
34 34
35   -*Note: Your code must abide by the* `repository polices <repository-rules>`_.
  35 +*Note: Your code must abide by the* `repository polices <Repository-Rules>`_.
36 36
37 37 To automatically deploy snapshot/release versions of your plugin use the following configuration:
38 38
2  0.12.1/docs/_sources/Community/Repository-Rules.txt
@@ -5,7 +5,7 @@
5 5 The community repository has the following guideline for artifacts
6 6 published to it:
7 7
8   -1. All pubished artifacts are the authors own work or have an
  8 +1. All published artifacts are the authors own work or have an
9 9 appropriate license which grants distribution rights.
10 10
11 11 2. All published artifacts come from open source projects, that have an
10 0.12.1/docs/_sources/Detailed-Topics/Running-Project-Code.txt
@@ -5,9 +5,8 @@ Running Project Code
5 5 The ``run`` and ``console`` actions provide a means for running user
6 6 code in the same virtual machine as sbt. This page describes the
7 7 problems with doing so, how sbt handles these problems, what types of
8   -code can use this feature, and what types of code must use a [[forked
9   -jvm\|Forking]]. Skip to User Code if you just want to see when you
10   -should use a [[forked jvm\|Forking]].
  8 +code can use this feature, and what types of code must use a :doc:`forked jvm <Forking>`.
  9 +Skip to User Code if you just want to see when you should use a :doc:`forked jvm <Forking>`.
11 10
12 11 Problems
13 12 ========
@@ -91,10 +90,9 @@ following situations must apply for user code to run in the same JVM:
91 90 The requirements on threading and shutdown hooks are required because
92 91 the JVM does not actually shut down. So, shutdown hooks cannot be run
93 92 and threads are not terminated unless they stop when interrupted. If
94   -these requirements are not met, code must run in a [[forked
95   -jvm\|Forking]].
  93 +these requirements are not met, code must run in a :doc:`forked jvm <Forking>`.
96 94
97 95 The feature of allowing ``System.exit`` and multiple threads to be used
98 96 cannot completely emulate the situation of running in a separate JVM and
99 97 is intended for development. Program execution should be checked in a
100   -[[forked jvm\|Forking]] when using multiple threads or ``System.exit``.
  98 +:doc:`forked jvm <Forking>` when using multiple threads or ``System.exit``.
2  0.12.1/docs/searchindex.js
1 addition, 1 deletion not shown
2  0.13.0-SNAPSHOT/docs/Community/Community-Plugins.html
@@ -104,7 +104,7 @@
104 104 </pre></div>
105 105 </div>
106 106 <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>
107   -<p><em>Note: Your code must abide by the</em> <a class="reference external" href="repository-rules">repository polices</a>.</p>
  107 +<p><em>Note: Your code must abide by the</em> <a class="reference external" href="Repository-Rules">repository polices</a>.</p>
108 108 <p>To automatically deploy snapshot/release versions of your plugin use the following configuration:</p>
109 109 <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>
110 110 <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>
2  0.13.0-SNAPSHOT/docs/Community/Repository-Rules.html
@@ -82,7 +82,7 @@
82 82 <p>The community repository has the following guideline for artifacts
83 83 published to it:</p>
84 84 <ol class="arabic simple">
85   -<li>All pubished artifacts are the authors own work or have an
  85 +<li>All published artifacts are the authors own work or have an
86 86 appropriate license which grants distribution rights.</li>
87 87 <li>All published artifacts come from open source projects, that have an
88 88 open patch acceptance policy.</li>
10 0.13.0-SNAPSHOT/docs/Detailed-Topics/Running-Project-Code.html
@@ -85,9 +85,8 @@
85 85 <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
86 86 code in the same virtual machine as sbt. This page describes the
87 87 problems with doing so, how sbt handles these problems, what types of
88   -code can use this feature, and what types of code must use a [[forked
89   -jvm|Forking]]. Skip to User Code if you just want to see when you
90   -should use a [[forked jvm|Forking]].</p>
  88 +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>.
  89 +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>
91 90 <div class="section" id="problems">
92 91 <h2>Problems<a class="headerlink" href="#problems" title="Permalink to this headline">¶</a></h2>
93 92 <div class="section" id="system-exit">
@@ -162,12 +161,11 @@
162 161 <p>The requirements on threading and shutdown hooks are required because
163 162 the JVM does not actually shut down. So, shutdown hooks cannot be run
164 163 and threads are not terminated unless they stop when interrupted. If
165   -these requirements are not met, code must run in a [[forked
166   -jvm|Forking]].</p>
  164 +these requirements are not met, code must run in a <a class="reference internal" href="Forking.html"><em>forked jvm</em></a>.</p>
167 165 <p>The feature of allowing <tt class="docutils literal"><span class="pre">System.exit</span></tt> and multiple threads to be used
168 166 cannot completely emulate the situation of running in a separate JVM and
169 167 is intended for development. Program execution should be checked in a
170   -[[forked jvm|Forking]] when using multiple threads or <tt class="docutils literal"><span class="pre">System.exit</span></tt>.</p>
  168 +<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>
171 169 </div>
172 170 </div>
173 171
9 0.13.0-SNAPSHOT/docs/Getting-Started/Setup.html
@@ -132,16 +132,11 @@
132 132 <h3>Apt<a class="headerlink" href="#apt" title="Permalink to this headline">¶</a></h3>
133 133 <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
134 134 typesafe debian repository to your list of approved sources. Then run:</p>
135   -<div class="highlight-console"><div class="highlight"><pre><span class="go">apt-get update</span>
136   -<span class="go">apt-get install sbt</span>
137   -</pre></div>
138   -</div>
139   -<p>to grab the latest typesafe stack release of sbt.
140   -If sbt cannot be found, dont forget to update your list of repositories.
141   -To do so, run:</p>
142 135 <div class="highlight-console"><div class="highlight"><pre><span class="gp">$</span> apt-get update
  136 +<span class="gp">$</span> apt-get install sbt
143 137 </pre></div>
144 138 </div>
  139 +<p>to grab the latest typesafe stack release of sbt.</p>
145 140 <div class="admonition note">
146 141 <p class="first admonition-title">Note</p>
147 142 <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>
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
32 32
33 33 Where ``@my encrypted password@`` is actually obtained using the following `instructions <http://wiki.jfrog.org/confluence/display/RTF/Centrally+Secure+Passwords>`_.
34 34
35   -*Note: Your code must abide by the* `repository polices <repository-rules>`_.
  35 +*Note: Your code must abide by the* `repository polices <Repository-Rules>`_.
36 36
37 37 To automatically deploy snapshot/release versions of your plugin use the following configuration:
38 38
2  0.13.0-SNAPSHOT/docs/_sources/Community/Repository-Rules.txt
@@ -5,7 +5,7 @@
5 5 The community repository has the following guideline for artifacts
6 6 published to it:
7 7
8   -1. All pubished artifacts are the authors own work or have an
  8 +1. All published artifacts are the authors own work or have an
9 9 appropriate license which grants distribution rights.
10 10
11 11 2. All published artifacts come from open source projects, that have an
10 0.13.0-SNAPSHOT/docs/_sources/Detailed-Topics/Running-Project-Code.txt
@@ -5,9 +5,8 @@ Running Project Code
5 5 The ``run`` and ``console`` actions provide a means for running user
6 6 code in the same virtual machine as sbt. This page describes the
7 7 problems with doing so, how sbt handles these problems, what types of
8   -code can use this feature, and what types of code must use a [[forked
9   -jvm\|Forking]]. Skip to User Code if you just want to see when you
10   -should use a [[forked jvm\|Forking]].
  8 +code can use this feature, and what types of code must use a :doc:`forked jvm <Forking>`.
  9 +Skip to User Code if you just want to see when you should use a :doc:`forked jvm <Forking>`.
11 10
12 11 Problems
13 12 ========
@@ -91,10 +90,9 @@ following situations must apply for user code to run in the same JVM:
91 90 The requirements on threading and shutdown hooks are required because
92 91 the JVM does not actually shut down. So, shutdown hooks cannot be run
93 92 and threads are not terminated unless they stop when interrupted. If
94   -these requirements are not met, code must run in a [[forked
95   -jvm\|Forking]].
  93 +these requirements are not met, code must run in a :doc:`forked jvm <Forking>`.
96 94
97 95 The feature of allowing ``System.exit`` and multiple threads to be used
98 96 cannot completely emulate the situation of running in a separate JVM and
99 97 is intended for development. Program execution should be checked in a
100   -[[forked jvm\|Forking]] when using multiple threads or ``System.exit``.
  98 +:doc:`forked jvm <Forking>` when using multiple threads or ``System.exit``.
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:
61 61
62 62 .. code-block:: console
63 63
64   - apt-get update
65   - apt-get install sbt
  64 + $ apt-get update
  65 + $ apt-get install sbt
66 66
67 67 to grab the latest typesafe stack release of sbt.
68   -If sbt cannot be found, dont forget to update your list of repositories.
69   -To do so, run:
70   -
71   -.. code-block:: console
72   -
73   - $ apt-get update
74 68
75 69 .. note::
76 70
2  0.13.0-SNAPSHOT/docs/searchindex.js
1 addition, 1 deletion not shown

0 comments on commit 47f625a

Please sign in to comment.
Something went wrong with that request. Please try again.