harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From nadi...@apache.org
Subject svn commit: r519951 [3/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/subcomponents/drlvm/TM.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/subcomponents/drlvm/TM.html?view=diff&rev=519951&r1=519950&r2=519951
==============================================================================
--- harmony/standard/site/docs/subcomponents/drlvm/TM.html (original)
+++ harmony/standard/site/docs/subcomponents/drlvm/TM.html Mon Mar 19 07:12:06 2007
@@ -222,108 +222,53 @@
       <h1>
          <a id="top" name="top"></a>Thread Manager
       </h1>
-   
-      <p class="TOCHeading">
-         <a href="#RevisionHistory">1. Revision History</a>
-      </p>
-      
-      <p class="TOCHeading">
-         <a href="#About_This_Document">2. About this Document</a>
-      </p>
-      <p class="TOC">
-         <a href="#Purpose">2.1 Purpose</a>
-      </p>
-      <p class="TOC">
-         <a href="#Intended_Audience">2.2 Intended Audience</a>
-      </p>
-      <p class="TOC">
-         <a href="#Documentation_Conventions">2.3 Documentation Conventions</a>
-      </p>
-      <p class="TOC">
-         <a href="#Using_this_document">2.4 Using this Document</a>
-      </p>
-      <p class="TOCHeading">
-         <a href="#Overview">2. Overview</a>
-      </p>
-      <p class="TOC">
-         <a href="#Key_Feature">2.1 Key Features</a>
-      </p>
-      <p class="TOC">
-         <a href="#TM_in_VM">2.2 Thread Manager in VM</a>
-      </p>
-      <p class="TOC">
-         <a href="#Portability">2.3 Portability</a>
-      </p>
-      <p class="TOCHeading">
-         <a href="#Achitecture">4. Architecture</a>
-      </p>
-      <p class="TOC">
-         <a href="#Exported_Interfaces">4.1 Exported interfaces</a>
-      </p>
-      <blockquote>
-         <p class="TOC">
-            <a href="#Native_Layer">4.1.1 Native Interface</a>
-         </p>
-         <p class="TOC">
-            <a href="#Java_interface">4.1.2 Java* Interface</a>
-         </p>
-      </blockquote>
-      <p class="TOC">
-         <a href="#Data_Structures">4.2 Data structures</a>
-      </p>
-      <p class="TOC">
-         <a href="#Thread_Control_Structure">4.3 Thread control structures</a>
-      </p>
-      <blockquote>
-         <p class="TOC">
-            <a href="#Native_Structure">4.3.1 Native Thread Structure</a>
-         </p>
-         <p class="TOC">
-            <a href="#Java_Structure">4.3.2 Java* Thread Structure</a>
-         </p>
-      </blockquote>
-      <p class="TOC">
-         <a href="#Thread_Group">4.4 Thread Groups</a>
-      </p>
-      <p class="TOC">
-         <a href="#Synchronizer">4.5 Synchronizers</a>
-      </p>
-      <p class="TOC">
-         <a href="#Monitors">4.6 Monitors</a>
-      </p>
-      <blockquote>
-         <p class="TOC">
-            <a href="#MonitorInflation">4.6.1 Inflation Technique</a>
-         </p>
-         <p class="TOC">
-            <a href="#Thin_monitors">4.6.2 Monitor Structure</a>
-         </p>
-         <p class="TOC">
-            <a href="#AcquireMonitor">4.6.3 Acquiring a Monitor</a>
-         </p>
-      </blockquote>
-      <p class="TOCHeading">
-         <a href="#Usage_Scenarios">5. Usage scenarios</a>
-      </p>
-      <p class="TOC">
-         <a href="#Thread_lifecycle">5.1 Java* Thread Life Cycle</a>
-      </p>
-      <p class="TOC">
-         <a href="#Thread_suspension">5.2 Thread Suspension</a>
-      </p>
-      <p class="TOC">
-         <a href="#Stop-the-world_Suspension">5.3 Stop-the-world Thread
-         Suspension</a>
-      </p>
-      <p class="TOC">
-         <a href="#Thread_locking">5.4 Thread Locking</a>
-      </p>
-      <p class="TOC">
-         <a href="#Monitor_scenarios">5.5 Monitor Enter and Exit</a>
-      </p>
-      <p class="TOCHeading">
-         <a href="#References">6. References</a>
-      </p>
+   <ol class="TOC">
+      <li><a href="#RevisionHistory">1. Revision History</a></li>
+      <li><a href="#About_This_Document">2. About this Document</a>
+         <ol>
+            <li><a href="#Purpose">2.1 Purpose</a></li>
+            <li><a href="#Intended_Audience">2.2 Intended Audience</a></li>
+            <li><a href="#Documentation_Conventions">2.3 Documentation Conventions</a></li>
+            <li><a href="#Using_this_document">2.4 Using this Document</a></li>
+         </ol></li>
+      <li><a href="#Overview">3. Overview</a>
+         <ol>
+            <li><a href="#Key_Feature">3.1 Key Features</a></li>
+            <li><a href="#TM_in_VM">3.2 Thread Manager in VM</a></li>
+            <li><a href="#Portability">3.3 Portability</a></li>
+         </ol></li>
+      <li><a href="#Achitecture">4. Architecture</a>
+         <ol>
+            <li><a href="#Exported_Interfaces">4.1 Exported interfaces</a>
+               <ul>
+                  <li><a href="#Native_Layer">4.1.1 Native Interface</a></li>
+                  <li><a href="#Java_interface">4.1.2 Java* Interface</a></li>
+               </ul></li>
+            <li><a href="#Data_Structures">4.2 Data structures</a></li>
+            <li><a href="#Thread_Control_Structure">4.3 Thread control structures</a>
+               <ul>
+                  <li><a href="#Native_Structure">4.3.1 Native Thread Structure</a></li>
+                  <li><a href="#Java_Structure">4.3.2 Java* Thread Structure</a></li>
+               </ul></li>
+            <li><a href="#Thread_Group">4.4 Thread Groups</a></li>
+            <li><a href="#Synchronizer">4.5 Synchronizers</a></li>
+            <li><a href="#Monitors">4.6 Monitors</a>
+               <ul>
+                  <li><a href="#MonitorInflation">4.6.1 Inflation Technique</a></li>
+                  <li><a href="#Thin_monitors">4.6.2 Monitor Structure</a></li>
+                  <li><a href="#AcquireMonitor">4.6.3 Acquiring a Monitor</a></li>
+               </ul></li>
+         </ol></li>
+      <li><a href="#Usage_Scenarios">5. Usage scenarios</a>
+         <ol>
+            <li><a href="#Thread_lifecycle">5.1 Java* Thread Life Cycle</a></li>
+            <li><a href="#Thread_suspension">5.2 Thread Suspension</a></li>
+            <li><a href="#Stop-the-world_Suspension">5.3 Stop-the-world Thread Suspension</a></li>
+            <li><a href="#Thread_locking">5.4 Thread Locking</a></li> 
+            <li><a href="#Monitor_scenarios">5.5 Monitor Enter and Exit</a></li>
+         </ol></li>
+      <li><a href="#References">6. References</a></li>
+   </ol>
       <h1>
          <a id="RevisionHistory" name="RevisionHistory"></a>1. Revision History
       </h1>
@@ -2102,6 +2047,7 @@
       </p>
    </body>
 </html>
+
 
 
 

Modified: harmony/standard/site/docs/subcomponents/drlvm/debugging_VM_and_JIT.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/subcomponents/drlvm/debugging_VM_and_JIT.html?view=diff&rev=519951&r1=519950&r2=519951
==============================================================================
--- harmony/standard/site/docs/subcomponents/drlvm/debugging_VM_and_JIT.html (original)
+++ harmony/standard/site/docs/subcomponents/drlvm/debugging_VM_and_JIT.html Mon Mar 19 07:12:06 2007
@@ -228,33 +228,28 @@
         The document includes two groups of debugging tips, one for VM tips, and the other
         for JIT compiler tips, as shown below.
     </p>
-    <p>
-        <a href="#Debugging_VM">Debugging the Virtual Machine</a>
+    <p class="TOCHeading">
+     <a href="#Debugging_VM">Debugging the Virtual Machine</a>
     </p>
-    <blockquote>
-        <p>
-            <a href="#How_to_debug_VM">How to debug the VM?</a>
+<p class="TOC">
+        <a href="#How_to_debug_VM">How to debug the VM?</a>
         </p>
-        <p>
+<p class="TOC">
             <a href="#Extended_Debug_VM">How to get more of your debugging?</a>
         </p>
-    </blockquote>
-    <p>
+<p class="TOCHeading">
         <a href="#Debugging_JIT">Debugging the Jitrino.JET Baseline Compiler</a>
     </p>
-    <blockquote>
-        <p>
-            <a href="#Enable_Tracing">How to enable tracing in Jitrino.JET?</a>
+<p class="TOC">
+        <a href="#Enable_Tracing">How to enable tracing in Jitrino.JET?</a>
         </p>
-        <p>
+<p class="TOC">
             <a href="#Config_Trace_Logging">How to configure trace logging?</a>
         </p>
-        <p>
+<p class="TOC">
             <a href="#Extend_Trace_JIT">How to get more of your tracing?</a>
         </p>
-    </blockquote>
-    <p>
-        <a href="#top">Back to top</a>
+        <p><a href="#top">Back to top</a>
     </p>
     <h1>
         <a name="Debugging_VM">Debugging the Virtual Machine</a>
@@ -915,6 +910,7 @@
     </p>
 </body>
 </html>
+
 
 
 </div>

Modified: harmony/standard/site/docs/subcomponents/drlvm/emguide.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/subcomponents/drlvm/emguide.html?view=diff&rev=519951&r1=519950&r2=519951
==============================================================================
--- harmony/standard/site/docs/subcomponents/drlvm/emguide.html (original)
+++ harmony/standard/site/docs/subcomponents/drlvm/emguide.html Mon Mar 19 07:12:06 2007
@@ -212,10 +212,7 @@
 Execution Manager (EM) is a component in DRLVM that controls 
 profile collection and recompilation processes.
 <br />
-For detailed information on EM, see the 
- <a href="EM.html">
-   Execution Manager Component Description
-   </a>.
+For detailed information on EM, see the <a href="EM.html">Execution Manager Component Description</a>.
 </p>
                    
                                     
@@ -225,24 +222,19 @@
       
                         <p>
 The set of JIT compilers and profile collectors used at run time and their
- relations is stored in the <i>EM configuration file</i>.
+relations is stored in the <i>EM configuration file</i>.
 During the VM initialization phase, EM uses hard-coded configuration or reads 
-it from the config file, if specified. 
-<br />
-You can use the following command-line option to make EM read its 
-configuration from the file:<br />
-<code>-Xem:&lt;path to configuration file&gt;</code>
-<br />
-or   <br />
-<code>-Dem.properties=&lt;configuration.file.path&gt;</code>
-</p>
+it from the config file, if specified.</p>
+                                <p>You can use the following command-line option to make EM read its configuration from the file:</p>
+                                <pre>-Xem:&lt;path to configuration file&gt;</pre>
+                                <pre>-Dem.properties=&lt;configuration.file.path&gt;</pre>
                                 <p>
-The following is a line-by-line description of the default EM configuration. 
-These configuration settings can be used as a prototype to create 
+The following is a line-by-line description of the default EM configuration.
+These configuration settings can be used as a prototype to create
 new custom EM configuration files.
 The default configuration is:
 </p>
-                                <p><pre>
+                                <pre>
 chains=chain1,chain2
 
 chain1.jits=JET_CLINIT
@@ -262,89 +254,75 @@
 JET_DPGO_PROFILE. mode=SYNC
 JET_DPGO_PROFILE.entryThreshold=10000
 JET_DPGO_PROFILE.backedgeThreshold=100000
-</pre></p>
-                                <p>A line-by-line description of the settings follows. </p>
+</pre>
+                                <p>A line-by-line description of the settings follows.</p>
                                 <pre>
 chains=chain1,chain2
 </pre>
                                 <p>
-Every EM configuration file must define the <code>chains</code> property 
+Every EM configuration file must define the <code>chains</code> property
 to indicate sequences of JIT compilers to be used to compile and/or recompile
- a method. In this example, two recompilation chains are set for the system: 
-<code>chain1</code> and <code>chain2</code>. EM analyzes chains until it has 
-chosen the chain for the method. 
+ a method. In this example, two recompilation chains are set for the system:
+<code>chain1</code> and <code>chain2</code>. EM analyzes chains until it has
+chosen the chain for the method.
 </p>
                                 <pre>
 chain1.jits=JET_CLINIT
 chain2.jits=JET_DPGO,OPT
 </pre>
                                 <p>
-In this case, <code>chain1</code> has one JIT compiler 
+In this case, <code>chain1</code> has one JIT compiler
 <code>JET_CLINIT</code>, and <code>chain2</code> has
  two compilers: <code>JET_DPGO</code> and <code>OPT</code>.
-Using these JIT names, EM reads JIT-specific configuration 
-and passes the names to JIT instances during initialization. 
-A compiler instance can use its name to distinguish between 
-its own properties and those of other JITs.  <br />
-</p>
-                                <p>
-<b>Note:</b> Jitrino, the current default DRLVM JIT compiler, 
-selects Jitrino.JET (fast, non-optimizing compiler) if the name 
-starts with the <code>JET</code> prefix. Otherwise, the JIT 
-instance is treated as Jitrino.OPT.
-</p>
+Using these JIT names, EM reads JIT-specific configuration
+and passes the names to JIT instances during initialization.
+A compiler instance can use its name to distinguish between
+its own properties and those of other JITs.</p>
+                                <p class="note">Note</p>
+                                <p class="notetext">Jitrino, the current default DRLVM JIT compiler,
+        selects Jitrino.JET (fast, non-optimizing compiler) if the name
+        starts with the <code>JET</code> prefix. Otherwise, the JIT
+        instance is treated as Jitrino.OPT.</p>
                                 <pre>
 chain1.filter=+::&lt;clinit&gt; 
 chain1.filter=-
 </pre>
                                 <p>
 Method filters are used to select methods that will be compiled
- by the first JIT in a chain. 
+by the first JIT in a chain.
 In this example, the first line configures <code>chain1</code> 
-to accept all <code>&lt;clinits&gt;</code> methods 
-and the second line - to refuse to compile all other methods. <br />
-The order of filters for every chain is significant. Chain
- filters can be considered as if-else clauses: <br />
+to accept all <code>&lt;clinits&gt;</code> methods
+and the second line - to refuse to compile all other methods </p>
+                                <p>The order of filters for every chain is significant. Chain
+filters can be considered as if-else clauses:<br />
 If a filter matches a method, EM stops examining other filters
- and analyzes the first sign in the filter: <br />
-<ul>
-<li>For a <code>+</code>, EM requests the first JIT in the 
-chain to compile the method. </li>
-<li>For a <code>-</code>, EM tries the next chain in the list. </li>
+and analyzes the first sign in the filter:</p>
+                                <ul>
+<li>For a <code>+</code>, EM requests the first JIT in the
+chain to compile the method.</li>
+<li>For a <code>-</code>, EM tries the next chain in the list.</li>
 </ul>
-If no filter has matched the compilation request, EM considers 
-that the method is accepted to be compiled by the chain. 
-<br />
-Here is a format of all currently supported method filters. 
+                                <p>
+If no filter has matched the compilation request, EM considers
+that the method is accepted to be compiled by the chain.
+Here is a format of all currently supported method filters.
 </p>
-                                <br />
                                 <table>
                         <tr>
-                        <td class="TableCell" colspan="" rowspan="" >
-    
-                
-<b>Filter Type</b>
-
-        </td>
-                                <td class="TableCell" colspan="" rowspan="" >
-    
-                
-<b>Filter Format   </b>
-
-        </td>
-                                <td class="TableCell" colspan="" rowspan="" >
-    
-                
-<b>Filter Examples </b>
-
-        </td>
+                        <th class="TableHeading" colspan="" rowspan="">
+                Filter Type
+        </th>
+                                <th class="TableHeading" colspan="" rowspan="">
+                Filter Format
+        </th>
+                                <th class="TableHeading" colspan="" rowspan="">
+                Filter Examples
+        </th>
             </tr>
                                 <tr>
                         <td class="TableCell" colspan="" rowspan="" >
     
-                
-Name filter
-
+                Name filter
         </td>
                                 <td class="TableCell" colspan="" rowspan="" >
     
@@ -378,9 +356,9 @@
                                 <td class="TableCell" colspan="" rowspan="" >
     
                 
-'<i>+10B..100B</i>' accepts all methods of bytecode size in range of 
+'<i>+10B..100B</i>' accepts all methods of bytecode size in range of
 [10..100].<br />
-'<i>-20B</i>' rejects all methods of bytecode size equal to 20. 
+'<i>-20B</i>' rejects all methods of bytecode size equal to 20.
 
         </td>
             </tr>
@@ -406,63 +384,58 @@
         </td>
             </tr>
             </table>
-                                <br />
-                                <p>
-<b>Note:</b> The sequential method number could be changed from run 
-to run in multithreaded environments. 
-</p>
-                                <p><pre>
+                                <p class="note">Note</p>
+                                <p class="notetext">The sequential method number could be changed from run
+to run in multithreaded environments.</p>
+                                <pre>
 JET_CLINIT.file=&lt;path to dll&gt;
 JET_DPGO.file=&lt;path to dll&gt;
 OPT.file=&lt;path to dll&gt;
-</pre></p>
+</pre>
                                 <p>
 For every JIT, the configuration file must define the location of the library
- file location.
-Multiple JIT compilers can be associated with the same library. 
-For example, all paths can point to the same jit.dll file. 
-</p>
-                                <p><pre>
+file location. Multiple JIT compilers can be associated with the same library.
+For example, all paths can point to the same jit.dll file.</p>
+                                <pre>
 JET_DPGO.genProfile=JET_DPGO_PROFILE
 JET_DPGO_PROFILE.profilerType=ENTRY_BACKEDGE_PROFILER
 OPT.useProfile=JET_DPGO_PROFILE
-</pre></p>
+</pre>
                                 <p>
-These settings define profile collection and recompilation event 
-configuration for two JIT compilers: <code>JET_DPGO</code> 
+These settings define profile collection and recompilation event
+configuration for two JIT compilers: <code>JET_DPGO</code>
 and <code>OPT</code>.
-The first line configures <code>JET_DPGO</code> to generate a 
-profile <code>JET_DPGO_PROFILE</code>, 
-with the type of associated profile collector specified in the 
-second line. <code>ENTRY_BACKEDGE_PROFILER</code> 
-is the built-in DRL EM profile collector type. 
-In the third line, the <code>OPT</code> compiler is configured 
+The first line configures <code>JET_DPGO</code> to generate a
+profile <code>JET_DPGO_PROFILE</code>,
+with the type of associated profile collector specified in the
+second line. <code>ENTRY_BACKEDGE_PROFILER</code>
+is the built-in DRL EM profile collector type.
+In the third line, the <code>OPT</code> compiler is configured
 to use the new profile.
-After reading these configuration settings, the execution 
-manager does the following: <br />
-<ol>
-<li>Instantiates the profile collector of the type 
-<code>ENTRY_BACKEDGE_PROFILER</code>. </li>
-<li>Checks whether the <code>JET_DPGO</code> JIT can generate 
+After reading these configuration settings, the execution
+manager does the following:</p>
+                                <ol>
+<li>Instantiates the profile collector of the type
+<code>ENTRY_BACKEDGE_PROFILER</code>.</li>
+<li>Checks whether the <code>JET_DPGO</code> JIT can generate
 method profiles of this type; if so, requests the JIT to enable
- profile generation. </li>
-<li>Checks whether the <code>OPT JIT</code> can use method 
-profiles of this type. </li>
-<li>Registers the profile collector as active. </li>
+ profile generation.</li>
+<li>Checks whether the <code>OPT JIT</code> can use method
+profiles of this type.</li>
+<li>Registers the profile collector as active.</li>
 </ol>
-</p>
-                                <p><pre>
+                                <pre>
 JET_DPGO_PROFILE. mode=SYNC
 JET_DPGO_PROFILE.entryThreshold=10000
-JET_DPGO_PROFILE.backedgeThreshold=100000 
-</pre></p>
+JET_DPGO_PROFILE.backedgeThreshold=100000
+</pre>
                                 <p>
-The last 4 lines contain the configuration of the <code>JET_DPGO_PROFILE</code>
- profiler. These properties are specific for every profile collector type. 
-The first option runs entry-backedge profile mode in the SYNC mode: counters 
-check is done during the code execution. Use  ASYNC to run counters 
-checking in a separate thread. The last 2 options set the profile readiness 
-threshold. Once the profile is ready, EM dispatches the method for 
+The last four lines contain the configuration of the <code>JET_DPGO_PROFILE</code>
+profiler. These properties are specific for every profile collector type.
+The first option runs entry-backedge profile mode in the SYNC mode: counters
+check is done during the code execution. Use  ASYNC to run counters
+checking in a separate thread. The last 2 options set the profile readiness
+threshold. Once the profile is ready, EM dispatches the method for
 recompilation with the next JIT in the current chain.
 </p>
                    
@@ -472,53 +445,45 @@
     </h2>
       
                         <p>
-Use the following command-line options to trace EM events:
-<br />
-<code>-verbose:em</code> dumps all EM events.<br />
-<code>-verbose:em.JIT_NAME</code> dumps only JIT named 
-"<code>JIT_NAME</code>" related events. <br />
-<code>-verbose:em.profiler.PROFILER_NAME</code> dumps only profiler
- "<code>PROFILER_NAME</code>" related events.<br />
-</p>
+Use the following command-line options to trace EM events:</p>
+                                <ul>
+<li><code>-verbose:em</code> dumps all EM events.</li>
+<li><code>-verbose:em.JIT_NAME</code> dumps only JIT named "<code>JIT_NAME</code>" related events.</li>
+<li><code>-verbose:em.profiler.PROFILER_NAME</code> dumps only profiler "<code>PROFILER_NAME</code>"
+related events.</li>
+</ul>
                                 <p class="example">
-    Example
-  </p>
+Example
+</p>
                                 <p class="exampletext">
 For the default EM configuration file, 
-<br /><code>
--verbose:em.OPT 
-</code><br /> dumps all methods names that are compiled with 
-Jitrino.OPT. According to the configuration details, these methods 
-are hot methods.
-</p>
-                                <p class="exampletext">Alternatively, you can get almost the same information by using 
-the following: 
-<br /><code>
--verbose:em.profiler.JET_DPGO_PROFILE 
-</code><br /> additionally dumps information about hot method profiles.
-</p>
+<code>-verbose:em.OPT</code>dumps all methods names that are compiled with
+Jitrino.OPT. According to the configuration details, these methods
+are hot methods.<br />
+Alternatively, you can get almost the same information by using
+the following:
+<code>-verbose:em.profiler.JET_DPGO_PROFILE</code> additionally dumps
+information about hot method profiles.</p>
                                 <p class="example">Examples of output:</p>
-                                <br />
-                                <code>
-C:\tools\decapo&gt;c:\tools\harmony0706\bin\java.exe  -verbose:em.OPT -jar dacapo-beta051009.jar xalan<br />
-EM: recompile start:[OPT n=1] java/io/ByteArrayOutputStream::write(I)V<br />
-EM: recompile done:[OPT n=1] java/io/ByteArrayOutputStream::write(I)V<br />
-EM: recompile start:[OPT n=2] java/lang/String::hashCode()I<br />
-EM: recompile done:[OPT n=2] java/lang/String::hashCode()I<br />
-...<br />
-C:\tools\decapo&gt;c:\tools\harmony0706\bin\java.exe  -verbose:em.profiler.JET_DPGO_PROFILE -jar dacapo-beta051009.jar xalan<br />
-EM: entry-backedge profiler intialized: JET_DPGO_PROFILE entry threshold:10000 backedge threshold:100000 mode:SYNC<br />
-EM: profiler[JET_DPGO_PROFILE] profile is ready [e:10000 b:0] java/io/ByteArrayOutputStream::write(I)V<br />
-EM: profiler[JET_DPGO_PROFILE] profile is ready [e:10000 b:59575] java/lang/String::hashCode()I<br />
-EM: profiler[JET_DPGO_PROFILE] profile is ready [e:10000 b:0] java/lang/String::length()I<br />
-EM: profiler[JET_DPGO_PROFILE] profile is ready [e:10000 b:0] java/lang/String::charAt(I)C<br />
-EM: profiler[JET_DPGO_PROFILE] profile is ready [e:10000 b:0] java/nio/charset/Charset::isLetter(C)Z<br />
-EM: profiler[JET_DPGO_PROFILE] profile is ready [e:10000 b:0] java/nio/charset/Charset::isDigit(C)Z<br />
-EM: profiler[JET_DPGO_PROFILE] profile is ready [e:10000 b:0] java/nio/Buffer::remaining()I<br />
-EM: profiler[JET_DPGO_PROFILE] profile is ready [e:10000 b:0] java/util/HashMap::getModuloHash(Ljava/lang/Object;)I<br />
-...  <br />
-</code>
-                                <br />
+                                <pre>
+C:\tools\decapo&gt;c:\tools\harmony0706\bin\java.exe  -verbose:em.OPT -jar dacapo-beta051009.jar xalan
+EM: recompile start:[OPT n=1] java/io/ByteArrayOutputStream::write(I)V
+EM: recompile done:[OPT n=1] java/io/ByteArrayOutputStream::write(I)V
+EM: recompile start:[OPT n=2] java/lang/String::hashCode()I
+EM: recompile done:[OPT n=2] java/lang/String::hashCode()I
+...
+C:\tools\decapo&gt;c:\tools\harmony0706\bin\java.exe  -verbose:em.profiler.JET_DPGO_PROFILE -jar dacapo-beta051009.jar xalan
+EM: entry-backedge profiler intialized: JET_DPGO_PROFILE entry threshold:10000 backedge threshold:100000 mode:SYNC
+EM: profiler[JET_DPGO_PROFILE] profile is ready [e:10000 b:0] java/io/ByteArrayOutputStream::write(I)V
+EM: profiler[JET_DPGO_PROFILE] profile is ready [e:10000 b:59575] java/lang/String::hashCode()I
+EM: profiler[JET_DPGO_PROFILE] profile is ready [e:10000 b:0] java/lang/String::length()I
+EM: profiler[JET_DPGO_PROFILE] profile is ready [e:10000 b:0] java/lang/String::charAt(I)C
+EM: profiler[JET_DPGO_PROFILE] profile is ready [e:10000 b:0] java/nio/charset/Charset::isLetter(C)Z
+EM: profiler[JET_DPGO_PROFILE] profile is ready [e:10000 b:0] java/nio/charset/Charset::isDigit(C)Z
+EM: profiler[JET_DPGO_PROFILE] profile is ready [e:10000 b:0] java/nio/Buffer::remaining()I
+EM: profiler[JET_DPGO_PROFILE] profile is ready [e:10000 b:0] java/util/HashMap::getModuloHash(Ljava/lang/Object;)I
+...  
+</pre>
                    
                                     
     <h2>
@@ -535,33 +500,32 @@
     prefix in the name is a Jitrino.JET instance. <br />
     Another difference in these configurations are options passed to the JIT compiler.
   </p>
-                                <p><i>These configurations have only one JIT and no profile collection or recompilation.</i></p>
+                                <p class="class">These configurations have only one JIT and no profile collection or recompilation.</p>
                                 <p><b>
   <code>-Xem:jet</code> - the baseline compiler mode configuration</b></p>
-                                <p><pre>
+                                <pre>
 chains=chain1
 chain1.jits=JET
 JET.file=&lt;path to dll&gt;
-</pre></p>
+</pre>
                                 <p><b>
   <code>-Xem:opt</code> - the client-static mode configuration</b></p>
-                                <p><pre>
+                                <pre>
 chains=chain1
 chain1.jits=CS_OPT
 OPT.file=&lt;path to dll&gt;
-</pre></p>
+</pre>
                                 <p><b>
   <code>-Xem:server_static</code> - the server-static mode configuration</b></p>
-                                <p><pre>
+                                <pre>
 chains=chain1
 chain1.jits=SS_OPT
 OPT.file=&lt;path to dll&gt;
-</pre></p>
-                                <br />
-                                <p><i>These configurations use recompilation and collect profiles.</i></p>
+</pre>
+                                <p class="class">These configurations use recompilation and collect profiles.</p>
                                 <p><b>
   <code>-Xem:client</code> - the default configuration, or client dynamic</b></p>
-                                <p><pre>
+                                <pre>
 chains=chain1,chain2
 chain1.jits=JET_CLINIT
 chain2.jits=JET_DPGO,CD_OPT
@@ -586,10 +550,10 @@
 EB_PROF.mode=SYNC
 EB_PROF.entryThreshold=10000
 EB_PROF.backedgeThreshold=100000
-</pre></p>
+</pre>
                                 <p><b>
   <code>-Xem:server</code> - the server mode configuration, or server dynamic</b></p>
-                                <p><pre>
+                                <pre>
 chains=chain1,chain2
 chain1.jits=JET_CLINIT
 chain2.jits=SD1_OPT,SD2_OPT
@@ -610,7 +574,7 @@
 
 SD1_OPT.genProfile=EDGE_PROF
 SD2_OPT.useProfile=EDGE_PROF
-</pre></p>
+</pre>
                                 <p class="note">Note</p>
                                 <p class="notetext">To run VM in the intereter mode, use the <code>-Xint</code> 
 command-line option to override any other EM settings. Currently, DRLVM does

Modified: harmony/standard/site/docs/subcomponents/drlvm/encoder_library.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/subcomponents/drlvm/encoder_library.html?view=diff&rev=519951&r1=519950&r2=519951
==============================================================================
--- harmony/standard/site/docs/subcomponents/drlvm/encoder_library.html (original)
+++ harmony/standard/site/docs/subcomponents/drlvm/encoder_library.html Mon Mar 19 07:12:06 2007
@@ -198,7 +198,7 @@
       
                         <ol>
           <li>
-            <a href="#1. Revision History">Revision Ristory</a>
+            <a href="#1. Revision History">Revision History</a>
           </li>
           <li><a href="#2. About this document">About
     this Document</a> </li>
@@ -256,9 +256,9 @@
                                 <td class="TableCell" colspan="" rowspan="" >
     
                 
-              Alexander Astapchuk, Svetlana
-              Konovalova: document created.
-            
+                      Alexander Astapchuk, Svetlana
+                      Konovalova: document created.
+                  
         </td>
                                 <td class="TableCell" colspan="" rowspan="" >
     
@@ -558,7 +558,7 @@
         <a name="6. How It Works">6. How It Works</a>
     </h2>
       
-                        <a name="6.1 Usage Model"><b>6.1 Usage Model</b></a>
+                        <h3><a name="6.1 Usage Model"><b>6.1 Usage Model</b></a></h3>
                                 <p>
         The base encoding interface
         <code>EncoderBase::encode()</code> is a common generic
@@ -605,7 +605,7 @@
         <code>vm/vmcore/src/jvmti/jvmti_dasm.cpp</code>,
         <code>vm/vmcore/include/jvmti_dasm.h</code>.
       </p>
-                                <a name="6.2 Under the Hood"><b>6.2 Under the Hood</b></a>
+                                <h3><a name="6.2 Under the Hood"><b>6.2 Under the Hood</b></a></h3>
                                 <p>
         The engine gets its input as an operation and a set of
         operands, and performs the following operations:

Modified: harmony/standard/site/xdocs/code_scan_tools.xml
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/code_scan_tools.xml?view=diff&rev=519951&r1=519950&r2=519951
==============================================================================
--- harmony/standard/site/xdocs/code_scan_tools.xml (original)
+++ harmony/standard/site/xdocs/code_scan_tools.xml Mon Mar 19 07:12:06 2007
@@ -1,13 +1,12 @@
 <?xml version="1.0" encoding="ISO-8859-1"?>
 
 <!--
-
     Licensed to the Apache Software Foundation (ASF) under one or more
-    contributor license agreements.  See the NOTICE file distributed with
+    contributor license agreements. See the NOTICE file distributed with
     this work for additional information regarding copyright ownership.
     The ASF licenses this file to You under the Apache License, Version 2.0
     (the "License"); you may not use this file except in compliance with
-    the License.  You may obtain a copy of the License at
+    the License. You may obtain a copy of the License at
 
        http://www.apache.org/licenses/LICENSE-2.0
 
@@ -19,56 +18,51 @@
 -->
 
 <document>
-
- <properties>
-  <title>Apache Harmony Code Scanning Tools</title>
-  <author email="dev@harmony.apache.org">Harmony Documentation Team</author>
- </properties>
-
-<body>
-<section name="Apache Harmony Code Scanning Tools">
-
-<p>
-The Apache Harmony project is dedicated to producing a codebase that 
-has clear IP pedigree and protects the IP rights of others.  As part 
-of this effort, we are developing and using tools that help us examine
-code in a more effient way.  Below are some tools that we either have
-created, or are listing to provide awareness.  The Apache Harmony project
-or the ASF does not endorse or promote any of these tools, projects
-or commercial organizations, and does not make any claims as to  
-suitability, accuracy or dependability.
-</p>
-
-<subsection name="Apache Harmony Keyword Scanner">
-
-<p>
-Keyword scanning is a simple technique to find "the code you never 
-knew you had."   By searching for a set of well chosen keywords (like 
-"copyright", "license" etc), you can discover code that may not 
-be redistributable (you have the license to use by not re-distribute 
-or re-license), or that you didn't want to contribute.
-</p>
-
-<p>
-The Apache Harmony Keyword Scanner is a new contribution that can be found
-here :
-</p>
-
-<p>
-<a href="http://svn.apache.org/viewcvs.cgi/harmony/standard/tools/keywordscan/">
-http://svn.apache.org/viewcvs.cgi/harmony/standard/tools/keywordscan/
-</a>
-</p>
-
-<p>
-We welcome any feedback and further contributions to this or other code-provenance
-utilities and tools.
-</p>
+    <properties>
+        <title>Apache Harmony Code Scanning Tools</title>
+        <author email="dev@harmony.apache.org">Harmony Documentation Team</author>
+    </properties>
+
+    <body>
+        <section name="Apache Harmony Code Scanning Tools">
+
+            <p>
+                The Apache Harmony project is dedicated to producing a codebase that
+                has clear IP pedigree and protects the IP rights of others. As part
+                of this effort, we are developing and using tools that help us examine
+                code in a more effient way. Below are some tools that we either have
+                created, or are listing to provide awareness. The Apache Harmony project
+                or the ASF does not endorse or promote any of these tools, projects
+                or commercial organizations, and does not make any claims as to
+                suitability, accuracy or dependability.
+            </p>
+              <subsection name="Apache Harmony Keyword Scanner">
+                <p>
+                    Keyword scanning is a simple technique to find "the code you never
+                    knew you had." By searching for a set of well chosen keywords (like
+                    "copyright", "license" etc), you can discover code that may not
+                    be redistributable (you have the license to use by not re-distribute
+                    or re-license), or that you didn't want to contribute.
+                </p>
+                <p>
+                    The Apache Harmony Keyword Scanner is a new contribution that can be found
+                    here:
+                </p>
+                <p>
+                    <a href="http://svn.apache.org/viewcvs.cgi/harmony/standard/tools/keywordscan/">
+                        http://svn.apache.org/viewcvs.cgi/harmony/standard/tools/keywordscan/
+                    </a>
+                </p>
+                <p>
+                    We welcome any feedback and further contributions to this or other code-provenance
+                    utilities and tools.
+                </p>
 
 
-</subsection>
+            </subsection>
 
