svn commit: r1340844 - in /maven/plugin-testing/trunk: maven-plugin-testing-harness/src/site/apt/ maven-plugin-testing-harness/src/site/apt/examples/ maven-plugin-testing-harness/src/site/fml/ maven-plugin-testing-tools/src/site/apt/

[hb...@apache.org]

Author: hboutemy
Date: Sun May 20 21:27:50 2012
New Revision: 1340844

URL: http://svn.apache.org/viewvc?rev=1340844&view=rev
Log:
fixed links

Modified:
    maven/plugin-testing/trunk/maven-plugin-testing-harness/src/site/apt/examples/repositories.apt
    maven/plugin-testing/trunk/maven-plugin-testing-harness/src/site/apt/index.apt
    maven/plugin-testing/trunk/maven-plugin-testing-harness/src/site/fml/faq.fml
    maven/plugin-testing/trunk/maven-plugin-testing-tools/src/site/apt/index.apt

Modified: maven/plugin-testing/trunk/maven-plugin-testing-harness/src/site/apt/examples/repositories.apt
URL: http://svn.apache.org/viewvc/maven/plugin-testing/trunk/maven-plugin-testing-harness/src/site/apt/examples/repositories.apt?rev=1340844&r1=1340843&r2=1340844&view=diff
==============================================================================
--- maven/plugin-testing/trunk/maven-plugin-testing-harness/src/site/apt/examples/repositories.apt (original)
+++ maven/plugin-testing/trunk/maven-plugin-testing-harness/src/site/apt/examples/repositories.apt Sun May 20 21:27:50 2012
@@ -100,7 +100,7 @@ public class MyProjectStub
     /** {@inheritDoc} */
     public List getRemoteArtifactRepositories()
     {
-        ArtifactRepository repository = new DefaultArtifactRepository( "central", "http://repo1.maven.org/maven2",
+        ArtifactRepository repository = new DefaultArtifactRepository( "central", "http://repo.maven.apache.org/maven2",
                                                                        new DefaultRepositoryLayout() );
 
         return Collections.singletonList( repository );

Modified: maven/plugin-testing/trunk/maven-plugin-testing-harness/src/site/apt/index.apt
URL: http://svn.apache.org/viewvc/maven/plugin-testing/trunk/maven-plugin-testing-harness/src/site/apt/index.apt?rev=1340844&r1=1340843&r2=1340844&view=diff
==============================================================================
--- maven/plugin-testing/trunk/maven-plugin-testing-harness/src/site/apt/index.apt (original)
+++ maven/plugin-testing/trunk/maven-plugin-testing-harness/src/site/apt/index.apt Sun May 20 21:27:50 2012
@@ -29,18 +29,18 @@ Maven Plugin Testing Harness
  {{{http://plexus.codehaus.org}Plexus}} components, providing stub objects for Maven functionality such as projects,
  and populating fields from an XML file that resembles the plugin configuration in the POM.
 
- The best way to start is to read the cookbook {{{getting-started/index.html}How to use Maven Plugin Testing Harness}}.
+ The best way to start is to read the cookbook {{{./getting-started/index.html}How to use Maven Plugin Testing Harness}}.
 
 * Examples
 
    The following examples shows how to use the Testing Harness in more advanced usecases:
 
-   * {{{examples/complex-mojo-parameters.html}Testing Complex Mojo Parameters}}
+   * {{{./examples/complex-mojo-parameters.html}Testing Complex Mojo Parameters}}
 
-   * {{{examples/multiproject.html}Testing Multiproject}}
+   * {{{./examples/multiproject.html}Testing Multiproject}}
 
-   * {{{examples/repositories.html}Testing Using Repositories}}
+   * {{{./examples/repositories.html}Testing Using Repositories}}
 
-   * {{{examples/artifact.html}Testing Project Artifact}}
+   * {{{./examples/artifact.html}Testing Project Artifact}}
 
    []

Modified: maven/plugin-testing/trunk/maven-plugin-testing-harness/src/site/fml/faq.fml
URL: http://svn.apache.org/viewvc/maven/plugin-testing/trunk/maven-plugin-testing-harness/src/site/fml/faq.fml?rev=1340844&r1=1340843&r2=1340844&view=diff
==============================================================================
--- maven/plugin-testing/trunk/maven-plugin-testing-harness/src/site/fml/faq.fml (original)
+++ maven/plugin-testing/trunk/maven-plugin-testing-harness/src/site/fml/faq.fml Sun May 20 21:27:50 2012
@@ -46,8 +46,8 @@ under the License.
               the same way you'd write any other JUnit test cases, i.e. by writing a test class which extends
               <i>TestCase</i>.</dd>
             <dt>TestCase from Plexus</dt>
-            <dd>Mojos are written to take specific advantage of the <a href="http://plexus.codehaus.org/">Plexus</a>
-              container. If you need Plexus container services, you could write your class which extends <i>PlexusTestCase</i>,
+            <dd>Mojos are written to take specific advantage of the <a href="http://plexus.codehaus.org/plexus-containers/">Plexus
+              container</a>. If you need Plexus container services, you could write your class which extends <i>PlexusTestCase</i>,
               instead of <i>TestCase</i>.</dd>
             <dt>TestCase from Testing Harness</dt>
             <dd>If you need to inject Maven objects into your mojo, you could use the <i>maven-plugin-testing-harness</i>.

Modified: maven/plugin-testing/trunk/maven-plugin-testing-tools/src/site/apt/index.apt
URL: http://svn.apache.org/viewvc/maven/plugin-testing/trunk/maven-plugin-testing-tools/src/site/apt/index.apt?rev=1340844&r1=1340843&r2=1340844&view=diff
==============================================================================
--- maven/plugin-testing/trunk/maven-plugin-testing-tools/src/site/apt/index.apt (original)
+++ maven/plugin-testing/trunk/maven-plugin-testing-tools/src/site/apt/index.apt Sun May 20 21:27:50 2012
@@ -36,7 +36,7 @@ Maven Plugin Testing Tools
   (possibly after resolving them from a remote repository). Because of this, the only practical way 
   to use the current plugin within an integration-test build is to install it into some sort of local 
   repository, then direct Maven to use that local repository for the build. To avoid side effects in
-  other builds (remember, we're building Maven plugins here...and they're used to build other projects),
+  other builds (remember, we're building Maven plugins here... and they're used to build other projects),
   it's critical to avoid using the main local repository used for normal Maven builds. Therefore,
   plugin integration tests require a custom local repository, to which the integration-testing builds
   can be directed. Further complicating this testing scenario is the fact that the plugin's parent
@@ -96,7 +96,7 @@ Maven Plugin Testing Tools
     
 * Utilities Included in this Library
 
-  For more information on the APIs described below, see the {{{apidocs/index.html}JavaDocs}}.
+  For more information on the APIs described below, see the {{{./apidocs/index.html}JavaDocs}}.
 
   * <<PluginTestTool>> - The main entry point for setting up the plugin-testing environment, this
     utility orchestrates the ProjectTool, RepositoryTool, and BuildTool in order to produce a local