harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From nadi...@apache.org
Subject svn commit: r519951 [2/5] - in /harmony/standard/site: docs/ docs/subcomponents/classlibrary/ docs/subcomponents/drlvm/ xdocs/ xdocs/subcomponents/classlibrary/ xdocs/subcomponents/drlvm/
Date Mon, 19 Mar 2007 14:12:08 GMT
Modified: harmony/standard/site/docs/sitemap.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/sitemap.html?view=diff&rev=519951&r1=519950&r2=519951
==============================================================================
--- harmony/standard/site/docs/sitemap.html (original)
+++ harmony/standard/site/docs/sitemap.html Mon Mar 19 07:12:06 2007
@@ -383,39 +383,33 @@
         </a> - documentation links specific to DRLVM effort
         underway at Apache Harmony
       </p>
-                                <p>
-        <strong>
-          Developing and Building the Code Documentation
-        </strong>
-      </p>
-                                <p>
+                                <dl>
+        <dt>Developing and Building the Code Documentation</dt>
+      <dd>
         <a href="subcomponents/drlvm/debugging_VM_and_JIT.html">
           Debugging the DRL Virtual Machine and the JIT Compiler
         </a> - practical instructions on how to debug the DRL virtual machine and its
         baseline just-in-time compiler Jitrino.JET
-      </p>
-                                <p>
-        <a href="subcomponents/drlvm/getting_started.html">
+      </dd>
+      <dd><a href="subcomponents/drlvm/getting_started.html">
           Getting Started with DRLVM
         </a> - basic usage scenarios of VM: starting an
         application, working in Eclipse
-      </p>
-                                <p>
+      </dd>
+      <dd>
         <a href="https://svn.apache.org/viewcvs.cgi/*checkout*/harmony/enhanced/drlvm/trunk/README.txt">
           README
         </a> - source package and building instructions for
         the VM source code
-      </p>
-                                <p>
-        <strong>Architecture and Component Documentation</strong>
-      </p>
-                                <p>
+      </dd>
+      <dt>Architecture and Component Documentation</dt>
+     <dd>
         <a href="subcomponents/drlvm/developers_guide.html">
           DRLVM Developer's Guide
         </a> - in-depth description of the DRLVM
         internal architecture and components' interaction
-      </p>
-                                <ul>
+      </dd>
+      <ul>
         <li>
           
             <a href="subcomponents\drlvm\encoder_library.html">
@@ -463,6 +457,7 @@
               
             </li>
           </ul>
+            
         </li>
         <li>
           
@@ -470,7 +465,6 @@
             details on the PopFrame implementation as currently done in DRLVM, description of the functions
             responsible for the operation and gives info on specifics of the current implementation
           
-
         </li>
         <li>
           
@@ -488,27 +482,28 @@
          
         </li>
        </ul>
-                                <p>
+
+      <dd>
         <a href="subcomponents/drlvm/DoxygenStart.html">DRLVM Source Code Generated Documentation Index</a> -
         a landing page with links to autogenerated Doxygen documentation for DRLVM interface headers
-      </p>
-                                <p>
-        <strong>How-tos and Guides</strong>
-      </p>
-                                <p>
-
+      </dd>
+      
+      <dt>How-tos and Guides</dt>
+      <dd>
         <a href="subcomponents/drlvm/emguide.html">
           Configuring Execution Manager 
         </a> - guide to Execution Manager (EM)
         options and configuration file format
-      </p>
-                                <p>
+      </dd>
+
+        <dd>
           <a href="subcomponents/drlvm/gc-howto.html">
             How to Write DRL GC
           </a> - instructions on creating a custom garbage collector
           implementation in C++ and configuring the DRL virtual machine to use it
           with a real-life example of a copying GC implementation (source included)
-        </p>
+        </dd>
+</dl>
                    
                                     
     <h2>
@@ -527,78 +522,75 @@
       </a> - comparisons of JDK 1.4 and JDK 1.5. against
       the Harmony class library snapshots
     </p>
-                                <p>
-      <strong>
-        Project Conventions
-      </strong>
-    </p>
-                                <p>
+                                <dl>
+    <dt>Project Conventions</dt>
+    <dd>
       <a href="subcomponents/classlibrary/pkgnaming.html">
         Class Library Package Naming Conventions
       </a> - the package naming conventions used in the Apache Harmony Class Library
-    </p>
-                                <p>
+    </dd>
+
+    <dd>
       <a href="subcomponents/classlibrary/testing.html">
         Class Library Testing Conventions
       </a> - description of the PROPOSED
       placement and package naming conventions for different types of Harmony
       class library tests; general guidlines and recomendations
       that might be adapted/modified to reflect module specifics
-    </p>
-                                <p>
+    </dd>
+    <dd>
       <a href="subcomponents/classlibrary/compat.html">
         Compatibility Guidelines</a> - compatibility goals in the Apache Harmony Class Library
-    </p>
-                                <p>
+    </dd>
+       <dd>
       <a href="subcomponents/classlibrary/ser_testing.html">
         Framework for Testing Serialization
       </a> - guidelines for creating tests and
       conventions for resource files
-    </p>
-                                <p>
-      <strong>Architecture and Guides Documentation</strong>
-    </p>
-                                <p>
+    </dd>
+    <dt>Architecture and Guides Documentation</dt>
+    <dd>
       <a href="subcomponents/classlibrary/asn1_framework.html">
         ASN.1 Framework
       </a> - introduction to the ASN.1 (Abstract Syntax Notation) framework
       with an overview of ASN.1 types and encoding rules focusing on the
       characteristics of the current implementation
-    </p>
-                                <p>
+    </dd>
+    <dd>
       <a href="subcomponents/classlibrary/awt.html">
         Abstract Window Toolkit Framework
       </a> - description of the AWT (Abstract Window Toolkit) framework covering
       major design features and internal implementation specifics, such as the
       event handling mechanism, the focus dispatching flow, appearance handling
       with custom visual themes and multi-threading support
-    </p>
-                                <p>
+    </dd>
+    <dd>
       <a href="subcomponents/classlibrary/dns_support.html">
         DNS Service Provider
       </a> - implementation description of the DNS service provider
       for the Java Naming Directory Interface (JNDI) including a package overview, a
       design description and a guide to using the provider
-    </p>
-                                <p>
+    </dd>
+    <dd>
       <a href="subcomponents/classlibrary/java2d.html">
         Java 2D
       </a> - introduction to the Java two-dimensional (2D) graphics
       and image processing technology implementation focusing on the internal
       specifics of implementation
-    </p>
-                                <p>
+    </dd>
+    <dd>
       <a href="subcomponents/classlibrary/regexp.html">
         Regex Processing Framework
       </a> - overview of the <code>java.util.regex</code>
       package and implementation architecture focusing on the performance
       improvement aspects
-    </p>
-                                <p>
+    </dd>
+      <dd>
      <a href="subcomponents/classlibrary/rmi_provider.html">
      RMI Registry Service Provider</a> - description of the functionality of the
           DRL RMI Registry Service Provider for the Java Naming Directory Interface (JNDI)
-          including details on the provider design</p>
+          including details on the provider design</dd>
+    </dl>
                    
                 <p><a href="#top">Back to top</a></p>
                     

Modified: harmony/standard/site/docs/subcomponents/classlibrary/agreements.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/subcomponents/classlibrary/agreements.html?view=diff&rev=519951&r1=519950&r2=519951
==============================================================================
--- harmony/standard/site/docs/subcomponents/classlibrary/agreements.html (original)
+++ harmony/standard/site/docs/subcomponents/classlibrary/agreements.html Mon Mar 19 07:12:06 2007
@@ -193,7 +193,7 @@
     </h1>
                         <p>
     <big><em>The summary of agreements and recommendations that were  
-    discussed on the development mailing list <code>dev@harmony.apache.org</code>.  
+    discussed on the development mailing list <code>dev@harmony.apache.org</code>.
     Please feel free to send your comments and questions there.</em></big>
 </p>
                                     
@@ -202,90 +202,94 @@
     </h2>
       
                         <ul>
-    <li>serialVersionUID MUST be explicitly specified for each Serializable class to provide compatibility
-    (<a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200601.mbox/%3c906dd82e0601190059x3162c6c6u533928579c226572@mail.gmail.com%3e">
-    [classlib] serialVersionUIDs for Serializable classes</a>)
+    <li><code>serialVersionUID</code> MUST be explicitly specified for each Serializable class to
+    provide compatibility.<br />
+    <a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200601.mbox/%3c906dd82e0601190059x3162c6c6u533928579c226572@mail.gmail.com%3e">
+    [classlib] serialVersionUIDs for Serializable classes</a>
     </li>
 