-</section>
-</body>
+        </section>
+    </body>
 </document>
+
 

Modified: harmony/standard/site/xdocs/contribution_policy.xml
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/contribution_policy.xml?view=diff&rev=519951&r1=519950&r2=519951
==============================================================================
--- harmony/standard/site/xdocs/contribution_policy.xml (original)
+++ harmony/standard/site/xdocs/contribution_policy.xml Mon Mar 19 07:12:06 2007
@@ -1,13 +1,12 @@
 <?xml version="1.0" encoding="ISO-8859-1"?>
 
 <!--
-
     Licensed to the Apache Software Foundation (ASF) under one or more
-    contributor license agreements.  See the NOTICE file distributed with
+    contributor license agreements. See the NOTICE file distributed with
     this work for additional information regarding copyright ownership.
     The ASF licenses this file to You under the Apache License, Version 2.0
     (the "License"); you may not use this file except in compliance with
-    the License.  You may obtain a copy of the License at
+    the License. You may obtain a copy of the License at
 
        http://www.apache.org/licenses/LICENSE-2.0
 
@@ -20,65 +19,56 @@
 
 <document>
 
- <properties>
-  <title>Apache Harmony Contribution Policy</title>
-  <author email="dev@harmony.apache.org">Harmony Documentation Team</author>
- </properties>
-
-<body>
-<section name="Apache Harmony Contribution Policy">
-
-<p>
-Due to the oversight which we wish to provide for the Harmony community, the following 
-process is used for committers, contributors and their contributions.
-</p>
-
-<p>
-In summary : 
-</p>
-
-<ul>
-<li>
-  We are working to ensure that we have broad participation from the community, 
-  at all experience levels and interests, but at the same time we are working to 
-  minimize any risks to the ASF, the project and our community due to 
-  inappropriate contributions of the intellectual property of others.
-</li>
-<li>
-   We adhere to the standard Apache process and contribution agreements, and 
-   enhance them to gather information about contributor's previous experience with
-   similar technology.  This information is used to ensure that the work
-   contributed to the project does not infringe the intellectual or other
-   property rights of others. 
-</li>
-<li>
-   We have compartmentalized our repository and use fine-grained access control
-   to ensure broad participation while still ensuring that inappropriate or 
-   questionable contributions do no occur.
-</li>
-<li>
-  We require every contributor to fill out an
-  <a href="auth_cont_quest.html">Authorized Contributor Questionnaire</a>, 
-  which is used to help limit the risks to our source base from inappropriate 
-  contributions.
-</li>
-</ul>
-
-
-<subsection name="Division of Repository">
-
-<p>
-  We have divided
-  <a href="http://harmony.apache.org/svn.html">our Subversion(SVN)
-  repository</a> into sections.  There are two main sections, the "standard"
-  section, for which the standard Apache process applies (namely, the standard 
-  <a href="http://www.apache.org/licenses/icla.txt">Apache ICLA</a>
-  is all that is required) and the "enhanced" section, which requires any
-  committer to also be an Authorized Contributor.  Project code is in the
-  "enhanced" section, and website, documentation and other miscellany is in
-  the "standard" section.  For the purposes of illustration :
-</p>
-
+    <properties>
+        <title>Apache Harmony Contribution Policy</title>
+        <author email="dev@harmony.apache.org">Harmony Documentation Team</author>
+    </properties>
+    <body>
+        <section name="Apache Harmony Contribution Policy">
+            <p>
+                Due to the oversight which we wish to provide for the Harmony community, the following
+                process is used for committers, contributors and their contributions.
+            </p>
+            <p>
+                In summary :
+            </p>
+            <ul>
+                <li>
+                    We are working to ensure that we have broad participation from the community,
+                    at all experience levels and interests, but at the same time we are working to
+                    minimize any risks to the ASF, the project and our community due to
+                    inappropriate contributions of the intellectual property of others.
+                </li>
+                <li>
+                    We adhere to the standard Apache process and contribution agreements, and
+                    enhance them to gather information about contributor's previous experience with
+                    similar technology. This information is used to ensure that the work
+                    contributed to the project does not infringe the intellectual or other
+                    property rights of others.
+                </li>
+                <li>
+                    We have compartmentalized our repository and use fine-grained access control
+                    to ensure broad participation while still ensuring that inappropriate or
+                    questionable contributions do no occur.
+                </li>
+                <li>
+                    We require every contributor to fill out an
+                    <a href="auth_cont_quest.html">Authorized Contributor Questionnaire</a>,
+                    which is used to help limit the risks to our source base from inappropriate
+                    contributions.
+                </li>
+            </ul>
+            <subsection name="Division of Repository">
+                <p>
+                    We have divided <a href="http://harmony.apache.org/svn.html">
+                    our Subversion(SVN) repository</a> into sections. There are two main sections, the "standard"
+                    section, for which the standard Apache process applies (namely, the standard
+                    <a href="http://www.apache.org/licenses/icla.txt">Apache ICLA</a>
+                    is all that is required) and the "enhanced" section, which requires any
+                    committer to also be an Authorized Contributor. Project code is in the
+                    "enhanced" section, and website, documentation and other miscellany is in
+                    the "standard" section. For the purposes of illustration:
+                </p>
 <pre>
 enhanced
     /admin
