This is an automated email from the ASF dual-hosted git repository.

rombert pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/sling-site.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new 6473c7c  SLING-7161 - Update site to reference git instead of svn
6473c7c is described below

commit 6473c7ccd1c3be87189268ad146ed694779915ab
Author: Robert Munteanu <[email protected]>
AuthorDate: Wed Nov 22 23:26:28 2017 +0200

    SLING-7161 - Update site to reference git instead of svn
---
 documentation.html                                               | 5 ++---
 documentation/bundles/caching-services.html                      | 4 ++--
 documentation/bundles/org-apache-sling-junit-bundles.html        | 5 ++---
 documentation/development/release-management.html                | 5 ++---
 documentation/development/sling-mock.html                        | 9 ++++-----
 .../tutorials-how-tos/testing-sling-based-applications.html      | 5 ++---
 6 files changed, 14 insertions(+), 19 deletions(-)

diff --git a/documentation.html b/documentation.html
index 1a42825..e32042b 100644
--- a/documentation.html
+++ b/documentation.html
@@ -107,13 +107,12 @@
 <h2><a href="#the-public-wiki" name="the-public-wiki">The Public Wiki</a></h2>
 <p>The public wiki of Sling is available at <a 
href="http://cwiki.apache.org/SLING";>http://cwiki.apache.org/SLING</a> and is 
maintained in the Confluence space <em>SLING</em>. Everyone can create an 
account there. To gain edit rights please ask via the <a 
href="/project-information.html">mailing list</a>. Any of the administrators 
listed in the <a 
href="https://cwiki.apache.org/confluence/spaces/viewspacesummary.action?key=SLING&showAllAdmins=true";>Space
 Overview</a> can give you access.</p>
 <h2><a href="#the-javadoc" name="the-javadoc">The JavaDoc</a></h2>
-<!-- GIT-TODO - no migrated yet -->
-<p>With every major release of Sling the JavaDoc of all containing bundles are 
published below <a 
href="http://sling.apache.org/apidocs/";>http://sling.apache.org/apidocs/</a>. 
The script for generating this aggregation JavaDoc is at <a 
href="http://svn.apache.org/repos/asf/sling/trunk/tooling/release/";>http://svn.apache.org/repos/asf/sling/trunk/tooling/release/</a>
 in <code>generate_javadoc_for_release.sh</code></p>
+<p>With every major release of Sling the JavaDoc of all containing bundles are 
published below <a 
href="http://sling.apache.org/apidocs/";>http://sling.apache.org/apidocs/</a>. 
The script for generating this aggregation JavaDoc is in the 
sling-tooling-release repo, at <a 
href="https://github.com/apache/sling-tooling-release/blob/master/generate_javadoc_for_release.sh";>generate_javadoc_for_release.sh</a>.</p>
 <p>In addition every released bundle is released together with its JavaDoc 
(which is also pushed to Maven Central).</p>
 <h2><a href="#the-maven-plugin-documentation" 
name="the-maven-plugin-documentation">The Maven Plugin Documentation</a></h2>
 <p>For the most important Maven Plugins the according Maven Sites (generated 
with the <code>maven-site-plugin</code>) are published at <a 
href="http://sling.apache.org/components/";>http://sling.apache.org/components/</a>.
 The description on how to publish can be found at <a 
href="/documentation/development/release-management.html">Release 
Management</a>.</p></section></div></div>            
             <div class="footer">
-<div class="revisionInfo">Last modified by <span class="author">Robert 
Munteanu</span> on <span class="comment">Wed Nov 22 22:30:38 2017 
+0200</span></div>                <p>
+<div class="revisionInfo">Last modified by <span class="author">Robert 
Munteanu</span> on <span class="comment">Wed Nov 22 23:22:38 2017 
+0200</span></div>                <p>
                     Apache Sling, Sling, Apache, the Apache feather logo, and 
the Apache Sling project logo are trademarks of The Apache Software Foundation. 
All other marks mentioned may be trademarks or registered trademarks of their 
respective owners.
                 </p><p>
                     Copyright © 2011-2017 The Apache Software Foundation.
diff --git a/documentation/bundles/caching-services.html 
b/documentation/bundles/caching-services.html
index c5a0a54..7683eb7 100644
--- a/documentation/bundles/caching-services.html
+++ b/documentation/bundles/caching-services.html
@@ -79,10 +79,10 @@
             </h1><div id="generatedToC"></div><script 