-    <li>Exception messages MUST be internationalized
-    (<a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200604.mbox/%3c44478DC3.4070206@gmail.com%3e">
-    Internationalized messages</a>)
+    <li>Exception messages MUST be internationalized.<br />
+    <a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200604.mbox/%3c44478DC3.4070206@gmail.com%3e">
+    Internationalized messages</a>
     </li>
 
-    <li>A golden ticket MUST be acquired to update java.lang.String class
-    (<a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200604.mbox/%3c444788A0.6000102@gmail.com%3e">
-    [classlib] String is special</a>)
+    <li>A golden ticket MUST be acquired to update the <code>java.lang.String</code> class.<br />
+    <a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200604.mbox/%3c444788A0.6000102@gmail.com%3e">
+        [classlib] String is special
+    </a>
     </li>
 
-    <li>Mark deprecated stuff with @deprecated keyword
-    (<a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200603.mbox/%3c4405BE70.1020307@gmail.com%3e">
-    deprecated methods , javadocs</a>)
-    </li>
+    <li>Mark deprecated stuff with <code>@deprecated</code> keyword.<br />
+    <a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200603.mbox/%3c4405BE70.1020307@gmail.com%3e">
+        deprecated methods, javadocs</a>
+</li>
 
-    <li>Error messages should contain helpfull information
-    (<a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200603.mbox/%3cfcb9f9160603240835i792de7dobabfc43a44e7c752@mail.gmail.com%3e">
-    More helpful error messages</a>)
+<li>
+    Error messages should contain helpfull information.<br />
+    <a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200603.mbox/%3cfcb9f9160603240835i792de7dobabfc43a44e7c752@mail.gmail.com%3e">
+    More helpful error messages</a>
     </li>
 
     <li>We clarify/add Harmony classlib specific to javadoc, provide examples.
-    Also javadoc should contain a reference to Sun's javadoc
-    (<a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200601.mbox/%3c43C38BCC.6070308@gmail.com%3e">
-    Writing JavaDoc</a>)
-    </li>
-
-    <li>Implementation code should not contain logging.
-    (<a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200605.mbox/%3c447C3186.4000208@gmail.com%3e">
-    [classlib] JNDI provider's dependency on logging</a>) and
-    (<a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200605.mbox/%3c447C6E8B.8020202@pobox.com%3e">
-    [classlib] logging from within our implementation</a>)
-    </li>
-
-    <li>java.util.concurrent issue was resolved by taking code from
-    independent source(Doug Lea). And we'll offer fixes made in Harmony back to
-    original repository.
-    (<a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200606.mbox/%3c4486FEAE.5000607@pobox.com%3e">
-    [classlib] proposal - resolution to java.util.concurrent issue</a>),
-    (<a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200607.mbox/%3c005401c6a56e$79234ce0$0c01a8c0@LITTLEGUY%3e">
-    [classlib][concurrent] java.util.concurrent module proposal</a>) and
-    (<a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200607.mbox/%3c44B60C4E.80003@gmail.com%3e">
-    [legal] taking concurrency utils code into the project</a>)
-    </li>
+    Also javadoc should contain a reference to Sun's javadoc.<br />
+    <a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200601.mbox/%3c43C38BCC.6070308@gmail.com%3e">
+    Writing JavaDoc</a>
+    </li>
+
+    <li>Implementation code should not contain logging.<br />
+    <a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200605.mbox/%3c447C3186.4000208@gmail.com%3e">
+    [classlib] JNDI provider's dependency on logging</a> and
+    <a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200605.mbox/%3c447C6E8B.8020202@pobox.com%3e">
+    [classlib] logging from within our implementation</a>
+    </li>
+
+    <li>The <code>java.util.concurrent</code> issue was resolved by taking code from
+    independent source (Doug Lea). And we'll offer fixes made in Harmony back to
+    original repository.<br />
+    <a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200606.mbox/%3c4486FEAE.5000607@pobox.com%3e">
+    [classlib] proposal - resolution to java.util.concurrent issue</a>,
+    <a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200607.mbox/%3c005401c6a56e$79234ce0$0c01a8c0@LITTLEGUY%3e">
+    [classlib][concurrent] java.util.concurrent module proposal</a> and
+    <a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200607.mbox/%3c44B60C4E.80003@gmail.com%3e">
+    [legal] taking concurrency utils code into the project</a></li>
 
     <li>Ant build files should use 1.6 style (using macros and avoiding
-    antcall invocations).
-    (<a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200606.mbox/%3c20060629155612.72153.qmail@web55112.mail.re4.yahoo.com%3e">
-    [classlib] build file stuff</a>)
+    antcall invocations).<br />
+    <a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200606.mbox/%3c20060629155612.72153.qmail@web55112.mail.re4.yahoo.com%3e">
+    [classlib] build file stuff</a>
     </li>
 
