svn commit: r633829 - in /maven/site/trunk/src/site/apt/guides: mini/guide-configuring-maven.apt mini/guide-m1-m2.apt plugin/guide-java-plugin-development.apt

[vs...@apache.org]

Author: vsiveton
Date: Wed Mar  5 03:57:22 2008
New Revision: 633829

URL: http://svn.apache.org/viewvc?rev=633829&view=rev
Log:
o fixed links to relative paths (partially due to r616127) 
o linkedcheck is happy now :)

Modified:
    maven/site/trunk/src/site/apt/guides/mini/guide-configuring-maven.apt
    maven/site/trunk/src/site/apt/guides/mini/guide-m1-m2.apt
    maven/site/trunk/src/site/apt/guides/plugin/guide-java-plugin-development.apt

Modified: maven/site/trunk/src/site/apt/guides/mini/guide-configuring-maven.apt
URL: http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/guides/mini/guide-configuring-maven.apt?rev=633829&r1=633828&r2=633829&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/guides/mini/guide-configuring-maven.apt (original)
+++ maven/site/trunk/src/site/apt/guides/mini/guide-configuring-maven.apt Wed Mar  5 03:57:22 2008
@@ -27,7 +27,7 @@
   ~~TODO: versioning doc that discusses this
 
   You can specify your user configuration in <<<$\{user.home\}/.m2/settings.xml>>>. A
-  {{{maven-settings/settings.html}full reference}} to the configuration file is available. This section will show how
+  {{{../../maven-settings/settings.html}full reference}} to the configuration file is available. This section will show how
   to make some common configurations. Note that the file is not required - defaults will be used if it is not found.
 
 * Configuring your Local Repository

Modified: maven/site/trunk/src/site/apt/guides/mini/guide-m1-m2.apt
URL: http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/guides/mini/guide-m1-m2.apt?rev=633829&r1=633828&r2=633829&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/guides/mini/guide-m1-m2.apt (original)
+++ maven/site/trunk/src/site/apt/guides/mini/guide-m1-m2.apt Wed Mar  5 03:57:22 2008
@@ -98,30 +98,30 @@
 +----+
 
  For more details, check out the
- {{{guides/introduction/introduction-to-the-pom.html}POM Guide}}.
+ {{{../introduction/introduction-to-the-pom.html}POM Guide}}.
 
 * build.properties and project.properties
 
  These files have been replaced with
- {{{settings.html}settings.xml}}.
+ {{{../../settings.html}settings.xml}}.
  Like with the POM, you can establish a parallel build environment, so the m1 build
  never breaks while the m2 build is being debugged.
 
  Additional local build customization options can also be created using
- {{{guides/introduction/introduction-to-profiles.html}profiles}}.
+ {{{../introduction/introduction-to-profiles.html}profiles}}.
 
 * What to do with maven.xml?
 
- See {{maven1.html#m1-maven-xml}} for an explanation of
+ See {{{../../maven1.html#m1-maven-xml}}How do I write custom scripts without a maven.xml file?} for an explanation of
  why maven.xml was discarded, and
- {{guides/introduction/introduction-to-plugins.html}} for
+ {{{../introduction/introduction-to-plugins.html}}Introduction to Maven 2.0 Plugin Development} for
  a guide to writing your own plug-ins.
 
 * Directory Structure
 
  The POM allows customization of the directory structure in both Maven 1 and Maven 2
  using the <<<\<build\>>>> tag. For simplicity, it would be ideal to move source to the
- {{{guides/introduction/introduction-to-the-standard-directory-layout.html}Maven 2 default structure}},
+ {{{../introduction/introduction-to-the-standard-directory-layout.html}Maven 2 default structure}},
  but it is not required. You can begin by customizing the
  directories in Maven 2, then when satisfied that both build paths are working, move
  to the Maven 2 structure and customize the settings in Maven 1.
@@ -132,25 +132,25 @@
  a build cycle in Maven 2. Instead of using <<<preGoal>>> and <<<postGoal>>> tags
  in <<<maven.xml>>> to tie plugin goals into the build process, the goals of a
  plugin are associated with the pre-defined stages of the build cycle. See the
- {{{guides/introduction/introduction-to-the-lifecycle.html}Introduction to the Build Lifecycle}}
+ {{{../introduction/introduction-to-the-lifecycle.html}Introduction to the Build Lifecycle}}
  for more on how plugins relate.
 
 ** Re-use Ant Tasks
 
- See the {{{general.html#using-ant-tasks}Ant Script FAQ}}.
+ See the {{{../../general.html#using-ant-tasks}Ant Script FAQ}}.
 
 ** Replace scripts with Mojos
 
   The new plugin architecture does not specify a specific language implementation, so
   Jelly scripts and other such artifacts should be re-usable with wrappers. It is recommended
   that you look into moving to
-  {{{guides/plugin/guide-java-plugin-development.html}Mojos}}.
+  {{{../plugin/guide-java-plugin-development.html}Mojos}}.
 
 ** Utilize built-in Maven 2 capabilities
 
 *** Resource filtering to inject POM variables into application
 
- You can turn on {{{guides/getting-started/index.html#How_do_I_filter_resource_files?}resource filtering}}
+ You can turn on {{{../getting-started/index.html#How_do_I_filter_resource_files?}resource filtering}}
  in your POM. Tokens of the form <<<$\{pom.variable\}>>> in resource files will be replaced with the  corresponding POM property.
 
 +----+
@@ -181,11 +181,10 @@
 
 * Related links
 
- * {{{http://maven.apache.org/plugins/maven-one-plugin}Maven 2 One Plugin}}
+ * {{{http://maven.apache.org/plugins/maven-one-plugin/}Maven 2 One Plugin}}
 
  * {{{https://svn.apache.org/repos/asf/maven/sandbox/trunk/other/m1-m2/maven1+project+to+maven2+pom.xsl}XSLT}} from {{{http://jira.codehaus.org/browse/MNG-2337}MNG-2337}}
 
  * {{{http://www.nabble.com/using-preGoal-and-postGoal-in-m2--td1151533s177.html}using preGoal and postGoal in m2?}} Thread.
 
  []
-

Modified: maven/site/trunk/src/site/apt/guides/plugin/guide-java-plugin-development.apt
URL: http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/guides/plugin/guide-java-plugin-development.apt?rev=633829&r1=633828&r2=633829&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/guides/plugin/guide-java-plugin-development.apt (original)
+++ maven/site/trunk/src/site/apt/guides/plugin/guide-java-plugin-development.apt Wed Mar  5 03:57:22 2008
@@ -272,7 +272,7 @@
 
   This causes the simple mojo to be executed whenever Java code is compiled.
   For more information on binding a mojo to phases in the lifecycle, please
-  refer to the {{{guides/introduction/introduction-to-the-lifecycle.html}Build Lifecycle}} document.
+  refer to the {{{../introduction/introduction-to-the-lifecycle.html}Build Lifecycle}} document.
 
 * Mojo archetype
 
@@ -755,7 +755,7 @@
   the parameter <<<outputDirectory>>> from the mojo itself is used. In the second case however, the Maven Site Plugin
   will set the output directory according to its own configuration by calling <<<MavenReport.setReportOutputDirectory()>>>
   on the reports being generated. Therefore, developers should always use <<<MavenReport.getReportOutputDirectory()>>> if they
-  need to query the effective output directory for the report. 
+  need to query the effective output directory for the report.
 
 ** Using Plexus Utilities