svn commit: r560790 - in /commons/proper/cli/trunk/xdocs: properties.xml usage.xml

[ba...@apache.org]

Author: bayard
Date: Sun Jul 29 12:41:30 2007
New Revision: 560790

URL: http://svn.apache.org/viewvc?view=rev&rev=560790
Log:
Fixing javadoc links

Modified:
    commons/proper/cli/trunk/xdocs/properties.xml
    commons/proper/cli/trunk/xdocs/usage.xml

Modified: commons/proper/cli/trunk/xdocs/properties.xml
URL: http://svn.apache.org/viewvc/commons/proper/cli/trunk/xdocs/properties.xml?view=diff&rev=560790&r1=560789&r2=560790
==============================================================================
--- commons/proper/cli/trunk/xdocs/properties.xml (original)
+++ commons/proper/cli/trunk/xdocs/properties.xml Sun Jul 29 12:41:30 2007
@@ -28,10 +28,10 @@
     <section name="Option Properties">
       <p>
         The following are the properties that each 
-        <a href="apidocs/org/apache/commons/cli/Option.html">Option</a> has.  All of these
+        <a href="api-1.1/org/apache/commons/cli/Option.html">Option</a> has.  All of these
         can be set using the accessors or using the methods
         defined in the
-        <a href="apidocs/org/apache/commons/cli/OptionBuilder.html">OptionBuilder</a>.
+        <a href="api-1.1/org/apache/commons/cli/OptionBuilder.html">OptionBuilder</a>.
       </p>
       <table>
         <tr>

Modified: commons/proper/cli/trunk/xdocs/usage.xml
URL: http://svn.apache.org/viewvc/commons/proper/cli/trunk/xdocs/usage.xml?view=diff&rev=560790&r1=560789&r2=560790
==============================================================================
--- commons/proper/cli/trunk/xdocs/usage.xml (original)
+++ commons/proper/cli/trunk/xdocs/usage.xml Sun Jul 29 12:41:30 2007
@@ -45,7 +45,7 @@
       </subsection>
       <subsection name="Create the Options">
         <p>
-          An <a href="apidocs/org/apache/commons/cli/Options.html">
+          An <a href="api-1.1/org/apache/commons/cli/Options.html">
           Options</a> object must be created and the <code>Option</code> must be 
           added to it.
         </p>
@@ -78,7 +78,7 @@
         <p>
           Now we need to check if the <code>t</code> option is present.  To do
           this we will interrogate the 
-          <a href="apidocs/org/apache/commons/cli/CommandLine.html">CommandLine
+          <a href="api-1.1/org/apache/commons/cli/CommandLine.html">CommandLine
           </a> object.  The <code>hasOption</code> method takes a 
           <code>java.lang.String</code> parameter and returns <code>true</code> if the option 
           represented by the <code>java.lang.String</code> is present, otherwise 
@@ -208,11 +208,11 @@
       <subsection name="Create the Options">
         <p>
           Now that we have created each 
-          <a href="apidocs/org/apache/commons/cli/Option.html">Option</a> we need 
+          <a href="api-1.1/org/apache/commons/cli/Option.html">Option</a> we need 
           to create the 
-          <a href="apidocs/org/apache/commons/cli/Options.html">Options</a> 
+          <a href="api-1.1/org/apache/commons/cli/Options.html">Options</a> 
           instance.  This is achieved using the 
-          <a href="apidocs/org/apache/commons/cli/CommandLine.html#addOption(org.apache.commons.cli.Option)">addOption</a> 
+          <a href="api-1.1/org/apache/commons/cli/CommandLine.html#addOption(org.apache.commons.cli.Option)">addOption</a> 
           method of <code>Options</code>.
         </p>
         <source>Options options = new Options();
@@ -239,8 +239,8 @@
         <p>
           We now need to create a <code>Parser</code>.  This will parse the command
           line arguments, using the rules specified by the <code>Options</code> and
-          return an instance of <a href="apidocs/org/apache/commons/cli/CommandLine.html">CommandLine</a>.
-          This time we will use a <a href="apidocs/org/apache/commons/cli/GnuParser.html">GnuParser</a>
+          return an instance of <a href="api-1.1/org/apache/commons/cli/CommandLine.html">CommandLine</a>.
+          This time we will use a <a href="api-1.1/org/apache/commons/cli/GnuParser.html">GnuParser</a>
           which is able to handle options that are more than one character long.
         </p>
         <source>public static void main( String[] args ) {
@@ -272,7 +272,7 @@
         <p>
           CLI also provides the means to automatically generate usage
           and help information.  This is achieved with the
-          <a href="apidocs/org/apache/commons/cli/HelpFormatter.html">HelpFormatter</a>
+          <a href="api-1.1/org/apache/commons/cli/HelpFormatter.html">HelpFormatter</a>
           class.
         </p>
         <source>// automatically generate the help statement
@@ -307,7 +307,7 @@
       <p>
         One of the most widely used command line applications in the *nix world
         is <code>ls</code>.  To parse a command line for an application like this
-        we will use the <a href="apidocs/org/apache/commons/cli/PosixParser.html">PosixParser</a>.
+        we will use the <a href="api-1.1/org/apache/commons/cli/PosixParser.html">PosixParser</a>.
         Due to the large number of options required for <code>ls</code> this
         example will only cover a small proportion of the options.  The following
         is a section of the help output.
@@ -328,7 +328,7 @@
 -C                         list entries by columns</source>
       <p>
         The following is the code that is used to create the 
-        <a href="apidocs/org/apache/commons/cli/Options.html">Options</a> for this example.
+        <a href="api-1.1/org/apache/commons/cli/Options.html">Options</a> for this example.
       </p>
       <source>// create the command line parser
 CommandLineParser parser = new PosixParser();