-    <li>It is OK to use Sun's messages for expections and toString() methods
-    (<a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200607.mbox/%3c44BAE039.3060903@pobox.com%3e">
-    [general] Sun's permission to use exception messages and toString() formats</a>)
+    <li>It is OK to use Sun's messages for expections and <code>toString()</code> methods.<br />
+    <a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200607.mbox/%3c44BAE039.3060903@pobox.com%3e">
+    [general] Sun's permission to use exception messages and toString() formats</a>
     </li>
 
-    <li>We use Apache Yoko as CORBA for Harmony
-    (<a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200607.mbox/%3cc3755b3a0607180804r2ac264aei8adb967e6e64ae35@mail.gmail.com%3e">
-    [classlib] Using Yoko as CORBA for Harmony</a>).
-    And CORBA v.2.4 is acceptable (1.5 spec requires CORBA v.2.3.1).
-    (<a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200607.mbox/%3cc3755b3a0607260005j6c51c983k511828945dbf4412@mail.gmail.com%3e">
-    Yoko is CORBA 2.4. Is this acceptable for Harmony?</a>).
-    </li>
+    <li>We use Apache Yoko as CORBA for Harmony.<br />
+    <a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200607.mbox/%3cc3755b3a0607180804r2ac264aei8adb967e6e64ae35@mail.gmail.com%3e">
+        [classlib] Using Yoko as CORBA for Harmony</a><br />
+        And CORBA v.2.4 is acceptable (1.5 spec requires CORBA v.2.3.1).<br />
+    <a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200607.mbox/%3cc3755b3a0607260005j6c51c983k511828945dbf4412@mail.gmail.com%3e">
+        Yoko is CORBA 2.4. Is this acceptable for Harmony?</a>
+</li>
 
-    <li>We will support 3.2 and 4.01 versions of HTML (RI is based on 3.2)
-    (<a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200607.mbox/%3c9b6bea40607211316t36e7c665g7452feea3f99b8ce@mail.gmail.com%3e">
-    [classlib][html] HTML 3.2 or 4.01</a>)
+<li>
+    We will support 3.2 and 4.01 versions of HTML (RI is based on 3.2).<br />
+    <a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200607.mbox/%3c9b6bea40607211316t36e7c665g7452feea3f99b8ce@mail.gmail.com%3e">
+    [classlib][html] HTML 3.2 or 4.01</a>
     </li>
 
-    <li>sun.* classes issue was resolved by creating suncompat.jar
-    (<a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200608.mbox/%3c44DB0537.6090408@gmail.com%3e">
-    [classlib][suncompat] created</a>)
-    </li>
+    <li><code>sun.*</code> classes issue was resolved by creating <code>suncompat.jar</code>.<br />
+    <a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200608.mbox/%3c44DB0537.6090408@gmail.com%3e">
+        [classlib][suncompat] created</a>
+</li>
 
-    <li>Throws clause of stub method should include
+<li>
+    Throws clause of stub method should include
     <a href="http://svn.apache.org/viewvc/incubator/harmony/enhanced/classlib/trunk/modules/luni/src/main/java/org/apache/harmony/luni/util/NotImplementedException.java?view=markup">
-    NotImplementedException</a> to be recognized by Japi tool.
-    (<a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200611.mbox/%3cba76afd90611071842w264a2519q1f5a123154759ad6@mail.gmail.com%3e">
-    Japi diffs for harmony</a>)
-    </li>
+        NotImplementedException</a> to be recognized by Japi tool.<br />
+    <a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200611.mbox/%3cba76afd90611071842w264a2519q1f5a123154759ad6@mail.gmail.com%3e">
+    Japi diffs for harmony</a>
+</li>
 
 </ul>
                    
@@ -295,37 +299,40 @@
     </h2>
       
                         <ul>
-    <li>Follow <a href="http://www.javaworld.com/javaworld/jw-12-2000/jw-1221-junit_p.html">guidelines</a> for unit tests
-    (<a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200603.mbox/%3c442B7857.7040002@gmail.com%3e">
-    [Testing Convention] Keep tests small and fast</a>)
-    </li>
-
-    <li>There is no separate regression testsuite. Regression tests are
-    added to unit tests with comments pointing out to JIRA bug.
-    (<a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200512.mbox/%3ce3b630230512300651t574d876ex5de59ad667697acb@mail.gmail.com%3e">
-    regression test suite</a>)
-    (<a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200603.mbox/%3c6e47b64f0603280346u3dc491edp8f06bacdbd04c626@mail.gmail.com%3e">
-    Regression tests</a>)
-    </li>
-
-    <li>Create separate test suites for exotic configurations
-    (<a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200601.mbox/%3c906dd82e0601260338i61bc439fr708c664181dc8f20@mail.gmail.com%3e">
-    [testing] code for exotic configurations</a>)
-    </li>
-
-    <li>No logging for unit tests
-    (<a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200601.mbox/%3c906dd82e0601232340n5de6f561v8bb6db7ac4756f1c@mail.gmail.com%3e">
-    [classlib] Unit and performance testing</a>)
-    </li>
-    
-    <li>All resource files are located in &lt;module root&gt;/src/test/resources folder and added to classpath
-    (<a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200603.mbox/%3c44126B5C.1020104@gmail.com%3e">
-    Location of test data files</a>)
+<li>
+    Follow <a href="http://www.javaworld.com/javaworld/jw-12-2000/jw-1221-junit_p.html">guidelines</a> for unit tests.<br />
+    <a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200603.mbox/%3c442B7857.7040002@gmail.com%3e">
+    [Testing Convention] Keep tests small and fast</a>
+</li>
+
+<li>
+    There is no separate regression testsuite. Regression tests are
+    added to unit tests with comments pointing out to JIRA bug.<br />
+    <a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200512.mbox/%3ce3b630230512300651t574d876ex5de59ad667697acb@mail.gmail.com%3e">
+    regression test suite</a> and
+    <a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200603.mbox/%3c6e47b64f0603280346u3dc491edp8f06bacdbd04c626@mail.gmail.com%3e">
+    Regression tests</a>
+    </li>
+
+    <li>Create separate test suites for exotic configurations.<br />
+    <a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200601.mbox/%3c906dd82e0601260338i61bc439fr708c664181dc8f20@mail.gmail.com%3e">
+    [testing] code for exotic configurations</a>
+    </li>
+
+    <li>No logging for unit tests.<br />
+    <a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200601.mbox/%3c906dd82e0601232340n5de6f561v8bb6db7ac4756f1c@mail.gmail.com%3e">
+        [classlib] Unit and performance testing</a>
     </li>
     
-    <li>Network tests should use embedded jetty server
-    (<a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200605.mbox/%3c446DF7A9.6040702@gmail.com%3e">
-    [classlib] jetty based tests</a>)
+    <li>All resource files are located in &lt;module root&gt;/src/test/resources folder and added to classpath.<br />
+    <a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200603.mbox/%3c44126B5C.1020104@gmail.com%3e">
+        Location of test data files</a>
+</li>
+
+<li>
+    Network tests should use embedded jetty server.<br />
+    <a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200605.mbox/%3c446DF7A9.6040702@gmail.com%3e">
+    [classlib] jetty based tests</a>
     </li>
     
 </ul>
@@ -336,29 +343,31 @@
     </h2>
       
                         <ul>
-    <li>Separate module for providers should be created 
-    (<a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200601.mbox/%3c6e47b64f0601170332k3d418fabwd25a264c5e0f1532@mail.gmail.com%3e">
-    componentization: more modules might be necessary</a>)
+    <li>Separate module for providers should be created.<br />
+    <a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200601.mbox/%3c6e47b64f0601170332k3d418fabwd25a264c5e0f1532@mail.gmail.com%3e">
+    componentization: more modules might be necessary</a>
     </li>
 
-    <li>JIRA issue can be reassigned if it is not marked as 'In Progress'
-    (<a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200601.mbox/%3c43D76E6A.90509@gmail.com%3e">
-    Stealing JIRA issues</a>)
+    <li>
+        JIRA issue can be reassigned if it is not marked as 'In Progress'.<br />
+        <a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200601.mbox/%3c43D76E6A.90509@gmail.com%3e">
+            Stealing JIRA issues</a>
     </li>
 
-    <li>New files should be created with svn property eol-style=native 
-    (<a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200603.mbox/%3c442AF8CD.6040004@gmail.com%3e">
-    EOL differences in svn diffs</a>)
+    <li>New files should be created with svn property <code>eol-style=native</code>.<br />
+    <a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200603.mbox/%3c442AF8CD.6040004@gmail.com%3e">
+    EOL differences in svn diffs</a>
     </li>
 
-    <li>Mail threads should have subject with prefix 
-    (<a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200604.mbox/%3c443133C5.3010602@pobox.com%3e">
-    [admin] prefixes?</a>)
+    <li>Mail threads should have subject with prefix.<br />
+    <a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200604.mbox/%3c443133C5.3010602@pobox.com%3e">
+    [admin] prefixes?</a>
     </li>
 
-    <li>Create component status pages and keep them up to date  
-    (<a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200603.mbox/%3c440D8F7B.3080902@googlemail.com%3e">
-    Component status pages</a>)
+    <li>
+        Create component status pages and keep them up to date.<br />
+    <a href="http://mail-archives.apache.org/mod_mbox/harmony-dev/200603.mbox/%3c440D8F7B.3080902@googlemail.com%3e">
+    Component status pages</a>
     </li>
 </ul>
                    

Modified: harmony/standard/site/docs/subcomponents/classlibrary/asn1_framework.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/subcomponents/classlibrary/asn1_framework.html?view=diff&rev=519951&r1=519950&r2=519951
==============================================================================
--- harmony/standard/site/docs/subcomponents/classlibrary/asn1_framework.html (original)
+++ harmony/standard/site/docs/subcomponents/classlibrary/asn1_framework.html Mon Mar 19 07:12:06 2007
@@ -511,197 +511,199 @@
     </p>
     <table cellspacing="0" cellpadding="0" align="center" width="60%">
         <tr>
-            <th class="TableHeading" colspan="2">
+        <th class="TableHeading">
+                   </th>
+            <th class="TableHeading">
                 ASN.1 Type
             </th>
-            <th class="TableHeading" style="text-align: center" width="25%">
+            <th class="TableHeading">
                 Java<a href="#*">*</a> Type
             </th>
-            <th class="TableHeading" width="30%">
+            <th class="TableHeading">
                 Framework Class
             </th>
         </tr>
         <tr>
-            <th class="TableHeading" rowspan="5" width="11%">
+            <th class="TableHeading" rowspan="5">
                 <a id="Primitive" name="Primitive">Primitive</a>
-            </td>
+            </th>
         </tr>
         <tr>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code>INTEGER</code>
             </td>
-            <td align="center" width="25%">
+            <td class="TableCell" align="center" width="25%">
                 <code>byte[]</code>
             </td>
-            <td width="25%">
+            <td class="TableCell" width="25%">
                 <code><a href="#ASN1Integer">ASN1Integer</a></code>
             </td>
         </tr>
         <tr>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code>ENUMERATED</code>
             </td>
-            <td align="center" width="25%">
+            <td class="TableCell" align="center" width="25%">
                 <code>byte[]</code>
             </td>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code><a href="#ASN1Enumerated">ASN1Enumerated</a></code>
             </td>
         </tr>
         <tr>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code>OBJECT IDENTIFIER</code>
             </td>
-            <td align="center" width="25%">
+            <td class="TableCell" align="center" width="25%">
                 <code>int[]</code>
             </td>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code><a href="#ASN1Oid">ASN1Oid</a></code>
             </td>
         </tr>
         <tr>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code>BOOLEAN</code>
             </td>
-            <td align="center" width="25%">
+            <td class="TableCell" align="center" width="25%">
                 <code>java.lang.Boolean</code>
             </td>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code><a href="#ASN1Boolean">ASN1Boolean</a></code>
             </td>
         </tr>
         <tr>
-            <th class="TableHeading" rowspan="12" width="11%">
+            <th class="TableHeading" rowspan="12">
                 <a id="String" name="String">String</a>
             </th>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code>BitString</code>
             </td>
-            <td align="center" width="25%">
+            <td class="TableCell" align="center" width="25%">
                 <code>asn1.BitString</code>
             </td>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code><a href="#ASN1BitString">ASN1BitString</a></code>
             </td>
         </tr>
         <tr>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code>OctetString</code>
             </td>
-            <td align="center" width="25%">
+            <td class="TableCell" align="center" width="25%">
                 <code>byte[]</code>
             </td>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code><a href="#ASN1OctetString">ASN1OctetString</a></code>
             </td>
         </tr>
         <tr>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code>PrintableString</code>
             </td>
-            <td align="center" width="25%">
+            <td class="TableCell" align="center" width="25%">
                 <code>java.lang.String</code>
             </td>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code><a href="#ASN1StringType">ASN1StringType</a></code>
             </td>
         </tr>
         <tr>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code>T61String</code>
             </td>
-            <td align="center" width="25%">
+            <td class="TableCell" align="center" width="25%">
                 <code>java.lang.String</code>
             </td>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code><a href="#ASN1StringType">ASN1StringType</a></code>
             </td>
         </tr>
         <tr>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code>IA5String</code>
             </td>
-            <td align="center" width="25%">
+            <td class="TableCell" align="center" width="25%">
                 <code>java.lang.String</code>
             </td>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code><a href="#ASN1StringType">ASN1StringType</a></code>
             </td>
         </tr>
         <tr>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code>UTF8String</code>
             </td>
-            <td align="center" width="25%">
+            <td class="TableCell" align="center" width="25%">
                 <code>java.lang.String</code>
             </td>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code><a href="#ASN1StringType">ASN1StringType</a></code>
             </td>
         </tr>
         <tr>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code>BMPString</code>
             </td>
-            <td align="center" width="25%">
+            <td class="TableCell" align="center" width="25%">
                 <code>java.lang.String</code>
             </td>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code><a href="#ASN1StringType">ASN1StringType</a></code>
             </td>
         </tr>
         <tr>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code>GeneralString</code>
             </td>
-            <td align="center" width="25%">
+            <td class="TableCell" align="center" width="25%">
                 <code>java.lang.String</code>
             </td>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code><a href="#ASN1StringType">ASN1StringType</a></code>
             </td>
         </tr>
         <tr>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code>TeletexString</code>
             </td>
-            <td align="center" width="25%">
+            <td class="TableCell" align="center" width="25%">
                 <code>java.lang.String</code>
             </td>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code><a href="#ASN1StringType">ASN1StringType</a></code>
             </td>
         </tr>
         <tr>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code>UniversalString</code>
             </td>
-            <td align="center" width="25%">
+            <td class="TableCell" align="center" width="25%">
                 <code>java.lang.String</code>
             </td>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code><a href="#ASN1StringType">ASN1StringType</a></code>
             </td>
         </tr>
         <tr>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code>UTCTime</code>
             </td>
-            <td align="center" width="25%">
+            <td class="TableCell" align="center" width="25%">
                 <code>java.util.Date</code>
             </td>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code><a href="#ASN1UTCTime">ASN1UTCTime</a></code>
             </td>
         </tr>
         <tr>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code>GeneralizedTime</code>
             </td>
-            <td align="center" width="25%">
+            <td class="TableCell" align="center" width="25%">
                 <code>java.util.Date</code>
             </td>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code><a href="#ASN1UTCTime">ASN1GeneralizedTime</a></code>
             </td>
         </tr>
@@ -709,35 +711,35 @@
             <th rowspan="3" class="TableHeading">
                 <a id="Constructed" name="Constructed">Constructed</a>
             </th>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code>SEQUENCE</code>
             </td>
-            <td align="center" width="25%">
+            <td class="TableCell" align="center" width="25%">
                 <code>Object[]</code>
             </td>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code><a href="#ASN1Sequence">ASN1Sequence</a></code>
             </td>
         </tr>
         <tr>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code>SEQUENCE OF</code>
             </td>
-            <td align="center" width="25%">
+            <td class="TableCell" align="center" width="25%">
                 <code>java.util.List</code>
             </td>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code><a href="#ASN1SequenceOf">ASN1SequenceOf</a></code>
             </td>
         </tr>
         <tr>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code>SET OF</code>
             </td>
-            <td width="25%" align="center">
+            <td class="TableCell" width="25%" align="center">
                 <code>java.util.List</code>
             </td>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code><a href="#ASN1SetOf">ASN1SetOf</a></code>
             </td>
         </tr>
@@ -745,24 +747,24 @@
             <th rowspan="2" width="11%" class="TableHeading">
                 <a id="Tagged" name="Tagged">Tagged</a>
             </th>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code>EXPLICIT</code>
             </td>
-            <td width="25%" style="text-align: center">
+            <td class="TableCell" width="25%" style="text-align: center">
                 <i>based type</i>
             </td>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <a href="#ASN1Explicit"><code>ASN1Explicit</code></a>
             </td>
         </tr>
         <tr>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code>IMPLICIT</code>
             </td>
-            <td align="center" width="25%" style="text-align: center">
+            <td class="TableCell" align="center" width="25%" style="text-align: center">
                 <i>based type</i>
             </td>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <a href="#Class_ASNImplicit"><code>ASN1Implicit</code></a>
             </td>
         </tr>
@@ -770,24 +772,24 @@
             <th rowspan="2" width="11%" class="TableHeading">
                 <a id="Other" name="Other">Other</a>
             </th>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code>ANY</code>
             </td>
-            <td align="center" width="25%">
+            <td class="TableCell" align="center" width="25%">
                 <code>byte[]</code>
             </td>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code><a href="#Class_ASNAny">ASN1Any</a></code>
             </td>
         </tr>
         <tr>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code>CHOICE</code>
             </td>
-            <td align="center" width="25%" style="text-align: center">
+            <td class="TableCell" align="center" width="25%" style="text-align: center">
                 <i>one of chosen types</i>
             </td>
-            <td width="30%">
+            <td class="TableCell" width="30%">
                 <code><a href="#Class_ASNChoice">ASN1Choice</a></code>
             </td>
         </tr>
@@ -1408,6 +1410,7 @@
     </p>
 </body>
 </html>
+
 
 
 </div>

Modified: harmony/standard/site/docs/subcomponents/classlibrary/compat.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/subcomponents/classlibrary/compat.html?view=diff&rev=519951&r1=519950&r2=519951
==============================================================================
--- harmony/standard/site/docs/subcomponents/classlibrary/compat.html (original)
+++ harmony/standard/site/docs/subcomponents/classlibrary/compat.html Mon Mar 19 07:12:06 2007
@@ -195,7 +195,7 @@
                 <big>
                     <em>
                         The following guidelines are currently PROPOSED and being discussed on the
-                        development mailing list <code>dev@harmony.apache.org</code>.  Please
+                        development mailing list <code>dev@harmony.apache.org</code>. Please
                         direct comments and questions there.
                     </em>
                 </big>
@@ -218,16 +218,13 @@
                     effort is producing a set of class library code that is compatible with
                     <a href="http://java.sun.com/j2se/1.5.0/docs/api/index.html">
                         the Java SE 5.0 API
-                        specification
-                    </a>.
+                        specification</a>.
                 </p>
                                 <p>
                     At times (discussed below) it is necessary to augment the specification based on the
-                    behavior of the reference implementation (RI) of the Java SE 5.0 specification.  In
+                    behavior of the reference implementation (RI) of the Java SE 5.0 specification. In
                     such cases we use <a href="http://java.sun.com/j2se/1.5.0/download.jsp">
-                        the latest
-                        official release of the Java SE 5.0 RI
-                    </a>.
+                        the latest official release of the Java SE 5.0 RI</a>.
                 </p>
                                 <p>
                     We are aware that there are other compliant implementations of Java 5.0 available
@@ -242,60 +239,50 @@
                         <p>
                     The following general guidelines apply when developing class library code for Apache
                     Harmony:
-                    <ul>
-                        <li>
-                            <b>Comply with the Java Specification</b>
-                            <p>
-                                In the first instance we follow the description of each part of the class
-                                library given in the <a href="#referenceImpl">Java specification</a>.  To
-                                the large part, this adequately describes the behavior of the class library
-                                implementation including methods, exceptions, and serialization.  However,
-                                where the specification is silent on a particular issue facing the implementor,
-                                or the described behavior is clearly illogical, then we follow the behavior
-                                of the reference implementation.
-                            </p>
-                        </li>
-                        <li>
-                            <b>Follow the Reference Implementation</b>
-                            <p>
-                                The Reference Implementation (RI) is used to resolve issues that are not
-                                adequately addressed in the specification.  In such cases we use the RI as a
-                                guide to the compliant and expected behavior; however, developers <em>must</em>
-                                ensure that the behaviour of the RI is determined soley through exercising the
-                                public Java APIs -- specifically we avoid any notion of reverse engineering or
-                                exposition of the RI's implementation by exercising non-API types and methods.
-                            </p>
-                            <p>
-                                There are a few occasions where both the specification is quiet on a given
-                                issue, and the RI exhibits behaviour that we would consider illogical.  In such
-                                cases we discuss the issue on
-                                <a href="../../mailing.html">
-                                    the Harmony developers'
-                                    mailing list
-                                </a>, and code the class libraries to do what the development community
-                                conclude is "the logical thing".
-                            </p>
-                        </li>
-                        <li>
-                            <b>Do "the Logical Thing"</b>
-                            <p>
-                                The final decision about how a piece of code should behave, on those rare occasions
-                                where the specification and RI do not provide a satisfactory answer, is reached
-                                by concensus on the Harmony developers' mailing list.  Each issue is debated based
-                                on it's individual circumstances, but the developers are aware that breaking popular
-                                applications is invariably not "the logical thing" to do.
-                                <p>
-                                </p>
-                                Once a decision has been made it is documented in the code comments and an issue
-                                raised in <a href="http://issues.apache.org/jira/browse/HARMONY">
-                                    the Harmony JIRA issue
-                                    tracking system
-                                </a> to record the conclusion.  It should be noted that very few issues
-                                need to be resolved this way.
-                            </p>
-                        </li>
-                    </ul>
                 </p>
+                                <dl>
+                    <dt>Comply with the Java Specification</dt>
+                    <dd>
+                        In the first instance we follow the description of each part of the class
+                        library given in the <a href="#referenceImpl">Java specification</a>. To
+                        the large part, this adequately describes the behavior of the class library
+                        implementation including methods, exceptions, and serialization. However,
+                        where the specification is silent on a particular issue facing the implementor,
+                        or the described behavior is clearly illogical, then we follow the behavior
+                        of the reference implementation.
+                    </dd>
+                    <dt>Follow the Reference Implementation</dt>
+                    <dd>
+                        The Reference Implementation (RI) is used to resolve issues that are not
+                        adequately addressed in the specification. In such cases we use the RI as a
+                        guide to the compliant and expected behavior; however, developers <em>must</em>
+                        ensure that the behaviour of the RI is determined soley through exercising the
+                        public Java APIs -- specifically we avoid any notion of reverse engineering or
+                        exposition of the RI's implementation by exercising non-API types and methods.
+                        <br />
+                        There are a few occasions where both the specification is quiet on a given
+                        issue, and the RI exhibits behaviour that we would consider illogical. In such
+                        cases we discuss the issue on <a href="../../mailing.html">
+                            the Harmony developers' mailing list</a>, and code the class libraries to
+                        do what the development community
+                        conclude is "the logical thing".
+                    </dd>
+                    <dt>
+                        <b>Do "the Logical Thing"</b>
+                    </dt>
+                    <dd>
+                        The final decision about how a piece of code should behave, on those rare occasions
+                        where the specification and RI do not provide a satisfactory answer, is reached
+                        by concensus on the Harmony developers' mailing list. Each issue is debated based
+                        on it's individual circumstances, but the developers are aware that breaking popular
+                        applications is invariably not "the logical thing" to do.
+                        <br />
+                        Once a decision has been made it is documented in the code comments and an issue
+                        raised in <a href="http://issues.apache.org/jira/browse/HARMONY">
+                            the Harmony JIRA issue tracking system</a> to record the conclusion. It should be
+                        noted that very few issues need to be resolved this way.
+                    </dd>
+                </dl>
                    
                                     
     <h2>
@@ -304,7 +291,7 @@
       
                         <p>
                     There are a number of methods in the Java specification that describe the conditions under
-                    which exceptions are thrown.  However, in most cases the specification does not describe all possible
+                    which exceptions are thrown. However, in most cases the specification does not describe all possible
                     exceptions that may be thrown, the order of exception throwing (i.e. where there are multiple
                     conditions that would result in an exception), and so on.
                 </p>
@@ -315,60 +302,56 @@
                                 <p>
                     Harmony
                     <b>classlib</b> developers write test cases that deliberately cause exceptions to be thrown
-                    so that we can match exception behaviour like-for-like.  Harmony class library code throws exceptions
+                    so that we can match exception behaviour like-for-like. Harmony class library code throws exceptions
                     of the same runtime class (or a subtype of that runtime class) as the RI, other than
                     in cases where the RI throws non-public types whereupon Harmony will throw an exception with the same public supertype.
                 </p>
                                 <p>
                     Generally, we could refer to the following steps.
+                </p>
+                                <dl>
+                    <dt>If RI is compliant with the Java Specification</dt>
+                    <dd>
+                        We shall follow RI's behavior, that is, throws exactly the same exception or a subclass of the exception.
+                    </dd>
                     <ul>
                         <li>
-                            <b>If RI is compliant with the Java Specification</b>
-                            <p>
-                                We shall follow RI's behavior, that is, throws exactly the same exception or a subclass of the exception.
-                                <ul>
-                                    <li>
-                                        But there are some cases that RI throws an implementation specific exception,
-                                        which is not in the Java Specification, we shall throw an equivalent Harmony specific exception,
-                                        or its superclass in the Java Specification.
-                                        <p>
-                                            <i>
-                                                e.g., If RI throws sun.io.MalformedInputException,
-                                                we could throw org.apache.harmony.io.MalformedInputException or java.io.CharConversionException.
-                                            </i>
-                                        </p>
-                                    </li>
-                                </ul>
+                            But there are some cases that RI throws an implementation specific exception,
+                            which is not in the Java Specification, we shall throw an equivalent Harmony specific exception,
+                            or its superclass in the Java Specification.
+                            <p class="example">Example</p>
+                            <p class="exampletext">
+                                If RI throws <code>sun.io.MalformedInputException</code>,
+                                we can throw <code>org.apache.harmony.io.MalformedInputException</code>
+                                or <code>java.io.CharConversionException</code>.
                             </p>
                         </li>
-                        <li>
-                            <b>If RI is not compliant with the Java Specification</b>
-                            <p>
+                    </ul>
+                    <dt>If RI is not compliant with the Java Specification</dt>
+                    <dd>
+                        <ul>
+                            <li>
+                                If the Java Specification describes the exceptional situation explicitly,
+                                and RI throws different kind of exception or even does not throw any exception,
+                                we shall discuss them case by case in harmony-dev mailing list.
                                 <ul>
-                                    <li>
-                                        If the Java Specification describes the exceptional situation explicitly,
-                                        and RI throws different kind of exception or even does not throw any exception,
-                                        we shall discuss them case by case in harmony-dev mailing list.
-                                        <ul>
-                                            <li>If we decide to follow RI, we will raise an "Non-bug differences from Spec" JIRA.</li>
-                                            <li>If we decide to follow the Java Specification, we will raise an "Non-bug differences from RI" JIRA.</li>
-                                        </ul>
-                                    </li>
-                                    <li>
-                                        If the Java Specification does NOT describe the exceptional situation explicitly,
-                                        and RI's behavior is either hard to reproduce or illogical, we shall discuss them case by case.
-                                        And we may decide to:
-                                        <ul>
-                                            <li>Follow RI</li>
-                                            <li>Follow the Java Specification</li>
-                                            <li>Implement the functions in our own way</li>
-                                        </ul>
-                                    </li>
+                                    <li>If we decide to follow RI, we will raise an "Non-bug differences from Spec" JIRA.</li>
+                                    <li>If we decide to follow the Java Specification, we will raise an "Non-bug differences from RI" JIRA.</li>
                                 </ul>
-                            </p>
-                        </li>
-                    </ul>
-                </p>
+                            </li>
+                            <li>
+                                If the Java Specification does NOT describe the exceptional situation explicitly,
+                                and RI's behavior is either hard to reproduce or illogical, we shall discuss them case by case.
+                                And we may decide to:
+                                <ul>
+                                    <li>Follow RI</li>
+                                    <li>Follow the Java Specification</li>
+                                    <li>Implement the functions in our own way</li>
+                                </ul>
+                            </li>
+                        </ul>
+                    </dd>
+                </dl>
                    
                                     
     <h2>
@@ -380,8 +363,8 @@
                     implementation (RI).
                 </p>
                                 <p>
-                    The Java Specification describes the serialized form of many Java types.  Where given, <b>classlib</b> will follow
-                    the specified serialized form.  When the serialized form is <u>not</u> given we will ensure that the
+                    The Java Specification describes the serialized form of many Java types. Where given, <b>classlib</b> will follow
+                    the specified serialized form. When the serialized form is NOT given we will ensure that the
                     serialization data is compatible with the RI by ensuring that objects serialized from the RI
                     can be read by Harmony's <b>classlib</b> code, and vice versa.
                 </p>

Modified: harmony/standard/site/docs/subcomponents/classlibrary/pkgnaming.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/subcomponents/classlibrary/pkgnaming.html?view=diff&rev=519951&r1=519950&r2=519951
==============================================================================
--- harmony/standard/site/docs/subcomponents/classlibrary/pkgnaming.html (original)
+++ harmony/standard/site/docs/subcomponents/classlibrary/pkgnaming.html Mon Mar 19 07:12:06 2007
@@ -221,19 +221,12 @@
                     Each Java package is owned by a specific module of the Harmony class library.
                     The module name immediately follows the <code>org.apache.harmony</code> prefix.
                 </p>
-                                <pre>
-                    org.apache.harmony.<b>&lt;module&gt;</b>
-                </pre>
+                                <pre>org.apache.harmony.<b>&lt;module&gt;</b></pre>
                                 <p class="example">
                     Example
                 </p>
-                                <p class="exampletext">
-                    <pre>
-                        org.apache.harmony.luni
-                        org.apache.harmony.security
-                    </pre>
-
-                </p>
+                                <pre>org.apache.harmony.luni
+org.apache.harmony.security</pre>
                    
                                     
     <h2>
@@ -250,49 +243,49 @@
                     The following package name segements are <b>reserved</b> to indicate the meanings
                     defined below:
                 </p>
-                                <ul>
-                    <li>
+                                <dl>
+                    <dt>
                         <code>
                             org.apache.harmony.&lt;modulename&gt;.<b>internal</b>
                         </code>
-                        <p>
-                            Packages with this prefix are implementation packages for use within
-                            the given module. Types and fields that are visible within these
-                            packages <em>MUST NOT</em> be used outside the module itself.
-                            Some runtime environments may enforce this reduced visibility scope.
-                        </p>
-                    </li>
-                    <li>
+                    </dt>
+                    <dd>
+                        Packages with this prefix are implementation packages for use within
+                        the given module. Types and fields that are visible within these
+                        packages <em>MUST NOT</em> be used outside the module itself.
+                        Some runtime environments may enforce this reduced visibility scope.
+                    </dd>
+                    <dt>
                         <code>
                             org.apache.harmony.&lt;modulename&gt;.<b>tests</b>
                         </code>
-                        <p>
-                            Packages with this prefix contain test code that is not part of the
-                            module API or implementation.  Some builds may not include these
-                            packages. See <a href="testing.html">Testing conventions in the Apache Harmony Classlib</a>
-                            for details.
-                        </p>
-                    </li>
-                    <li>
+                    </dt>
+                    <dd>
+                        Packages with this prefix contain test code that is not part of the
+                        module API or implementation. Some builds may not include these
+                        packages. See <a href="testing.html">Testing conventions in the Apache Harmony Classlib</a>
+                        for details.
+                    </dd>
+                    <dt>
                         <code>
                             org.apache.harmony.&lt;modulename&gt;.<b>examples</b>
                         </code>
-                        <p>
-                            Packages with this prefix contain example code that is not part of the
-                            module API or implementation. Some builds may not include these
-                            packages.
-                        </p>
-                    </li>
-                    <li>
+                    </dt>
+                    <dd>
+                        Packages with this prefix contain example code that is not part of the
+                        module API or implementation. Some builds may not include these
+                        packages.
+                    </dd>
+                    <dt>
                         <code>
                             org.apache.harmony.&lt;modulename&gt;.<b>&lt;anything_else&gt;</b>
                         </code>
-                        <p>
-                            All other packages within a module contain internal APIs that may
-                            be referenced from any module.
-                        </p>
-                    </li>
-                </ul>
+                    </dt>
+                    <dd>
+                        All other packages within a module contain internal APIs that may
+                        be referenced from any module.
+                    </dd>
+                </dl>
                                 <p>
                     In practice, this means that module developers are free to change the code within an
                     <code>internal</code> package without expecting any consequences beyond the module

Modified: harmony/standard/site/docs/subcomponents/classlibrary/ser_testing.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/subcomponents/classlibrary/ser_testing.html?view=diff&rev=519951&r1=519950&r2=519951
==============================================================================
--- harmony/standard/site/docs/subcomponents/classlibrary/ser_testing.html (original)
+++ harmony/standard/site/docs/subcomponents/classlibrary/ser_testing.html Mon Mar 19 07:12:06 2007
@@ -251,23 +251,18 @@
                             conventions
                         </a>
                     </li>
-
                     <li>
                         Add the <code>testSerializationCompatibility</code> method to a unit test
                     </li>
-
                     <li>
                         Invoke one of the methods, mentioned above, with corresponding arguments
                     </li>
                 </ul>
                                 <p class="example">Example</p>
-                                <pre>
-                    public void testSerializationCompatibility()
-                    throws Exception {
-
-                    SerializationTest.verifyGolden(this, new SomeSerializableClass());
-                    }
-                </pre>
+                                <pre>public void testSerializationCompatibility()
+throws Exception {
+SerializationTest.verifyGolden(this, new SomeSerializableClass());
+}</pre>
                                 <h3>Self-Testing</h3>
                                 <p>
                     Verifies that an object can be smoothly serialized and deserialized on
@@ -303,13 +298,10 @@
                     </li>
                 </ul>
                                 <p class="example">Example</p>
-                                <pre>
-                    public void testSerializationSelf() throws Exception {
-
-                    SerializationTest.verifySelf(new SomeSerializableClass(),
-                    new MyComparator());
-                    }
-                </pre>
+                                <pre>public void testSerializationSelf() throws Exception {
+SerializationTest.verifySelf(new SomeSerializableClass(),
+new MyComparator());
+}</pre>
                                 <h3>Negative Testing</h3>
                                 <big>
                     <em>TBD</em>
@@ -339,65 +331,51 @@
                     <li>
                         Root folder for resource files is <code>&lt;module root&gt;/src/test/resources/serialization</code>
                     </li>
-
                     <li>
                         Relative path to a resource file <em>MUST</em> match a test's package name
                     </li>
-
                     <li>
                         A resource file <em>MUST</em> start with a test's name
                     </li>
-
                     <li>
                         A resource file <em>MUST</em> contain keywords pointing out to testing scenario
                         <ol>
-
                             <li>
                                 <code>&lt;golden&gt;</code> keyword is used for files generated on RI
                             </li>
-
                             <li>
                                 <code>&lt;harmony&gt;</code> keyword is used for files generated on
                                 Harmony	implementation
                             </li>
-
                             <li>
                                 <code>&lt;negative&gt;</code> keyword is used for files that contain
                                 broken serial form
                             </li>
-
                         </ol>
                     </li>
-
                     <li>
                         A resource file name <em>MUST</em> contain some index
                         <p class="note">Note</p>
                         <p class="notetext">If only one file exists, the index is not required.</p>
-
                     </li>
-
                     <li>
                         Extension for resource files is <code>ser</code>
-
                         <p class="example">Example</p>
                         <p class="exampletext">
                             For the test <code>org.apache.harmony.tests.java.lang.SomeClassTest</code>,
                             we have the following resource files:
                         </p>
-                        <pre>
-                            modules/luni/src/test/resources/serialization
-                            |
-                            \---org/apache/harmony/tests/java/lang
-                            |
-                            \---SomeClassTest.golden.0.ser
-                            SomeClassTest.golden.1.ser
-                            SomeClassTest.golden.2.ser
-                            SomeClassTest.harmony.0.ser
-                            SomeClassTest.harmony.1.ser
-                            SomeClassTest.negative.ser
-                        </pre>
+<pre>modules/luni/src/test/resources/serialization
+|
+\---org/apache/harmony/tests/java/lang
+|
+\---SomeClassTest.golden.0.ser
+    SomeClassTest.golden.1.ser
+    SomeClassTest.golden.2.ser
+    SomeClassTest.harmony.0.ser
+    SomeClassTest.harmony.1.ser
+    SomeClassTest.negative.ser</pre>
                     </li>
-
                 </ul>
                    
                 <p><a href="#top">Back to top</a></p>

Modified: harmony/standard/site/docs/subcomponents/classlibrary/testing.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/subcomponents/classlibrary/testing.html?view=diff&rev=519951&r1=519950&r2=519951
==============================================================================
--- harmony/standard/site/docs/subcomponents/classlibrary/testing.html (original)
+++ harmony/standard/site/docs/subcomponents/classlibrary/testing.html Mon Mar 19 07:12:06 2007
@@ -192,8 +192,8 @@
       <a name="Testing Conventions Used in the Apache Harmony Class Library">Testing Conventions Used in the Apache Harmony Class Library</a>
     </h1>
                         <p>
-                This document describes PROPOSED placement and package naming conventions for
-                different types of Harmony class library tests.
+                <big><i>This document describes PROPOSED placement and package naming conventions for
+                different types of Harmony class library tests.</i></big>
             </p>
                                 <p>
                 The Harmony class library code is organized into modules that might have their own
@@ -219,41 +219,31 @@
                     on RI or other compliant implementations are separated from the imlpementation-independent
                     tests that must pass on RI and all conformant implementations.
                 </p>
-                                <pre>
-                    &lt;modulename&gt;/src/test/<b>impl</b> - Harmony specific tests<br />
-                    &lt;modulename&gt;/src/test/<b>api</b> - Implementation-independent tests
-                </pre>
+                                <pre>&lt;modulename&gt;/src/test/<b>impl</b> - Harmony specific tests
+&lt;modulename&gt;/src/test/<b>api</b> - Implementation-independent tests</pre>
                                 <p>
                     Special-purpose tests like stress tests or tests that require special configuration are
                     separated from general-purpose tests.
                 </p>
-                                <pre>
-                    &lt;modulename&gt;/src/test/<b>stress</b>
-                </pre>
+                                <pre>&lt;modulename&gt;/src/test/<b>stress</b></pre>
                                 <p>
                     Tests are not separated by functionality under test, for example, tests against <code>clone()</code>
-                    methods are <b>not</b> separated from tests against <code>equals()</code> methods.
-
+                    methods are NOT separated from tests against <code>equals()</code> methods.
                     Classpath tests are separated from bootclasspath tests on a directory level:
                 </p>
-                                <pre>
-                    &lt;modulename&gt;/src/test/api/<b>java</b> - Classpath tests<br />
-                    &lt;modulename&gt;/src/test/api/<b>java.injected</b> - Bootclasspath tests
-                </pre>
+                                <pre>&lt;modulename&gt;/src/test/api/<b>java</b> - Classpath tests
+&lt;modulename&gt;/src/test/api/<b>java.injected</b> - Bootclasspath tests</pre>
                                 <p>
                     Find more details <a href="#Package and Class Names for Different Types of the Tests">
-                        below
-                    </a>.
-                </p>
+                        below</a>.
+               </p>
                                 <p>
                     Some modules might have platform specific tests that are in the case separated on a directory
                     level:
                 </p>
-                                <pre>
-                    &lt;modulename&gt;/src/test/api/<b>common</b><br />
-                    &lt;modulename&gt;/src/test/api/<b>windows</b><br />
-                    &lt;modulename&gt;/src/test/api/<b>linux</b>
-                </pre>
+                                <pre>&lt;modulename&gt;/src/test/api/<b>common</b>
+&lt;modulename&gt;/src/test/api/<b>windows</b>
+&lt;modulename&gt;/src/test/api/<b>linux</b></pre>
                    
                                     
     <h2>
@@ -271,40 +261,30 @@
                     <li>
                         If the package under test belongs to a public package, for example, it
                         is a part of the API specification, then the test's package is:
-                        <pre>
-                            org.apache.harmony.&lt;modulename&gt;.tests.<b>&lt;package under test&gt;</b>
-                        </pre>
+<pre>org.apache.harmony.&lt;modulename&gt;.tests.<b>&lt;package under test&gt;</b></pre>
                         <p class="example">Example</p>
-
-                        <pre>
-                            org.apache.harmony.luni.tests.<b>java.lang</b><br />
-                            org.apache.harmony.crypto.tests.<b>javax.crypto</b><br />
-                            org.apache.harmony.auth.tests.<b>org.ietf.jgss</b>
-                        </pre>
+<pre>org.apache.harmony.luni.tests.<b>java.lang</b>
+org.apache.harmony.crypto.tests.<b>javax.crypto</b>
+org.apache.harmony.auth.tests.<b>org.ietf.jgss</b></pre>
                     </li>
                     <li>
                         If the package under test belongs to <code>org.apache.harmony</code>
                         namespace so that class's package is:
-                        <pre>
-                            org.apache.harmony.&lt;modulename&gt;.<b>&lt;rest of the package name&gt;</b>
-                        </pre>
+<pre>org.apache.harmony.&lt;modulename&gt;.<b>&lt;rest of the package name&gt;</b></pre>
                         then the test's package is:
-                        <pre>
-                            org.apache.harmony.&lt;modulename&gt;.tests.<b>&lt;rest of the package name&gt;</b>
-                        </pre>
+<pre>org.apache.harmony.&lt;modulename&gt;.tests.<b>&lt;rest of the package name&gt;</b></pre>
                         <p class="example">Example</p>
-                        <p class="notetext">
+                        <p class="exampletext">
                             <code>org.apache.harmony.luni.internal.net.www.protocol</code> - package under test<br />
                             <code>org.apache.harmony.luni.tests.internal.net.www.protocol</code> - package for the test
                         </p>
-
                     </li>
                 </ol>
                                 <p>
                     To avoid collision of test results for various type of tests, reflect a test type in a test name.
                 </p>
                                 <p class="example">Example</p>
-                                <p class="notetext">
+                                <p class="exampletext">
                     To separate the <code>impl</code> test results from
                     the <code>api</code> ones, the <code>impl</code> test names end with
                     <code>_ImplTest</code>:<br />

Modified: harmony/standard/site/docs/subcomponents/drlvm/DoxygenStart.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/subcomponents/drlvm/DoxygenStart.html?view=diff&rev=519951&r1=519950&r2=519951
==============================================================================
--- harmony/standard/site/docs/subcomponents/drlvm/DoxygenStart.html (original)
+++ harmony/standard/site/docs/subcomponents/drlvm/DoxygenStart.html Mon Mar 19 07:12:06 2007
@@ -191,41 +191,41 @@
                                                                     <h1>
       <a name="DRLVM Source Code Generated Documentation Index">DRLVM Source Code Generated Documentation Index</a>
     </h1>
-                        <p>This is a landing page for Doxygen source code reference generated automatically from interface headers.
-Each link should lead to a documentation bundle generated from a component-related set of header files. 
-The purpose of these documents is to provide a complete reference of available code in DRLVM interfaces. 
-Because the code base is being actively developed, not all interfaces are well-documented at this point, so that
-you can find some interfaces not documented. Everyone's welcome to contribute to this initiative.
+                        <p>This is a landing page for Doxygen source code reference generated automatically from interface headers.
+Each link should lead to a documentation bundle generated from a component-related set of header files. 
+The purpose of these documents is to provide a complete reference of available code in DRLVM interfaces. 
+Because the code base is being actively developed, not all interfaces are well-documented at this point, so that
+you can find some interfaces not documented. Everyone's welcome to contribute to this initiative.
 </p>
-                                <p>
-The documentation bundles were generated automatically and posted on the site server. You can regenerate the docs
-from your source files locally, as described in section <a href="#Regenerating the Reference">Regenerating the Reference</a>.
+                                <p>
+The documentation bundles were generated automatically and posted on the site server. You can regenerate the docs
+from your source files locally, as described in section <a href="#Regenerating the Reference">Regenerating the Reference</a>.
 </p>
                                     
     <h2>
         <a name="Doxygen API Reference for DRLVM Sources">Doxygen API Reference for DRLVM Sources</a>
     </h2>
       
-                        <p>This is a list of links to generated  source code documentation bundles. 
+                        <p>This is a list of links to generated  source code documentation bundles. 
     </p>
-                                <ul>
-      <li><a href="doxygen/intf/html/index.html">DRLVM Interfaces</a> - the high-level interface headers</li>
-      <li><a href="doxygen/em/html/index.html">Execution Manager</a></li>
-      <li>Garbage Collectors:
-      <ul>
-          <li><a href="doxygen/gc_cc/html/index.html">Copying/Compacting Garbage Collector</a></li>
-          <li><a href="doxygen/gc_gen/html/index.html">Generational Garbage Collector</a></li>
-          <li><a href="doxygen/gcv4/html/index.html">Obsolete v.4 Garbage Collector</a></li>
-      </ul></li>
-      <li><a href="doxygen/interpreter/html/index.html">Interpreter</a></li>
-      <li><a href="doxygen/jitrino/html/index.html">Jitrino</a>- the just-in-time compiler </li>
-      <li><a href="doxygen/apr_extension/html/index.html">Porting Layer</a> - the extensions to APR</li>
-      <li><a href="doxygen/thread/html/index.html">Thread Manager</a></li>
-      <li><a href="doxygen/vmcore/html/index.html">VM Infrastructure</a> - the VM core component interfaces</li>
-      <li><a href="doxygen/vmi/html/index.html">Class Library Support</a> -  the VMI interface</li>
-      <li><a href="doxygen/component_manager/html/index.html">Component Manager</a></li>
-      <li><a href="doxygen/tests/html/index.html">DTLVM Tests</a></li>
-      <li><a href="doxygen/drlvm/html/index.html">All DRLVM</a> - the big bundle with all of the above</li>
+                                <ul>
+      <li><a href="doxygen/intf/html/index.html">DRLVM Interfaces</a> - the high-level interface headers</li>
+      <li><a href="doxygen/em/html/index.html">Execution Manager</a></li>
+      <li>Garbage Collectors:
+      <ul>
+          <li><a href="doxygen/gc_cc/html/index.html">Copying/Compacting Garbage Collector</a></li>
+          <li><a href="doxygen/gc_gen/html/index.html">Generational Garbage Collector</a></li>
+          <li><a href="doxygen/gcv4/html/index.html">Obsolete v.4 Garbage Collector</a></li>
+      </ul></li>
+      <li><a href="doxygen/interpreter/html/index.html">Interpreter</a></li>
+      <li><a href="doxygen/jitrino/html/index.html">Jitrino</a>- the just-in-time compiler </li>
+      <li><a href="doxygen/apr_extension/html/index.html">Porting Layer</a> - the extensions to APR</li>
+      <li><a href="doxygen/thread/html/index.html">Thread Manager</a></li>
+      <li><a href="doxygen/vmcore/html/index.html">VM Infrastructure</a> - the VM core component interfaces</li>
+      <li><a href="doxygen/vmi/html/index.html">Class Library Support</a> -  the VMI interface</li>
+      <li><a href="doxygen/component_manager/html/index.html">Component Manager</a></li>
+      <li><a href="doxygen/tests/html/index.html">DTLVM Tests</a></li>
+      <li><a href="doxygen/drlvm/html/index.html">All DRLVM</a> - the big bundle with all of the above</li>
     </ul>
                    
                                     
@@ -233,49 +233,49 @@
         <a name="Other Useful DRLVM documents">Other Useful DRLVM documents</a>
     </h2>
       
-                        <ul>
-      <li><a href="index.html" target="_blank">DRLVM
-      website documentation page</a> with links to all DRLVM documents</li>
-      <li><a href="http://wiki.apache.org/harmony/DRLVM_Documentation_Quality">Status
-      metrics for Doxygen API reference</a>, Wiki page with metrics that show improvement metrics for the reference </li>
+                        <ul>
+      <li><a href="index.html" target="_blank">DRLVM
+      website documentation page</a> with links to all DRLVM documents</li>
+      <li><a href="http://wiki.apache.org/harmony/DRLVM_Documentation_Quality">Status
+      metrics for Doxygen API reference</a>, Wiki page with metrics that show improvement metrics for the reference </li>
     </ul>
                    
                 <p><a href="#top">Back to top</a></p>
                                                 <h1>
       <a name="Regenerating the Reference">Regenerating the Reference</a>
     </h1>
-                        <p>
-You can locally regenerate reference materials analogous to those posted on the website. This can be especially useful when writing comments to your code: parsing the newly added comments with Doxygen is an ideal test. To avoid parsing the whole source tree, you can adjust the list of files to include into a specific documentation bundle or configure Doxygen to produce a different output, see section <a href="#Advanced Tasks">Advanced Tasks</a>.
+                        <p>
+You can locally regenerate reference materials analogous to those posted on the website. This can be especially useful when writing comments to your code: parsing the newly added comments with Doxygen is an ideal test. To avoid parsing the whole source tree, you can adjust the list of files to include into a specific documentation bundle or configure Doxygen to produce a different output, see section <a href="#Advanced Tasks">Advanced Tasks</a>.
 </p>
                                 <p>Follow these instructions to regenerate the Doxygen reference documentation locally:</p>
-                                <ol>
-<li>Check out the source code tree. Run <code>svn update</code> to make sure you have the latest version of doc-generation support files.
-</li>
-<li>Go to the directory <code>trunk/working_vm/vm/doc</code> and run:
-<pre>$ ant</pre>
-</li>
+                                <ol>
+<li>Check out the source code tree. Run <code>svn update</code> to make sure you have the latest version of doc-generation support files.
+</li>
+<li>Go to the directory <code>trunk/working_vm/vm/doc</code> and run:
+<pre>$ ant</pre>
+</li>
 </ol>
-                                <p>
-That's it! You should get the Doxygen docs in a set of subdirectories in <code>doc</code>. 
+                                <p>
+That's it! You should get the Doxygen docs in a set of subdirectories in <code>doc</code>. 
 <br />Use the <code>DoxygenStart.html</code> file as your starting point. </p>
                                     
     <h2>
         <a name="Advanced Tasks">Advanced Tasks</a>
     </h2>
       
-                        <p>
-Generation of Doxygen reference is adjusted by the following files located in <code>trunk/vm/doc</code>:
+                        <p>
+Generation of Doxygen reference is adjusted by the following files located in <code>trunk/vm/doc</code>:
 </p>
-                                <dl>
-<dt>doc.properties</dt>
-<dd>Defines the input files included in each bundle. Edit the file per source tree changes. You can also create a new target in this file to include your customized set of files. In this case, remember to add corresponding <code>clean</code> and <code>create</code> targets into <code>build.xml</code>. 
-</dd>
-<dt>build.xml</dt>
-<dd>Lists all doc build targets. When called, <code>ant</code> deletes all previously generated content (if any) and creates new directories for each bundle and places documentation there in the <code>html</code> subfolder. That location also contains the <code>log.txt</code> file with the list of errors and warnings produced by Doxygen. Use the log to track progress with commenting.
-</dd>
-<dt>vm.cfg</dt> 
-<dd>Is a copy of classlib configuration files and defines formatting and other output properties for Doxygen. Modify this file to get a different output format, adjust the header and footer in resulting docs, edit the parsing conditions, etc.
-</dd>
+                                <dl>
+<dt>doc.properties</dt>
+<dd>Defines the input files included in each bundle. Edit the file per source tree changes. You can also create a new target in this file to include your customized set of files. In this case, remember to add corresponding <code>clean</code> and <code>create</code> targets into <code>build.xml</code>. 
+</dd>
+<dt>build.xml</dt>
+<dd>Lists all doc build targets. When called, <code>ant</code> deletes all previously generated content (if any) and creates new directories for each bundle and places documentation there in the <code>html</code> subfolder. That location also contains the <code>log.txt</code> file with the list of errors and warnings produced by Doxygen. Use the log to track progress with commenting.
+</dd>
+<dt>vm.cfg</dt> 
+<dd>Is a copy of classlib configuration files and defines formatting and other output properties for Doxygen. Modify this file to get a different output format, adjust the header and footer in resulting docs, edit the parsing conditions, etc.
+</dd>
 </dl>
                                 <p class="note">Note</p>
                                 <p class="notetext">The file <code>vm.cfg</code> now depends on the <code>css</code> and other support files located in the classlib trunk. To parse DRLVM sources with Doxygen, you also need to have class library sources checked out. </p>



Mime
View raw message