commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r530051 - in /jakarta/commons/proper/commons-build/trunk: project.xml xdocs/building.xml xdocs/components.xml xdocs/releases/prepare.xml xdocs/releases/release.xml
Date Wed, 18 Apr 2007 15:12:25 GMT
Author: niallp
Date: Wed Apr 18 08:12:24 2007
New Revision: 530051

Fix broken links


Modified: jakarta/commons/proper/commons-build/trunk/project.xml
--- jakarta/commons/proper/commons-build/trunk/project.xml (original)
+++ jakarta/commons/proper/commons-build/trunk/project.xml Wed Apr 18 08:12:24 2007
@@ -60,13 +60,13 @@
       <name>Commons Dev List</name>
-      <archive></archive>
+      <archive></archive>
       <name>Commons User List</name>
-      <archive></archive>
+      <archive></archive>

Modified: jakarta/commons/proper/commons-build/trunk/xdocs/building.xml
--- jakarta/commons/proper/commons-build/trunk/xdocs/building.xml (original)
+++ jakarta/commons/proper/commons-build/trunk/xdocs/building.xml Wed Apr 18 08:12:24 2007
@@ -42,7 +42,7 @@
     Some knowledge of maven is assumed in this document.  Please refer to the
-    <a href="">maven user guide</a> and
+    <a href="">maven user guide</a>
     <a href="">reference</a>
     for more information. Most commons components now use version 1 of maven,
     so this is the maven version assumed throughout this document. Updates
@@ -60,7 +60,7 @@
     <subsection name='Getting and installing maven'>
       Follow the 
-      <a href="">
+      <a href="">
       maven download instructions</a> to download and install maven. You will
       need Maven version 1.0.2.
@@ -127,7 +127,7 @@
   <section name='Maven POM (project.xml) configuration'>
   This section describes the key elements in the maven POM and how the 
-  <a href="">
+  <a href="">
   sample <code>project.xml</code></a> file needs to be modified or customized
   for different components.
@@ -194,7 +194,7 @@
       <code>maven-changes-plugin</code> should only be used if the component
       maintains a <code>changes.xml</code> file in <code>/xdocs</code>

       following the format described in the
-      <a href="">
+      <a href="">
       maven changes plugin documentation</a></td></tr></table>
@@ -204,7 +204,7 @@
     There is very little that needs to be customized for individual components
     in the
-    <a href="">
+    <a href="">
     sample <code></code> file</a>. The table below calls
     a few properties which individual components may wish to modify.  The
     deployment and site generation properties (which should not be changed) are
@@ -230,7 +230,7 @@
     Use <code>maven site:generate</code> to generate the component web site
     locally. Then review the generated html in <code>target/docs.</code>
     Navigation is specified in <code>xdocs/navigation.xml.</code> The
-    <a href="">
+    <a href="">
     sample navigation file</a> refers to entities defined in 
     <code>../../commons-build/menus/menus.dtd,</code> so, as mentioned above,
     commons-build has to be checked out as a peer to the component whose web
@@ -256,9 +256,9 @@
     <li> You have to be a member of the <code>jakarta</code> unix group

     (should happen when you are set up as a jakarta committer).</li>
-    <li> You have an ssh key set up. Follow the instructions at the bottom
-    of the <a href="">
-    apache cvs info page</a> to get this set up correctly.</li></ol>
+    <li> You have an ssh key set up. Follow the instructions on the
+    <a href="">
+    apache SSH Access page</a> to get this set up correctly.</li></ol>
     Assuming the second condition above is met, you can also deploy sites
     manually using scp or by tarring / zipping and extracting the content
     to the path above on <code></code>  In either case,
@@ -275,7 +275,7 @@
     maven repositories.  This powerful feature makes distribution easy, but
     also makes inadvertent deployment of development jars possible. The
     setup in 
-    <a href="">
+    <a href="">
     <code></code></a> ensures that this does not
     happen.  This section explains how to deploy jars using maven at apache.
@@ -314,7 +314,7 @@
       to set the <code>maven.repo.list</code> property to refer to 
       <code>java-repository.</code>  The safest way to do this (to minimize
       risk of inadvertent production deployment) is to rely on the setup in
-      <a href="">
+      <a href=""></a>, which leaves <code>java-repository</code>
       off of the repo list, so you have to overrride the list on the command
@@ -357,7 +357,7 @@
     plugin extended to perform the function than to script around the problem.
     That said, there are some standard customizations for commons
     components shown in
-    <a href="">

+    <a href="">

     maven.xml.sample</a> The pre- and post-goals defined there copy the
     resources required to ensure that all web sites have a common look and feel
     and that required licenses and notices are included in release distributions.

Modified: jakarta/commons/proper/commons-build/trunk/xdocs/components.xml
--- jakarta/commons/proper/commons-build/trunk/xdocs/components.xml (original)
+++ jakarta/commons/proper/commons-build/trunk/xdocs/components.xml Wed Apr 18 08:12:24 2007
@@ -58,7 +58,7 @@
-         <a href=""><b>HiveMind</b></a>:
+         <a href=""><b>HiveMind</b></a>:
          HiveMind is a services and configuration microkernel. HiveMind allows
          you to create your application using a service oriented architecture.

Modified: jakarta/commons/proper/commons-build/trunk/xdocs/releases/prepare.xml
--- jakarta/commons/proper/commons-build/trunk/xdocs/releases/prepare.xml (original)
+++ jakarta/commons/proper/commons-build/trunk/xdocs/releases/prepare.xml Wed Apr 18 08:12:24
@@ -171,7 +171,7 @@
     Check that the documentation has been generated correctly. Check that all links are working.
     Those using maven can use the 
-    <a href=''>LinkCheck plugin</a>
+    <a href=''>LinkCheck plugin</a>
     to automate this check.

Modified: jakarta/commons/proper/commons-build/trunk/xdocs/releases/release.xml
--- jakarta/commons/proper/commons-build/trunk/xdocs/releases/release.xml (original)
+++ jakarta/commons/proper/commons-build/trunk/xdocs/releases/release.xml Wed Apr 18 08:12:24
@@ -383,12 +383,12 @@
     Maven users can deploy release jars automatically using maven's jar plugin.
     See the 
-<a href="">
+<a href=""></a> file in the commons-build directory for
     an example showing how to configure the necessary properties to support jar
     deployment using scp. A how-to showing how to get an apache ssh key set up
     can be found  
-    <a href="">
+    <a href="">
     here.</a>  Given this setup, 
       maven -Dmaven.repo.list=apache.releases jar:deploy

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message