src='/res/jquery-3.2.1.min.js' type='text/javascript'></script><script 
src='/res/tocjs-1-1-2.js' type='text/javascript'></script><script 
type='text/javascript'>$(document).ready(function() { 
$('#generatedToC').toc({'selector':'h1[class!=pagetitle],h2,h3'}); } );</script>
 <div class="row"><div class="small-12 columns"><section 
class="wrap"><p>Caching services are available under multiple repositories at 
<a 
href="https://github.com/apache/?utf8=✓&q=sling-cache";>https://github.com/apache/?utf8=✓&amp;q=sling-cache</a></p>
 <p>Both EhCache and Infinispan implementations are provided, with good unit 
and integration tests coverage.</p>
-<!-- GIT-TODO portal stuff must be moved to the Git portal -->
+<!-- GIT-TODO portal stuff must be moved to the Git whiteboard -->
 <p>A portal cache provider API implementation is provided, that depends on the 
whiteboard portal modules found under <a 
href="https://svn.apache.org/repos/asf/sling/whiteboard/portal";>https://svn.apache.org/repos/asf/sling/whiteboard/portal</a></p></section></div></div>
            
             <div class="footer">
-<div class="revisionInfo">Last modified by <span class="author">Robert 
Munteanu</span> on <span class="comment">Wed Nov 22 22:30:38 2017 
+0200</span></div>                <p>
+<div class="revisionInfo">Last modified by <span class="author">Robert 
Munteanu</span> on <span class="comment">Wed Nov 22 23:22:38 2017 
+0200</span></div>                <p>
                     Apache Sling, Sling, Apache, the Apache feather logo, and 
the Apache Sling project logo are trademarks of The Apache Software Foundation. 
All other marks mentioned may be trademarks or registered trademarks of their 
respective owners.
                 </p><p>
                     Copyright © 2011-2017 The Apache Software Foundation.
diff --git a/documentation/bundles/org-apache-sling-junit-bundles.html 
b/documentation/bundles/org-apache-sling-junit-bundles.html
index c160634..f1d66b1 100644
--- a/documentation/bundles/org-apache-sling-junit-bundles.html
+++ b/documentation/bundles/org-apache-sling-junit-bundles.html
@@ -153,8 +153,7 @@ public final TeleporterRule teleporter =
 <p>If <code>TeleporterRule.forClass(getClass())</code> is used (the method 
without an additional 2nd parameter) the default customizer is used (<a 
href="https://issues.apache.org/jira/browse/SLING-5677";>SLING-5677</a>, since 
version 1.0.8). </p>
 <p>The following customizers are currently used in Sling</p>
 <h3><a href="#default-customizer" name="default-customizer">Default 
Customizer</a></h3>
-<!-- GIT-TODO - not yet migrated -->
-<p><em><a 
href="https://svn.apache.org/repos/asf/sling/trunk/testing/junit/teleporter/src/main/java/org/apache/sling/testing/teleporter/client/DefaultPropertyBasedCustomizer.java";>DefaultPropertyBasedCustomizer.java</a></em>
 is used by default when no other customizer is referenced in 
<code>TeleporterRule.forClass(getClass())</code>. It relies on the following 
system properties:</p>
+<p><em><a 
href="https://github.com/apache/sling-org-apache-sling-junit-teleporter/blob/master/src/main/java/org/apache/sling/testing/teleporter/client/DefaultPropertyBasedCustomizer.java";>DefaultPropertyBasedCustomizer.java</a></em>
 is used by default when no other customizer is referenced in 
<code>TeleporterRule.forClass(getClass())</code>. It relies on the following 
system properties:</p>
 <table>
   <thead>
     <tr>
@@ -305,7 +304,7 @@ TEST_PASSED
 <h2><a href="#org-apache-sling-junit-remote-obsolete" 
name="org-apache-sling-junit-remote-obsolete">org.apache.sling.junit.remote: 
obsolete</a></h2>
 <p>The <code>org.apache.sling.junit.remote</code> bundle provides utilities to 
