mrglavas    2003/07/17 15:30:33

  Modified:    java/docs install.xml
  Log:
  Replaced instances of xmlParserAPIs.jar with xml-apis.jar.
  Documented the deprecation of xmlParserAPIs.jar.
  Capitalized each occurence of Xerces, Xalan, and Ant.
  
  Revision  Changes    Path
  1.16      +20 -14    xml-xerces/java/docs/install.xml
  
  Index: install.xml
  ===================================================================
  RCS file: /home/cvs/xml-xerces/java/docs/install.xml,v
  retrieving revision 1.15
  retrieving revision 1.16
  diff -u -r1.15 -r1.16
  --- install.xml       6 Nov 2002 22:38:18 -0000       1.15
  +++ install.xml       17 Jul 2003 22:30:33 -0000      1.16
  @@ -34,13 +34,19 @@
       one of the standard API&apos;s supported by the parser</td>
      </tr>
      <tr>
  -    <td>xmlParserAPIs.jar</td>
  +    <td>xml-apis.jar</td>
       <td>Jar file containing all the standard API&apos;s implemented by
       the parser.  Currently, &ParserName; supports DOM level 2, SAX
       2.0 R2 PR1, and the <code>javax.xml.parsers</code> part of JAXP
       1.2.  </td>
      </tr>
      <tr>
  +    <td>xmlParserAPIs.jar</td>
  +    <td>Jar file with the same contents as xml-apis.jar. This file has
  +    been deprecated. Users are encouraged to use xml-apis.jar, as
  +    xmlParserAPIs.jar will disappear in some future release.</td>
  +   </tr>
  +   <tr>
       <td>xercesSamples.jar</td>
       <td>Jar file containing all sample class files</td>
      </tr>
  @@ -71,7 +77,7 @@
       xerces.jar is no longer available in the main distribution. You can still 
       download this jar from deprecated distribution. xerces.jar is a Jar file 
       that contains all the parser class files (i.e., it contains
  -    the intersection of the contents of xercesImpl.jar and xmlParserAPIs.jar). 
  +    the intersection of the contents of xercesImpl.jar and xml-apis.jar). 
      </note>
    </s2>
    <s2 title='Files in the Source Package'>
  @@ -136,31 +142,31 @@
      In order to compile the source code using Ant or to build the
      release distributions yourself, you must have the contents of 
      <code>&ParserName;-tools.&parserversion;.zip</code>
  -   on your classpath; i.e., you will need access to a version of ant,
  -   xalan, StyleBook and an XML parser such as xerces.
  +   on your classpath; i.e., you will need access to a version of Ant,
  +   Xalan, StyleBook and an XML parser such as Xerces.
      For ease of use, we recommend extracting
      <code>&ParserName;-tools.&parserversion;.zip</code>
  -   in your xerces root directory; the build.sh and build.bat scripts
  +   in your Xerces root directory; the build.sh and build.bat scripts
      are written for this case.
     </note>
    </s2>
    <s2 title='Changes in Xerces jar files'>
  - <p>In order to accomodate the very common case in which xerces is
  - used with an XSL processor such as xalan, between Xerces 2.0.0 beta 3
  - and beta 4 a change in the default organization of xerces&apos;s jar
  + <p>In order to accomodate the very common case in which Xerces is
  + used with an XSLT processor such as Xalan, between Xerces 2.0.0 beta 3
  + and beta 4 a change in the default organization of Xerces&apos;s jar
    files was introduced.  As well as the <code>xercesSamples.jar</code>
  - file, which we still produce, xerces formerly came with a file called
  + file, which we still produce, Xerces formerly came with a file called
    <code>xerces.jar</code>.  This file contained all of the
    parser&apos;s functionality.  Two files are now included:
    <code>xercesImpl.jar</code>, our implementation of various API&apos;s,
  - and <code>xmlParserAPIs.jar</code>, the API&apos;s themselves.  This
  + and <code>xml-apis.jar</code>, the API&apos;s themselves.  This
    was done so that, if your XSLT processor ships with API&apos;s at the
    same level as those supported by &ParserName;, you can avoid putting
  - <code>xmlParserAPIs.jar</code> on your classpath.</p>
  + <code>xml-apis.jar</code> on your classpath.</p>
   
    <p>Should you wish to use the <code>xerces.jar</code> instead, we have
  - included several ant targets for backward compatibility.  An
  - &quot;ant target&quot; is an argument given to ant, our build tool,
  + included several Ant targets for backward compatibility.  An
  + &quot;Ant target&quot; is an argument given to Ant, our build tool,
    that tells it which portions of the <code>build.xml</code> file to
    apply. 
   </p>
  @@ -171,7 +177,7 @@
    deprecatedjars</code>.  
    </p>
    <p>
  - If you want to regenerate new versions of the xerces
  + If you want to regenerate new versions of the Xerces
    binary, source and tools distributions with the old-style jarfiles,
    you would execute <code>build.bat deprecatedall</code>.  
   
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to