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 42e8f19  SLING-7161 - Update site to reference git instead of svn
42e8f19 is described below

commit 42e8f19ab078a3a96ac606a8a3f7eb65a74da47c
Author: Robert Munteanu <[email protected]>
AuthorDate: Wed Nov 22 23:22:38 2017 +0200

    SLING-7161 - Update site to reference git instead of svn
    
    Cleanup more SVN references after migrating identified leftover repos.
---
 src/main/jbake/content/documentation.md                               | 3 +--
 src/main/jbake/content/documentation/bundles/caching-services.md      | 2 +-
 .../content/documentation/bundles/org-apache-sling-junit-bundles.md   | 3 +--
 .../jbake/content/documentation/development/release-management.md     | 3 +--
 src/main/jbake/content/documentation/development/sling-mock.md        | 4 +---
 .../tutorials-how-tos/testing-sling-based-applications.md             | 3 +--
 6 files changed, 6 insertions(+), 12 deletions(-)

diff --git a/src/main/jbake/content/documentation.md 
b/src/main/jbake/content/documentation.md
index 982a916..6a6867f 100644
--- a/src/main/jbake/content/documentation.md
+++ b/src/main/jbake/content/documentation.md
@@ -49,9 +49,8 @@ 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`
+The script for generating this aggregation JavaDoc is in the 
sling-tooling-release repo, at 
[generate_javadoc_for_release.sh](https://github.com/apache/sling-tooling-release/blob/master/generate_javadoc_for_release.sh).
 
 In addition every released bundle is released together with its JavaDoc (which 
is also pushed to Maven Central).
 
diff --git a/src/main/jbake/content/documentation/bundles/caching-services.md 
b/src/main/jbake/content/documentation/bundles/caching-services.md
index 11522e3..51dd8d3 100644
--- a/src/main/jbake/content/documentation/bundles/caching-services.md
+++ b/src/main/jbake/content/documentation/bundles/caching-services.md
@@ -8,6 +8,6 @@ Caching services are available under multiple repositories at 
[https://github.co
 
 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 -->
+<!-- GIT-TODO portal stuff must be moved to the Git whiteboard -->
 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/org-apache-sling-junit-bundles.md
 
b/src/main/jbake/content/documentation/bundles/org-apache-sling-junit-bundles.md
index 569ca18..74485d9 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
@@ -140,8 +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:
+*[DefaultPropertyBasedCustomizer.java](https://github.com/apache/sling-org-apache-sling-junit-teleporter/blob/master/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 |
 
|------------------------------|-------------------------------------------------|------------------|
 ----- | ---| --- |
diff --git 
a/src/main/jbake/content/documentation/development/release-management.md 
b/src/main/jbake/content/documentation/development/release-management.md
index 8bfadd6..70523ff 100644
--- a/src/main/jbake/content/documentation/development/release-management.md
+++ b/src/main/jbake/content/documentation/development/release-management.md
@@ -116,8 +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
+    
https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blob;f=check_staged_release.sh;hb=HEAD
     
     Usage:
     sh check_staged_release.sh [YOUR REPOSITORY ID] /tmp/sling-staging
diff --git a/src/main/jbake/content/documentation/development/sling-mock.md 
b/src/main/jbake/content/documentation/development/sling-mock.md
index f0961df..14777d6 100644
--- a/src/main/jbake/content/documentation/development/sling-mock.md
+++ b/src/main/jbake/content/documentation/development/sling-mock.md
@@ -440,13 +440,11 @@ 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]: https://github.com/apache/sling-org-apache-sling-jcr-resource
-[sling-commons-testing]: 
http://svn.apache.org/repos/asf/sling/trunk/bundles/commons/testing
+[sling-commons-testing]: 
https://github.com/apache/sling-org-apache-sling-commons-testing
 [mockito-testrunner]: 
http://mockito.github.io/mockito/docs/current/org/mockito/runners/MockitoJUnitRunner.html
 [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/tutorials-how-tos/testing-sling-based-applications.md
 
b/src/main/jbake/content/documentation/tutorials-how-tos/testing-sling-based-applications.md
index ae02ca7..a2cf416 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,8 +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.
+Utility classes from our 
[commons/testing](https://github.com/apache/sling-org-apache-sling-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.
 

-- 
To stop receiving notification emails like this one, please contact
['"[email protected]" <[email protected]>'].

Reply via email to