run server-side JUnit tests, but using the newer <code>TeleporterRule</code> 
described above is much simpler. As a result, this bundle should only be needed 
for existing tests that were written using its mechanisms. 
</p></section></div></div>            
             <div class="footer">
-<div class="revisionInfo">Last modified by <span class="author">Robert 
Munteanu</span> on <span class="comment">Wed Nov 22 22:30:38 2017 
+0200</span></div>                <p>
+<div class="revisionInfo">Last modified by <span class="author">Robert 
Munteanu</span> on <span class="comment">Wed Nov 22 23:22:38 2017 
+0200</span></div>                <p>
                     Apache Sling, Sling, Apache, the Apache feather logo, and 
the Apache Sling project logo are trademarks of The Apache Software Foundation. 
All other marks mentioned may be trademarks or registered trademarks of their 
respective owners.
                 </p><p>
                     Copyright © 2011-2017 The Apache Software Foundation.
diff --git a/documentation/development/release-management.html 
b/documentation/development/release-management.html
index 2862569..b3f5e34 100644
--- a/documentation/development/release-management.html
+++ b/documentation/development/release-management.html
@@ -184,8 +184,7 @@ Staging repository:
 https://repository.apache.org/content/repositories/orgapachesling-[YOUR 
REPOSITORY ID]/
 
 You can use this UNIX script to download the release and verify the signatures:
-&lt;!-- GIT-TODO - Reference the GitBox URL after migrating the 
sling-tooling-release stuff --&gt;
-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
@@ -517,7 +516,7 @@ $ rm the_module-version.jar the_module-version.pom
   </li>
 </ol></section></div></div>            
             <div class="footer">
-<div class="revisionInfo">Last modified by <span class="author">Robert 
Munteanu</span> on <span class="comment">Wed Nov 22 22:30:38 2017 
+0200</span></div>                <p>
+<div class="revisionInfo">Last modified by <span class="author">Robert 
Munteanu</span> on <span class="comment">Wed Nov 22 23:22:38 2017 
+0200</span></div>                <p>
                     Apache Sling, Sling, Apache, the Apache feather logo, and 
the Apache Sling project logo are trademarks of The Apache Software Foundation. 
All other marks mentioned may be trademarks or registered trademarks of their 
respective owners.
                 </p><p>
                     Copyright © 2011-2017 The Apache Software Foundation.
diff --git a/documentation/development/sling-mock.html 
b/documentation/development/sling-mock.html
index 9ab5c3a..4f3e815 100644
--- a/documentation/development/sling-mock.html
+++ b/documentation/development/sling-mock.html
@@ -221,7 +221,7 @@
 <p>See latest version on the <a href="/downloads.cgi">downloads page</a>.</p>
 <p><strong>JCR_JACKRABBIT</strong></p>
 <ul>
-  <li>Uses a real JCR Jackrabbit implementation (not Oak) as provided by <a 
href="http://svn.apache.org/repos/asf/sling/trunk/bundles/commons/testing";>sling/commons/testing</a></li>
+  <li>Uses a real JCR Jackrabbit implementation (not Oak) as provided by <a 
href="https://github.com/apache/sling-org-apache-sling-commons-testing";>sling/commons/testing</a></li>
   <li>Full JCR/Sling features supported e.g. observations manager, 
transactions, versioning</li>
   <li>Uses the productive <a 
href="https://github.com/apache/sling-org-apache-sling-jcr-resource";>Sling JCR 
resource provider implementation</a> internally to do the Resource-JCR 
mapping</li>
   <li>Takes some seconds for startup on the first access</li>
@@ -238,7 +238,7 @@
 <p><em>Remarks on the JCR_JACKRABBIT type:</em></p>
 <ul>
   <li>The repository is not cleared for each unit test, so make sure to use a 
unique node path for each unit test. You may use the <code>uniquePath()</code> 
helper object of the SlingContext rule for this.</li>
-  <li>The <a 
href="http://svn.apache.org/repos/asf/sling/trunk/bundles/commons/testing";>sling/commons/testing</a>
 dependency introduces a lot of further dependencies from  jackrabbit and 
others, be careful that they do not conflict and are imported in the right 
order in your test project</li>
+  <li>The <a 
href="https://github.com/apache/sling-org-apache-sling-commons-testing";>sling/commons/testing</a>
 dependency introduces a lot of further dependencies from  jackrabbit and 
