husted      02/01/30 17:48:19

  Modified:    xdocs    index.xml
  Log:
  Add headlines section.
  
  Revision  Changes    Path
  1.22      +6 -22     jakarta-site2/xdocs/index.xml
  
  Index: index.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-site2/xdocs/index.xml,v
  retrieving revision 1.21
  retrieving revision 1.22
  diff -u -r1.21 -r1.22
  --- index.xml 30 Jan 2002 21:53:03 -0000      1.21
  +++ index.xml 31 Jan 2002 01:48:19 -0000      1.22
  @@ -9,30 +9,14 @@
   
   <body>
   
  -<section name="That flaming fireball in the sky...">
  -<p>
  -In a recent <a
  -href="http://www.theserverside.com/resources/article.jsp?l=SunInterview";
  ->article</a>, Karen Tegan, Director of J2EE Compatibility and Platform
  -Services for Sun Microsystems, had the following to say:
  -</p>
  -
  -<p>
  -"The J2EE Compatible brand has achieved significant momentum over the
  -past two years, and we want to make sure that any open source efforts
  -don't impact the viability of that effort."
  -</p>
  +<section name="Headlines">
   
   <p>
  -In other words, Sun doesn't give a hoot about whether J2EE licensing
  -restricts open source J2EE products (in case you missed it, it does).
  -Thus, the Apache Software Foundation's involvement in the Java Community
  -Process (JCP) is simply an advertising statement for Sun to claim that
  -they have a 'vision which uses open standards and non-proprietary
  -interfaces'. If you would like to express your opinions of Sun's
  -licensing terms, feel free to contact <a
  -href="mailto:[EMAIL PROTECTED]";>[EMAIL PROTECTED]</a> and let us know what you
  -think. Thanks.
  +<ul>
  +<li><a href="site/news.html#0130.2">30 Jan 2002 - That flaming fireball in the 
sky...</a></li>
  +<li><a href="site/news.html#0130">30 Jan 2002 - Avalon Excalibur 4.1 
Released</a></li>
  +<li><a href="site/news.html#0121">21 Jan 2001 - Tomcat 4.0.2 Beta 2 
Released</a></li>
  +</ul>
   </p>
   
   </section>
  
  
  

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

Reply via email to