yoavs       2004/08/31 12:55:17

  Modified:    webapps/docs status.xml
               webapps/docs/config context.xml
  Log:
  Cleaned up status and correct the XML for tld validation attributes.
  
  Revision  Changes    Path
  1.7       +11 -9     jakarta-tomcat-catalina/webapps/docs/status.xml
  
  Index: status.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/status.xml,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- status.xml        5 Aug 2004 13:10:35 -0000       1.6
  +++ status.xml        31 Aug 2004 19:55:17 -0000      1.7
  @@ -30,21 +30,18 @@
     <section name="Current Status Summary">
       <p>
         <b>Tomcat 5.0.27</b> was released on June 17th, 2004.  At that time, the 
TOMCAT_5_0
  -      branch was tagged in CVS, and work on Tomcat 5.1 (or 5.5, or 5.next, we 
haven't
  -      decided yet) began.  Until the first stable release of Tomcat 5.1, building 
from
  +      branch was tagged in CVS, and work on Tomcat 5.5 began.  Until the first 
stable 
  +      release of Tomcat 5.1, building from
         CVS head may be unstable or broken: use the TOMCAT_5_0 branch tag to build
         the Tomcat 5.0 releases.
       </p>
       <p>
  -      <b>Tomcat 5.1</b> has several major goals.  They are discussed in the 
tomcat-dev
  +      <b>Tomcat 5.5</b> has several major goals.  They are discussed in the 
tomcat-dev
         mailing list's "5.next" thread: 
         <a 
href="http://marc.theaimsgroup.com/?l=tomcat-dev&amp;w=2&amp;r=1&amp;s=5.next&amp;q=b";>MARC</a>.
  -      The status of some of these items is detailed below.
  -    </p>
  -    <p>
  -      <b>Tomcat 4.0.x</b> is relatively old, and not actively maintained or 
supported.
  -      It is strongly recommended that users of these releases upgrade to the latest
  -      stable Tomcat 5.0 release or at least the latest stable Tomcat 4.1 release.
  +      The status of some of these items is detailed below.  Once 5.5 releases are
  +      available, please refer to the Changelog accompanying each release for 
detailed
  +      changes, enhancements, and fixes.
       </p>
       <p>
         <b>Tomcat 4.1.x</b> is no longer actively developed.  It is maintained to 
address
  @@ -52,6 +49,11 @@
         for Tomcat 4.1.x will likely cease once a stable release or two of Tomcat 5.1 
are out.
         Users of Tomcat 4.1.x are strongly encouraged to upgrade to the latest stable 
Tomcat
         5.0 release.
  +    </p>
  +    <p>
  +      <b>Tomcat 4.0.x</b> is relatively old, and not actively maintained or 
supported.
  +      It is strongly recommended that users of these releases upgrade to the latest
  +      stable Tomcat 5.0 release or at least the latest stable Tomcat 4.1 release.
       </p>
       <p>
         <b>Tomcat 3.3.x</b> is in roughly the same maintenance mode as Tomcat 4.1.x.
  
  
  
  1.13      +2 -2      jakarta-tomcat-catalina/webapps/docs/config/context.xml
  
  Index: context.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/config/context.xml,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -u -r1.12 -r1.13
  --- context.xml       31 Aug 2004 14:41:48 -0000      1.12
  +++ context.xml       31 Aug 2004 19:55:17 -0000      1.13
  @@ -277,7 +277,7 @@
           of the flag is <code>false</code>.</p>
         </attribute>
   
  -      <attribute value="tldNamespaceAware" required="false">
  +      <attribute name="tldNamespaceAware" required="false">
           <p>If the value of this flag is <code>true</code>, the TLD files
           XML validation will be namespace-aware.  If you turn this flag on,
           you should probably also turn <code>tldValidation</code> on.  The
  @@ -286,7 +286,7 @@
           </p>
         </attribute>
   
  -      <attribute value="tldValidation" required="false">
  +      <attribute name="tldValidation" required="false">
           <p>If the value of this flag is <code>true</code>, the TLD files
           will be XML validated on context startup.  The default value for
           this flag is <code>false</code>, and setting it to true will incur
  
  
  

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

Reply via email to