BIGTOP-1000. Remove remaining references to the Incubator

4 files changed, 7 insertions, 9 deletions

diff --git a/test/site/pom.xml b/test/site/pom.xml
index 508a0557..26023ce5 100644
--- a/test/site/pom.xml
+++ b/test/site/pom.xml
@@ -47,7 +47,7 @@
     <url>https://issues.apache.org/jira/browse/BIGTOP</url>
   </issueManagement>
   <scm>
-    <url>https://svn.apache.org/repos/asf/incubator/bigtop/</url>
+    <url>http://git-wip-us.apache.org/repos/asf/bigtop.git</url>
   </scm>
   <distributionManagement>
     <site>
diff --git a/test/site/src/site/apt/devguide.apt b/test/site/src/site/apt/devguide.apt
index c35f843c..5be190e0 100644
--- a/test/site/src/site/apt/devguide.apt
+++ b/test/site/src/site/apt/devguide.apt
@@ -22,7 +22,7 @@ How to contribute to iTest
   If you find this project interesting and want to contribute your time, ideas,
   code, documentation writing skills, testing cycles - you are very welcome!
 
-  Contributing is easy! Simply go to the {{{http://incubator.apache.org/bigtop/}project website}},
+  Contributing is easy! Simply go to the {{{http://bigtop.apache.org/}project website}},
   join it and go ahead! 
 
   If you find a problem with iTest, or have a feature request you can
diff --git a/test/site/src/site/apt/downloads.apt b/test/site/src/site/apt/downloads.apt
index 7f5a95c3..f713e556 100644
--- a/test/site/src/site/apt/downloads.apt
+++ b/test/site/src/site/apt/downloads.apt
@@ -47,5 +47,5 @@ repository http://mvnrepository.com/artifact/org.apache.bigtop.itest/itest-commo
 </dependency>
 +--------------------------------------+
 
-  Or you can fetch iTest workspace from https://svn.apache.org/repos/asf/incubator/bigtop/
+  Or you can fetch iTest workspace from https://git-wip-us.apache.org/repos/asf?p=bigtop.git
 
diff --git a/test/site/src/site/apt/examples.apt b/test/site/src/site/apt/examples.apt
index d40849a6..f2d1c429 100644
--- a/test/site/src/site/apt/examples.apt
+++ b/test/site/src/site/apt/examples.apt
@@ -85,9 +85,8 @@ mvn verify
 
 * Putting it all together
 
-  As you can see in the {{{https://svn.apache.org/repos/asf/incubator/bigtop/trunk/test/suites/}suites}}
-  we are using Maven failsafe plugin to execute tests in the integration testing
-  phase of a maven project lifecycle.
+  We are using the Maven failsafe plugin to execute tests in the integration
+  testing phase of a maven project lifecycle.
 
   One of the issues with this plugin is that it requires a presence of a physical
   files somewhere on the disk in order to run appropriate tests (which might
@@ -96,9 +95,8 @@ mvn verify
   class files in the location where failsafe will be looking for them, however
   ones from jars found in the classpath will be executed.
 
-  You can see this step being done in the toplevel
-  {{{https://svn.apache.org/repos/asf/incubator/bigtop/trunk/test/suites/common/pom.xml}pom.xml}}
-  file in the configuration section of <<<org.codehaus.groovy.maven>>> plugin
+  This step is done in the toplevel pom.xml file in the configuration section
+  of <<<org.codehaus.groovy.maven>>> plugin
 
   iTest provides a convenient method of unpacking data files included
   into test artifacts (if needed). It is can be done from the code of the tests