others, be careful that they do not conflict and are imported in the right 
order in your test project</li>
 </ul>
 <h3><a href="#sling-resource-resolver" name="sling-resource-resolver">Sling 
Resource Resolver</a></h3>
 <p>Example:</p>
@@ -415,10 +415,9 @@ public SlingContext context = new 
SlingContextBuilder().plugin(MY_PLUGIN).build(
 <ul>
   <li><a 
href="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";>Apache
 Sling Context-Aware Configuration Mock Plugin</a></li>
   <li><a 
href="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";>Apache
 Sling Context-Aware Configuration Mock Plugin Test</a></li>
-</ul>
-<!-- GIT-TODO - commons/testing is missing --></section></div></div>           
 
+</ul></section></div></div>            
             <div class="footer">
-<div class="revisionInfo">Last modified by <span class="author">Robert 
Munteanu</span> on <span class="comment">Wed Nov 22 22:30:38 2017 
+0200</span></div>                <p>
+<div class="revisionInfo">Last modified by <span class="author">Robert 
Munteanu</span> on <span class="comment">Wed Nov 22 23:22:38 2017 
+0200</span></div>                <p>
                     Apache Sling, Sling, Apache, the Apache feather logo, and 
the Apache Sling project logo are trademarks of The Apache Software Foundation. 
All other marks mentioned may be trademarks or registered trademarks of their 
respective owners.
                 </p><p>
                     Copyright © 2011-2017 The Apache Software Foundation.
diff --git 
a/documentation/tutorials-how-tos/testing-sling-based-applications.html 
b/documentation/tutorials-how-tos/testing-sling-based-applications.html
index 511a7f1..c2af596 100644
--- a/documentation/tutorials-how-tos/testing-sling-based-applications.html
+++ b/documentation/tutorials-how-tos/testing-sling-based-applications.html
@@ -85,8 +85,7 @@
 <p>When possible, unit tests are obviously the fastest executing ones, and 
it's easy to keep them close to the code that they're testing. </p>
 <p>We have quite a lot of those in Sling, the older use the JUnit3 TestCase 
base class, and later ones use JUnit4 annotations. Mixing both approaches is 
possible, there's no need to rewrite existing tests.</p>
 <h2><a href="#tests-that-use-a-jcr-repository" 
name="tests-that-use-a-jcr-repository">Tests that use a JCR repository</a></h2>
-<!-- GIT-TODO commons/testing not migrated  -->
-<p>Utility classes from our <a 
href="https://svn.apache.org/repos/asf/sling/trunk/bundles/commons/testing";>commons/testing</a>
 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.</p>
+<p>Utility classes from our <a 
href="https://github.com/apache/sling-org-apache-sling-commons-testing";>commons/testing</a>
 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.</p>
 <p>The <code>RepositoryProviderTest</code> in that module uses this technique 
to get a JCR repository.</p>
 <p>Note that our utilities do not cleanup the repository between tests, so you 
must be careful about test isolation, for example by using unique paths for 
each test.</p>
 <h2><a href="#mock-classes-and-services" name="mock-classes-and-services">Mock 
classes and services</a></h2>
@@ -145,7 +144,7 @@ resolverField.set(servletResolver, factory);
 <h2><a href="#summary" name="summary">Summary</a></h2>
 <p>Combining the above testing techniques has worked well for us in creating 
and testing Sling. Being able to test things at different levels of integration 
has proved an efficient way to get good test coverage without having to write 
too much boring test code.</p></section></div></div>            
             <div class="footer">
-<div class="revisionInfo">Last modified by <span class="author">Robert 
Munteanu</span> on <span class="comment">Wed Nov 22 22:30:38 2017 
+0200</span></div>                <p>
+<div class="revisionInfo">Last modified by <span class="author">Robert 
Munteanu</span> on <span class="comment">Wed Nov 22 23:22:38 2017 
+0200</span></div>                <p>
                     Apache Sling, Sling, Apache, the Apache feather logo, and 
the Apache Sling project logo are trademarks of The Apache Software Foundation. 
All other marks mentioned may be trademarks or registered trademarks of their 
respective owners.
                 </p><p>
                     Copyright © 2011-2017 The Apache Software Foundation.

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

Reply via email to