Author: buildbot
Date: Thu Feb 23 16:43:23 2017
New Revision: 1007194
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 Thu Feb 23 16:43:23 2017
@@ -1 +1 @@
-1783986
+1784170
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
Thu Feb 23 16:43:23 2017
@@ -243,40 +243,76 @@ classes which are used only on the clien
</thead>
<tbody>
<tr>
-<td>ClientSideTeleporter.baseUrl</td>
+<td><code>ClientSideTeleporter.baseUrl</code></td>
<td>base url of the Sling Server to which to deploy</td>
<td>yes</td>
<td>-</td>
</tr>
<tr>
-<td>ClientSideTeleporter.includeDependencyPrefixes</td>
+<td><code>ClientSideTeleporter.includeDependencyPrefixes</code></td>
<td>comma-separated list of package prefixes for classes referenced from the
IT. Only the classes having one of the given package prefix are included in the
bundle being deployed to the given Sling instance together with the IT class
itself. They are only included though in case they are referenced! If this is
not set, no referenced classes will be included.</td>
<td>no</td>
<td>-</td>
</tr>
<tr>
-<td>ClientSideTeleporter.excludeDependencyPrefixes</td>
+<td><code>ClientSideTeleporter.excludeDependencyPrefixes</code></td>
<td>comma-separated list of package prefixes for classes referenced from the
IT. Classes having one of the given package prefix will not be included in the
bundle being deployed to the given Sling instance together with the IT class
itself. This takes precedence over the
<code>ClientSideTeleporter.includeDependencyPrefixes</code>.</td>
<td>no</td>
<td>-</td>
</tr>
<tr>
-<td>ClientSideTeleporter.testReadyTimeoutSeconds</td>
+<td><code>ClientSideTeleporter.embedClasses</code></td>
+<td>comma-separated list of fully qualified class names which should be
embedded in the test bundle. Use this only for classes which are not detected
automatically by the Maven Dependency Analyzer but still should be embedded in
the test bundle</td>
+<td>no</td>
+<td>-</td>
+</tr>
+<tr>
+<td><code>ClientSideTeleporter.embedClassesDirectories</code></td>
+<td>comma-separated list directories containing class files which should be
embedded in the test bundle. Use this only for classes which are not detected
automatically by the Maven Dependency Analyzer but still should be embedded in
the test bundle</td>
+<td>no</td>
+<td>-</td>
+</tr>
+<tr>
+<td><code>ClientSideTeleporter.additionalBundleHeaders</code></td>
+<td>comma-separated list of entries in the format
<code><name>:<value></code> which should be added to the test
bundle as additional headers</td>
+<td>no</td>
+<td>-</td>
+</tr>
+<tr>
+<td><code>ClientSideTeleporter.testReadyTimeoutSeconds</code></td>
<td>how long to wait for our test to be ready on the server-side in seconds,
after installing the test bundle.</td>
<td>no</td>
-<td>12</td>
+<td><code>12</code></td>
</tr>
<tr>
-<td>ClientSideTeleporter.serverUsername</td>
+<td><code>ClientSideTeleporter.serverUsername</code></td>
<td>the username with which to send requests to the Sling server.</td>
<td>no</td>
-<td>admin</td>
+<td><code>admin</code></td>
</tr>
<tr>
-<td>ClientSideTeleporter.serverPassword</td>
+<td><code>ClientSideTeleporter.serverPassword</code></td>
<td>the password with which to send requests to the Sling server.</td>
<td>no</td>
-<td>admin</td>
+<td><code>admin</code></td>
+</tr>
+<tr>
+<td><code>ClientSideTeleporter.enableLogging</code></td>
+<td>set to <code>true</code> to log the tasks being performed by the
teleporter. Useful for debugging</td>
+<td>no</td>
+<td><code>false</code></td>
+</tr>
+<tr>
+<td><code>ClientSideTeleporter.preventToUninstallBundle</code></td>
+<td>set to <code>true</code> to not automatically uninstall the test bundle
after test execution. Useful for debugging.</td>
+<td>no</td>
+<td><code>false</code></td>
+</tr>
+<tr>
+<td><code>ClientSideTeleporter.testBundleDirectory</code></td>
+<td>if set the test bundles are being persisted (before being installed)
within the given directory name. If the directory does not exist, it will be
automatically created. Useful for debugging.</td>
+<td>no</td>
+<td>-</td>
</tr>
</tbody>
</table>
@@ -330,7 +366,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. 1783850 by kwin on Tue, 21 Feb 2017 09:10:48 +0000
+ Rev. 1784170 by kwin on Thu, 23 Feb 2017 16:42:53 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
