This is an automated email from the ASF dual-hosted git repository.
rombert pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-site.git
The following commit(s) were added to refs/heads/master by this push:
new 4a732b4 SLING-7161 - Update site to reference git instead of svn
4a732b4 is described below
commit 4a732b4193371625db5c32f6596f3f35f38dd72f
Author: Robert Munteanu <[email protected]>
AuthorDate: Wed Nov 22 22:30:38 2017 +0200
SLING-7161 - Update site to reference git instead of svn
Change more references from svn to git
---
src/main/jbake/content/documentation.md | 1 +
...g-filesystem-resources-extensions-fsresource.md | 4 +-
.../documentation/bundles/caching-services.md | 3 +-
.../bundles/configuration-installer-factory.md | 2 +-
.../bundles/content-loading-jcr-contentloader.md | 2 +-
.../documentation/bundles/dynamic-includes.md | 4 +-
.../bundles/file-installer-provider.md | 2 +-
.../bundles/jcr-installer-provider.md | 12 ++--
...anaging-permissions-jackrabbit-accessmanager.md | 9 +--
...ging-users-and-groups-jackrabbit-usermanager.md | 12 +---
...g-content-the-slingpostservlet-servlets-post.md | 10 +--
.../bundles/org-apache-sling-junit-bundles.md | 5 +-
.../documentation/bundles/osgi-installer.md | 2 +-
.../bundles/repository-initialization.md | 2 +-
.../documentation/bundles/request-analysis.md | 2 +-
.../bundles/scripting/scripting-thymeleaf.md | 2 +-
.../documentation/bundles/servlet-helpers.md | 2 +-
.../bundles/sling-health-check-tool.md | 10 +--
.../sling-settings-org-apache-sling-settings.md | 2 +-
.../bundles/subsystem-installer-factory.md | 2 +-
.../content/documentation/bundles/validation.md | 4 +-
.../content/documentation/bundles/xml-support.md | 6 +-
.../jbake/content/documentation/development.md | 2 +-
.../documentation/development/embedding-sling.md | 10 +--
.../content/documentation/development/hamcrest.md | 2 +-
.../documentation/development/ide-tooling.md | 2 +-
.../content/documentation/development/logging.md | 2 +-
.../development/maven-launchpad-plugin.md | 7 +-
.../documentation/development/maven-usage.md | 2 +-
.../development/release-management.md | 81 ++++++++++------------
.../documentation/development/sling-mock.md | 8 +--
.../development/sling-testing-tools.md | 12 ++--
.../discover-sling-in-15-minutes.md | 3 +-
.../jbake/content/documentation/pax-exam-utils.md | 4 +-
.../authentication/authentication-actors.md | 2 +-
.../form-based-authenticationhandler.md | 4 +-
.../openid-authenticationhandler.md | 7 +-
.../the-sling-engine/errorhandling.md | 2 +-
.../documentation/the-sling-engine/filters.md | 2 +-
.../documentation/the-sling-engine/resources.md | 8 +--
.../documentation/the-sling-engine/servlets.md | 4 +-
.../the-sling-engine/the-sling-launchpad.md | 2 +-
.../the-sling-engine/url-decomposition.md | 4 +-
.../the-sling-engine/url-to-script-resolution.md | 2 +-
.../tutorials-how-tos/46-line-blog.md | 4 +-
.../tutorials-how-tos/jackrabbit-persistence.md | 8 ++-
.../testing-sling-based-applications.md | 13 ++--
src/main/jbake/content/news.md | 1 +
48 files changed, 132 insertions(+), 166 deletions(-)
diff --git a/src/main/jbake/content/documentation.md
b/src/main/jbake/content/documentation.md
index 417b6f6..982a916 100644
--- a/src/main/jbake/content/documentation.md
+++ b/src/main/jbake/content/documentation.md
@@ -49,6 +49,7 @@ The public wiki of Sling is available at
[http://cwiki.apache.org/SLING](http://
## The JavaDoc
+<!-- GIT-TODO - no migrated yet -->
With every major release of Sling the JavaDoc of all containing bundles are
published below
[http://sling.apache.org/apidocs/](http://sling.apache.org/apidocs/).
The script for generating this aggregation JavaDoc is at
[http://svn.apache.org/repos/asf/sling/trunk/tooling/release/](http://svn.apache.org/repos/asf/sling/trunk/tooling/release/)
in `generate_javadoc_for_release.sh`
diff --git
a/src/main/jbake/content/documentation/bundles/accessing-filesystem-resources-extensions-fsresource.md
b/src/main/jbake/content/documentation/bundles/accessing-filesystem-resources-extensions-fsresource.md
index cfc6112..a16f9cf 100644
---
a/src/main/jbake/content/documentation/bundles/accessing-filesystem-resources-extensions-fsresource.md
+++
b/src/main/jbake/content/documentation/bundles/accessing-filesystem-resources-extensions-fsresource.md
@@ -118,8 +118,8 @@ Notes:
-[src-trunk]:
https://svn.apache.org/repos/asf/sling/trunk/bundles/extensions/fsresource/
-[src-branch]: https://svn.apache.org/repos/asf/sling/branches/fsresource-1.x/
+[src-trunk]: https://github.com/apache/sling-org-apache-sling-fsresource
+[src-branch]:
https://github.com/apache/sling-org-apache-sling-fsresource/tree/release/1.x
[maven-central]:
https://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache.sling%22%20AND%20a%3A%22org.apache.sling.fsresource%22
[jcr-contentloader]: content-loading-jcr-contentloader.html
[maven-sling-plugin]: http://sling.apache.org/components/maven-sling-plugin/
diff --git a/src/main/jbake/content/documentation/bundles/caching-services.md
b/src/main/jbake/content/documentation/bundles/caching-services.md
index 836a42f..11522e3 100644
--- a/src/main/jbake/content/documentation/bundles/caching-services.md
+++ b/src/main/jbake/content/documentation/bundles/caching-services.md
@@ -4,9 +4,10 @@ status=published
tags=caching
~~~~~~
-Caching services are available as a contribution at
[https://svn.apache.org/repos/asf/sling/trunk/contrib/extensions/cache](https://svn.apache.org/repos/asf/sling/trunk/contrib/extensions/cache)
+Caching services are available under multiple repositories at
[https://github.com/apache/?utf8=✓&q=sling-cache](https://github.com/apache/?utf8=✓&q=sling-cache)
Both EhCache and Infinispan implementations are provided, with good unit and
integration tests coverage.
+<!-- GIT-TODO portal stuff must be moved to the Git portal -->
A portal cache provider API implementation is provided, that depends on the
whiteboard portal modules
found under
[https://svn.apache.org/repos/asf/sling/whiteboard/portal](https://svn.apache.org/repos/asf/sling/whiteboard/portal)
diff --git
a/src/main/jbake/content/documentation/bundles/configuration-installer-factory.md
b/src/main/jbake/content/documentation/bundles/configuration-installer-factory.md
index b35ba01..51275f6 100644
---
a/src/main/jbake/content/documentation/bundles/configuration-installer-factory.md
+++
b/src/main/jbake/content/documentation/bundles/configuration-installer-factory.md
@@ -80,5 +80,5 @@ A number of such .config files exist in the Sling codebase
and can be used as ex
# Project Info
-* Configuration installer factory
([org.apache.sling.installer.factory.configuration](http://svn.apache.org/repos/asf/sling/trunk/installer/factories/configuration))
+* Configuration installer factory
([org.apache.sling.installer.factory.configuration](https://github.com/apache/sling-org-apache-sling-installer-factory-configuration))
diff --git
a/src/main/jbake/content/documentation/bundles/content-loading-jcr-contentloader.md
b/src/main/jbake/content/documentation/bundles/content-loading-jcr-contentloader.md
index 6a1f6b0..6523643 100644
---
a/src/main/jbake/content/documentation/bundles/content-loading-jcr-contentloader.md
+++
b/src/main/jbake/content/documentation/bundles/content-loading-jcr-contentloader.md
@@ -280,7 +280,7 @@ Support for re-registration of node types is relatively
limited. In Jackrabbit,
### Automated tests
-The initial content found in the [sling-test folder of the launchpad initial
content](http://svn.apache.org/repos/asf/sling/trunk/launchpad/content/src/main/resources/content/sling-test)
is verified by the
[InitialContentTest](http://svn.apache.org/repos/asf/sling/trunk/launchpad/testing/src/test/java/org/apache/sling/launchpad/webapp/integrationtest/InitialContentTest.java)
when running the *launchpad/testing* integration tests.
+The initial content found in the [sling-test folder of the launchpad initial
content](https://github.com/apache/sling-org-apache-sling-launchpad-content/tree/master/src/main/resources/content/sling-test)
is verified by the
[InitialContentTest](https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/blob/master/src/main/java/org/apache/sling/launchpad/webapp/integrationtest/InitialContentTest.java)
when running the *launchpad testing* integration tests.
Those tests can be used as verified examples of initial content loading.
Contributions are welcome to improve the coverage of those tests.
diff --git a/src/main/jbake/content/documentation/bundles/dynamic-includes.md
b/src/main/jbake/content/documentation/bundles/dynamic-includes.md
index 326037d..76a8348 100644
--- a/src/main/jbake/content/documentation/bundles/dynamic-includes.md
+++ b/src/main/jbake/content/documentation/bundles/dynamic-includes.md
@@ -23,6 +23,4 @@ Notice: Licensed to the Apache Software Foundation (ASF)
under one
Sling Dynamic Include (org.apache.sling.dynamic-include)
========================================================
For now the Sling Dynamic Include documentation can be found
-[in the Sling
codebase](https://svn.apache.org/repos/asf/sling/trunk/contrib/extensions/sling-dynamic-include/README.md)
-or
-[on our GitHub
mirror](https://github.com/apache/sling/tree/trunk/contrib/extensions/sling-dynamic-include)
if that's in sync.
+[in the module's
README.md](https://github.com/apache/sling-org-apache-sling-dynamic-include).
diff --git
a/src/main/jbake/content/documentation/bundles/file-installer-provider.md
b/src/main/jbake/content/documentation/bundles/file-installer-provider.md
index 0a26040..a396058 100644
--- a/src/main/jbake/content/documentation/bundles/file-installer-provider.md
+++ b/src/main/jbake/content/documentation/bundles/file-installer-provider.md
@@ -40,4 +40,4 @@ You can even combine start level and run mode support. Just
pay attention that t
# Project Info
-* File installer provider
([org.apache.sling.installer.provider.file](http://svn.apache.org/repos/asf/sling/trunk/installer/providers/file))
+* File installer provider
([org.apache.sling.installer.provider.file](https://github.com/apache/sling-org-apache-sling-installer-provider-file))
diff --git
a/src/main/jbake/content/documentation/bundles/jcr-installer-provider.md
b/src/main/jbake/content/documentation/bundles/jcr-installer-provider.md
index 67347ba..4fe69b9 100644
--- a/src/main/jbake/content/documentation/bundles/jcr-installer-provider.md
+++ b/src/main/jbake/content/documentation/bundles/jcr-installer-provider.md
@@ -38,11 +38,7 @@ If the parent folder of a bundle has a name which is a
number, this is used as t
Here's a quick walkthrough of the JCR installer functionality.
## Installation
-Start the Sling
[launchpad/app](http://svn.apache.org/repos/asf/sling/trunk/launchpad/app) and
make sure that the following bundles are present and started:
-
- * [Sling Settings](sling-settings-org-apache-sling-settings.html)
- * OSGi installer service
([org.apache.sling.installer.core](http://svn.apache.org/repos/asf/sling/trunk/installer/core))
- * JCR installer provider
([org.apache.sling.installer.provider.jcr](http://svn.apache.org/repos/asf/sling/trunk/installer/providers/jcr))
+Run the [Sling
Starter](https://github.com/apache/sling-org-apache-sling-starter).
To watch the logs produced by these modules, you can filter
`sling/logs/error.log` using `egrep 'jcrinstall|osgi.installer'`.
@@ -150,11 +146,11 @@ A node named like `o.a.s.foo.bar-a` uses *o.a.s.foo.bar*
as its factory PID crea
# Automated Tests
The following modules contain lots of automated tests (under `src/test`, as
usual):
-* OSGi installer integration tests
([org.apache.sling.installer.it](http://svn.apache.org/repos/asf/sling/trunk/installer/it))
-* JCR installer service
([org.apache.sling.installer.providers.jcr](http://svn.apache.org/repos/asf/sling/trunk/installer/providers/jcr))
+* OSGi installer integration tests
([org.apache.sling.installer.it](https://github.com/apache/sling-org-apache-sling-installer-it))
+* JCR installer service
([org.apache.sling.installer.providers.jcr](https://github.com/apache/sling-org-apache-sling-installer-provider-jcr))
Many of these tests are fairly readable, and can be used to find out in more
detail how these modules work.
# Project Info
-* JCR installer provider
([org.apache.sling.installer.provider.jcr](http://svn.apache.org/repos/asf/sling/trunk/installer/providers/jcr))
+* JCR installer provider
([org.apache.sling.installer.provider.jcr](https://github.com/apache/sling-org-apache-sling-installer-provider-jcr))
diff --git
a/src/main/jbake/content/documentation/bundles/managing-permissions-jackrabbit-accessmanager.md
b/src/main/jbake/content/documentation/bundles/managing-permissions-jackrabbit-accessmanager.md
index 03b350c..10a10ce 100644
---
a/src/main/jbake/content/documentation/bundles/managing-permissions-jackrabbit-accessmanager.md
+++
b/src/main/jbake/content/documentation/bundles/managing-permissions-jackrabbit-accessmanager.md
@@ -102,11 +102,4 @@ Example:
<div class="note">
See section 16.3 of the JCR 2.0 specification for an explanation of the
difference between bound and effective policies.
-</div>
-
-
-## Sample User Interface Implementation
-
-*Since Version 2.1.1*
-
-A sample implementation of ui pages for permissions management is provided @
http://svn.apache.org/viewvc/sling/trunk/samples/accessmanager-ui/
+</div>
\ No newline at end of file
diff --git
a/src/main/jbake/content/documentation/bundles/managing-users-and-groups-jackrabbit-usermanager.md
b/src/main/jbake/content/documentation/bundles/managing-users-and-groups-jackrabbit-usermanager.md
index 3cc9a55..781bcc9 100644
---
a/src/main/jbake/content/documentation/bundles/managing-users-and-groups-jackrabbit-usermanager.md
+++
b/src/main/jbake/content/documentation/bundles/managing-users-and-groups-jackrabbit-usermanager.md
@@ -261,7 +261,7 @@ Example
## Automated Tests
-The
[launchpad/testing](http://svn.apache.org/repos/asf/sling/trunk/launchpad/testing/src/test/java/org/apache/sling/launchpad/webapp/integrationtest/accessManager/)
module contains test classes for various operations of the
`jackrabbit-usermanager`. Such tests run as part of our continuous integration
process, to demonstrate and verify the behavior of the various operations, in a
way that's guaranteed to be in sync with the actual Sling core code. If you
have an idea for additional test [...]
+The
[launchpad/testing](https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/blob/master/src/main/java/org/apache/sling/launchpad/webapp/integrationtest/accessManager/)
module contains test classes for various operations of the
`jackrabbit-usermanager`. Such tests run as part of our continuous integration
process, to demonstrate and verify the behavior of the various operations, in a
way that's guaranteed to be in sync with the actual Sling core code. If you
have [...]
## Permissions checking from scripts
@@ -307,12 +307,4 @@ Example:
if (privilegesInfo.canUpdateGroupMembers(currentSession, "GroupName"))
{
//TODO: draw your UI that allows the user to update the group
memebership here
}
- %>
-
-
-
-## Sample User Interface Implementation
-
-*Since Version 2.1.1*
-
-A sample implementation of ui pages for user/group management is provided @
[http://svn.apache.org/viewvc/sling/trunk/samples/usermanager-ui/](http://svn.apache.org/viewvc/sling/trunk/samples/usermanager-ui/).
+ %>
\ No newline at end of file
diff --git
a/src/main/jbake/content/documentation/bundles/manipulating-content-the-slingpostservlet-servlets-post.md
b/src/main/jbake/content/documentation/bundles/manipulating-content-the-slingpostservlet-servlets-post.md
index 0d5031a..2b04c1f 100644
---
a/src/main/jbake/content/documentation/bundles/manipulating-content-the-slingpostservlet-servlets-post.md
+++
b/src/main/jbake/content/documentation/bundles/manipulating-content-the-slingpostservlet-servlets-post.md
@@ -81,7 +81,7 @@ Please note that operations are mutually exclusive. For a
single POST request on
<div class="note">
<b>Automated tests</b>:
-Note that the `launchpad/testing` module contains a number of <a
href="http://svn.apache.org/repos/asf/sling/trunk/launchpad/test-services/src/main/java/org/apache/sling/launchpad/testservices/post/";>integration
tests</a> for the SlingPostServlet. Most of these tests are fairly readable,
and can be used to find out more details about the servlet's behavior.
+Note that the launchpad test services module contains a number of <a
href="https://github.com/apache/sling-org-apache-sling-launchpad-test-services/tree/master/src/main/java/org/apache/sling/launchpad/testservices/post";>integration
tests</a> for the SlingPostServlet. Most of these tests are fairly readable,
and can be used to find out more details about the servlet's behavior.
</div>
@@ -106,7 +106,7 @@ If the resource of the request is a synthetic resource,
e.g. `NonExistingResourc
In both cases the path may still include selectors and extensions, which are
cut off the path before finding out, what to do.
-To illustrate this algorithm, lets look at some examples (and check the
[`PostServletCreateTest`](https://svn.apache.org/repos/asf/sling/trunk/launchpad/integration-tests/src/main/java/org/apache/sling/launchpad/webapp/integrationtest/servlets/post/PostServletCreateTest.java)
in case of doubt):
+To illustrate this algorithm, lets look at some examples (and check the
[`PostServletCreateTest`](https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/blob/master/src/main/java/org/apache/sling/launchpad/webapp/integrationtest/servlets/post/PostServletCreateTest.java)
in case of doubt):
| Resource Path | Item path |
|--|--|
@@ -158,7 +158,7 @@ following property names _if they are supplied with empty
values in such a reque
* `lastModifiedBy`, `jcr:lastModifiedBy` are set to the name of the user who
modified the node.
-This is demonstrated by the
[SlingAutoPropertiesTest](https://svn.apache.org/repos/asf/sling/trunk/launchpad/integration-tests/src/main/java/org/apache/sling/launchpad/webapp/integrationtest/servlets/post/SlingAutoPropertiesTest.java)
which is part of our launchpad integration tests.
+This is demonstrated by the
[SlingAutoPropertiesTest](https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/blob/master/src/main/java/org/apache/sling/launchpad/webapp/integrationtest/servlets/post/SlingAutoPropertiesTest.java)
which is part of our launchpad integration tests.
##### File Uploads
@@ -881,7 +881,7 @@ Such services must have a `sling.post.operation` service
registration property s
Before version 2.1.2 of the *org.apache.sling.servlets.post* bundle, such
additional operations were implemented by the
`org.apache.sling.servlets.post.SlingPostOperation` interface, which is now
deprecated but still supported via a bridge. See
[SLING-1725](https://issues.apache.org/jira/browse/SLING-1725) for details and
discussions about this change.
-Two examples (old and new style) of additional POST operations are found in
the
[test-services](http://svn.apache.org/repos/asf/sling/trunk/launchpad/test-services/src/main/java/org/apache/sling/launchpad/testservices/post/)
module, with the corresponding test code in the
[integration-tests](http://svn.apache.org/repos/asf/sling/trunk/launchpad/integration-tests/src/main/java/org/apache/sling/launchpad/webapp/integrationtest/servlets/post/CustomPostOperationTest.java)
module.
+Two examples (old and new style) of additional POST operations are found in
the
[test-services](https://github.com/apache/sling-org-apache-sling-launchpad-test-services/tree/master/src/main/java/org/apache/sling/launchpad/testservices/post)
module, with the corresponding test code in the
[integration-tests](https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/blob/master/src/main/java/org/apache/sling/launchpad/webapp/integrationtest/servlets/post/CustomPostOperat
[...]
### SlingPostProcessor
@@ -890,4 +890,4 @@ OSGi services of the
`org.apache.sling.servlets.post.SlingPostOperation` type ca
A `SlingPostProcessor` may perform additional changes or revert previous ones.
It is important that the `SlingPostProcessor` does not commit its changes but
rather only performs the changes in the transient space (with the resource
resolver bound to the current request) and in addition reports the changes
through the 2nd parameter of the method `process(SlingHttpServletRequest,
List<Modification>)`.
-Two examples of SlingPostProcessors are found in the
[test-services](http://svn.apache.org/repos/asf/sling/trunk/launchpad/test-services/src/main/java/org/apache/sling/launchpad/testservices/post/)
module, with the corresponding test code in the
[integration-tests](http://svn.apache.org/repos/asf/sling/trunk/launchpad/integration-tests/src/main/java/org/apache/sling/launchpad/webapp/integrationtest/servlets/post/SlingPostProcessorTest)
module.
+Two examples of SlingPostProcessors are found in the
[test-services](https://github.com/apache/sling-org-apache-sling-launchpad-test-services/tree/master/src/main/java/org/apache/sling/launchpad/testservices/post)
module, with the corresponding test code in the
[integration-tests](https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/blob/master/src/main/java/org/apache/sling/launchpad/webapp/integrationtest/servlets/post/SlingPostProcessorTest.java)
module.
diff --git
a/src/main/jbake/content/documentation/bundles/org-apache-sling-junit-bundles.md
b/src/main/jbake/content/documentation/bundles/org-apache-sling-junit-bundles.md
index 18cb601..569ca18 100644
---
a/src/main/jbake/content/documentation/bundles/org-apache-sling-junit-bundles.md
+++
b/src/main/jbake/content/documentation/bundles/org-apache-sling-junit-bundles.md
@@ -89,7 +89,7 @@ bundle, making them available to the server-side tests.
This teleporter mechanism is used in our integration tests, search for
`TeleporterRule` in there
for examples or look at the
-[`integrationtest.teleporter`](
https://svn.apache.org/repos/asf/sling/trunk/launchpad/integration-tests/src/main/java/org/apache/sling/launchpad/webapp/integrationtest/teleporter)
+[`integrationtest.teleporter`](https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/tree/master/src/main/java/org/apache/sling/launchpad/webapp/integrationtest/teleporter)
package.
As I write this the teleporter mechanism is quite new, I suspect there might
be some weird interactions
@@ -140,6 +140,7 @@ The following customizers are currently used in Sling
### Default Customizer ###
+<!-- GIT-TODO - not yet migrated -->
*[DefaultPropertyBasedCustomizer.java](https://svn.apache.org/repos/asf/sling/trunk/testing/junit/teleporter/src/main/java/org/apache/sling/testing/teleporter/client/DefaultPropertyBasedCustomizer.java)*
is used by default when no other customizer is referenced in
`TeleporterRule.forClass(getClass())`. It relies on the following system
properties:
| Property Name | Description
| Mandatory to set | Default value | Since version | Related JIRA |
@@ -161,7 +162,7 @@ The following customizers are currently used in Sling
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
[`sling-samples/testing/module-with-it`](https://github.com/apache/sling-samples/tree/master/testing/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/jir [...]
#### LaunchpadCustomizer ####
-The
*[`LaunchpadCustomizer.java`](https://svn.apache.org/repos/asf/sling/trunk/launchpad/integration-tests/src/main/java/org/apache/sling/junit/teleporter/customizers/LaunchpadCustomizer.java)*
only verifies that a Sling instance is ready at a given port and configures
the `ClientSideTeleporter` to deploy to `http://localhost:8080` with the
credentials `admin`:`admin`. `LaunchpadCustomizer` uses the `HttpTestBase`
therefore some parameters are customizable through system properties. Ther [...]
+The
*[`LaunchpadCustomizer.java`](https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/blob/master/src/main/java/org/apache/sling/junit/teleporter/customizers/LaunchpadCustomizer.java)*
only verifies that a Sling instance is ready at a given port and configures
the `ClientSideTeleporter` to deploy to `http://localhost:8080` with the
credentials `admin`:`admin`. `LaunchpadCustomizer` uses the `HttpTestBase`
therefore some parameters are customizable through system [...]
#### BWIT_TeleporterCustomizer ####
The
*[`BWIT_TeleporterCustomizer.java`](https://github.com/apache/sling-samples/tree/master/testing/bundle-with-it/src/test/java/org/apache/sling/junit/teleporter/customizers/BWIT_TeleporterCustomizer.java)*
relies on `SlingTestBase` to set the server's base url and credentials.
Additionally the test bundle is adjusted so that the API is not included in it
(but rather referenced from another bundle). The bootstrapping of the Sling
instance is tweaked through system properties which are d [...]
diff --git a/src/main/jbake/content/documentation/bundles/osgi-installer.md
b/src/main/jbake/content/documentation/bundles/osgi-installer.md
index 54978af..d393fc1 100644
--- a/src/main/jbake/content/documentation/bundles/osgi-installer.md
+++ b/src/main/jbake/content/documentation/bundles/osgi-installer.md
@@ -20,7 +20,7 @@ It's possible to add own providers, transformers and
installer factories to supp
## API
The installer API is defined by the `org.apache.sling.installer.api` package
-of the
[org.apache.sling.installer.core](http://svn.apache.org/repos/asf/sling/trunk/installer/core/)
module. The main
+of the
[org.apache.sling.installer.core](https://github.com/apache/sling-org-apache-sling-installer-core)
module. The main
interface is the `OsgiInstaller` with which installable resources can be
registered.
The [installer integration tests][1] module can be useful to understand the
details of how the installer works.
diff --git
a/src/main/jbake/content/documentation/bundles/repository-initialization.md
b/src/main/jbake/content/documentation/bundles/repository-initialization.md
index ae50bf6..b037b73 100644
--- a/src/main/jbake/content/documentation/bundles/repository-initialization.md
+++ b/src/main/jbake/content/documentation/bundles/repository-initialization.md
@@ -28,7 +28,7 @@ If any of them throws an Exception, the `SlingRepository`
service is not registe
The `org.apache.sling.repoinit.parser` implements a mini-language meant to
create paths, service users and Access Control Lists in a content repository,
as
well as registering JCR namespaces and node types.
-The language grammar is defined (using the JavaCC compiler-compiler, which has
no runtime dependencies) in the `RepoInitGrammar.jjt` file in that module, and
the automated tests provide a number of [test
cases](https://svn.apache.org/repos/asf/sling/trunk/bundles/extensions/repoinit/parser/src/test/resources/testcases)
which demonstrate various features.
+The language grammar is defined (using the JavaCC compiler-compiler, which has
no runtime dependencies) in the `RepoInitGrammar.jjt` file in that module, and
the automated tests provide a number of [test
cases](https://github.com/apache/sling-org-apache-sling-repoinit-parser/tree/master/src/test/resources/testcases)
which demonstrate various features.
The companion `org.apache.sling.jcr.repoinit` module implements those
operations on an Oak JCR repository, using a `SlingRepositoryInitializer`
registered by default with a service ranking of 100. It also provides a
`JcrRepoInitOpsProcessor` service to explicitly apply the output
diff --git a/src/main/jbake/content/documentation/bundles/request-analysis.md
b/src/main/jbake/content/documentation/bundles/request-analysis.md
index 8cefce8..ff4034f 100644
--- a/src/main/jbake/content/documentation/bundles/request-analysis.md
+++ b/src/main/jbake/content/documentation/bundles/request-analysis.md
@@ -18,7 +18,7 @@ Scripts and servlets called during Sling's request processing
may themselves use
Usually the data collected by the `RequestProgressTracker` is just dropped or
it may be visible for a certain number of recent requests on the *Recent
Requests* page of the Web Console. When doing load tests, though, this Web
Console page is of limited use because a lot more requests are handled than can
be displayed in the Web Console.
-This is where the [Request Processing
Analyzer](http://svn.apache.org/repos/asf/sling/trunk/contrib/extensions/reqanalyzer)
comes in handy. When deployed as a bundle it registers as a request level
servlet Filter with the Sling Main Servlet. Each request is logged in a special
file (currently fixed at `${sling.home}/logs/requesttracker.txt`) with a header
line provding core information on the request:
+This is where the [Request Processing
Analyzer](https://github.com/apache/sling-org-apache-sling-reqanalyzer) comes
in handy. When deployed as a bundle it registers as a request level servlet
Filter with the Sling Main Servlet. Each request is logged in a special file
(currently fixed at `${sling.home}/logs/requesttracker.txt`) with a header line
provding core information on the request:
* Start time stamp in ms since the Epoch
* Request processing time in ms
diff --git
a/src/main/jbake/content/documentation/bundles/scripting/scripting-thymeleaf.md
b/src/main/jbake/content/documentation/bundles/scripting/scripting-thymeleaf.md
index 58c606c..c2a2784 100644
---
a/src/main/jbake/content/documentation/bundles/scripting/scripting-thymeleaf.md
+++
b/src/main/jbake/content/documentation/bundles/scripting/scripting-thymeleaf.md
@@ -82,6 +82,6 @@ Sling Scripting Thymeleaf comes with its own dialect using
the `sling` prefix/na
# Sample
-The [Sling Fling
Sample](http://svn.apache.org/repos/asf/sling/trunk/samples/fling/) is a sample
using Sling Scripting Thymeleaf with [Sling
Models](/documentation/bundles/models.html) and [Sling
Query](/documentation/bundles/sling-query.html).
+The [Sling Fling
Sample](https://github.com/apache/sling-samples/tree/master/fling) is a sample
using Sling Scripting Thymeleaf with [Sling
Models](/documentation/bundles/models.html) and [Sling
Query](/documentation/bundles/sling-query.html).
diff --git a/src/main/jbake/content/documentation/bundles/servlet-helpers.md
b/src/main/jbake/content/documentation/bundles/servlet-helpers.md
index bbbcbd0..e8f538d 100644
--- a/src/main/jbake/content/documentation/bundles/servlet-helpers.md
+++ b/src/main/jbake/content/documentation/bundles/servlet-helpers.md
@@ -11,7 +11,7 @@ Those mock implementations are meant to be used in tests and
also with services
like the `SlingRequestProcessor` when making requests to that service outside
of
an HTTP request processing context.
-See the [automated
tests](https://svn.apache.org/repos/asf/sling/trunk/bundles/extensions/servlet-helpers)
+See the [automated
tests](https://github.com/apache/sling-org-apache-sling-servlet-helpers)
of the `servlet-helpers` module for more info.
diff --git
a/src/main/jbake/content/documentation/bundles/sling-health-check-tool.md
b/src/main/jbake/content/documentation/bundles/sling-health-check-tool.md
index e089704..ba6397f 100644
--- a/src/main/jbake/content/documentation/bundles/sling-health-check-tool.md
+++ b/src/main/jbake/content/documentation/bundles/sling-health-check-tool.md
@@ -16,7 +16,7 @@ is a good starting point to run existing checks and to get
familiar with how hea
See also:
-* Source code at
[http://svn.apache.org/repos/asf/sling/trunk/bundles/extensions/healthcheck](http://svn.apache.org/repos/asf/sling/trunk/bundles/extensions/healthcheck)
+* [Source code for the HealthCheck modules on
GitHub](https://github.com/apache?utf8=%E2%9C%93&q=sling%20hc)
* adaptTo slides about Health Checks:
[Introduction](http://www.slideshare.net/bdelacretaz/slinghc-bdelacretazadaptto2013)
and [Health Check
Executor](https://adapt.to/content/dam/adaptto/production/presentations/2014/adaptTo2014-Sling-Health-Checks-New-And-Noteworthy-Georg-Henzler.pdf/_jcr_content/renditions/original.media_file.download_attachment.file/adaptTo2014-Sling-Health-Checks-New-And-Noteworthy-Georg-Henzler.pdf)
## Use cases
@@ -176,7 +176,7 @@ based on their tags (positive and negative selection, see
the `HealthCheckFilter
The DEBUG logs of health checks can optionally be displayed, and an option
allows for showing only health checks that have a non-OK status.
-The screenshot below shows an example, as of svn revision 1513462.
+The screenshot below shows an example.
@@ -217,9 +217,3 @@ remote testing utilities, and also as plain Health Checks
for monitoring or trou
To use this module, configure sets of tags at
`/system/console/configMgr/org.apache.sling.hc.junitbridge.HealthCheckTestsProvider`
using the standard `includeThisTag,-omitThatTag` syntax, and JUnit tests will
be available at /system/sling/junit/HealthChecks.html
to run the corresponding Health Checks.
-
-To run the Health Check tests at build time, see the
[testing/samples/integration-tests](http://svn.apache.org/repos/asf/sling/trunk/testing/samples/integration-tests)
-sample module.
-
-
-
diff --git
a/src/main/jbake/content/documentation/bundles/sling-settings-org-apache-sling-settings.md
b/src/main/jbake/content/documentation/bundles/sling-settings-org-apache-sling-settings.md
index 6ad630c..d67054a 100644
---
a/src/main/jbake/content/documentation/bundles/sling-settings-org-apache-sling-settings.md
+++
b/src/main/jbake/content/documentation/bundles/sling-settings-org-apache-sling-settings.md
@@ -22,7 +22,7 @@ The run modes are selected based on the `sling.run.modes`
property (the "selecti
Using `-Dsling.run.modes=foo,bar` on the JVM command-line, for example,
activates the *foo* and *bar* run modes if that combination is valid.
-The absolute truth about run modes definition and selection is found in the
[RunModeImplTest](https://svn.apache.org/repos/asf/sling/trunk/bundles/extensions/settings/src/test/java/org/apache/sling/settings/impl/RunModeImplTest.java)
which should be self-explaining.
+The absolute truth about run modes definition and selection is found in the
[RunModeImplTest](https://github.com/apache/sling-org-apache-sling-settings/blob/master/src/test/java/org/apache/sling/settings/impl/RunModeImplTest.java)
which should be self-explaining.
## Defining valid run modes
Since [SLING-2662](https://issues.apache.org/jira/browse/SLING-2662) the valid
run modes are defined by the `sling.run.mode.options` and
`sling.run.mode.install.options` configuration properties, usually defined in
the `sling.properties` file or in the provisioning model of a Sling Launchpad
instance.
diff --git
a/src/main/jbake/content/documentation/bundles/subsystem-installer-factory.md
b/src/main/jbake/content/documentation/bundles/subsystem-installer-factory.md
index d9741e7..b814b52 100644
---
a/src/main/jbake/content/documentation/bundles/subsystem-installer-factory.md
+++
b/src/main/jbake/content/documentation/bundles/subsystem-installer-factory.md
@@ -13,4 +13,4 @@ The subsystem file must end with ".esa" and the manifest must
at least contain t
# Project Info
-* Subsystems installer factory
([org.apache.sling.installer.factory.subsystems](http://svn.apache.org/repos/asf/sling/trunk/installer/factories/subsystems))
+* Subsystems installer factory
([org.apache.sling.installer.factory.subsystems](https://github.com/apache/sling-org-apache-sling-installer-factory-subsystems))
diff --git a/src/main/jbake/content/documentation/bundles/validation.md
b/src/main/jbake/content/documentation/bundles/validation.md
index c523f37..97bc968 100644
--- a/src/main/jbake/content/documentation/bundles/validation.md
+++ b/src/main/jbake/content/documentation/bundles/validation.md
@@ -129,10 +129,10 @@ One needs to call the validate method within the
PostConstruct method of the acc
Validator ID | Description | Parameters | Since
---------------|-------------|------------|-------
-[`org.apache.sling.validation.core.RegexValidator`](https://svn.apache.org/repos/asf/sling/trunk/bundles/extensions/validation/core/src/main/java/org/apache/sling/validation/impl/validators/RegexValidator.java)
| Validates that a property value matches a given regular expression |
`regex`, mandatory parameter giving a regular expression according to the
pattern described in
[java.util.regex.Pattern](http://docs.oracle.com/javase/8/docs/api/java/util/regex/Pattern.html).
Only if the prope [...]
+[`org.apache.sling.validation.core.RegexValidator`](https://github.com/apache/sling-org-apache-sling-validation-core/blob/master/src/main/java/org/apache/sling/validation/impl/validators/RegexValidator.java)
| Validates that a property value matches a given regular expression |
`regex`, mandatory parameter giving a regular expression according to the
pattern described in
[java.util.regex.Pattern](http://docs.oracle.com/javase/8/docs/api/java/util/regex/Pattern.html).
Only if the property [...]
# Writing Validators
-To write a validator one needs to implement the
[`org.apache.sling.validation.spi.Validator`](https://svn.apache.org/repos/asf/sling/trunk/bundles/extensions/validation/api/src/main/java/org/apache/sling/validation/spi/Validator.java)
interface in an OSGi service (look at
[`org.apache.sling.validation.core.RegexValidator`](https://svn.apache.org/repos/asf/sling/trunk/bundles/extensions/validation/core/src/main/java/org/apache/sling/validation/impl/validators/RegexValidator.java)
for an e [...]
+To write a validator one needs to implement the
[`org.apache.sling.validation.spi.Validator`](https://github.com/apache/sling-org-apache-sling-validation-api/blob/master/src/main/java/org/apache/sling/validation/spi/Validator.java)
interface in an OSGi service (look at
[`org.apache.sling.validation.core.RegexValidator`](https://github.com/apache/sling-org-apache-sling-validation-core/blob/master/src/main/java/org/apache/sling/validation/impl/validators/RegexValidator.java)
for an example).
That interface defines the method `validate`. That is called for each property
which is bound to the validator through the validation model.
Each validator needs to specify one type parameter which defines upon which
classes the validator can act (usually `String`). Array types are also
supported here. Collection types are not supported. If a property value cannot
be converted to the requested type from the validator (through
`ValueMap.get(name, type)`), validation will fail.
diff --git a/src/main/jbake/content/documentation/bundles/xml-support.md
b/src/main/jbake/content/documentation/bundles/xml-support.md
index dfb9ceb..354195d 100644
--- a/src/main/jbake/content/documentation/bundles/xml-support.md
+++ b/src/main/jbake/content/documentation/bundles/xml-support.md
@@ -7,6 +7,6 @@ tags=xml
Out of the box, Sling provides no special bundles for XML. However, Sling
supports multiple mechanisms and libraries. The ones we have validated with
integration tests are:
-* XPath ( see the
[XPathServlet](http://svn.apache.org/repos/asf/sling/trunk/launchpad/test-services/src/main/java/org/apache/sling/launchpad/testservices/servlets/XpathServlet.java)
)
-* SAX ( see the
[SaxServlet](http://svn.apache.org/repos/asf/sling/trunk/launchpad/test-services/src/main/java/org/apache/sling/launchpad/testservices/servlets/SaxServlet.java)
)
-* DOM ( see the
[DomServlet](http://svn.apache.org/repos/asf/sling/trunk/launchpad/test-services/src/main/java/org/apache/sling/launchpad/testservices/servlets/DomServlet.java)
)
+* XPath ( see the
[XPathServlet](https://github.com/apache/sling-org-apache-sling-launchpad-test-services/blob/master/src/main/java/org/apache/sling/launchpad/testservices/servlets/XpathServlet.java)
)
+* SAX ( see the
[SaxServlet](https://github.com/apache/sling-org-apache-sling-launchpad-test-services/blob/master/src/main/java/org/apache/sling/launchpad/testservices/servlets/SaxServlet.java)
)
+* DOM ( see the
[DomServlet](https://github.com/apache/sling-org-apache-sling-launchpad-test-services/blob/master/src/main/java/org/apache/sling/launchpad/testservices/servlets/DomServlet.java)
)
diff --git a/src/main/jbake/content/documentation/development.md
b/src/main/jbake/content/documentation/development.md
index eea248d..35f9f6e 100644
--- a/src/main/jbake/content/documentation/development.md
+++ b/src/main/jbake/content/documentation/development.md
@@ -54,5 +54,5 @@ Last but not least, here is some more information on how we
ourselves are workin
* [Issue Tracker](/documentation/development/issue-tracker.html)
* [Release Management](/documentation/development/release-management.html)
* [Maven Usage](/documentation/development/maven-usage.html)
-* To run our integration tests suite see the [launchpad/testing module
README](http://svn.apache.org/repos/asf/sling/trunk/launchpad/testing/README.txt)
and the [launchpad/integration-tests
README](http://svn.apache.org/repos/asf/sling/trunk/launchpad/integration-tests/README.txt)
for how to run individual integration tests. We use the
[sling-IT](https://issues.apache.org/jira/issues/?jql=labels%20%3D%20sling-IT)
label in JIRA for known issues with our integration tests.
+* To run our integration tests suite see the [launchpad/testing module
README](https://github.com/apache/sling-org-apache-sling-launchpad-testing/blob/master/README.md)
and the [launchpad/integration-tests
README](https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/blob/master/README.md)
for how to run individual integration tests. We use the
[sling-IT](https://issues.apache.org/jira/issues/?jql=labels%20%3D%20sling-IT)
label in JIRA for known issues with our int [...]
* A Sonar analysis is available on the
[analysis.apache.org](https://analysis.apache.org/dashboard/index/org.apache.sling:sling-builder)
server.
diff --git
a/src/main/jbake/content/documentation/development/embedding-sling.md
b/src/main/jbake/content/documentation/development/embedding-sling.md
index 7bde4b0..1a445b4 100644
--- a/src/main/jbake/content/documentation/development/embedding-sling.md
+++ b/src/main/jbake/content/documentation/development/embedding-sling.md
@@ -4,7 +4,7 @@ status=published
tags=launchpad,embedding
~~~~~~
-The Sling Launchpad Launcher can be used to embed the OSGi Framework startup
in your own Java application. This functionality is implemented in the [Sling
Launchpad Base
project](http://svn.apache.org/repos/asf/sling/trunk/launchpad/base). This
project has the following features:
+The Sling Launchpad Launcher can be used to embed the OSGi Framework startup
in your own Java application. This functionality is implemented in the [Sling
Launchpad Base
project](https://github.com/apache/sling-org-apache-sling-launchpad-base). This
project has the following features:
* Builds three artifacts:
* A standalone Java Application with the artifact qualifier *app*; e.g.
`org.apache.sling.launchpad.base-2.3.1-SNAPSHOT-app.jar`
@@ -46,13 +46,13 @@ The bridging part is provided in the
`org.apache.sling.launchpad.base.shared` pa
# The Internal Part
-The main class from the internal class directly used is
[`Sling`](http://svn.apache.org/repos/asf/sling/trunk/launchpad/base/src/main/java/org/apache/sling/launchpad/base/impl/Sling.java)
which instantiated to start the OSGi Framework. This class is responsible for
setting up the environment to finally start the OSGi Framework:
+The main class from the internal class directly used is
[`Sling`](https://github.com/apache/sling-org-apache-sling-launchpad-base/blob/master/src/main/java/org/apache/sling/launchpad/base/impl/Sling.java)
which instantiated to start the OSGi Framework. This class is responsible for
setting up the environment to finally start the OSGi Framework:
* Read the `sling.properties` file
* Ensure the presence of the JMX MBeanServer service
* Execute the bootstrap installations, updates and uninstallations
-The
[`SlingFelix`](http://svn.apache.org/repos/asf/sling/trunk/launchpad/base/src/main/java/org/apache/sling/launchpad/base/impl/SlingFelix.java)
class extends the Apache Felix `Felix` class which is the actual OSGi
framework implementation. We extend the class to be able to notify the
`Notifiable` implementation and update the OSGi framework from within the OSGi
framework by updating the system bundle.
+The
[`SlingFelix`](https://github.com/apache/sling-org-apache-sling-launchpad-base/blob/master/src/main/java/org/apache/sling/launchpad/base/impl/SlingFelix.java)
class extends the Apache Felix `Felix` class which is the actual OSGi
framework implementation. We extend the class to be able to notify the
`Notifiable` implementation and update the OSGi framework from within the OSGi
framework by updating the system bundle.
## The External Part
@@ -74,10 +74,6 @@ At the moment these classes are not directly suitable to be
embedded in an exist
### Embedding the Standalone Java Application
-<div class="info">
-This work is being done as part of
[SLING-2225](https://issues.apache.org/jira/browse/SLING-2225) and will be
officially available with the Sling Launchpad Base release 2.4.0. If you want
to use the embedding before the release, you have to checkout the source from
[SVN|http://svn.apache.org/repos/asf/sling/trunk/launchpad/base] and build
yourself.
-</div>
-
To embedd the Sling Launcher in an application, the `Main` class is extended
from. To manage the launcher, the following API is available:
| Method | Description |
diff --git a/src/main/jbake/content/documentation/development/hamcrest.md
b/src/main/jbake/content/documentation/development/hamcrest.md
index 7e48e66..a032236 100644
--- a/src/main/jbake/content/documentation/development/hamcrest.md
+++ b/src/main/jbake/content/documentation/development/hamcrest.md
@@ -43,4 +43,4 @@ The class
`org.apache.sling.testing.hamcrest.ResourceMatchers` is the main entry
}
-The Slingshot sample application uses these matchers, see
[SetupServiceTest.java](http://svn.apache.org/repos/asf/sling/trunk/samples/slingshot/src/test/java/org/apache/sling/sample/slingshot/impl/SetupServiceTest.java)
for an example.
+The Slingshot sample application uses these matchers, see
[SetupServiceTest.java](https://github.com/apache/sling-samples/blob/master/slingshot/src/test/java/org/apache/sling/sample/slingshot/impl/SetupServiceTest.java)
for an example.
diff --git a/src/main/jbake/content/documentation/development/ide-tooling.md
b/src/main/jbake/content/documentation/development/ide-tooling.md
index 35da548..b0e98cc 100644
--- a/src/main/jbake/content/documentation/development/ide-tooling.md
+++ b/src/main/jbake/content/documentation/development/ide-tooling.md
@@ -20,7 +20,7 @@ The links to the latest update site, including a permanent
URL which stays up to
### Building from source
-The update sites are provided as a convenience for users that do not wish to
build the project themselves. Building the project only requires a recent Maven
installation. The project can be checked out, either [from trunk for the latest
development version](https://svn.apache.org/repos/asf/sling/trunk/tooling/ide/)
or [from a tag for released
versions](https://svn.apache.org/repos/asf/sling/tags/), where the tags names
have the format sling-ide-tooling-$VERSION. Once you have obtained th [...]
+The update sites are provided as a convenience for users that do not wish to
build the project themselves. Building the project only requires a recent Maven
installation. The project can be checked out from
[https://github.com/apache/sling-ide-tooling](https://github.com/apache/sling-ide-tooling).
Once you have obtained the source code, it is enough to run
mvn package
diff --git a/src/main/jbake/content/documentation/development/logging.md
b/src/main/jbake/content/documentation/development/logging.md
index 265a646..3c5680e 100644
--- a/src/main/jbake/content/documentation/development/logging.md
+++ b/src/main/jbake/content/documentation/development/logging.md
@@ -562,6 +562,6 @@ You need to specify the location of logback.xml via
`org.apache.sling.commons.lo
[11]: http://www.slf4j.org/manual.html#mdc
[12]: http://sling.apache.org/downloads.cgi
[13]:
http://logback.qos.ch/apidocs/ch/qos/logback/classic/spi/ILoggingEvent.html
-[14]:
http://svn.apache.org/repos/asf/sling/trunk/contrib/extensions/logback-groovy-fragment/
+[14]:
https://github.com/apache/sling-org-apache-sling-extensions-logback-groovy-fragment
[15]: http://logback.qos.ch/manual/layouts.html#conversionWord
[SLING-6144]: https://issues.apache.org/jira/browse/SLING-6144
diff --git
a/src/main/jbake/content/documentation/development/maven-launchpad-plugin.md
b/src/main/jbake/content/documentation/development/maven-launchpad-plugin.md
index f7ba305..1f9f45c 100644
--- a/src/main/jbake/content/documentation/development/maven-launchpad-plugin.md
+++ b/src/main/jbake/content/documentation/development/maven-launchpad-plugin.md
@@ -5,8 +5,7 @@ tags=development,maven
~~~~~~
<div class="note">
-This page is out of sync with the latest maven-launchpad-plugin features and
settings. For now,
-refer to the source code and the launchpad/builder and launchpad/testing
modules for more information.
+The launchpad plugin has been retired in favour of the provisioning model and
associated tooling, see <a
href="http://sling.apache.org/documentation/development/slingstart.html";>the
provisioning model documentation</a>.
</div>
The Maven Launchpad Plugin provides goals which facilitate the creation of
OSGi applications. It supports the following runtime scenarios:
@@ -17,8 +16,8 @@ The Maven Launchpad Plugin provides goals which facilitate
the creation of OSGi
In addition, the Maven Launchpad Plugin supports the publishing of an
application descriptor, in the form of a *bundle list*, as a Maven artifact.
This descriptor can then be used by downstream application builders as the
basis for other applications. In Sling, this is embodied by two Maven projects:
- *
[org.apache.sling.launchpad](http://svn.apache.org/repos/asf/sling/trunk/launchpad/builder)
- produces an application descriptor.
- *
[org.apache.sling.launchpad.testing](http://svn.apache.org/repos/asf/sling/trunk/launchpad/testing/)
- uses the application descriptor from `org.apache.sling.launchpad` and adds
two bundles.
+ *
[org.apache.sling.launchpad](https://github.com/apache/sling-org-apache-sling-starter)
- produces an application descriptor.
+ *
[org.apache.sling.launchpad.testing](https://github.com/apache/sling-org-apache-sling-launchpad-testing)
- uses the application descriptor from `org.apache.sling.launchpad` and adds
two bundles.
Maven Launchpad Plugin provides the following goals:
diff --git a/src/main/jbake/content/documentation/development/maven-usage.md
b/src/main/jbake/content/documentation/development/maven-usage.md
index 0875ff2..8fd6ef0 100644
--- a/src/main/jbake/content/documentation/development/maven-usage.md
+++ b/src/main/jbake/content/documentation/development/maven-usage.md
@@ -8,7 +8,7 @@ Apache Sling uses Maven as a build tool. This page documents
some of the choices
## Parent POM
-We separate the reactor POM from the parent POM. While the reactor POM
functions as a simple aggregator, the parent POM, currently located at
[parent/pom.xml](http://svn.apache.org/repos/asf/sling/trunk/parent/pom.xml),
holds the common build configuration for all modules.
+We separate the reactor POM from the parent POM. While the reactor POM
functions as a simple aggregator, the parent POM, currently located at
[parent/pom.xml](https://github.com/apache/sling-parent/blob/master/pom.xml),
holds the common build configuration for all modules.
The reference to the parent POM is usually set to a released version since we
don't deploy it as a SNAPSHOT during the build process. That reference must
also contain an empty parentPath element, otherwise recent version of Maven
will try to find it in the local filesystem, disregarding the version if the
groupId and artifactId match. An example of how to reference the parent POM is
diff --git
a/src/main/jbake/content/documentation/development/release-management.md
b/src/main/jbake/content/documentation/development/release-management.md
index 4c4aab5..8bfadd6 100644
--- a/src/main/jbake/content/documentation/development/release-management.md
+++ b/src/main/jbake/content/documentation/development/release-management.md
@@ -116,6 +116,7 @@ Propose a vote on the dev list with the closed issues, the
issues left, and the
https://repository.apache.org/content/repositories/orgapachesling-[YOUR
REPOSITORY ID]/
You can use this UNIX script to download the release and verify the
signatures:
+ <!-- GIT-TODO - Reference the GitBox URL after migrating the
sling-tooling-release stuff -->
http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
Usage:
@@ -261,6 +262,8 @@ releases which are just announced on our [news](/news.html)
page.
## Releasing the Sling IDE Tooling
+<!-- GIT-TODO - update after releasing the IDE tooling from Git -->
+
While the Sling IDE tooling is built using Maven, the toolchain that it is
based around does not cooperate well with the maven-release-plugin. As such,
the release preparation and execution are slightly different. The whole process
is outlined below, assuming that we start with a development version of
1.0.1-SNAPSHOT.
1. set the fix version as released: `mvn tycho-versions:set-version
-DnewVersion=1.0.2`
@@ -374,18 +377,43 @@ Considering that you are using a \*nix system with a
working OpenSSH, GnuPG, and
$ gpg --keyserver pool.sks-keyservers.net --send-key <key-id>
+## Appendix B: Deploy Maven plugin documentation (if applicable)
+When releasing a Maven plugin, the Maven-generated documentation published
under
[http://sling.apache.org/components/](http://sling.apache.org/components/) needs
+to be updated.
-## Appendix B: Maven and SCM credentials
+This is currently supported for:
-For running the `mvn release:prepare` command without giving credentials on
command line add `svn.apache.org` to your `settings.xml`:
+* `maven-sling-plugin`
+* `htl-maven-plugin`
+* `slingstart-maven-plugin`
+* `jspc-maven-plugin`
+
+To publish the plugin documentation execute the following steps after the
release:
+
+1. Checkout the release tag of the released plugin (or reset your workspace)
+
+2. Build and stage the maven site of the plugin. Note that this *commits* the
generated content to the components folder mentioned below.
+
+ $ mvn clean site:site site:stage scm-publish:publish-scm
+
+3. Checkout the Sling website and navigate to the 'components' directory
+
+ $ git clone https://github.com/apache/sling-site.git
+ $ cd sling-site/src/main/jbake/assets/components/
+
+4. SVN-rename the generated documenation that the site plugin commited to
`<plugin-name>-archives/<plugin-name>-LATEST` to
`<plugin-name>-archives/<plugin-name>-<version>`
+
+5. SVN-remove the existing folder `<plugin-name>` and SVN-copy the folder
`<plugin-name>-archives/<plugin-name>-<version>` to `<plugin-name>`
+
+6. Commit the changes.
+
+7. Publish the Sling site to production
+
+8. Check the results at
[http://sling.apache.org/components/](http://sling.apache.org/components/)
+
+For background information about this process see the [Maven components
reference
documentation](http://maven.apache.org/developers/website/deploy-component-reference-documentation.html).
- <server>
- <id>svn.apache.org</id>
- <username>USERNAME</username>
- <password>ENCRYPTED_PASSWORD</password>
- </server>
-
## Appendix C: Deploy bundles on the Sling OBR (obsolete)
*Update November 2016: We do now longer maintain the Sling OBR for new
releases.*
@@ -440,40 +468,3 @@ To update the OBR you may use the Apache Felix Maven
Bundle Plugin which prepare
Wait for the buildbot to update the staging area with your site update
(see dev list for an email).
Then go to the CMS at
[https://cms.apache.org/redirect?uri=http://sling.apache.org/obr](https://cms.apache.org/redirect?uri=http://sling.apache.org/obr)
,
update your checkout and then publish the site.
-
-
-## Appendix D: Deploy Maven plugin documentation (if applicable)
-
-When releasing a Maven plugin, the Maven-generated documentation published
under
[http://sling.apache.org/components/](http://sling.apache.org/components/) needs
-to be updated.
-
-This is currently supported for:
-
-* `maven-sling-plugin`
-* `htl-maven-plugin`
-* `slingstart-maven-plugin`
-* `jspc-maven-plugin`
-
-To publish the plugin documentation execute the following steps after the
release:
-
-1. Checkout the release tag of the released plugin (or reset your workspace)
-
-2. Build and stage the maven site of the plugin. Note that this *commits* the
generated content to the components folder mentioned below.
-
- $ mvn clean site:site site:stage scm-publish:publish-scm
-
-3. Checkout the 'components' subtree of the Sling website
-
- $ svn checkout
https://svn.apache.org/repos/asf/sling/site/trunk/content/components
-
-4. SVN-rename the generated documenation that the site plugin commited to
`<plugin-name>-archives/<plugin-name>-LATEST` to
`<plugin-name>-archives/<plugin-name>-<version>`
-
-5. SVN-remove the existing folder `<plugin-name>` and SVN-copy the folder
`<plugin-name>-archives/<plugin-name>-<version>` to `<plugin-name>`
-
-6. Commit the changes.
-
-7. Publish the Sling site to production
-
-8. Check the results at
[http://sling.apache.org/components/](http://sling.apache.org/components/)
-
-For background information about this process see the [Maven components
reference
documentation](http://maven.apache.org/developers/website/deploy-component-reference-documentation.html).
diff --git a/src/main/jbake/content/documentation/development/sling-mock.md
b/src/main/jbake/content/documentation/development/sling-mock.md
index 2dcaf01..f0961df 100644
--- a/src/main/jbake/content/documentation/development/sling-mock.md
+++ b/src/main/jbake/content/documentation/development/sling-mock.md
@@ -440,13 +440,13 @@ More examples:
* [Apache Sling Context-Aware Configuration Mock Plugin][caconfig-mock-plugin]
* [Apache Sling Context-Aware Configuration Mock Plugin
Test][caconfig-mock-plugin-test]
-
+<!-- GIT-TODO - commons/testing is missing -->
[osgi-mock]: /documentation/development/osgi-mock.html
[jcr-mock]: /documentation/development/jcr-mock.html
[resourceresolver-mock]: /documentation/development/resourceresolver-mock.html
-[jcr-resource]:
http://svn.apache.org/repos/asf/sling/trunk/bundles/jcr/resource
+[jcr-resource]: https://github.com/apache/sling-org-apache-sling-jcr-resource
[sling-commons-testing]:
http://svn.apache.org/repos/asf/sling/trunk/bundles/commons/testing
[mockito-testrunner]:
http://mockito.github.io/mockito/docs/current/org/mockito/runners/MockitoJUnitRunner.html
-[caconfig-mock-plugin]:
https://github.com/apache/sling/blob/trunk/contrib/extensions/contextaware-config/testing/mocks/caconfig-mock-plugin/src/main/java/org/apache/sling/testing/mock/caconfig/ContextPlugins.java
-[caconfig-mock-plugin-test]:
https://github.com/apache/sling/blob/trunk/contrib/extensions/contextaware-config/testing/mocks/caconfig-mock-plugin/src/test/java/org/apache/sling/testing/mock/caconfig/ContextPluginsTest.java
+[caconfig-mock-plugin]:
https://github.com/apache/sling-org-apache-sling-testing-caconfig-mock-plugin/blob/master/src/main/java/org/apache/sling/testing/mock/caconfig/ContextPlugins.java
+[caconfig-mock-plugin-test]:
https://github.com/apache/sling-org-apache-sling-testing-caconfig-mock-plugin/blob/master/src/test/java/org/apache/sling/testing/mock/caconfig/ContextPluginsTest.java
diff --git
a/src/main/jbake/content/documentation/development/sling-testing-tools.md
b/src/main/jbake/content/documentation/development/sling-testing-tools.md
index 1049a76..c71dc58 100644
--- a/src/main/jbake/content/documentation/development/sling-testing-tools.md
+++ b/src/main/jbake/content/documentation/development/sling-testing-tools.md
@@ -19,18 +19,16 @@ Sling provides a number of testing tools to support the
following use cases:
This page describes those tools, and points to the bundles that implement them.
-The
[testing/samples/integration-tests](http://svn.apache.org/repos/asf/sling/trunk/testing/samples/integration-tests)
module demonstrates these tools, and is also meant as a sample project to show
how to run integration tests for Sling-based applications.
-
-The main Sling integration tests at
[launchpad/integration-tests](https://svn.apache.org/repos/asf/sling/trunk/launchpad/integration-tests)
were created before this testing framework, and do not use it yet (as of March
2011). The new testing tools are simpler to use, but the "old" tests (all 400
of them as I write this) fulfill their validation role for testing Sling
itself, there's no real need to modify them to use the new tools.
+The main Sling integration tests at
[launchpad/integration-tests](https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests)
were created before this testing framework, and do not use it yet (as of March
2011). The new testing tools are simpler to use, but the "old" tests (all 400
of them as I write this) fulfill their validation role for testing Sling
itself, there's no real need to modify them to use the new tools.
See also [Testing Sling-based
applications](/documentation/tutorials-how-tos/testing-sling-based-applications.html)
which discusses testing in general.
## Required bundles
-These tools require a number of bundles on top of the standard Sling
launchpad. See the [sample tests
pom.xml](http://svn.apache.org/repos/asf/sling/trunk/testing/samples/integration-tests/pom.xml)
+These tools require a number of bundles on top of the standard Sling
launchpad. See the for instance [Sling Models IT
pom.xml](https://github.com/apache/sling-org-apache-sling-models-integration-tests/blob/master/pom.xml)
for an up-to-date list. Look for `sling.additional.bundle.*` entries in that
pom for the bundle artifact IDs, and see the `dependencies` section for their
version numbers.
# Server-side JUnit tests contributed by bundles
-The services provided by the
[org.apache.sling.junit.core](http://svn.apache.org/repos/asf/sling/trunk/testing/junit/core)
bundle allow bundles to register JUnit tests, which are executed server-side
by the JUnitServlet registered by default at `/system/sling/junit`. This bundle
is not dependent on Sling, it should work in other OSGi environments.
+The services provided by the
[org.apache.sling.junit.core](https://github.com/apache/sling-org-apache-sling-junit-core)
bundle allow bundles to register JUnit tests, which are executed server-side
by the JUnitServlet registered by default at `/system/sling/junit`. This bundle
is not dependent on Sling, it should work in other OSGi environments.
<div class="warning">
Note that the JUnitServlet does not require authentication, so it would allow
any client to run tests. The servlet can be disabled by configuration if
needed, but in general the `/system` path should not be accessible to website
visitors anyway.
@@ -75,14 +73,12 @@ And another example with a test that fails:
$ curl -X POST
http://localhost:8080/system/sling/junit/org.apache.sling.testing.samples.failingtests.JUnit4FailingTest.json
# Scriptable server-side tests
-If the
[org.apache.sling.junit.scriptable](http://svn.apache.org/repos/asf/sling/trunk/testing/junit/scriptable)
bundle is active in a Sling system, (in addition to the
`org.apache.sling.junit.core` bundle), scriptable tests can be executed by the
`JUnitServlet` according to the following rules:
+If the
[org.apache.sling.junit.scriptable](https://github.com/apache/sling-org-apache-sling-junit-scriptable)
bundle is active in a Sling system, (in addition to the
`org.apache.sling.junit.core` bundle), scriptable tests can be executed by the
`JUnitServlet` according to the following rules:
* A node that has the `sling:Test` mixin is a scriptable test node.
* For security reasons, scriptable test nodes are only executed as tests if
they are found under `/libs` or `/apps`, or more precisely under a path that's
part of Sling's `ResourceResolver` search path.
* To execute a test, the scriptable tests provider makes an HTTP request to
the test node's path, with a `.test.txt` selector and extension, and expects
the output to contain only the string `TEST_PASSED`. Empty lines and comment
lines starting with a hash sign (#) are ignored in the output, and other lines
are reported as failures.
-The
[ScriptableTestsTest](http://svn.apache.org/repos/asf/sling/trunk/testing/samples/integration-tests/src/test/java/org/apache/sling/testing/samples/integrationtests/serverside/scriptable/ScriptableTestsTest.java)
class, from the integration test samples module described below, sets up such
a test node and its accompanying script, and calls the JUnitServlet to execute
the test. It can be used as a detailed example of how this works.
-
Here's a minimal example that sets up and executes a scriptable test:
$ curl -u admin:admin -Fjcr:primaryNodeType=sling:Folder
-Fsling:resourceType=foo -Fjcr:mixinTypes=sling:Test
http://localhost:8080/apps/foo
diff --git
a/src/main/jbake/content/documentation/getting-started/discover-sling-in-15-minutes.md
b/src/main/jbake/content/documentation/getting-started/discover-sling-in-15-minutes.md
index f7cb5d8..f6be6d9 100644
---
a/src/main/jbake/content/documentation/getting-started/discover-sling-in-15-minutes.md
+++
b/src/main/jbake/content/documentation/getting-started/discover-sling-in-15-minutes.md
@@ -19,9 +19,8 @@ While simple to run and understand, the Launchpad is a
full-featured instance of
## See Also
-
More Sling samples can be found under
-[http://svn.apache.org/repos/asf/sling/trunk/samples/](http://svn.apache.org/repos/asf/sling/trunk/samples/)
+[https://github.com/apache/sling-samples/](https://github.com/apache/sling-samples/)
Once you grok the basic examples of this page, we recommend studying the
*slingbucks* and *espblog* samples. Both have README files with more info.
diff --git a/src/main/jbake/content/documentation/pax-exam-utils.md
b/src/main/jbake/content/documentation/pax-exam-utils.md
index a738f76..929819a 100644
--- a/src/main/jbake/content/documentation/pax-exam-utils.md
+++ b/src/main/jbake/content/documentation/pax-exam-utils.md
@@ -5,11 +5,11 @@ tags=development,testing
~~~~~~
Utilities to help testing Sling components with Pax Exam are available at
-[https://svn.apache.org/repos/asf/sling/trunk/testing/sling-pax-util](https://svn.apache.org/repos/asf/sling/trunk/testing/sling-pax-util)
+[https://github.com/apache/sling-org-apache-sling-paxexam-util](https://github.com/apache/sling-org-apache-sling-paxexam-util)
The focus is on making it easier to test Sling components against a full Sling
launchpad,
with minimal boilerplate code.
See the
-[SlingRepositoryTest](https://svn.apache.org/repos/asf/sling/trunk/testing/sling-pax-util/src/test/java/org/apache/sling/paxexam/util/SlingRepositoryTest.java)
class
+[SlingRepositoryTest](https://github.com/apache/sling-org-apache-sling-paxexam-util/blob/master/src/test/java/org/apache/sling/paxexam/util/SlingRepositoryTest.java)
class
for an example test.
diff --git
a/src/main/jbake/content/documentation/the-sling-engine/authentication/authentication-actors.md
b/src/main/jbake/content/documentation/the-sling-engine/authentication/authentication-actors.md
index c563153..d257796 100644
---
a/src/main/jbake/content/documentation/the-sling-engine/authentication/authentication-actors.md
+++
b/src/main/jbake/content/documentation/the-sling-engine/authentication/authentication-actors.md
@@ -45,7 +45,7 @@ The actual process of logging into the repository and
provided a `Session` is im
The Sling Jackrabbit Embedded Repository bundle provides additional plugin
interfaces to extend the login process dynamically using OSGi services. To this
avail the bundle configures a `LoginModule` with the provided default
Jackrabbit configuration supporting these plugins:
- * `LoginModulePlugin` -- The main service interface. Plugins must implement
this interface to be able to extend the login process. See for example the
[Sling OpenID authentication
handler](http://svn.apache.org/repos/asf/sling/trunk/bundles/auth/openid/),
which implements this interface to support OpenID authentication.
+ * `LoginModulePlugin` -- The main service interface. Plugins must implement
this interface to be able to extend the login process.
* `AuthenticationPlugin` -- Helper interface for the `LoginModulePlugin`.
diff --git
a/src/main/jbake/content/documentation/the-sling-engine/authentication/authentication-authenticationhandler/form-based-authenticationhandler.md
b/src/main/jbake/content/documentation/the-sling-engine/authentication/authentication-authenticationhandler/form-based-authenticationhandler.md
index 151669c..c70813c 100644
---
a/src/main/jbake/content/documentation/the-sling-engine/authentication/authentication-authenticationhandler/form-based-authenticationhandler.md
+++
b/src/main/jbake/content/documentation/the-sling-engine/authentication/authentication-authenticationhandler/form-based-authenticationhandler.md
@@ -13,7 +13,7 @@ The implementation of the Form Based Authentication Handler
follows the guidelin
* For the initial form submission, the request URL must end with
`/j_security_check` and the user name and password names must be `j_username`
and `j_password`, resp.
* The authentication type as returned by `HttpServletRequest.getAuthType()` is
set to `HttpServletRequest.FORM_AUTH`.
-The Form Based Authentication Handler is maintained in the [Sling
SVN](http://svn.apache.org/repos/asf/sling/trunk/bundles/auth/form)
+The Form Based Authentication Handler is maintained in the [the Sling
repo](https://github.com/apache/sling-org-apache-sling-auth-form).
### AuthenticationHandler implementation
@@ -66,7 +66,7 @@ If the `j_validate` parameter is not set or is set to any
value other than `true
The `resource` and `sling.auth.redirect` parameters provide similar
functionality but with differing historical backgrounds. The `resource`
parameter is based on the `resource` request attribute which is set by the
login servlet to indicate the original target resource the client desired when
it was forced to authenticate. The `sling.auth.redirect` parameter can be used
by clients (applications like cURL or plain HTML forms) to request being
redirected after successful login. If both par [...]
-The Form Based Authentication Handler contains a [default form
servlet](http://svn.apache.org/repos/asf/sling/trunk/bundles/auth/form/src/main/java/org/apache/sling/auth/form/impl/AuthenticationFormServlet.java)
and [HTML form
template](http://svn.apache.org/repos/asf/sling/trunk/bundles/auth/form/src/main/resources/org/apache/sling/auth/form/impl/login.html).
+The Form Based Authentication Handler contains a [default form
servlet](https://github.com/apache/sling-org-apache-sling-auth-form/blob/master/src/main/java/org/apache/sling/auth/form/impl/AuthenticationFormServlet.java)
and [HTML form
template](https://github.com/apache/sling-org-apache-sling-auth-form/blob/master/src/main/resources/org/apache/sling/auth/form/impl/login.html).
### Phase 2: Authenticated Requests
diff --git
a/src/main/jbake/content/documentation/the-sling-engine/authentication/authentication-authenticationhandler/openid-authenticationhandler.md
b/src/main/jbake/content/documentation/the-sling-engine/authentication/authentication-authenticationhandler/openid-authenticationhandler.md
index 5523d6e..53261e2 100644
---
a/src/main/jbake/content/documentation/the-sling-engine/authentication/authentication-authenticationhandler/openid-authenticationhandler.md
+++
b/src/main/jbake/content/documentation/the-sling-engine/authentication/authentication-authenticationhandler/openid-authenticationhandler.md
@@ -6,15 +6,16 @@ tags=core,authentication,openid
[TOC]
+<div class="note">
+This module has been deprecated and retired. It can be found in the <a
href="https://svn.apache.org/repos/asf/sling/attic/openid/";>Sling attic: OpenID
module</a> but is no longer maintained or supported.
+</div>
+
The OpenID Authentication Handler supports authentication of request users
using the [OpenID](http://www.openid.net) authentication protocol. If the user
has successfully authenticated with his OpenID provider a signed OpenID
identity is further used to identify the user.
Since generally an OpenID identity is an URL and URLs may not be used as JCR
user names, an association mechanism is used by the OpenID authentication
handler to associate an OpenID identity with an existing JCR user: The OpenID
identity URL is set as the value of a JCR user property. When a user
authenticates with his OpenID identity the matching user searched for by
looking for a match in this property.
*NOTE:* This association currently only works with Jackrabbit (or Jackrabbit
based repositories) because user management is not part of the JCR 2
specification and the OpenID authentication handler uses the Jackrabbit
`UserManager` to find users by a user property value.
-The OpenID Authentication Handler is maintained in the [Sling
SVN](http://svn.apache.org/repos/asf/sling/trunk/bundles/auth/openid/)
-
-
### Credentials Extraction
Theoretically each request with the `openid_identifier` request parameter set
may initiate an OpenID authentication process which involves resolving the
OpenID provider for the identifier and subsequently authentication with the
provider authorizing the Sling instance to use the OpenID identity.
diff --git
a/src/main/jbake/content/documentation/the-sling-engine/errorhandling.md
b/src/main/jbake/content/documentation/the-sling-engine/errorhandling.md
index 271424e..03ce1a8 100644
--- a/src/main/jbake/content/documentation/the-sling-engine/errorhandling.md
+++ b/src/main/jbake/content/documentation/the-sling-engine/errorhandling.md
@@ -67,4 +67,4 @@ Starting with Sling Servlet Resolver version 2.0.10 the
default error handler se
Thus to overwrite the default error handler servlet provide a servlet or
script for the `default` extension, for example
`/apps/sling/servlet/errorhandler/default.groovy`.
- [1]:
https://svn.apache.org/repos/asf/sling/trunk/launchpad/integration-tests/src/main/java/org/apache/sling/launchpad/webapp/integrationtest/servlets/resolver/errorhandler/ErrorHandlingTest.java
+ [1]:
https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/blob/master/src/main/java/org/apache/sling/launchpad/webapp/integrationtest/servlets/resolver/errorhandler/ErrorHandlingTest.java
diff --git a/src/main/jbake/content/documentation/the-sling-engine/filters.md
b/src/main/jbake/content/documentation/the-sling-engine/filters.md
index 93072d0..c172e1f 100644
--- a/src/main/jbake/content/documentation/the-sling-engine/filters.md
+++ b/src/main/jbake/content/documentation/the-sling-engine/filters.md
@@ -11,7 +11,7 @@ See <a
href="https://issues.apache.org/jira/browse/SLING-1213";>SLING-1213</a>,
<a href="https://issues.apache.org/jira/browse/SLING-1734";>SLING-1734</a>, and
<a href="http://markmail.org/message/quxhm7d5s6u66crr";>Registering filters
with Sling</a>
for more details. The
-<a
href="https://svn.apache.org/repos/asf/sling/trunk/launchpad/test-services/src/main/java/org/apache/sling/launchpad/testservices/filters/NoPropertyFilter.java";>NoPropertyFilter</a>
+<a
href="https://github.com/apache/sling-org-apache-sling-launchpad-test-services/blob/master/src/main/java/org/apache/sling/launchpad/testservices/filters/NoPropertyFilter.java";>NoPropertyFilter</a>
from our integration tests shows an example Sling Filter.
</div>
diff --git a/src/main/jbake/content/documentation/the-sling-engine/resources.md
b/src/main/jbake/content/documentation/the-sling-engine/resources.md
index 05f612e..3b33101 100644
--- a/src/main/jbake/content/documentation/the-sling-engine/resources.md
+++ b/src/main/jbake/content/documentation/the-sling-engine/resources.md
@@ -178,9 +178,9 @@ The Sling API provides an easy way to wrap or decorate a
resource before returni
[1]:
http://sling.apache.org/apidocs/sling8/org/apache/sling/api/resource/ResourceMetadata.html
"ResourceMetadata"
[2]:
http://sling.apache.org/apidocs/sling8/org/apache/sling/api/resource/Resource.html
"Resource"
[3]:
http://sling.apache.org/apidocs/sling8/org/apache/sling/api/resource/AbstractResource.html
"AbstractResource"
- [4]:
https://svn.apache.org/repos/asf/sling/trunk/launchpad/test-services/src/main/java/org/apache/sling/launchpad/testservices/resourceprovider/
- [5]:
https://svn.apache.org/repos/asf/sling/trunk/launchpad/test-services/src/main/java/org/apache/sling/launchpad/testservices/serversidetests/WriteableResourcesTest.java
- [6]:
https://svn.apache.org/repos/asf/sling/trunk/bundles/api/src/main/java/org/apache/sling/api/resource/observation/ResourceChangeListener.java
- [7]:
https://svn.apache.org/repos/asf/sling/trunk/bundles/api/src/main/java/org/apache/sling/api/resource/observation/ExternalResourceChangeListener.java
+ [4]:
https://github.com/apache/sling-org-apache-sling-launchpad-test-services/tree/master/src/main/java/org/apache/sling/launchpad/testservices/resourceprovider
+ [5]:
https://github.com/apache/sling-org-apache-sling-launchpad-test-services/blob/master/src/main/java/org/apache/sling/launchpad/testservices/serversidetests/WriteableResourcesTest.java
+ [6]:
https://github.com/apache/sling-org-apache-sling-api/blob/master/src/main/java/org/apache/sling/api/resource/observation/ResourceChangeListener.java
+ [7]:
https://github.com/apache/sling-org-apache-sling-api/blob/master/src/main/java/org/apache/sling/api/resource/observation/ExternalResourceChangeListener.java
[8]:
https://osgi.org/javadoc/r6/cmpn/org/osgi/service/event/EventHandler.html
[9]:
http://sling.apache.org/apidocs/sling8/org/apache/sling/api/SlingConstants.html
diff --git a/src/main/jbake/content/documentation/the-sling-engine/servlets.md
b/src/main/jbake/content/documentation/the-sling-engine/servlets.md
index 95490cd..e5dd307 100644
--- a/src/main/jbake/content/documentation/the-sling-engine/servlets.md
+++ b/src/main/jbake/content/documentation/the-sling-engine/servlets.md
@@ -90,9 +90,9 @@ The following examples show example code how you can register
Servlets with Slin
### Automated tests
-The
[launchpad/test-services](http://svn.apache.org/repos/asf/sling/trunk/launchpad/test-services/)
module contains test servlets that use various combinations of the above
properties.
+The
[launchpad/test-services](https://github.com/apache/sling-org-apache-sling-launchpad-test-services)
module contains test servlets that use various combinations of the above
properties.
-The
[launchpad/integration-tests](http://svn.apache.org/repos/asf/sling/trunk/launchpad/integration-tests/)
module contains a number of tests (like the
[ExtensionServletTest|http://svn.apache.org/repos/asf/sling/trunk/launchpad/integration-tests/src/main/java/org/apache/sling/launchpad/webapp/integrationtest/servlets/resolution/ExtensionServletTest.java]
for example) that verify the results.
+The
[launchpad/integration-tests](https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests)
module contains a number of tests (like the
[ExtensionServletTest|https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/blob/master/src/main/java/org/apache/sling/launchpad/webapp/integrationtest/servlets/resolution/ExtensionServletTest.java]
for example) that verify the results.
Such tests run as part of our continuous integration process, to demonstrate
and verify the behavior of the various servlet registration mechanisms, in a
way that's guaranteed to be in sync with the actual Sling core code. If you
have an idea for additional tests, make sure to let us know!
diff --git
a/src/main/jbake/content/documentation/the-sling-engine/the-sling-launchpad.md
b/src/main/jbake/content/documentation/the-sling-engine/the-sling-launchpad.md
index 5b82c7b..e10a6a4 100644
---
a/src/main/jbake/content/documentation/the-sling-engine/the-sling-launchpad.md
+++
b/src/main/jbake/content/documentation/the-sling-engine/the-sling-launchpad.md
@@ -64,7 +64,7 @@ Currently supported commands are
* `status` to get the instance status (OK or STOPPING)
* `threads` to get a thread dump
-For the Whole Truth about this functionality see the [ControlListener class
source
code](https://svn.apache.org/repos/asf/sling/trunk/launchpad/base/src/main/java/org/apache/sling/launchpad/app/ControlListener.java).
+For the Whole Truth about this functionality see the [ControlListener class
source
code](https://github.com/apache/sling-org-apache-sling-launchpad-base/blob/master/src/main/java/org/apache/sling/launchpad/app/ControlListener.java).
The interface and port is configurable with the `-j` command line option. The
actual address and port used are written to the
`$\{sling.home}/conf/controlport` file. So technically the `-j` option is not
required for the `status` and `stop` operations because the port information
can be read from that file.
diff --git
a/src/main/jbake/content/documentation/the-sling-engine/url-decomposition.md
b/src/main/jbake/content/documentation/the-sling-engine/url-decomposition.md
index 2e3b1bf..724821e 100644
--- a/src/main/jbake/content/documentation/the-sling-engine/url-decomposition.md
+++ b/src/main/jbake/content/documentation/the-sling-engine/url-decomposition.md
@@ -44,7 +44,7 @@ Assume there is a Resource at `/a/b`, which has no children.
The tests at
-*
[ResourceResolverImplTest](http://svn.apache.org/repos/asf/sling/trunk/bundles/resourceresolver/src/test/java/org/apache/sling/resourceresolver/impl/ResourceResolverImplTest.java)
shows the split between resource path and the rest. Mostly in the method
`testBasicAPIAssumptions`.
-*
[SlingRequestPathInfoTest](http://svn.apache.org/repos/asf/sling/trunk/bundles/engine/src/test/java/org/apache/sling/engine/impl/request/SlingRequestPathInfoTest.java)
demonstrates the decomposition after the resource path part.
+*
[ResourceResolverImplTest](https://github.com/apache/sling-org-apache-sling-resourceresolver/blob/master/src/test/java/org/apache/sling/resourceresolver/impl/ResourceResolverImplTest.java)
shows the split between resource path and the rest. Mostly in the method
`testBasicAPIAssumptions`.
+*
[SlingRequestPathInfoTest](https://github.com/apache/sling-org-apache-sling-engine/blob/master/src/test/java/org/apache/sling/engine/impl/request/SlingRequestPathInfoTest.java)
demonstrates the decomposition after the resource path part.
Feel free to suggest additional tests that help clarify how this works!
diff --git
a/src/main/jbake/content/documentation/the-sling-engine/url-to-script-resolution.md
b/src/main/jbake/content/documentation/the-sling-engine/url-to-script-resolution.md
index 24b6f8f..3dfa77a 100644
---
a/src/main/jbake/content/documentation/the-sling-engine/url-to-script-resolution.md
+++
b/src/main/jbake/content/documentation/the-sling-engine/url-to-script-resolution.md
@@ -18,7 +18,7 @@ Scripts and servlets are itself resources in Sling and thus
have a resource path
JCR repository, the resource type in a servlet component configuration or the
"virtual" bundle resource path
(if a script is provided inside a bundle without being installed into the JCR
repository).
-For the whole Truth about script resolution, see the
[ScriptSelectionTest](http://svn.apache.org/repos/asf/sling/trunk/bundles/servlets/resolver/src/test/java/org/apache/sling/servlets/resolver/internal/helper/ScriptSelectionTest.java)
class. If you see interesting cases that are not
+For the whole Truth about script resolution, see the
[ScriptSelectionTest](https://github.com/apache/sling-org-apache-sling-servlets-resolver/blob/master/src/test/java/org/apache/sling/servlets/resolver/internal/helper/ScriptSelectionTest.java)
class. If you see interesting cases that are not
covered there, please let us know via the Sling users mailing list.
TODO: explain super types, servlet path mappings, node type resource types
(`my:type -> my/type`)
diff --git
a/src/main/jbake/content/documentation/tutorials-how-tos/46-line-blog.md
b/src/main/jbake/content/documentation/tutorials-how-tos/46-line-blog.md
index df09a52..9f7832c 100644
--- a/src/main/jbake/content/documentation/tutorials-how-tos/46-line-blog.md
+++ b/src/main/jbake/content/documentation/tutorials-how-tos/46-line-blog.md
@@ -18,7 +18,7 @@ Although this is a simple sample, it requires some custom
settings to work. If y
See [Getting and Building
Sling](/documentation/development/getting-and-building-sling.html) for how to
start Sling. Start it on port 8080 for the below links to work.
-For this sample we need the optional *org.apache.sling.samples.path-based.rtp*
bundle, if it's not present in the [OSGi
console](http://localhost:8080/system/console/bundles), install and start it.
That bundle is not released yet so you might need to build it yourself, from
its
[source](http://svn.apache.org/repos/asf/sling/trunk/samples/path-based-rtp).
The bundle must then appear in the [OSGI console's list of
bundles](http://localhost:8080/system/console/bundles), with name = *org.apa
[...]
+For this sample we need the optional *org.apache.sling.samples.path-based.rtp*
bundle, if it's not present in the [OSGi
console](http://localhost:8080/system/console/bundles), install and start it.
That bundle is not released yet so you might need to build it yourself, from
its
[source](https://github.com/apache/sling-samples/tree/master/path-based-rtp).
The bundle must then appear in the [OSGI console's list of
bundles](http://localhost:8080/system/console/bundles), with name = *org.apa
[...]
Then, login using <http://localhost:8080/?sling:authRequestLogin=1> which
should prompt you for a username and password, use *admin* and *admin*. Once
that's done, <http://localhost:8080/index.html> should say *You are currently
logged in as user *admin* to workspace *default**.
@@ -155,7 +155,7 @@ To keep things simple, we'll refrain from adding ESP-based
features at this poin
## That's the power of Sling
-The 46-line blog is a good example of the power of Sling. It leverages the
[SlingPostServlet](/documentation/bundles/manipulating-content-the-slingpostservlet-servlets-post.html),
which handles POST requests in a form-friendly way, and the
[`sling.js`](http://svn.apache.org/repos/asf/sling/trunk/bundles/servlets/post/src/main/resources/system/sling.js)
client library, which provides high-level functionality on the client side.
+The 46-line blog is a good example of the power of Sling. It leverages the
[SlingPostServlet](/documentation/bundles/manipulating-content-the-slingpostservlet-servlets-post.html),
which handles POST requests in a form-friendly way, and the
[`sling.js`](https://github.com/apache/sling-org-apache-sling-servlets-post/blob/master/src/main/resources/system/sling.js)
client library, which provides high-level functionality on the client side.
///Footnotes Go Here///
diff --git
a/src/main/jbake/content/documentation/tutorials-how-tos/jackrabbit-persistence.md
b/src/main/jbake/content/documentation/tutorials-how-tos/jackrabbit-persistence.md
index 455b76f..7a2bd04 100644
---
a/src/main/jbake/content/documentation/tutorials-how-tos/jackrabbit-persistence.md
+++
b/src/main/jbake/content/documentation/tutorials-how-tos/jackrabbit-persistence.md
@@ -4,6 +4,12 @@ status=published
tags=jcr,jackrabbit,repository
~~~~~~
+<div class="note">
+Recent versions of Apache Sling no longer use Apache Jackrabbit as their
persistence engine, but
+Apache Jackrabbit Oak. Oak is configured in a different, more OSGi-friendly
way. For more details,
+see <a href="http://jackrabbit.apache.org/oak/docs/";>The Jackrabbit Oak
documentation</a>. The Jackrabbit integration has also been moved to the attic
and is no longer maintained.
+</div>
+
Out-of-the-box the embedded Jackrabbit repository used by Sling (the Embedded
Jackrabbit Repository bundle) uses Derby to persist the JCR nodes and
properties. For some applications or environments it may be required or
required to replace Derby with another backing store such as PostgreSQL or
Oracle.
This page is based on the journey of Tony Giaccone to get Sling running with a
PostgreSQL based Jackrabbit instance.
@@ -62,7 +68,7 @@ Alternatively, you may wish to stop Sling after uninstalling
Derby and installin
To actually use a persistence manager other than the default (Derby)
persistence manager, you have to configure Jackrabbit to use it. Create a
`repository.xml` file in the `sling/jackrabbit` folder before starting Sling
for the first time. If the repository was already started, you can also modify
the existing file.
-To prepare a repository.xml file before first startup, use the
[`repository.xml`](http://svn.apache.org/repos/asf/sling/trunk/bundles/jcr/jackrabbit-server/src/main/resources/repository.xml)
as a template and modify it by replacing the `<PersistenceManager>` elements
to refer to the selected persistence manager.
+To prepare a repository.xml file before first startup, use the
[`repository.xml`](https://svn.apache.org/repos/asf/sling/attic/jackrabbit-server/src/main/resources/repository.xml)
as a template and modify it by replacing the `<PersistenceManager>` elements
to refer to the selected persistence manager.
If the file already exists, you can modifiy this existing file and there is no
need to get the original from the SVN repository.
diff --git
a/src/main/jbake/content/documentation/tutorials-how-tos/testing-sling-based-applications.md
b/src/main/jbake/content/documentation/tutorials-how-tos/testing-sling-based-applications.md
index b5dc338..ae02ca7 100644
---
a/src/main/jbake/content/documentation/tutorials-how-tos/testing-sling-based-applications.md
+++
b/src/main/jbake/content/documentation/tutorials-how-tos/testing-sling-based-applications.md
@@ -18,6 +18,7 @@ We have quite a lot of those in Sling, the older use the
JUnit3 TestCase base cl
## Tests that use a JCR repository
+<!-- GIT-TODO commons/testing not migrated -->
Utility classes from our
[commons/testing](https://svn.apache.org/repos/asf/sling/trunk/bundles/commons/testing)
module make it easy to get a real JCR repository for testing. That's a bit
slower than pure unit tests, of course, but this only adds 1-2 seconds to the
execution of a test suite.
The `RepositoryProviderTest` in that module uses this technique to get a JCR
repository.
@@ -30,7 +31,7 @@ The next step is to use mock classes and services to simulate
components that ar
The [Development](/documentation/development.html) documentation page contains
a section "Testing Sling-based Applications" lising all mock implementations
available as part of the Apache Sling project.
-In other cases we use [jmock](http://www.jmock.org/) or [Mockito][1] to help
create mock objects without having to write much code - such mocking libraries
take care of the plumbing and allow you to write just the bits of code that
matter (often with funny syntaxes). The tests of the
[org.apache.sling.event](https://svn.apache.org/repos/asf/sling/trunk/bundles/extensions/event/)
bundle, for example, make extensive use of such mock services.
+In other cases we use [jmock](http://www.jmock.org/) or [Mockito][1] to help
create mock objects without having to write much code - such mocking libraries
take care of the plumbing and allow you to write just the bits of code that
matter (often with funny syntaxes). The tests of the
[org.apache.sling.event](https://github.com/apache/sling-org-apache-sling-event)
bundle, for example, make extensive use of such mock services.
The problem with mocks is that it can become hard to make sure you're actually
testing something, and not just "mocking mocks". At a certain level of
complexity, it becomes quicker and clearer to actually start an OSGi framework
for automated tests.
@@ -54,7 +55,7 @@ such as the
[PrivateAccessor](http://junit-addons.sourceforge.net/junitx/util/Pr
[Pax Exam](http://team.ops4j.org/wiki/display/paxexam/Pax+Exam) allows you to
easily start an OSGi framework during execution of a JUnit test suite.
-We currently use it for our [Sling installer integration
tests](https://svn.apache.org/repos/asf/sling/trunk/installer/it) for example.
As parts of the installer interact directly with the OSGi framework, it felt
safer to test it in a realistic situation rather than mock everything.
+We currently use it for our [Sling installer integration
tests](https://github.com/apache/sling-org-apache-sling-installer-it) for
example. As parts of the installer interact directly with the OSGi framework,
it felt safer to test it in a realistic situation rather than mock everything.
Such tests are obviously slower than plain unit tests and tests that use
mocks. Our installer integration tests, using Pax Exam, take about a minute to
execute on a 2010 macbook pro.
@@ -64,8 +65,8 @@ The tools described on the [JUnit server-side testing
support](/documentation/bu
running JUnit tests on an live Sling instance, as part of the normal
integration testing cycle.
## HTTP-based integration tests
-The [Sling HTTP Testing
Rules](https://svn.apache.org/repos/asf/sling/trunk/testing/junit/rules) allow
writing integration tests easily. They are primarily meant to be used for tests
that use http against
-a Sling instance and make use of the
[org.apache.sling.testing.clients](https://svn.apache.org/repos/asf/sling/trunk/testing/http/clients)
which offer a simple, immutable and extendable way of working
+The [Sling HTTP Testing
Rules](https://github.com/apache/sling-org-apache-sling-testing-rules) allow
writing integration tests easily. They are primarily meant to be used for tests
that use http against
+a Sling instance and make use of the
[org.apache.sling.testing.clients](https://github.com/apache/sling-org-apache-sling-testing-clients)
which offer a simple, immutable and extendable way of working
with specialized testing clients.
The JUnit rules incorporate boiler-plate logic that is shared in tests and
take the modern approach of using rules rather than
@@ -79,8 +80,8 @@ Starting an integration is very simple out of the box, but is
very extendable, b
using the versatile `SlingClient` (which can be extended or adapted by calling
`adaptTo(MyClient.class)` without losing the client
configuration)
-The
[README](https://svn.apache.org/repos/asf/sling/trunk/testing/junit/rules/README.md)
provides more detail, as do [the
tests](https://svn.apache.org/repos/asf/sling/trunk/testing/junit/rules/src/test/java).
-The [Sling HTTP Testing
Clients](https://svn.apache.org/repos/asf/sling/trunk/testing/http/clients)
provide simple explanations, and unit tests.
+The
[README](https://github.com/apache/sling-org-apache-sling-testing-rules/blob/master/README.md)
provides more detail, as do [the
tests](https://github.com/apache/sling-org-apache-sling-testing-rules/tree/master/src/test/java).
+The [Sling HTTP Testing
Clients](https://github.com/apache/sling-org-apache-sling-testing-clients)
provide simple explanations, and unit tests.
#### Maven Dependency
#!xml
diff --git a/src/main/jbake/content/news.md b/src/main/jbake/content/news.md
index 3347c05..c9c3952 100644
--- a/src/main/jbake/content/news.md
+++ b/src/main/jbake/content/news.md
@@ -4,6 +4,7 @@ status=published
tags=news
tableOfContents=false
~~~~~~
+* Sling has moved to Git (October 20, 2017)
* The [adaptTo() 2017 conference](https://adapt.to/2017/en.html) took place in
Berlin. (September 25-27, 2017).
* Released [Apache Sling 9](/news/sling-launchpad-9-released.html) (June 12th,
2017)
* The [adaptTo() 2016 conference](https://adapt.to/2016/en.html) took place in
Berlin. (September 26-28, 2016).
--
To stop receiving notification emails like this one, please contact
['"[email protected]" <[email protected]>'].
