Author: buildbot
Date: Tue Feb 21 09:11:05 2017
New Revision: 1007088
Log:
Staging update by buildbot for sling
Modified:
websites/staging/sling/trunk/content/ (props changed)
websites/staging/sling/trunk/content/documentation/bundles/org-apache-sling-junit-bundles.html
Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Feb 21 09:11:05 2017
@@ -1 +1 @@
-1783796
+1783850
Modified:
websites/staging/sling/trunk/content/documentation/bundles/org-apache-sling-junit-bundles.html
==============================================================================
---
websites/staging/sling/trunk/content/documentation/bundles/org-apache-sling-junit-bundles.html
(original)
+++
websites/staging/sling/trunk/content/documentation/bundles/org-apache-sling-junit-bundles.html
Tue Feb 21 09:11:05 2017
@@ -280,7 +280,7 @@ classes which are used only on the clien
</tr>
</tbody>
</table>
-<p>The provisioning of an appropriate instance can be done with the <a
href="/documentation/development/slingstart.html">slingstart-maven-plugin</a>.
An example for that is given at <a
href="https://svn.apache.org/viewvc/sling/trunk/testing/samples/module-with-it";><code>testing/samples/module-with-it</code></a>.
Unfortunately the <code>slingstart-maven-plugin</code> currently only allows
to bootstrap a Sling Server from a model.txt for packaging
<code>slingstart</code> which requires the ITs to be located in a dedicated
Maven module (see <a
href="https://issues.apache.org/jira/browse/SLING-6068";>SLING-6068</a>).</p>
+<p>The provisioning of an appropriate instance can be done with the <a
href="/documentation/development/slingstart.html">slingstart-maven-plugin</a>.
An example for that is given at <a
href="https://svn.apache.org/viewvc/sling/trunk/testing/samples/module-with-it";><code>testing/samples/module-with-it</code></a>.
Since <code>slingstart-maven-plugin</code> 1.5.0 it is possible to bootstrap a
Sling Server from a <code>model.txt</code> below
<code>src/test/provisioning</code> independent of the packaging (see <a
href="https://issues.apache.org/jira/browse/SLING-6068";>SLING-6068</a>).</p>
<h4 id="launchpadcustomizer">LaunchpadCustomizer<a class="headerlink"
href="#launchpadcustomizer" title="Permanent link">¶</a></h4>
<p>The <em><a
href="https://svn.apache.org/repos/asf/sling/trunk/launchpad/integration-tests/src/main/java/org/apache/sling/junit/teleporter/customizers/LaunchpadCustomizer.java";><code>LaunchpadCustomizer.java</code></a></em>
only verifies that a Sling instance is ready at a given port and configures
the <code>ClientSideTeleporter</code> to deploy to
<code>http://localhost:8888</code> with the credentials
<code>admin</code>:<code>admin</code>. <code>LaunchpadCustomizer</code> uses
the <code>HttpTestBase</code> therefore some parameters are customizable
through system properties. There is no bootstrapping of an instance done here,
so this must be done separately!</p>
<h4 id="bwit_teleportercustomizer">BWIT_TeleporterCustomizer<a
class="headerlink" href="#bwit_teleportercustomizer" title="Permanent
link">¶</a></h4>
@@ -330,7 +330,7 @@ same request again. </p>
but using the newer <code>TeleporterRule</code> described above is much
simpler. As a result, this bundle
should only be needed for existing tests that were written using its
mechanisms. </p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1762052 by kwin on Fri, 23 Sep 2016 11:08:24 +0000
+ Rev. 1783850 by kwin on Tue, 21 Feb 2017 09:10:48 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
