Fix table as in commit 825c0f9

Project: http://git-wip-us.apache.org/repos/asf/sling-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/sling-site/commit/f1fa8044
Tree: http://git-wip-us.apache.org/repos/asf/sling-site/tree/f1fa8044
Diff: http://git-wip-us.apache.org/repos/asf/sling-site/diff/f1fa8044

Branch: refs/heads/master
Commit: f1fa8044b74408331b7b5d372e0f8b0d728ddfe6
Parents: 825c0f9
Author: Bertrand Delacretaz <bdelacre...@apache.org>
Authored: Tue Jun 20 16:15:06 2017 +0200
Committer: Bertrand Delacretaz <bdelacre...@apache.org>
Committed: Tue Jun 20 16:15:06 2017 +0200

----------------------------------------------------------------------
 .../bundles/org-apache-sling-junit-bundles.md         | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/sling-site/blob/f1fa8044/content/documentation/bundles/org-apache-sling-junit-bundles.md
----------------------------------------------------------------------
diff --git a/content/documentation/bundles/org-apache-sling-junit-bundles.md 
b/content/documentation/bundles/org-apache-sling-junit-bundles.md
index adb6f11..b99d32c 100644
--- a/content/documentation/bundles/org-apache-sling-junit-bundles.md
+++ b/content/documentation/bundles/org-apache-sling-junit-bundles.md
@@ -143,18 +143,18 @@ The following customizers are currently used in Sling
 
 | Property Name                | Description                                   
  | Mandatory to set | Default value | Since version | Related JIRA |
 
|------------------------------|-------------------------------------------------|------------------|
 ----- | ---| --- |
-| `ClientSideTeleporter.baseUrl` | base url of the Sling Server to which to 
deploy. | yes | - | 1.0.8 | 
[SLING-5677](https://issues.apache.org/jira/browse/SLING-5677) |
-| `ClientSideTeleporter.includeDependencyPrefixes` | 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. | no | - | 1.0.8 | 
[SLING-5677](https://issues.apache.org/jira/browse/SLING-5677) |
-| `ClientSideTeleporter.excludeDependencyPrefixes` | 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 `ClientSideTeleporter.includeDependencyPrefixes`. | no | - | 1.0.8 | 
[SLING-5677](https://issues.apache.org/jira/browse/SLING-5677) |
-| `ClientSideTeleporter.embedClasses` | 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 | no | - | 1.0.8 | 
[SLING-5677](https://issues.apache.org/jira/browse/SLING-5677) |
-| `ClientSideTeleporter.embedClassesDirectories` | 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 | no | - | 
1.0.12 | [SLING-6551](https://issues.apache.org/jira/browse/SLING-6551) |
-| `ClientSideTeleporter.additionalBundleHeaders` | comma-separated list of 
entries in the format `<name>:<value>` which should be added to the test bundle 
as additional headers | no | - | 1.0.12 | 
[SLING-6558](https://issues.apache.org/jira/browse/SLING-6558) |
+| `ClientSideTeleporter.baseUrl` | base url of the Sling Server to which to 
deploy. | yes | (-) | 1.0.8 | 
[SLING-5677](https://issues.apache.org/jira/browse/SLING-5677) |
+| `ClientSideTeleporter.includeDependencyPrefixes` | 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. | no | (-) | 1.0.8 | 
[SLING-5677](https://issues.apache.org/jira/browse/SLING-5677) |
+| `ClientSideTeleporter.excludeDependencyPrefixes` | 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 `ClientSideTeleporter.includeDependencyPrefixes`. | no | (-) | 1.0.8 | 
[SLING-5677](https://issues.apache.org/jira/browse/SLING-5677) |
+| `ClientSideTeleporter.embedClasses` | 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 | no | (-) | 1.0.8 | 
[SLING-5677](https://issues.apache.org/jira/browse/SLING-5677) |
+| `ClientSideTeleporter.embedClassesDirectories` | 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 | no | (-) 
| 1.0.12 | [SLING-6551](https://issues.apache.org/jira/browse/SLING-6551) |
+| `ClientSideTeleporter.additionalBundleHeaders` | comma-separated list of 
entries in the format `<name>:<value>` which should be added to the test bundle 
as additional headers | no | (-) | 1.0.12 | 
[SLING-6558](https://issues.apache.org/jira/browse/SLING-6558) |
 | `ClientSideTeleporter.testReadyTimeoutSeconds` | how long to wait for our 
test to be ready on the server-side in seconds, after installing the test 
bundle. | no | `12` | 1.0.8 | 
[SLING-5677](https://issues.apache.org/jira/browse/SLING-5677) |
 | `ClientSideTeleporter.serverUsername` | the username with which to send 
requests to the Sling server. | no | `admin` | 1.0.8 | 
[SLING-5677](https://issues.apache.org/jira/browse/SLING-5677) |
 | `ClientSideTeleporter.serverPassword` | the password with which to send 
requests to the Sling server. | no | `admin` | 1.0.8 | 
[SLING-5677](https://issues.apache.org/jira/browse/SLING-5677) |
 | `ClientSideTeleporter.enableLogging` | set to `true` to log the tasks being 
performed by the teleporter. Useful for debugging. | no | `false` | 1.0.12 | 
[SLING-6546](https://issues.apache.org/jira/browse/SLING-6546) |
 | `ClientSideTeleporter.preventToUninstallBundle` | set to `true` to not 
automatically uninstall the test bundle after test execution. Useful for 
debugging. | no | `false` | 1.0.12 | 
[SLING-6546](https://issues.apache.org/jira/browse/SLING-6546) |
-| `ClientSideTeleporter.testBundleDirectory` | 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. Recommended value `${project.build.directory}/test-bundles`. | no | 
- | 1.0.12 | [SLING-6546](https://issues.apache.org/jira/browse/SLING-6546) |
+| `ClientSideTeleporter.testBundleDirectory` | 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. Recommended value `${project.build.directory}/test-bundles`. | no | 
(-) | 1.0.12 | [SLING-6546](https://issues.apache.org/jira/browse/SLING-6546) |
 
 
 The provisioning of an appropriate instance can be done with the 
[slingstart-maven-plugin](/documentation/development/slingstart.html). An 
example for that is given at 
[`testing/samples/module-with-it`](https://svn.apache.org/viewvc/sling/trunk/testing/samples/module-with-it).
 Since `slingstart-maven-plugin` 1.5.0 it is possible to bootstrap a Sling 
Server from a `model.txt` below `src/test/provisioning` independent of the 
packaging (see [SLING-6068](https://issues.apache.org/jira/browse/SLING-6068)).

Reply via email to