@@ -106,114 +96,93 @@
     /tools
     /...
 </pre>
-
-<p>
-  and we limit access within the enhanced part of the SVN by fine-grained
-  access control lists using information provided by Authorized Contributors,
-  as defined below.
-</p>
-
-<p>
-  We will be as liberal as possible - if your status as an Authorized Contributor
-  doesn't prevent it, access should be granted to any part of the SVN repository.
-</p>
-
-</subsection>
-
-<subsection name="Strict Limits on Committer Contribution">
-
-<p>
-Committers can only commit contributions to the repositories 
-that they personally created <i>specifically for contribution to Apache Harmony.</i>
-This is the standard stream of fresh original work, small enhancements 
-and patches that are the normal flow of project life.
-</p>
-
-<p>
-The purpose of 
-this rule is to explicitly prohibit re-purposed "bulk" code 
-that the contributor believes is their original work from being
-added to the codebase without explicit oversight and acceptance. 
-We can still accept contributions like that, but will track them explicitly
-as Bulk Contributions.
-</p>
-
-
-</subsection>
-
-
-<subsection name="Policy for Committers">
-
-<p>
-Each committer is required to complete a standard 
-<a href="http://www.apache.org/licenses/">Apache Individual Contributor License Agreement</a>.
-This document asserts that the contributor is licensing their 
-material to the ASF under the Apache license and is their original work (there's some other details).
-This document is maintained and managed by the Secretary of the Apache Software Foundation.
-</p>
-
-<p>
-In order for a committer to become an Authorized Contributor to Harmony, each committer
-is also required to complete the 
-<a href="auth_cont_quest.html">Authorized Contributor Questionnaire</a> and submit it to
-<a href="mailing.html">the Harmony PMC</a>.
-</p>
-
-<p>
-We encourage every committer, if appropriate, to have their employer execute a 
-<a href="http://www.apache.org/licenses/">Apache Corporate Contributor License Agreement</a>.
-Note that this is recommended, but not required.
-</p>
-
-</subsection>
-
-<subsection name="Policy for Bulk Contributions">
-
-<p>
-Any software or other contribution that was not created explicitly for 
-Apache Harmony <i>in</i> the Apache Harmony project is considered to
-be a 'Bulk Contribution'.  This status is independent of the purpose
-or author of said contribution.  For example:
-</p>
-
-<ul>
-<li> Personal utilities that a committer always uses on projects</li>
-<li> Code from other open source projects that have a compatible license</li>
-<li> Code from proprietary projects for which the donor has clear title</li>
-</ul>
-
-<p>
-Any Bulk Contribution  :
-</p>
-
-<ol>
-<li> Will be donated via the project bug tracking system (JIRA) as a contribution under the Apache License.</li>
-<li> Will be accompanied by a Software Grant or CCLA which will be registered with the Apache Incubator</li>
-<li> Will be registered in the Apache Harmony Bulk Contribution Repository
-      via a <a href="bulk_contribution_checklist.html">Bulk Contribution Checklist</a></li>
-<li> Will be made by an Authorized Contributor to Harmony (defined above)</li>
-</ol>
-
-<p>
-The Bulk Contribution Repository is a separate place in our administrative SVN in which each contribution 
-is committed, in it's entirety, before being combined with the project codebases.  We do this to
-ensure that we have a clear and unambiguous record of any repurposed software that was contributed or
-brought into the project source tree. Along with the source or other contributed materials, the 
-contribution will also include a description of the software and the name of the Authorized Contributor
-that made the donation.
-</p>
-
-<p>
-We strongly urge any potential contributor to carefully examine their candidate for contribution
-before offering to the project.  To that end, we have started collecting information on tools and
-other aids to help in this process, and it can be found <a href="code_scan_tools.html">here</a>.
-</p>
-
- 
-</subsection>
-
-
-</section>
-</body>
+                <p>
+                    and we limit access within the enhanced part of the SVN by fine-grained
+                    access control lists using information provided by Authorized Contributors,
+                    as defined below.
+                </p>
+                <p>
+                    We will be as liberal as possible - if your status as an Authorized Contributor
+                    doesn't prevent it, access should be granted to any part of the SVN repository.
+                </p>
+            </subsection>
+            <subsection name="Strict Limits on Committer Contribution">
+                <p>
+                    Committers can only commit contributions to the repositories
+                    that they personally created <i>specifically for contribution to Apache Harmony.</i>
+                    This is the standard stream of fresh original work, small enhancements
+                    and patches that are the normal flow of project life.
+                </p>
+                <p>
+                    The purpose of
+                    this rule is to explicitly prohibit re-purposed "bulk" code
+                    that the contributor believes is their original work from being
+                    added to the codebase without explicit oversight and acceptance.
+                    We can still accept contributions like that, but will track them explicitly
+                    as Bulk Contributions.
+                </p>
+            </subsection>
+            <subsection name="Policy for Committers">
+                <p>
+                    Each committer is required to complete a standard
+                    <a href="http://www.apache.org/licenses/">Apache Individual Contributor License Agreement</a>.
+                    This document asserts that the contributor is licensing their
+                    material to the ASF under the Apache license and is their original work (there's some other details).
+                    This document is maintained and managed by the Secretary of the Apache Software Foundation.
+               </p>
+                <p>
+                    In order for a committer to become an Authorized Contributor to Harmony, each committer
+                    is also required to complete the
+                    <a href="auth_cont_quest.html">Authorized Contributor Questionnaire</a> and submit it to
+                    <a href="mailing.html">the Harmony PMC</a>.
+                </p>
+                <p>
+                    We encourage every committer, if appropriate, to have their employer execute a
+                    <a href="http://www.apache.org/licenses/">Apache Corporate Contributor License Agreement</a>.
+                    Note that this is recommended, but not required.
+                </p>
+            </subsection>
+            <subsection name="Policy for Bulk Contributions">
+                <p>
+                    Any software or other contribution that was not created explicitly for
+                    Apache Harmony <i>in</i> the Apache Harmony project is considered to
+                    be a 'Bulk Contribution'. This status is independent of the purpose
+                    or author of said contribution. For example:
+                </p>
+
+                <ul>
+                    <li> Personal utilities that a committer always uses on projects</li>
+                    <li> Code from other open source projects that have a compatible license</li>
+                    <li> Code from proprietary projects for which the donor has clear title</li>
+                </ul>
+                <p>
+                    Any Bulk Contribution  :
+                </p>
+                <ol>
+                    <li>Will be donated via the project bug tracking system (JIRA) as a contribution under the Apache License</li>
+                    <li>Will be accompanied by a Software Grant or CCLA which will be registered with the Apache Incubator</li>
+                    <li>Will be registered in the Apache Harmony Bulk Contribution Repository
+                        via a <a href="bulk_contribution_checklist.html">Bulk Contribution Checklist</a>
+                    </li>
+                    <li> Will be made by an Authorized Contributor to Harmony (defined above)</li>
+                </ol>
+
+                <p>
+                    The Bulk Contribution Repository is a separate place in our administrative SVN in which each contribution
+                    is committed, in it's entirety, before being combined with the project codebases. We do this to
+                    ensure that we have a clear and unambiguous record of any repurposed software that was contributed or
+                    brought into the project source tree. Along with the source or other contributed materials, the
+                    contribution will also include a description of the software and the name of the Authorized Contributor
+                    that made the donation.
+                </p>
+                <p>
+                    We strongly urge any potential contributor to carefully examine their candidate for contribution
+                    before offering to the project. To that end, we have started collecting information on tools and
+                    other aids to help in this process, and it can be found <a href="code_scan_tools.html">here</a>.
+                </p>
+            </subsection>
+        </section>
+    </body>
 </document>
+
 

Modified: harmony/standard/site/xdocs/downloads.xml
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/downloads.xml?view=diff&rev=519951&r1=519950&r2=519951
==============================================================================
--- harmony/standard/site/xdocs/downloads.xml (original)
+++ harmony/standard/site/xdocs/downloads.xml Mon Mar 19 07:12:06 2007
@@ -61,14 +61,14 @@
     have not been tested, and are not official releases of the Apache Harmony project or
     the Apache Software Foundation.
     </p>
+<dl>
+    <dt>Java Development Kit (JDK)</dt>
 
-    <h3>Java Development Kit (JDK)</h3>
-
-    <p>
+    <dd>
         The JDK lets you build and run your Java programs. It include javac and other standard JDK tools.
         Note that it's safest to set <code>JAVA_HOME</code> to the root directory
         of the distribution, and put the <code>bin/</code> directory on your <code>PATH</code>.
-</p>
+</dd>
 
 <ul>
     <li>
@@ -88,12 +88,12 @@
     </li>
 </ul>
 
-<h3>Java Runtime Environment (JRE)</h3>
+<dt>Java Runtime Environment (JRE)</dt>
 
-<p>
+<dd>
     The JRE lets you run your Java programs. Note that it's safest to set <code>JAVA_HOME to</code> the root directory
 of the distribution, and put the <code>bin/</code> directory on your <code>PATH</code>.
-    </p>
+    </dd>
 
     <ul>
         <li>
@@ -113,12 +113,12 @@
         </li>
     </ul>
 
-    <h3>Harmony Development Kit (HDK)</h3>
+    <dt>Harmony Development Kit (HDK)</dt>
 
-    <p>
+    <dd>
         The HDK is targetted at Harmony developers. It includes the pre-built class library and VM binaries,
         necessary include files, test cases, and dependencies. It is not a replacement for the common JDK.
-    </p>
+    </dd>
 
     <ul> 
         <li>
@@ -137,7 +137,7 @@
             <a href="http://people.apache.org/builds/harmony/snapshots/latest-harmony-hdk-windows-x86.zip.sha">(SHA)</a>
         </li>
     </ul>
-
+</dl>
 <p>
     These are not official releases of the Apache Software Foundation, nor are they
     complete or compatible with the Java specification. They are snapshots provided
@@ -155,6 +155,7 @@
 </body>
 </document>
  
+
 
 
 

Modified: harmony/standard/site/xdocs/guidelines.xml
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/guidelines.xml?view=diff&rev=519951&r1=519950&r2=519951
==============================================================================
--- harmony/standard/site/xdocs/guidelines.xml (original)
+++ harmony/standard/site/xdocs/guidelines.xml Mon Mar 19 07:12:06 2007
@@ -37,7 +37,7 @@
 
 <p>
 The objective here is to avoid unnecessary conflict over changes and
-continue to produce a quality system in a timely manner.  Not all conflict
+continue to produce a quality system in a timely manner. Not all conflict
 can be avoided, but at least we can agree on the procedures for conflict
 to be resolved.
 </p>
@@ -49,7 +49,7 @@
 <dl>
   <dt><strong>Apache Harmony Project Management Committee</strong></dt>
   <dd>The group of volunteers who are responsible for managing the Apache
-      Harmony Project.  This includes deciding what is distributed 
+      Harmony Project. This includes deciding what is distributed 
       as products of the Project, maintaining the 
       Project's shared resources, speaking on behalf of the Project, 
       resolving license disputes regarding Apache products, nominating
@@ -58,46 +58,46 @@
       <p>Membership in the Apache PMC is by invitation only and must
       be approved by consensus of the active Apache PMC members.
       A PMC member is considered inactive by their own declaration or by 
-      not contributing in any form to the project for over six months.  
+      not contributing in any form to the project for over six months. 
       An inactive member can become active again by reversing whichever
       condition made them inactive (<em>i.e.</em>, by reversing their 
       earlier declaration or by once again contributing toward the 
-      project's work).  Membership can be revoked by a unanimous vote of 
+      project's work). Membership can be revoked by a unanimous vote of 
       all the active PMC members other than the member in question.</p>
 
       <p>
       Our goal is that every committer willing and interested in the day-to-day
       oversight and management of the project will be invited at the right time
-      to join the PMC.  Our goal is 100% of the committers on the PMC.
+      to join the PMC. Our goal is 100% of the committers on the PMC.
       </p>
      
      <p>
-     <b>Please Note : </b>  While in incubation, the PPMC of the incubating
+     <b>Please Note: </b> While in incubation, the PPMC of the incubating
        Harmony project will play the role of the official PMC.
      </p>
   </dd>
 
   <dt><strong>Apache Harmony Committers</strong></dt>
   <dd>The group of volunteers who are responsible for the technical
-      aspects of the Apache Harmony Project.  This group has
+      aspects of the Apache Harmony Project. This group has
       write access to the appropriate source repositories and these
       volunteers may cast binding votes on any technical discussion.
 
       <p>Membership as a Committer is by invitation only and must
       be approved by consensus of the active Apache PMC members.
       A Committer is considered inactive by their own declaration or by 
-      not contributing in any form to the project for over six months.  
+      not contributing in any form to the project for over six months. 
       An inactive member can become active again by reversing whichever
       condition made them inactive (<em>i.e.</em>, by reversing their 
       earlier declaration or by once again contributing toward the 
-      project's work).  Membership can be revoked by a unanimous vote of 
+      project's work). Membership can be revoked by a unanimous vote of 
       all the active PMC members (except the member in question if they
       are a PMC member).</p>
   </dd>
 
   <dt><strong>Apache Harmony Developers</strong></dt>
   <dd>All of the volunteers who are contributing time, code, documentation,
-      or resources to the Apache Harmony Project.  A developer that makes sustained,
+      or resources to the Apache Harmony Project. A developer that makes sustained,
       welcome contributions to the project for over six months is usually
       invited to become a Committer, though the exact timing of such
       invitations depends on many factors.</dd>
@@ -112,8 +112,8 @@
   <dt><strong>private@harmony.apache.org</strong></dt>
   <dd>The Apache Harmony PMC's private mailing list for discussion of issues
       that are inappropriate for public discussion, such as legal, personal,
-      or security issues prior to a published fix.  Subscription to the list
-      is only open to Apache Harmony PMC  members.
+      or security issues prior to a published fix. Subscription to the list
+      is only open to Apache Harmony PMC members.
   </dd>
 
   <dt><strong>commits@harmony.apache.org</strong></dt>
@@ -130,19 +130,19 @@
 
 <p>Each of the Apache Harmony's active source code repositories contain a 
 file called "STATUS" which is used to keep track of the agenda and plans 
-for work within that repository.  The STATUS file includes information 
+for work within that repository. The STATUS file includes information 
 about release plans, a summary of code changes committed since the last 
 release, a list of proposed changes that are under discussion, brief 
 notes about items that individual developers are working on or want 
 discussion about, and anything else that might be useful to help the 
-group track progress.  The active STATUS files are automatically posted 
+group track progress. The active STATUS files are automatically posted 
 to the mailing list each week.</p>
 
 <p>Many issues will be encountered by the project, each resulting in 
-zero or more proposed action items.  Issues should be raised on the
-mailing list as soon as they are identified.  Action items 
+zero or more proposed action items. Issues should be raised on the
+mailing list as soon as they are identified. Action items 
 <strong>must</strong> be raised on the mailing list and added to the 
-relevant STATUS file.  All action items may be voted on, but not all 
+relevant STATUS file. All action items may be voted on, but not all 
 of them will require a formal vote.</p>
 </section>
 
@@ -152,37 +152,37 @@
 However, the only binding votes are those cast by active members of the
 Apache Harmony PMC; if the vote is about a change to source code or 
 documentation, the primary author of what is being changed may also 
-cast a binding vote on that issue.  All other votes are non-binding.
+cast a binding vote on that issue. All other votes are non-binding.
 All developers are encouraged to participate in decisions, but the 
 decision itself is made by those who have been long-time contributors 
-to the project.  In other words, the Apache Harmony Project is a 
+to the project. In other words, the Apache Harmony Project is a 
 minimum-threshold meritocracy.</p>
 
 <p>The act of voting carries certain obligations -- voting members are 
 not only stating their opinion, they are agreeing to help do the work of 
-the Apache Harmony Project.  Since we are all volunteers, members often become 
+the Apache Harmony Project. Since we are all volunteers, members often become 
 inactive for periods of time in order to take care of their "real jobs" 
 or devote more time to other projects. It is therefore unlikely that the 
-entire group membership will vote on every issue.  To account for this, 
+entire group membership will vote on every issue. To account for this, 
 all voting decisions are based on a minimum quorum.</p>
 
 <p>Each vote can be made in one of three flavors:</p>
 
 <dl>
   <dt><strong>+1</strong></dt>
-  <dd>Yes, agree, or the action should be performed.  On some issues, this
+  <dd>Yes, agree, or the action should be performed. On some issues, this
       vote is only binding if the voter has tested the action on
       their own system(s).
   </dd>
   <dt><strong>0</strong></dt>
   <dd>Abstain, no opinion, or I am happy to let the other group members
-      decide this issue.  An abstention may have detrimental effects if
+      decide this issue. An abstention may have detrimental effects if
       too many people abstain.
   </dd>
   <dt><strong>-1</strong></dt>
   <dd>No. On issues where consensus is required, this vote counts as a
-      <strong>veto</strong>.  All vetos must include an explanation of
-      why the veto is appropriate.  A veto with no explanation is void.
+      <strong>veto</strong>. All vetos must include an explanation of
+      why the veto is appropriate. A veto with no explanation is void.
       No veto can be overruled. If you disagree with the veto, you
       should lobby the person who cast the veto. Voters intending to veto
       an action item should make their opinions known to the group immediately,
@@ -195,7 +195,7 @@
 An action item requiring <em>majority approval</em> must receive
 at least <strong>3 binding +1</strong> votes and more <strong>+1</strong>
 votes than <strong>-1</strong> votes (<em>i.e.</em>, a majority with a minimum
-quorum of three positive votes).  All other action items are considered
+quorum of three positive votes). All other action items are considered
 to have <em>lazy approval</em> until someone votes <strong>-1</strong>,
 after which point they are decided by either consensus or a majority vote,
 depending upon the type of action item.</p>
@@ -213,7 +213,7 @@
       These are not voted on,
       but group members who do not agree with a particular plan,
       or think an alternate plan would be better, are obligated to
-      inform the group of their feelings.  In general, it is always
+      inform the group of their feelings. In general, it is always
       better to hear about alternate plans <strong>prior</strong> to
       spending time on less adequate solutions.
   </dd>
@@ -222,7 +222,7 @@
   <dd>Short term plans are announcements that a developer is working on
       a particular set of documentation or code files, with the implication
       that other developers should avoid them or try to coordinate their
-      changes.  This is a good way to proactively avoid conflict and 
+      changes. This is a good way to proactively avoid conflict and 
       possible duplication of work.
   </dd>
 
@@ -231,20 +231,20 @@
       release is desired, who will be the release manager, when the
       repository will be frozen in order to create the release, and 
       assorted other trivia to keep us from tripping over ourselves
-      during the final moments.  Lazy majority decides each issue in
+      during the final moments. Lazy majority decides each issue in
       the release plan.
   </dd>
 
   <dt><strong>Release Testing</strong></dt>
   <dd>After a new release is built, colloquially termed a tarball, it
-      must be tested before being released to the public.  Majority
+      must be tested before being released to the public. Majority
       approval is required before the tarball can be publically released.
   </dd>
 
   <dt><strong>Showstoppers</strong></dt>
   <dd>Showstoppers are issues that require a fix be in place
-      before the next public release.  They are listed in the STATUS file
-      in order to focus special attention on the problem.  An issue becomes
+      before the next public release. They are listed in the STATUS file
+      in order to focus special attention on the problem. An issue becomes
       a showstopper when it is listed as such in STATUS and remains
       so by lazy consensus.
   </dd>
@@ -255,9 +255,9 @@
       to the change status:
       <dl>
       <dt><strong>concept/plan</strong></dt>
-      <dd>An idea or plan for a change.  These are usually only listed in
+      <dd>An idea or plan for a change. These are usually only listed in
           STATUS when the change is substantial, significantly impacts the
-          API, or is likely to be controversial.  Votes are being requested
+          API, or is likely to be controversial. Votes are being requested
           early so as to uncover conflicts before too much work is done.
       </dd>
       <dt><strong>proposed patch</strong></dt>
@@ -270,7 +270,7 @@
       </dd>
       </dl>
       <p>All product changes to the currently active repository are subject
-      to lazy consensus.  All product changes to a prior-branch (old version)
+      to lazy consensus. All product changes to a prior-branch (old version)
       repository require consensus before the change is committed.</p>
   </dd>
 </dl>
@@ -286,45 +286,44 @@
   being committed to a repository. Any major change
   must receive consensus approval on the mailing list before being committed.
   For detailed instructions on reporting, resolving and closing issues, refer to
-  <a href="issue_resolution_guideline.html">
-    Good Issue Resolution Guideline</a>. 
+  <a href="issue_resolution_guideline.html">Good Issue Resolution Guideline</a>. 
 </p>
 
 <p>Each developer is responsible for notifying the mailing list and 
 adding an action item to STATUS when they have an idea for a new feature 
-or major change to propose for the product.  The distributed nature of the
+or major change to propose for the product. The distributed nature of the
 Apache project requires an advance notice of 48 hours in order to properly
 review a major change -- consensus approval of either the concept or a
-specific patch is required before the change can be committed.  Note that
+specific patch is required before the change can be committed. Note that
 a committer might veto the concept (with an adequate explanation), but later
 rescind that veto if a specific patch satisfies their objections.
 No advance notice is required to commit singular bug fixes.</p>
 
 <p>Related changes should be committed as a group, or very closely 
-together.  Half-completed projects should not be committed unless 
+together. Half-completed projects should not be committed unless 
 doing so is necessary to pass the baton to another developer who has 
-agreed to complete the project in short order.  All code changes must 
+agreed to complete the project in short order. All code changes must 
 be successfully compiled on the developer's platform before being 
 committed.</p>
 
 <p>The current source code tree should be capable of complete compilation
-at all times.  However, it is sometimes impossible for a developer on
+at all times. However, it is sometimes impossible for a developer on
 one platform to avoid breaking some other platform when a change is
 committed, particularly when completing the change requires access to
-a special development tool on that other platform.  If it is anticipated
+a special development tool on that other platform. If it is anticipated
 that a given change will break some other platform, the committer must
 indicate that in the commit log.</p>
 
 <p>The committer is responsible to follow the Apache Harmony procedure
 for any third-party code
-or documentation they commit to the repository.  All software committed
+or documentation they commit to the repository. All software committed
 to the repository must be covered by the Apache LICENSE or contain a
 copyright and license that allows redistribution under the same conditions
 as the Apache LICENSE.</p>
 
 <p>A committed change must be reversed if it is vetoed by one of the 
 voting committers and the veto conditions cannot be immediately satisfied by 
-the equivalent of a "bug fix" commit.  The veto must be rescinded before 
+the equivalent of a "bug fix" commit. The veto must be rescinded before 
 the change can be included in any public release.</p>
 
 </section>
@@ -332,29 +331,29 @@
 <section id="Patch Format" name="Patch Format">
 <p>When a specific change to the software is proposed for discussion or
 voting on the mailing list, it should be presented in the form of input 
-to the patch command.  When sent to the mailing list, the message 
+to the patch command. When sent to the mailing list, the message 
 should contain a Subject beginning with <code>[PATCH]</code> and a 
 distinctive one-line summary corresponding to the action item for that 
-patch.  Afterwards, the patch summary in the STATUS file should be 
+patch. Afterwards, the patch summary in the STATUS file should be 
 updated to point to the Message-ID of that message.</p>
 
 <p>The patch should be created by using the <CODE>diff -u</CODE> 
 command from the original software file(s) to the modified software 
-file(s).  E.g.,</p>
-
-<pre>    diff -u http_main.c.orig http_main.c &gt;&gt; patchfile.txt</pre>
+file(s).</p>
+    <p class="example">Example</p>
+<pre>diff -u http_main.c.orig http_main.c &gt;&gt; patchfile.txt</pre>
 <p>or</p>
-<pre>    cvs diff -u http_main.c &gt;&gt; patchfile.txt</pre>
+<pre>cvs diff -u http_main.c &gt;&gt; patchfile.txt</pre>
 
 <p>All patches necessary to address an action item should be concatenated
-within a single patch message.  If later modification of the patch
+within a single patch message. If later modification of the patch
 proves necessary, the entire new patch should be posted and not just
-the difference between two patches.  The STATUS file entry should then
+the difference between two patches. The STATUS file entry should then
 be updated to point to the new patch message.</p>
 
 <p>The completed patchfile should produce no errors or prompts when the
 command,</p>
-<pre>    patch -s &lt; patchfile</pre>
+<pre>patch -s &lt; patchfile</pre>
 <p>is issued in the target repository.</p>
 </section>
 
@@ -366,7 +365,7 @@
     <li>We may need a better definition for "lazy consensus".</li>
     <li>We should clarify under what conditions a veto can be rescinded 
         or overridden.</li>
-    <li>Should we set a time limit on vetos of patches?  Two weeks?</li>
+    <li>Should we set a time limit on vetos of patches? Two weeks?</li>
 </ul>
 
 </section>

Modified: harmony/standard/site/xdocs/hdk.xml
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/hdk.xml?view=diff&rev=519951&r1=519950&r2=519951
==============================================================================
--- harmony/standard/site/xdocs/hdk.xml (original)
+++ harmony/standard/site/xdocs/hdk.xml Mon Mar 19 07:12:06 2007
@@ -129,10 +129,11 @@
                             </code>.
                         </li>
                     </ul>
-
-                    So, for example, if you wanted to build only the luni module against
+                    <p class="example">Example</p>
+                    <p class="exampletext">
+                   If you wanted to build only the luni module against
                     an HDK, and put the resulting artifacts into a separate target directory,
-                    you would do the following:
+                    do the following:
                     <ol>
                         <li>Checkout the luni module</li>
                         <li>cd into the root directory of the module</li>
@@ -143,7 +144,7 @@
                     The luni Java and native code will be built against the HDK location
                     specified, and all produced binaries placed under the target directory, laid
                     out in the HDK structure described at the top of this page.
-                </p>
+                </p></p>
             </subsection>
         </section>
     </body>

Modified: harmony/standard/site/xdocs/index.xml
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/index.xml?view=diff&rev=519951&r1=519950&r2=519951
==============================================================================
--- harmony/standard/site/xdocs/index.xml (original)
+++ harmony/standard/site/xdocs/index.xml Mon Mar 19 07:12:06 2007
@@ -39,7 +39,6 @@
         Please help us make this a world class, certified implementation of the
         Java Platform Standard Edition!
       </p>
-
       <p>
         The aim of the project is to produce a large and healthy community
         of those interested in runtime platforms tasked with creation of:
@@ -54,7 +53,6 @@
           architecture.
         </li>
       </ul>
-
       <p>
         We aim to support wide range of different platforms. The main criteria
         for whether a particular platform is supported or not is the involvement
@@ -65,11 +63,9 @@
           list of platforms
         </a> we are actively maintaining at the moment.
       </p>
-
       <p>
         Please see the following "Getting Started" guides:
       </p>
-
       <ul>
         <li>
           <a href="quickhelp_users.html">Getting Started for Harmony Users</a>: for those
@@ -81,7 +77,6 @@
         </li>
       </ul>
     </section>
-
     <section name="Harmony News">
       <dl>
         <dt>Harmony Classlib Enabled Version of JRockit VM Available for Project Use</dt>
@@ -122,21 +117,15 @@
           (<i>2006-10-29</i>)
         </dd>
       </dl>
-      <p>
-        <i>
-          Archived articles are <a href="newshistory.html">here</a>
-        </i>.
-      </p>
-
-
+        <p>
+            <i>
+                Archived articles are <a href="newshistory.html">here</a></i>.
+        </p>
     </section>
-
     <section name="Project Status">
-
       <p>
-        How are we doing?  We're making steady progress :
+        How are we doing? We're making steady progress:
       </p>
-
       <ol>
         <li>
           JRE and HDK snapshots <a href="http://people.apache.org/builds/harmony/snapshots/">available</a>
@@ -148,6 +137,5 @@
         <li>More than 1.25 Million Lines of Code</li>
       </ol>
     </section>
-
   </body>
 </document>

Modified: harmony/standard/site/xdocs/issue_resolution_guideline.xml
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/issue_resolution_guideline.xml?view=diff&rev=519951&r1=519950&r2=519951
==============================================================================
--- harmony/standard/site/xdocs/issue_resolution_guideline.xml (original)
+++ harmony/standard/site/xdocs/issue_resolution_guideline.xml Mon Mar 19 07:12:06 2007
@@ -1,11 +1,11 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
 <!--
     Licensed to the Apache Software Foundation (ASF) under one or more
-    contributor license agreements.  See the NOTICE file distributed with
+    contributor license agreements. See the NOTICE file distributed with
     this work for additional information regarding copyright ownership.
     The ASF licenses this file to You under the Apache License, Version 2.0
     (the "License"); you may not use this file except in compliance with
-    the License.  You may obtain a copy of the License at
+    the License. You may obtain a copy of the License at
 
        http://www.apache.org/licenses/LICENSE-2.0
 
@@ -51,17 +51,18 @@
 
     <subsection name="Resolving Issues">
       <p>To resolve an issue, define its type first.</p>
-    <p>   
-            If <i>the issue is a non-bug difference, not a bug or invalid</i>,
-            you should do the following:</p>
-            <ol>
+    <dl>
+        <dt>If the issue is a non-bug difference, not a bug or invalid,
+            you should do the following:</dt>
+            <dd><ol>
                 <li>Discuss the issue on the 
                 <a href="mailing.html">developer mailing list</a>.</li>
                 <li>Add a link to the discussion thread as a comment to the issue.</li>
             </ol>
+        </dd>
         
-       <p>If <i>the issue is a bug</i>, you should do the following:</p>:
-            <ol>
+       <dt>If the issue is a bug, you should do the following:</dt>
+            <dd><ol>
                 <li>
                   Notify the community that you started investigation by adding
                   a comment to the issue and send a message to the 
@@ -89,15 +90,16 @@
                 <li>If the issue is application-oriented, check the application.</li>
                 <li>Use issue links if applicable.</li>
             </ol>
-      
+      </dd></dl>
     </subsection>
 
     <subsection name="Closing Issues">
       <p>To close an issue, define its type first.</p>
-    <p>
-       If <i>the issue is a non-bug difference, not a bug or invalid</i>, you should close the issue.</p>
-            <p>If <i>the issue is a bug</i>, you should do the following: </p>
-                <ol>
+    <dl>
+        <dt>If the issue is a non-bug difference, not a bug or invalid, you should do the following:</dt>
+        <dd> Close the issue.</dd>
+            <dt>If the issue is a bug, you should do the following: </dt>
+              <dd>  <ol>
                     <li>If a patch to test is available, apply it.</li>
                     <li>Check that the test fails.</li>
                     <li>Apply the fix for the issue.</li>
@@ -109,7 +111,7 @@
                     <li>Make sure that the issue reporter is happy with the resolution.</li>
                     <li>Add revision info into the JIRA issue.</li>
                 </ol>
-         
+         </dd></dl>
     </subsection>
   </section>
 </body>

Modified: harmony/standard/site/xdocs/mailing.xml
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/mailing.xml?view=diff&rev=519951&r1=519950&r2=519951
==============================================================================
--- harmony/standard/site/xdocs/mailing.xml (original)
+++ harmony/standard/site/xdocs/mailing.xml Mon Mar 19 07:12:06 2007
@@ -22,12 +22,10 @@
         <title>Apache Harmony Mailing Lists</title>
         <author email="dev@harmony.apache.org">Harmony Documentation Team</author>
     </properties>
-
     <body>
         <section name="Apache Harmony Mailing Lists">
-
             <p>
-                Apache Harmony mailing lists operate under the following terms :
+                Apache Harmony mailing lists operate under the following terms:
             </p>
             <ul>
                 <li>
@@ -67,14 +65,14 @@
                 </li>
             </ul>
             <p>
-                There are currently three publicly available mailing lists for Harmony :
+                There are currently three publicly available mailing lists for Harmony:
             </p>
 
             <subsection name="Developer Mailing List">
 
                 <p>
                     The developer mailing list is used by the developers to discuss
-                    plans, make decisions, vote on technical issues, etc.  This
+                    plans, make decisions, vote on technical issues, etc. This
                     list has a higher volume, though some conversations take place on
                     <a href="get-involved.html#irc-channel">IRC</a> as
                     well.
@@ -140,22 +138,16 @@
                         [testing] or [qa] - for tools-related issues
                     </li>
                 </ul>
-
                 <p>
-                    Simply add the token to the start of your subject line. For example :
-                </p>
-
-                <source>
-                    To : dev@harmony.apache.org
-                    From : harmony_user@openjava.org
-                    Subject : [classlib][io] Problem with java.io.OutputSocket
-
-                    ....
-                </source>
+                    Simply add the token to the start of your subject line.</p>
+                <p class="example">Example</p>
+<source>
+To: dev@harmony.apache.org
+From: harmony_user@openjava.org
+Subject: [classlib][io] Problem with java.io.OutputSocket
+....</source>
             </subsection>
-
             <subsection name="Source Control Mailing List">
-
                 <p>
                     This list receives notifications (with diffs) every time a change is
                     committed to the Harmony source tree. It also receives change notices
@@ -177,11 +169,8 @@
                         View the <a href="http://mail-archives.apache.org/mod_mbox/harmony-commits/">commits@harmony.apache.org archives (Nov 2006 onwards)</a>
                     </li>
                 </ul>
-
             </subsection>
-
             <subsection name="Alerts Mailing List">
-
                 <p>
                     This list receives alerts from the various community-run build systems. These alerts contain
                     information on failed builds and test runs.
@@ -197,20 +186,17 @@
                         View the <a href="http://mail-archives.apache.org/mod_mbox/harmony-alerts/">alerts@harmony.apache.org archives</a>
                     </li>
                 </ul>
-
             </subsection>
-
             <subsection name="Other Mailing Lists">
-
                 <p>
                     The Harmony PMC has a mailing list to resolve any administrative issues,
                     This list is limited to PMC members (most committers on the project).
                 </p>
-
             </subsection>
         </section>
     </body>
 </document>
+
 
 
 



Mime
View raw message