harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From nadi...@apache.org
Subject svn commit: r515560 [1/3] - in /harmony/standard/site: docs/subcomponents/classlibrary/ docs/subcomponents/drlvm/ xdocs/ xdocs/documentation/ xdocs/subcomponents/classlibrary/ xdocs/subcomponents/drlvm/
Date Wed, 07 Mar 2007 13:29:13 GMT
Author: nadinem
Date: Wed Mar  7 05:29:12 2007
New Revision: 515560

URL: http://svn.apache.org/viewvc?view=rev&rev=515560
Log:
HARMONY-3296 fix + reformatting: migrating site to unix-style EOL symbols

Modified:
    harmony/standard/site/docs/subcomponents/classlibrary/asn1_framework.html
    harmony/standard/site/docs/subcomponents/classlibrary/java2d.html
    harmony/standard/site/docs/subcomponents/classlibrary/regexp.html
    harmony/standard/site/docs/subcomponents/classlibrary/rmi_provider.html
    harmony/standard/site/docs/subcomponents/drlvm/EM.html
    harmony/standard/site/docs/subcomponents/drlvm/JIT.html
    harmony/standard/site/docs/subcomponents/drlvm/JIT_PMF.html
    harmony/standard/site/docs/subcomponents/drlvm/TM.html
    harmony/standard/site/docs/subcomponents/drlvm/gc-howto.html
    harmony/standard/site/docs/subcomponents/drlvm/kernel_classes.html
    harmony/standard/site/xdocs/documentation/conventions.xml
    harmony/standard/site/xdocs/documentation/dev_eclipse.xml
    harmony/standard/site/xdocs/hdk.xml
    harmony/standard/site/xdocs/sitemap.xml
    harmony/standard/site/xdocs/subcomponents/classlibrary/ASN1Framework.html
    harmony/standard/site/xdocs/subcomponents/classlibrary/RMIprovider.html
    harmony/standard/site/xdocs/subcomponents/classlibrary/Regexp.html
    harmony/standard/site/xdocs/subcomponents/classlibrary/asn1_framework.xml
    harmony/standard/site/xdocs/subcomponents/classlibrary/regexp.xml
    harmony/standard/site/xdocs/subcomponents/classlibrary/rmi_provider.xml
    harmony/standard/site/xdocs/subcomponents/drlvm/DoxygenStart.xml
    harmony/standard/site/xdocs/subcomponents/drlvm/EM.html
    harmony/standard/site/xdocs/subcomponents/drlvm/JVMTI-PopFrame.xml
    harmony/standard/site/xdocs/subcomponents/drlvm/Jitrino.html
    harmony/standard/site/xdocs/subcomponents/drlvm/Jitrino_PMF.html
    harmony/standard/site/xdocs/subcomponents/drlvm/encoder_library.xml
    harmony/standard/site/xdocs/subcomponents/drlvm/gc-howto-content.html
    harmony/standard/site/xdocs/subcomponents/drlvm/internal_profiler.xml
    harmony/standard/site/xdocs/subcomponents/drlvm/kernel_classes.html

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=515560&r1=515559&r2=515560
==============================================================================
--- harmony/standard/site/docs/subcomponents/classlibrary/asn1_framework.html (original)
+++ harmony/standard/site/docs/subcomponents/classlibrary/asn1_framework.html Wed Mar  7 05:29:12 2007
@@ -192,11 +192,11 @@
                                                                 <div>
 <!--
     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
   
@@ -207,10 +207,6 @@
     limitations under the License.
 
 -->
-<!--
-Author:  Nadezhda Morozova, Stepan M. Mishura
-Version: $Revision$
--->
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <html xmlns="http://www.w3.org/1999/xhtml">
@@ -1599,6 +1595,7 @@
       </p>
    </body>
 </html>
+
 
 
 

Modified: harmony/standard/site/docs/subcomponents/classlibrary/java2d.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/subcomponents/classlibrary/java2d.html?view=diff&rev=515560&r1=515559&r2=515560
==============================================================================
--- harmony/standard/site/docs/subcomponents/classlibrary/java2d.html (original)
+++ harmony/standard/site/docs/subcomponents/classlibrary/java2d.html Wed Mar  7 05:29:12 2007
@@ -335,7 +335,7 @@
       </h2>
       <p>
          This document uses the <a href="../../documentation/conventions.html">unified conventions</a>
-		 for the DRL documentation kit.
+        for the DRL documentation kit.
       </p>
       <p class="backtotop">
          <a href="#top">Back to Top</a>

Modified: harmony/standard/site/docs/subcomponents/classlibrary/regexp.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/subcomponents/classlibrary/regexp.html?view=diff&rev=515560&r1=515559&r2=515560
==============================================================================
--- harmony/standard/site/docs/subcomponents/classlibrary/regexp.html (original)
+++ harmony/standard/site/docs/subcomponents/classlibrary/regexp.html Wed Mar  7 05:29:12 2007
@@ -190,6 +190,22 @@
                     <td width="80%" valign="top"><a name="top"></a>
                                         
                                                                 <div>
+ <!--
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    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
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
  <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <html xmlns="http://www.w3.org/1999/xhtml">
@@ -271,7 +287,7 @@
                December 16, 2005
             </td>
          </tr>
-		 <tr>
+        <tr>
             <td class="TableCell" width="24%">
                Formatting update
             </td>
@@ -284,8 +300,8 @@
          </tr>
       </table>
        <h1>
-	   <a id="About_this_document" name="About_this_document"></a>
-	   About this Document</h1>
+    <a id="About_this_document" name="About_this_document"></a>
+    About this Document</h1>
       <h2>
          <a id="Purpose" name="Purpose"></a>Purpose
       </h2>
@@ -740,6 +756,7 @@
       </p>
    </body>
 </html>
+
 
 
 

Modified: harmony/standard/site/docs/subcomponents/classlibrary/rmi_provider.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/subcomponents/classlibrary/rmi_provider.html?view=diff&rev=515560&r1=515559&r2=515560
==============================================================================
--- harmony/standard/site/docs/subcomponents/classlibrary/rmi_provider.html (original)
+++ harmony/standard/site/docs/subcomponents/classlibrary/rmi_provider.html Wed Mar  7 05:29:12 2007
@@ -190,255 +190,272 @@
                     <td width="80%" valign="top"><a name="top"></a>
                                         
                                                                 <div>
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html>
-   <head>
-      <meta http-equiv="Content-Type" content=
-      "text/html; charset=ISO-8859-1">
-      <title>
-         DRL RMI Registry Service Provider for JNDI
-      </title>
-   </head>
-   <body>
-      
-<h1> <a name="top"></a>DRL RMI Registry Service Provider for JNDI </h1>
-      <p class="TOCHeading">
-         <a href="#Revision_History">Revision History</a>
-      </p>
-      <p class="TOCHeading">
-         <a href="#About_This_Document">About This Document</a>
-      </p>
-      <p class="TOC">
-         <a href="#Purpose">Purpose</a>
-      </p>
-      <p class="TOC">
-         <a href="#Intended_Audience">Intended Audience</a>
-      </p>
-      <p class="TOC">
-         <a href="#Documentation_Conventions">Documentation Conventions</a>
-      </p>
-      <p class="TOCHeading">
-         <a href="#overview">RMI Provider Overview</a>
-      </p>
-      <p class="TOCHeading">
-         <a href="#drl">RMI Provider in DRL</a>
-      </p>
-      <p class="TOC">
-         <a href="#about">About</a>
-      </p>
-      <p class="TOC">
-         <a href="#environment">Environment Properties</a>
-      </p>
-      <p class="TOC">
-         <a href="#urls">RMI URLs</a>
-      </p>
-      <p class="TOC">
-         <a href="#bindings">Binding Registry Contexts and Remote Objects</a>
-      </p>
-      <p class="TOCHeading">
-         <a href="#References">References</a>
-      </p>
-      <h1>
-         <a name="Revision_History"></a>Revision History
-      </h1>
-      <table border="0" cellpadding="0" width="100%">
-         <tr>
-            <th width="24%" class="TableHeading">
-               Version
-            </th>
-            <th width="49%" class="TableHeading">
-               Version Information
-            </th>
-            <th class="TableHeading">
-               Date
-            </th>
-         </tr>
-         <tr>
-            <td width="24%" class="TableCell">
-               Initial version
-            </td>
-            <td width="49%" class="TableCell">
-               Vasily Zakharov, Nadya Morozova: document created.
-            </td>
-            <td class="TableCell">
-               March 23, 2006
-            </td>
-         </tr>
-		<tr>
-            <td width="24%" class="TableCell">
-               Formatting update
-            </td>
-            <td width="49%" class="TableCell">
-              Nadya Morozova: document created.
-            </td>
-            <td class="TableCell">
-              September 21, 2006
-            </td>
-         </tr>
-         <tr>
-            <td width="24%" class="TableCell">
-               Linking update
-            </td>
-            <td width="49%" class="TableCell">
-              Sveta Konovalova: incorporating in website, removing disclaimer.
-            </td>
-            <td class="TableCell">
-              March 2007
-            </td>
-         </tr>
-      </table>
-     
-      <h1>
-         <a name="About_This_Document"></a>About This Document
-      </h1>
-      <h2>
-         <a name="Purpose"></a>Purpose
-      </h2>
-      
-<p> This document describes the functionality of the DRL RMI  [<a href="#RMIspec">2</a>] Registry Service 
-  Provider for JNDI [<a href="#Sunjndi">1</a>]. The document gives details on the provider design. </p>
-      <h2>
-         <a name="Intended_Audience"></a>Intended Audience
-      </h2>
-      
-<p> The target audience for the document includes a wide community of engineers 
-  interested in using the RMI registry in their JNDI applications and in further 
-  work with the product to contribute to its development. The document assumes 
-  that readers are familiar with RMI, JNDI and the Java programming language. 
-</p>
-      <h2>
-         <a name="Documentation_Conventions"></a>Documentation Conventions
-      </h2>
-      
-<p> This document uses the <a href="../../documentation/conventions.html">
-unified conventions</a> for the DRL documentation kit. </p>
-      <p class="backtotop">
-         <a href="#top">Back to Top</a>
-      </p>
-      <h1>
-         <a name="overview"></a>RMI Provider Overview
-      </h1>
-      
-<p> The RMI registry context, based on a registry location, and the RMI Registry 
-  Service Provider allow JNDI applications to access remote objects bound in the 
-  RMI registry, as described in the Java<a name="*">*</a> RMI Specification  [<a href="#RMIspec">2</a>]. </p>
-      <p>
-         The provider supplies JNDI with the same essential functionality as
-         the <code>java.rmi.Naming</code> class does.
-      </p>
-      <p class="backtotop">
-         <a href="#top">Back to Top</a>
-      </p>
-      
-<h1> <a name="drl"></a>RMI Provider in DRL</h1>
-      <h2>
-         <a name="about"></a>About
-      </h2>
-      
-<p> The DRL RMI Service Provider is an independent implementation of the RMI Service Provider for JNDI. 
-You can also consult additional information resources on RMI [<a href="#RMIspec">2</a>], RMI Service Provider [<a href="#RMIprovider">3</a>] and JNDI in general [<a href="#Sunjndi">1</a>]. </p>
-      
-<p>The provider can store <code>java.rmi.Remote</code>, <code>javax.naming.Reference</code> 
-  and <code>javax.naming.Referenceable</code> objects. The RMI registry context 
-  and references to individual RMI objects can be bound into other JNDI contexts. 
-  The DRL provider does not support binding other contexts into the RMI registry, 
-  so that you cannot address objects in this context using composite name requests 
-  through the registry. </p>
-      <p class="backtotop">
-         <a href="#top">Back to Top</a>
-      </p>
-      <h2>
-         <a name="environment"></a>Environment Properties
-      </h2>
-      
-<p> In addition to the general properties [<a href="#RMIprovider">3</a>], the DRL RMI Registry 
-  Provider uses the following JNDI environment properties: </p>
-      <dl>
-         <dt>
-            <a name="prop_initial"></a>
-            <code>java.naming.factory.initial</code>
-         </dt>
-         <dd>
-		 <p>
-            Specifies the RMI registry service provider class name as the
-            initial context factory to be used by the
-            <code>javax.naming.InitialContext</code> class. </p>
-            <p class="example">
-               Example
-            </p>
-    <pre class="exampletext">
-  env.put(Context.INITIAL_CONTEXT_FACTORY,
-        "org.apache.harmony.jndi.provider.rmi.registry.RegistryContextFactory");
-</pre> <p class="exampletext">
-            Use this property with the <code>java.naming.provider.url
-            </code>property, which specifies the location of the RMI registry
-            for the usage of the initial context. Otherwise, the initial
-            context you created can only resolve complete RMI URLs.
-			</p>
-         </dd>
-      </dl>
-      <dl>
-         
-  <dt> <a name="prop_socket"></a> <code>org.apache.harmony.jndi.provider.rmi.registry.clientSocketFactory</code> 
-  </dt>
-         
-  <dd> Can contain the name of a class implementing the<code> java.rmi.server.RMIClientSocketFactory</code> 
-    interface. The instance of this class is passed to the <code>java.rmi.registry.LocateRegistry.getRegistry()</code> 
-    method. </dd>
-      </dl>
-      <p class="backtotop">
-         <a href="#top">Back to Top</a>
-      </p>
-      <h2>
-         <a name="urls"></a>RMI URLs
-      </h2>
-      
-<p> The URL context factory, <code>org.apache.harmony.jndi.provider.rmi.rmiURLContextFactory</code>, 
-  enables passing RMI URLs as names to the JNDI initial context. </p>
-      <p class="backtotop">
-         <a href="#top">Back to Top</a>
-      </p>
-      <h2>
-         <a name="bindings"></a>Binding Registry Contexts and Remote Objects
-      </h2>
-      
-<p> The class <code>org.apache.harmony.jndi.provider.rmi.registry.</code><code>RegistryContextFactory</code> 
-  implements the <code>javax.naming.spi.</code><code>ObjectFactory </code> interface 
-  and provides converting registry references into the corresponding registry 
-  contexts or remote objects. </p>
-      <p class="backtotop">
-         <a href="#top">Back to Top</a>
-      </p>
-      <h1>
-         <a name="References"></a>References
-      </h1>
-      <p>
-         [<a name="Sunjndi">1</a>] Sun about JNDI, <a href= 
-         "http://java.sun.com/j2se/1.5.0/docs/guide/jndi/" target=
-         "_blank">http://java.sun.com/j2se/1.5.0/docs/guide/jndi/</a>
-      </p>
-      <p>
-         [<a name="RMIspec">2</a>] RMI Specification, <a href= 
-         "http://java.sun.com/j2se/1.5.0/docs/guide/rmi/spec/rmiTOC.html" target=
-         "_blank">http://java.sun.com/j2se/1.5.0/docs/guide/rmi/spec/rmiTOC.html</a>
-      </p>
-	  <p>
-         [<a name="RMIprovider">3</a>] Sun's RMI Provider, <a href= 
-         "http://java.sun.com/j2se/1.5.0/docs/guide/jndi/jndi-rmi.html" target=
-         "_blank">http://java.sun.com/j2se/1.5.0/docs/guide/jndi/jndi-rmi.html</a>
-      </p>
-      <p class="backtotop">
-         <a href="#top">Back to Top</a>
-      </p>
-      <p>
-         <a name="*">*</a> Other brands and names are the property of their
-         respective owners.
-      </p>
-   </body>
-</html>
-
-
+<!--
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    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
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+"http://www.w3.org/TR/html4/loose.dtd">
+<html>
+   <head>
+      <meta http-equiv="Content-Type" content=
+      "text/html; charset=ISO-8859-1">
+      <title>
+         DRL RMI Registry Service Provider for JNDI
+      </title>
+   </head>
+   <body>
+      
+<h1> <a name="top"></a>DRL RMI Registry Service Provider for JNDI </h1>
+      <p class="TOCHeading">
+         <a href="#Revision_History">Revision History</a>
+      </p>
+      <p class="TOCHeading">
+         <a href="#About_This_Document">About This Document</a>
+      </p>
+      <p class="TOC">
+         <a href="#Purpose">Purpose</a>
+      </p>
+      <p class="TOC">
+         <a href="#Intended_Audience">Intended Audience</a>
+      </p>
+      <p class="TOC">
+         <a href="#Documentation_Conventions">Documentation Conventions</a>
+      </p>
+      <p class="TOCHeading">
+         <a href="#overview">RMI Provider Overview</a>
+      </p>
+      <p class="TOCHeading">
+         <a href="#drl">RMI Provider in DRL</a>
+      </p>
+      <p class="TOC">
+         <a href="#about">About</a>
+      </p>
+      <p class="TOC">
+         <a href="#environment">Environment Properties</a>
+      </p>
+      <p class="TOC">
+         <a href="#urls">RMI URLs</a>
+      </p>
+      <p class="TOC">
+         <a href="#bindings">Binding Registry Contexts and Remote Objects</a>
+      </p>
+      <p class="TOCHeading">
+         <a href="#References">References</a>
+      </p>
+      <h1>
+         <a name="Revision_History"></a>Revision History
+      </h1>
+      <table border="0" cellpadding="0" width="100%">
+         <tr>
+            <th width="24%" class="TableHeading">
+               Version
+            </th>
+            <th width="49%" class="TableHeading">
+               Version Information
+            </th>
+            <th class="TableHeading">
+               Date
+            </th>
+         </tr>
+         <tr>
+            <td width="24%" class="TableCell">
+               Initial version
+            </td>
+            <td width="49%" class="TableCell">
+               Vasily Zakharov, Nadya Morozova: document created.
+            </td>
+            <td class="TableCell">
+               March 23, 2006
+            </td>
+         </tr>
+		<tr>
+            <td width="24%" class="TableCell">
+               Formatting update
+            </td>
+            <td width="49%" class="TableCell">
+              Nadya Morozova: document created.
+            </td>
+            <td class="TableCell">
+              September 21, 2006
+            </td>
+         </tr>
+         <tr>
+            <td width="24%" class="TableCell">
+               Linking update
+            </td>
+            <td width="49%" class="TableCell">
+              Sveta Konovalova: incorporating in website, removing disclaimer.
+            </td>
+            <td class="TableCell">
+              March 2007
+            </td>
+         </tr>
+      </table>
+     
+      <h1>
+         <a name="About_This_Document"></a>About This Document
+      </h1>
+      <h2>
+         <a name="Purpose"></a>Purpose
+      </h2>
+      
+<p> This document describes the functionality of the DRL RMI  [<a href="#RMIspec">2</a>] Registry Service 
+  Provider for JNDI [<a href="#Sunjndi">1</a>]. The document gives details on the provider design. </p>
+      <h2>
+         <a name="Intended_Audience"></a>Intended Audience
+      </h2>
+      
+<p> The target audience for the document includes a wide community of engineers 
+  interested in using the RMI registry in their JNDI applications and in further 
+  work with the product to contribute to its development. The document assumes 
+  that readers are familiar with RMI, JNDI and the Java programming language. 
+</p>
+      <h2>
+         <a name="Documentation_Conventions"></a>Documentation Conventions
+      </h2>
+      
+<p> This document uses the <a href="../../documentation/conventions.html">
+unified conventions</a> for the DRL documentation kit. </p>
+      <p class="backtotop">
+         <a href="#top">Back to Top</a>
+      </p>
+      <h1>
+         <a name="overview"></a>RMI Provider Overview
+      </h1>
+      
+<p> The RMI registry context, based on a registry location, and the RMI Registry 
+  Service Provider allow JNDI applications to access remote objects bound in the 
+  RMI registry, as described in the Java<a name="*">*</a> RMI Specification  [<a href="#RMIspec">2</a>]. </p>
+      <p>
+         The provider supplies JNDI with the same essential functionality as
+         the <code>java.rmi.Naming</code> class does.
+      </p>
+      <p class="backtotop">
+         <a href="#top">Back to Top</a>
+      </p>
+      
+<h1> <a name="drl"></a>RMI Provider in DRL</h1>
+      <h2>
+         <a name="about"></a>About
+      </h2>
+      
+<p> The DRL RMI Service Provider is an independent implementation of the RMI Service Provider for JNDI. 
+You can also consult additional information resources on RMI [<a href="#RMIspec">2</a>], RMI Service Provider [<a href="#RMIprovider">3</a>] and JNDI in general [<a href="#Sunjndi">1</a>]. </p>
+      
+<p>The provider can store <code>java.rmi.Remote</code>, <code>javax.naming.Reference</code> 
+  and <code>javax.naming.Referenceable</code> objects. The RMI registry context 
+  and references to individual RMI objects can be bound into other JNDI contexts. 
+  The DRL provider does not support binding other contexts into the RMI registry, 
+  so that you cannot address objects in this context using composite name requests 
+  through the registry. </p>
+      <p class="backtotop">
+         <a href="#top">Back to Top</a>
+      </p>
+      <h2>
+         <a name="environment"></a>Environment Properties
+      </h2>
+      
+<p> In addition to the general properties [<a href="#RMIprovider">3</a>], the DRL RMI Registry 
+  Provider uses the following JNDI environment properties: </p>
+      <dl>
+         <dt>
+            <a name="prop_initial"></a>
+            <code>java.naming.factory.initial</code>
+         </dt>
+         <dd>
+		 <p>
+            Specifies the RMI registry service provider class name as the
+            initial context factory to be used by the
+            <code>javax.naming.InitialContext</code> class. </p>
+            <p class="example">
+               Example
+            </p>
+    <pre class="exampletext">
+  env.put(Context.INITIAL_CONTEXT_FACTORY,
+        "org.apache.harmony.jndi.provider.rmi.registry.RegistryContextFactory");
+</pre> <p class="exampletext">
+            Use this property with the <code>java.naming.provider.url
+            </code>property, which specifies the location of the RMI registry
+            for the usage of the initial context. Otherwise, the initial
+            context you created can only resolve complete RMI URLs.
+			</p>
+         </dd>
+      </dl>
+      <dl>
+         
+  <dt> <a name="prop_socket"></a> <code>org.apache.harmony.jndi.provider.rmi.registry.clientSocketFactory</code> 
+  </dt>
+         
+  <dd> Can contain the name of a class implementing the<code> java.rmi.server.RMIClientSocketFactory</code> 
+    interface. The instance of this class is passed to the <code>java.rmi.registry.LocateRegistry.getRegistry()</code> 
+    method. </dd>
+      </dl>
+      <p class="backtotop">
+         <a href="#top">Back to Top</a>
+      </p>
+      <h2>
+         <a name="urls"></a>RMI URLs
+      </h2>
+      
+<p> The URL context factory, <code>org.apache.harmony.jndi.provider.rmi.rmiURLContextFactory</code>, 
+  enables passing RMI URLs as names to the JNDI initial context. </p>
+      <p class="backtotop">
+         <a href="#top">Back to Top</a>
+      </p>
+      <h2>
+         <a name="bindings"></a>Binding Registry Contexts and Remote Objects
+      </h2>
+      
+<p> The class <code>org.apache.harmony.jndi.provider.rmi.registry.</code><code>RegistryContextFactory</code> 
+  implements the <code>javax.naming.spi.</code><code>ObjectFactory </code> interface 
+  and provides converting registry references into the corresponding registry 
+  contexts or remote objects. </p>
+      <p class="backtotop">
+         <a href="#top">Back to Top</a>
+      </p>
+      <h1>
+         <a name="References"></a>References
+      </h1>
+      <p>
+         [<a name="Sunjndi">1</a>] Sun about JNDI, <a href= 
+         "http://java.sun.com/j2se/1.5.0/docs/guide/jndi/" target=
+         "_blank">http://java.sun.com/j2se/1.5.0/docs/guide/jndi/</a>
+      </p>
+      <p>
+         [<a name="RMIspec">2</a>] RMI Specification, <a href= 
+         "http://java.sun.com/j2se/1.5.0/docs/guide/rmi/spec/rmiTOC.html" target=
+         "_blank">http://java.sun.com/j2se/1.5.0/docs/guide/rmi/spec/rmiTOC.html</a>
+      </p>
+	  <p>
+         [<a name="RMIprovider">3</a>] Sun's RMI Provider, <a href= 
+         "http://java.sun.com/j2se/1.5.0/docs/guide/jndi/jndi-rmi.html" target=
+         "_blank">http://java.sun.com/j2se/1.5.0/docs/guide/jndi/jndi-rmi.html</a>
+      </p>
+      <p class="backtotop">
+         <a href="#top">Back to Top</a>
+      </p>
+      <p>
+         <a name="*">*</a> Other brands and names are the property of their
+         respective owners.
+      </p>
+   </body>
+</html>
+
+
+
 </div>
                                         </td>
                 </tr>

Modified: harmony/standard/site/docs/subcomponents/drlvm/EM.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/subcomponents/drlvm/EM.html?view=diff&rev=515560&r1=515559&r2=515560
==============================================================================
--- harmony/standard/site/docs/subcomponents/drlvm/EM.html (original)
+++ harmony/standard/site/docs/subcomponents/drlvm/EM.html Wed Mar  7 05:29:12 2007
@@ -190,6 +190,22 @@
                     <td width="80%" valign="top"><a name="top"></a>
                                         
                                                                 <div>
+<!--
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    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
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <html xmlns="http://www.w3.org/1999/xhtml">
@@ -845,6 +861,7 @@
       </p>
    </body>
 </html>
+
 
 
 

Modified: harmony/standard/site/docs/subcomponents/drlvm/JIT.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/subcomponents/drlvm/JIT.html?view=diff&rev=515560&r1=515559&r2=515560
==============================================================================
--- harmony/standard/site/docs/subcomponents/drlvm/JIT.html (original)
+++ harmony/standard/site/docs/subcomponents/drlvm/JIT.html Wed Mar  7 05:29:12 2007
@@ -190,6 +190,22 @@
                     <td width="80%" valign="top"><a name="top"></a>
                                         
                                                                 <div>
+<!--
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    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
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <html xmlns="http://www.w3.org/1999/xhtml">
@@ -2718,6 +2734,7 @@
       </p>
    </body>
 </html>
+
 
 </div>
                                         </td>

Modified: harmony/standard/site/docs/subcomponents/drlvm/JIT_PMF.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/subcomponents/drlvm/JIT_PMF.html?view=diff&rev=515560&r1=515559&r2=515560
==============================================================================
--- harmony/standard/site/docs/subcomponents/drlvm/JIT_PMF.html (original)
+++ harmony/standard/site/docs/subcomponents/drlvm/JIT_PMF.html Wed Mar  7 05:29:12 2007
@@ -190,6 +190,25 @@
                     <td width="80%" valign="top"><a name="top"></a>
                                         
                                                                 <div>
+<!--
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    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
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <html xmlns="http://www.w3.org/1999/xhtml">
 <head>
     <meta http-equiv="Content-Type"
@@ -1482,7 +1501,8 @@
        name="*">*</a> Other brands and names are the property of
        their respective owners.</p>
 </body>
-</html></div>
+</html>
+</div>
                                         </td>
                 </tr>
 

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=515560&r1=515559&r2=515560
==============================================================================
--- harmony/standard/site/docs/subcomponents/drlvm/TM.html (original)
+++ harmony/standard/site/docs/subcomponents/drlvm/TM.html Wed Mar  7 05:29:12 2007
@@ -383,7 +383,7 @@
       </h2>
       <p>
          This document uses the <a href="../../documentation/conventions.html">
-		 unified conventions</a> for the DRL documentation kit.
+        unified conventions</a> for the DRL documentation kit.
       </p>
       <h2>
          <a id="Using_this_document" name="Using_this_document"></a>2.4 Using

Modified: harmony/standard/site/docs/subcomponents/drlvm/gc-howto.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/subcomponents/drlvm/gc-howto.html?view=diff&rev=515560&r1=515559&r2=515560
==============================================================================
--- harmony/standard/site/docs/subcomponents/drlvm/gc-howto.html (original)
+++ harmony/standard/site/docs/subcomponents/drlvm/gc-howto.html Wed Mar  7 05:29:12 2007
@@ -190,6 +190,22 @@
                     <td width="80%" valign="top"><a name="top"></a>
                                         
                                                                 <div>
+<!--
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    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
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <html xmlns="http://www.w3.org/1999/xhtml">

Modified: harmony/standard/site/docs/subcomponents/drlvm/kernel_classes.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/subcomponents/drlvm/kernel_classes.html?view=diff&rev=515560&r1=515559&r2=515560
==============================================================================
--- harmony/standard/site/docs/subcomponents/drlvm/kernel_classes.html (original)
+++ harmony/standard/site/docs/subcomponents/drlvm/kernel_classes.html Wed Mar  7 05:29:12 2007
@@ -190,6 +190,22 @@
                     <td width="80%" valign="top"><a name="top"></a>
                                         
                                                                 <div>
+<!--
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    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
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <html xmlns="http://www.w3.org/1999/xhtml">
@@ -723,6 +739,7 @@
       </p>
    </body>
 </html>
+
 
 
 

Modified: harmony/standard/site/xdocs/documentation/conventions.xml
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/documentation/conventions.xml?view=diff&rev=515560&r1=515559&r2=515560
==============================================================================
--- harmony/standard/site/xdocs/documentation/conventions.xml (original)
+++ harmony/standard/site/xdocs/documentation/conventions.xml Wed Mar  7 05:29:12 2007
@@ -1,19 +1,18 @@
 <?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
-    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
-
-       http://www.apache.org/licenses/LICENSE-2.0
-
-    Unless required by applicable law or agreed to in writing, software
-    distributed under the License is distributed on an "AS IS" BASIS,
-    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-    See the License for the specific language governing permissions and
-    limitations under the License.
+<!--    Licensed to the Apache Software Foundation (ASF) under one or more
+    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
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
 -->
 
 <document>
@@ -25,86 +24,86 @@
   </properties>
 
   <body>
-    <section name="Conventions">
-      <p>The DRL (dynamic run-time layer) documentation set uses the following conventions.</p>
-
-      <table>
-        <tr>
-          <th class="TableHeading">Convention </th>
-          <th class="TableHeading"> Explanation</th>
-          <th class="TableHeading">Example</th>
-        </tr>
-        <tr>
-          <td class="TableCell"> <code> monospace </code> </td>
-          <td class="TableCell">Filenames</td>
-          <td class="TableCell"> <code> ippsapi.h </code> </td>
-         </tr>
-        <tr>
-          <td class="TableCell"> <code> monospace </code> </td>
-          <td class="TableCell">Directory names and pathnames </td>
-          <td class="TableCell"> <code> \alt\include</code> </td>
-        </tr>
-        <tr>
-          <td class="TableCell"> <code> monospace </code> </td>
-          <td class="TableCell"> Commands and command-line options</td>
-          <td class="TableCell"> <code> ecl -O2 </code> </td>
-        </tr>
-        <tr>
-          <td class="TableCell"> <code> monospace </code> </td>
-          <td class="TableCell">Function names, methods, classes, data structures in
-            running text</td>
-          <td class="TableCell">Use the <code> okCreateObjs </code> function to ...</td>
-        </tr>
-        <tr>
-          <td class="TableCell"> <code> monospace </code> </td>
-          <td class="TableCell"> Parameters or other placeholders </td>
-          <td class="TableCell"> <code> ippiMalloc(int widthPixels, ...)<br/>
-                    int* pStepBytes </code> </td>
-        </tr>
-        <tr>
-          <td class="TableCell">
-            <code>
-              <b>monospace bold</b>
-            </code>
-          </td>
-          <td class="TableCell">User input</td>
-          <td class="TableCell">
-            <code>
-              [c:] <b> dir</b>
-            </code>
-          </td>
-        </tr>
-        <tr>
-          <td class="TableCell">
-            <i>italics </i>
-          </td>
-          <td class="TableCell"> Emphasis; introducing or defining terms</td>
-          <td class="TableCell">
-            The term <i> access</i> takes as its subject ...
-          </td>
-        </tr>
-        <tr>
-          <td class="TableCell"> [ ]</td>
-          <td class="TableCell"> Optional items</td>
-          <td class="TableCell">
-            <code> -Fa[c]</code> Indicates these command-line
-            options: <code> -Fa</code> and <code> -Fac</code>
-          </td>
-        </tr>
-        <tr>
-          <td class="TableCell"> { | }  </td>
-          <td class="TableCell">
-            Choice of one item from a selection of two or more
-            items.
-          </td>
-          <td class="TableCell">
-            <code> -aX{K | W | P}</code> Indicates these command-line
-            options:<br/>
-              <code>  -aXK <br/>
-                  -aXW <br/> -aXP</code></td>
-          </tr>
-      </table>
-
-    </section>
+    <section name="Conventions">
+      <p>The DRL (dynamic run-time layer) documentation set uses the following conventions.</p>
+
+      <table>
+        <tr>
+          <th class="TableHeading">Convention </th>
+          <th class="TableHeading"> Explanation</th>
+          <th class="TableHeading">Example</th>
+        </tr>
+        <tr>
+          <td class="TableCell"> <code> monospace </code> </td>
+          <td class="TableCell">Filenames</td>
+          <td class="TableCell"> <code> ippsapi.h </code> </td>
+         </tr>
+        <tr>
+          <td class="TableCell"> <code> monospace </code> </td>
+          <td class="TableCell">Directory names and pathnames </td>
+          <td class="TableCell"> <code> \alt\include</code> </td>
+        </tr>
+        <tr>
+          <td class="TableCell"> <code> monospace </code> </td>
+          <td class="TableCell"> Commands and command-line options</td>
+          <td class="TableCell"> <code> ecl -O2 </code> </td>
+        </tr>
+        <tr>
+          <td class="TableCell"> <code> monospace </code> </td>
+          <td class="TableCell">Function names, methods, classes, data structures in
+            running text</td>
+          <td class="TableCell">Use the <code> okCreateObjs </code> function to ...</td>
+        </tr>
+        <tr>
+          <td class="TableCell"> <code> monospace </code> </td>
+          <td class="TableCell"> Parameters or other placeholders </td>
+          <td class="TableCell"> <code> ippiMalloc(int widthPixels, ...)<br/>
+                    int* pStepBytes </code> </td>
+        </tr>
+        <tr>
+          <td class="TableCell">
+            <code>
+              <b>monospace bold</b>
+            </code>
+          </td>
+          <td class="TableCell">User input</td>
+          <td class="TableCell">
+            <code>
+              [c:] <b> dir</b>
+            </code>
+          </td>
+        </tr>
+        <tr>
+          <td class="TableCell">
+            <i>italics </i>
+          </td>
+          <td class="TableCell"> Emphasis; introducing or defining terms</td>
+          <td class="TableCell">
+            The term <i> access</i> takes as its subject ...
+          </td>
+        </tr>
+        <tr>
+          <td class="TableCell"> [ ]</td>
+          <td class="TableCell"> Optional items</td>
+          <td class="TableCell">
+            <code> -Fa[c]</code> Indicates these command-line
+            options: <code> -Fa</code> and <code> -Fac</code>
+          </td>
+        </tr>
+        <tr>
+          <td class="TableCell"> { | }  </td>
+          <td class="TableCell">
+            Choice of one item from a selection of two or more
+            items.
+          </td>
+          <td class="TableCell">
+            <code> -aX{K | W | P}</code> Indicates these command-line
+            options:<br/>
+              <code>  -aXK <br/>
+                  -aXW <br/> -aXP</code></td>
+          </tr>
+      </table>
+
+    </section>
   </body>
 </document>

Modified: harmony/standard/site/xdocs/documentation/dev_eclipse.xml
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/documentation/dev_eclipse.xml?view=diff&rev=515560&r1=515559&r2=515560
==============================================================================
--- harmony/standard/site/xdocs/documentation/dev_eclipse.xml (original)
+++ harmony/standard/site/xdocs/documentation/dev_eclipse.xml Wed Mar  7 05:29:12 2007
@@ -1,244 +1,244 @@
-<?xml version="1.0" encoding="UTF-8"?>
-
-<!--
-
-    Licensed to the Apache Software Foundation (ASF) under one or more
-    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
-
-       http://www.apache.org/licenses/LICENSE-2.0
-
-    Unless required by applicable law or agreed to in writing, software
-    distributed under the License is distributed on an "AS IS" BASIS,
-    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-    See the License for the specific language governing permissions and
-    limitations under the License.
--->
-
-<document>
-
- <properties>
-  <title>Apache Harmony Development Using Eclipse</title>
-  <author email="dev@harmony.apache.org">Harmony Documentation Team</author>
- </properties>
-
-<body>
-  <section name="Introduction">
-    <p>
-      The current page provides instructions on how to set up Eclipse to develop Java code
-      in Apache Harmony, with sections for both DRLVM and class library development.
-    </p>
-    <p>
-      DRLVM specific instructions are only emerging, while class library specific
-      instructions are in two sets: the <a href="#fastpath">fast path</a>
-      for people familiar with Eclipse and the source code layout in Harmony's
-      Subversion repository; and the
-      <a href="#step_guide">step-by-step guide</a>
-      for novices who want to follow the details of a setup and see a brief
-      development example.
-    </p>
-    <p>
-      All instructions assume you satisfy the same Eclipse-based
-      development prerequsities, as described in the following section.
-    </p>
-    <subsection name="Prerequisites">
-      <p>
-        To develop Apache Harmony Java code with Eclipse JDT, you need:
-      </p>
-      <ol>
-        <li>
-          Eclipse: version 3.2 or later, from
-          <a href="http://download.eclipse.org">eclipse.org</a>
-        </li>
-        <li>
-          A Subversion plug-in: Either Subclipse from <a href="http://subclipse.tigris.org/">
-            tigris.org
-          </a> or Subversive from <a href="http://www.polarion.org">
-            polarion.org
-          </a>
-        </li>
-      </ol>
-      
-      <p>
-      Optionally, you may wish to use one of the external, production-grade virtual machines
-      that work with the Apache Harmony class library.  These can be found on our 
-      <a href="../related.html">Other Projects</a> page.
-      </p>
-      
-    </subsection>
-    <subsection name="Getting the Code">
-      <p>
-        Next you will need the code to work with. <i>For class library development</i>,
-        you will need a compatible VM, such as DRLVM or IBM virtual machine (the latter
-        available under a non-open source, binary evaluation license). Install the VM following the 
-        instructions that accompany that VM in the same location as the class libraries build (or the
-        location you will be building to if you are building the class libararies yourself).
-        <br />
-        You will also need a class libraries build if you want to work
-        on an individual module. 
-       </p>
-      <p>Analogously, you will need the class libraries for <i>DRLVM development</i>.
-        Follow one of these ways depending on your needs:
-      </p>
-      <ul>
-        <li>
-          <b>Get a pre-built snapshot</b> from the
-          <a href="http://people.apache.org/builds/harmony/snapshots/">download page</a>.
-        </li>
-        <li>
-          <b>Download the source code</b> to be built manually. For that, create an SVN repository location
-          using the URL:
-          <pre>
-///for the class libraries
-https://svn.apache.org/repos/asf/harmony/enhanced/classlib
-
-///for DRLVM
-https://svn.apache.org/repos/asf/harmony/enhanced/drlvm</pre>
-          Check out the code from SVN selecting <b>Checkout...</b> from the context menu of <code>trunk</code>.
-        </li>
-      </ul>
-    </subsection>
-  </section>
-<section name="DRLVM Development">
-<a name="drlvm"/>
-      <p>For details on how to build DRLVM and other related documentation, please see
-      the <a href="../subcomponents/drlvm/index.html">DRLVM web pages</a>.
-    </p>
-</section>
-
-<section name="Class Library Development: Fast Path - for Experienced Eclipse developers">
-<a name="fastpath"/>
-  <p>
-    If you know your way around Eclipse JDT, then following these steps will
-    have you hacking Harmony Java code in no time at all!
-  </p>
-
-<subsection name="Configuring Eclipse">
-  <p>
-    Ensure that you have <a href="#Prerequisites">the development prerequisites</a>
-    in place.  Then if you are using Linux start Eclipse as normal with the arguments 
-    <code>-vmargs -Dpde.jreProfile=none -Dpde.allowCycles=true</code> and skip to step 4. If
-    you are using Windows do the following:</p>
-    <ol>
-      <li>Copy the <code>vsvars32.bat</code> file from your Visual Studio install directory
-        to any convenient location. If you have chosen the defaults when installing, you 
-        will find the given file in the <code>
-          C:\Program Files\Microsoft Visual Studio.NET 2003\Common7\Tools</code> directory.</li> 
-         <li>Edit the <code>vsvars32.bat</code> file adding the following line right after the 
-        last line beginning with <code>@set...</code>: 
-        <pre>start C:\...\eclipse\eclipse.exe -vmargs -Xmx512M -Dpde.jreProfile=none -Dpde.allowCycles=true</pre>
-      In the line above, <code>"..."</code> is the path to your Eclipse installation directory.
-          
-        <p class="note">Note</p>
-      <p class="notetext">Using <code>-vmargs -Xmx512M</code> is optional, 
-      but helpful to stop Eclipse running out of memory.</p></li>
-         <li>To start Eclipse, double click on the <code>vsvars32.bat</code> file.
-        </li>
-
-      <li>
-        Configure the following settings in <b>Window</b> &gt; <b>Preferences</b>:
-      </li>
-        <ul>
-          <li>Change the Java compiler settings:
-            <ol>
-              <li>In the <b>Java</b> &gt; <b>Compiler</b> preferences ensure the
-                <b>Compiler compliance level</b> is set to
-                <b>1.4</b>.
-            </li>
-              <li>In the <b>Java</b> &gt; <b>Compiler</b> &gt; <b>Building</b> preferences,
-                open the <b>Build Path Problems</b> section
-                and change <b>Circular Dependencies</b> from
-                <b>Error</b> to <b>Warning</b>.
-            
-            </li>
-            </ol></li>
-          <li>Change the PDE settings:
-            <ol>
-              <li>In the <b>Plug-in Development</b> &gt; <b>Compilers</b> preferences
-              change <b>Unresolved Dependencies</b> from
-                <b>Error</b> to <b>Warning</b>.
-            </li>
-              <li>In the <b>Plug-in Development</b> &gt; <b>Target Platform</b>
-                preferences, change the <b>Location</b> box to be the
-                <code>jre/lib/boot</code> directory of the classlib snapshot.</li>
-            </ol></li>
-        </ul>
-      <li>Copy the <code>ecj_3.2.jar</code> file into the 
-      <code>...\eclipse\plugins\org.apache.ant_1.6.5\lib</code> directory.</li>
-      <li>To include the given file, configure the following Ant settings in 
-      <b>Window</b> &gt; <b>Preferences</b> &gt; <b>Ant</b> &gt; <b>Runtime</b>:
-    </li>
-      <ul>
-        <li>Select <b>Global Entries</b>
-      </li>
-        <li>Select <b>Add External Jars</b>
-    </li>
-        <li>Add the <code>ecj_3.2.jar</code> file from
-          the <code>org.apache.ant_1.6.5\lib</code> directory.
-        </li>
-        </ul>
-    </ol>
-  
-  
-</subsection>
-
-<subsection name="Developing and Testing Code">
-  <p>
-    The Apache Harmony class library is structured to allow developers to work on individual
-    <em>modules</em> in the class library without having to load and compile the entire
-    project source tree.
-  </p>
-  <p>
-    This is best illustrated by a worked example. In this example, assume you want to make
-    a change to the <code>NIO</code> module. This is how you would proceed:
-    <ol>
-      <li>Go to the SVN repository view, open the Harmony URL and browse to
-        <code>trunk &gt; modules</code>. Select
-        <code>nio</code> and from the context menu select
-        <b>Checkout...</b>, and on the checkout dialog box click <b>Finish</b>.</li>
-      <li>In the resulting project in your workspace the implementation code
-        is in the source folder <code>src/main/java</code> and the unit tests
-        are in the source folder <code>src/test/java</code>.</li>
-      <li>Hack away! Developers are encouraged to produce JUnit tests for new
-        implementation code.</li>
-      <li>To test the code you need to set-up a JUnit Run Configuration for the
-        unit test.  You can either run a single test case, or run the
-        <code>AllTests</code> suite for all tests in a package or module.
-        For example, to run the test suite
-        <code>org.apache.harmony.tests.nio.AllTests</code> set up a
-        run configuration with the following characteristics:
-        <ul>
-          <li><em>bootclasspath</em>: the folder nio/bin/main, followed by
-            the Harmony JRE library.</li>
-          <li><em>classpath</em>: the folder nio/bin/test, followed by the
-            <code>JUNIT JAR</code> file.</li>
-          <br/>
-          <img src="../images/dev_eclipse_runconf.jpg" alt="Java run configuration"/>
-          <li><em>VM</em>: the Harmony JRE as the launching VM.</li>
-        </ul>
-      </li>
-      <li>If everything looks good, go ahead and
-        <a href="../get-involved.html#create_patch">contribute a patch</a>.</li>
-    </ol>
-  </p>
-</subsection>
-</section>
-
-<section name="Class Library Development: Step-by-Step Guide">
-<a name="step_guide"/>
-  <p>
-    We have produced a brief webcast for those who want to see a step-by-step guide
-    to configuring Eclipse, and developing a patch to the classlibrary code.  The webcast
-    starts assuming you have already installed the pre-requisities for Eclipse-based
-    development, and launched Eclipse with the following commandline:
-    <pre>eclipse -vmargs -Dpde.jreProfile=none -Dpde.allowCycles=true</pre>
-    We <a href="dev_eclipse_movie.html">
-    pick up the story here...</a> (<em>Warning 8Mb flash download!</em>)
-  </p>
-</section>
-
-</body>
-</document>
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    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
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+
+<document>
+
+ <properties>
+  <title>Apache Harmony Development Using Eclipse</title>
+  <author email="dev@harmony.apache.org">Harmony Documentation Team</author>
+ </properties>
+
+<body>
+  <section name="Introduction">
+    <p>
+      The current page provides instructions on how to set up Eclipse to develop Java code
+      in Apache Harmony, with sections for both DRLVM and class library development.
+    </p>
+    <p>
+      DRLVM specific instructions are only emerging, while class library specific
+      instructions are in two sets: the <a href="#fastpath">fast path</a>
+      for people familiar with Eclipse and the source code layout in Harmony's
+      Subversion repository; and the
+      <a href="#step_guide">step-by-step guide</a>
+      for novices who want to follow the details of a setup and see a brief
+      development example.
+    </p>
+    <p>
+      All instructions assume you satisfy the same Eclipse-based
+      development prerequsities, as described in the following section.
+    </p>
+    <subsection name="Prerequisites">
+      <p>
+        To develop Apache Harmony Java code with Eclipse JDT, you need:
+      </p>
+      <ol>
+        <li>
+          Eclipse: version 3.2 or later, from
+          <a href="http://download.eclipse.org">eclipse.org</a>
+        </li>
+        <li>
+          A Subversion plug-in: Either Subclipse from <a href="http://subclipse.tigris.org/">
+            tigris.org
+          </a> or Subversive from <a href="http://www.polarion.org">
+            polarion.org
+          </a>
+        </li>
+      </ol>
+      
+      <p>
+      Optionally, you may wish to use one of the external, production-grade virtual machines
+      that work with the Apache Harmony class library.  These can be found on our 
+      <a href="../related.html">Other Projects</a> page.
+      </p>
+      
+    </subsection>
+    <subsection name="Getting the Code">
+      <p>
+        Next you will need the code to work with. <i>For class library development</i>,
+        you will need a compatible VM, such as DRLVM or IBM virtual machine (the latter
+        available under a non-open source, binary evaluation license). Install the VM following the 
+        instructions that accompany that VM in the same location as the class libraries build (or the
+        location you will be building to if you are building the class libararies yourself).
+        <br />
+        You will also need a class libraries build if you want to work
+        on an individual module. 
+       </p>
+      <p>Analogously, you will need the class libraries for <i>DRLVM development</i>.
+        Follow one of these ways depending on your needs:
+      </p>
+      <ul>
+        <li>
+          <b>Get a pre-built snapshot</b> from the
+          <a href="http://people.apache.org/builds/harmony/snapshots/">download page</a>.
+        </li>
+        <li>
+          <b>Download the source code</b> to be built manually. For that, create an SVN repository location
+          using the URL:
+          <pre>
+///for the class libraries
+https://svn.apache.org/repos/asf/harmony/enhanced/classlib
+
+///for DRLVM
+https://svn.apache.org/repos/asf/harmony/enhanced/drlvm</pre>
+          Check out the code from SVN selecting <b>Checkout...</b> from the context menu of <code>trunk</code>.
+        </li>
+      </ul>
+    </subsection>
+  </section>
+<section name="DRLVM Development">
+<a name="drlvm"/>
+      <p>For details on how to build DRLVM and other related documentation, please see
+      the <a href="../subcomponents/drlvm/index.html">DRLVM web pages</a>.
+    </p>
+</section>
+
+<section name="Class Library Development: Fast Path - for Experienced Eclipse developers">
+<a name="fastpath"/>
+  <p>
+    If you know your way around Eclipse JDT, then following these steps will
+    have you hacking Harmony Java code in no time at all!
+  </p>
+
+<subsection name="Configuring Eclipse">
+  <p>
+    Ensure that you have <a href="#Prerequisites">the development prerequisites</a>
+    in place.  Then if you are using Linux start Eclipse as normal with the arguments 
+    <code>-vmargs -Dpde.jreProfile=none -Dpde.allowCycles=true</code> and skip to step 4. If
+    you are using Windows do the following:</p>
+    <ol>
+      <li>Copy the <code>vsvars32.bat</code> file from your Visual Studio install directory
+        to any convenient location. If you have chosen the defaults when installing, you 
+        will find the given file in the <code>
+          C:\Program Files\Microsoft Visual Studio.NET 2003\Common7\Tools</code> directory.</li> 
+         <li>Edit the <code>vsvars32.bat</code> file adding the following line right after the 
+        last line beginning with <code>@set...</code>: 
+        <pre>start C:\...\eclipse\eclipse.exe -vmargs -Xmx512M -Dpde.jreProfile=none -Dpde.allowCycles=true</pre>
+      In the line above, <code>"..."</code> is the path to your Eclipse installation directory.
+          
+        <p class="note">Note</p>
+      <p class="notetext">Using <code>-vmargs -Xmx512M</code> is optional, 
+      but helpful to stop Eclipse running out of memory.</p></li>
+         <li>To start Eclipse, double click on the <code>vsvars32.bat</code> file.
+        </li>
+
+      <li>
+        Configure the following settings in <b>Window</b> &gt; <b>Preferences</b>:
+      </li>
+        <ul>
+          <li>Change the Java compiler settings:
+            <ol>
+              <li>In the <b>Java</b> &gt; <b>Compiler</b> preferences ensure the
+                <b>Compiler compliance level</b> is set to
+                <b>1.4</b>.
+            </li>
+              <li>In the <b>Java</b> &gt; <b>Compiler</b> &gt; <b>Building</b> preferences,
+                open the <b>Build Path Problems</b> section
+                and change <b>Circular Dependencies</b> from
+                <b>Error</b> to <b>Warning</b>.
+            
+            </li>
+            </ol></li>
+          <li>Change the PDE settings:
+            <ol>
+              <li>In the <b>Plug-in Development</b> &gt; <b>Compilers</b> preferences
+              change <b>Unresolved Dependencies</b> from
+                <b>Error</b> to <b>Warning</b>.
+            </li>
+              <li>In the <b>Plug-in Development</b> &gt; <b>Target Platform</b>
+                preferences, change the <b>Location</b> box to be the
+                <code>jre/lib/boot</code> directory of the classlib snapshot.</li>
+            </ol></li>
+        </ul>
+      <li>Copy the <code>ecj_3.2.jar</code> file into the 
+      <code>...\eclipse\plugins\org.apache.ant_1.6.5\lib</code> directory.</li>
+      <li>To include the given file, configure the following Ant settings in 
+      <b>Window</b> &gt; <b>Preferences</b> &gt; <b>Ant</b> &gt; <b>Runtime</b>:
+    </li>
+      <ul>
+        <li>Select <b>Global Entries</b>
+      </li>
+        <li>Select <b>Add External Jars</b>
+    </li>
+        <li>Add the <code>ecj_3.2.jar</code> file from
+          the <code>org.apache.ant_1.6.5\lib</code> directory.
+        </li>
+        </ul>
+    </ol>
+  
+  
+</subsection>
+
+<subsection name="Developing and Testing Code">
+  <p>
+    The Apache Harmony class library is structured to allow developers to work on individual
+    <em>modules</em> in the class library without having to load and compile the entire
+    project source tree.
+  </p>
+  <p>
+    This is best illustrated by a worked example. In this example, assume you want to make
+    a change to the <code>NIO</code> module. This is how you would proceed:
+    <ol>
+      <li>Go to the SVN repository view, open the Harmony URL and browse to
+        <code>trunk &gt; modules</code>. Select
+        <code>nio</code> and from the context menu select
+        <b>Checkout...</b>, and on the checkout dialog box click <b>Finish</b>.</li>
+      <li>In the resulting project in your workspace the implementation code
+        is in the source folder <code>src/main/java</code> and the unit tests
+        are in the source folder <code>src/test/java</code>.</li>
+      <li>Hack away! Developers are encouraged to produce JUnit tests for new
+        implementation code.</li>
+      <li>To test the code you need to set-up a JUnit Run Configuration for the
+        unit test.  You can either run a single test case, or run the
+        <code>AllTests</code> suite for all tests in a package or module.
+        For example, to run the test suite
+        <code>org.apache.harmony.tests.nio.AllTests</code> set up a
+        run configuration with the following characteristics:
+        <ul>
+          <li><em>bootclasspath</em>: the folder nio/bin/main, followed by
+            the Harmony JRE library.</li>
+          <li><em>classpath</em>: the folder nio/bin/test, followed by the
+            <code>JUNIT JAR</code> file.</li>
+          <br/>
+          <img src="../images/dev_eclipse_runconf.jpg" alt="Java run configuration"/>
+          <li><em>VM</em>: the Harmony JRE as the launching VM.</li>
+        </ul>
+      </li>
+      <li>If everything looks good, go ahead and
+        <a href="../get-involved.html#create_patch">contribute a patch</a>.</li>
+    </ol>
+  </p>
+</subsection>
+</section>
+
+<section name="Class Library Development: Step-by-Step Guide">
+<a name="step_guide"/>
+  <p>
+    We have produced a brief webcast for those who want to see a step-by-step guide
+    to configuring Eclipse, and developing a patch to the classlibrary code.  The webcast
+    starts assuming you have already installed the pre-requisities for Eclipse-based
+    development, and launched Eclipse with the following commandline:
+    <pre>eclipse -vmargs -Dpde.jreProfile=none -Dpde.allowCycles=true</pre>
+    We <a href="dev_eclipse_movie.html">
+    pick up the story here...</a> (<em>Warning 8Mb flash download!</em>)
+  </p>
+</section>
+
+</body>
+</document>

Modified: harmony/standard/site/xdocs/hdk.xml
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/hdk.xml?view=diff&rev=515560&r1=515559&r2=515560
==============================================================================
--- harmony/standard/site/xdocs/hdk.xml (original)
+++ harmony/standard/site/xdocs/hdk.xml Wed Mar  7 05:29:12 2007
@@ -1,137 +1,137 @@
-<?xml version="1.0" encoding="UTF-8"?>
-
-<!--
-
-    Licensed to the Apache Software Foundation (ASF) under one or more
-    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
-
-       http://www.apache.org/licenses/LICENSE-2.0
-
-    Unless required by applicable law or agreed to in writing, software
-    distributed under the License is distributed on an "AS IS" BASIS,
-    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-    See the License for the specific language governing permissions and
-    limitations under the License.
--->
-
-<document>
-
- <properties>
-  <title>Harmony Development Kit for the Apache Harmony Class Library</title>
-  <author email="dev@harmony.apache.org">Harmony Documentation Team</author>
- </properties>
-
-<body>
-
-<section name="Harmony Development Kit for the Apache Harmony Class Library">
-	<p>
-		The Harmony Development Kit (HDK) allows a Harmony developer to 
-		rebuild	any module of the Harmony Classlib in a standalone way by providing all the 
-		necesary supplementary binaries and header files. This document describes the layout 
-		of such an HDK and its contents.
-	</p>
-
-<subsection name="Layout of the HDK">
-	<p>
-		An HDK contains all the header files and binaries, both native and Java, required
-		for a Harmony classlib developer to build against. The directory structure for an
-		HDK is as follows:
-		<blockquote>
-		<pre>
-&lt;hdkbase&gt;
-     |
-     |---build
-     |     |---make
-     |     |---patternsets
-     |     \---test
-     |
-     |---jdk
-     |    |---jre
-     |    \---include
-     |
-     |---include
-     |
-     \---lib
-     
-		</pre>
-		</blockquote>
-		
-		The directories laid out above are used in the following manner:
-		
-		<ul>
-			<li><code>&lt;hdkbase&gt;/build/make</code> - this directory contains include
-			files used by native makefiles.
-			</li>
-			
-			<li><code>&lt;hdkbase&gt;/build/patternsets</code> - this directory contains
-			patternsets describing jar content.
-			</li>
-			
-			<li><code>&lt;hdkbase&gt;/build/test</code> - this directory contains test
-			support classes, bundled up into a jar file.
-			</li>
-			
-			<li><code>&lt;hdkbase&gt;/jdk/jre</code> - this directory contains the standard
-			jre layout, including <code>bin</code> and <code>lib</code> directories.
-			</li>
-			
-			<li><code>&lt;hdkbase&gt;/jdk/include</code> - this directory contains the standard
-			jdk header files. For example, jni.h is held here.
-			</li>
-			
-			<li><code>&lt;hdkbase&gt;/include</code> - this directory contains header files that
-			are Harmony specific and are used across multiple classlib modules.
-			</li>
-			
-			<li><code>&lt;hdkbase&gt;/lib</code> - this directory is used in HDKs on Windows for
-			.lib files and on Linux for .a files necessary for linking during compilation of 
-			classlib natives.
-			</li>
-		</ul>
-	</p>		
-</subsection>
-<subsection name="Building Classlib Against an HDK">
-	<p>
-		<i>Note: The HDK and relevant build system changes are work in progress. 
-		Not all of the Ant targets/properties described	exist yet, and thus not 
-		all of what is described below currently works. This disclaimer will be 
-		removed once work on the HDK is completed.</i><br/>
-		<br/>
-		The Harmony Class Library can be built at the global or modular level.
-		At the modular level, there are three ways to build:
-		<ul>
-			<li><b>Building the default target</b> - An HDK is not required here, and the class
-			library is built against and into the default (deploy) directory. This is the
-			standard way to build, and is what happens when you just run "ant" at the
-			command line.</li>
-			<li><b>Building against an HDK</b> - The location of an HDK must be specified at
-			the Ant command line, and the ouptut will be built into the default (deploy)
-			directory. The command line for this is "ant -DHY.HDK=path/to/HDK".</li>
-			<li><b>Building against an HDK and into a target directory</b> - The location of
-			an HDK and of a target directory must be specified on the Ant command line.
-			The Class Library code will be compiled against the libraries contained in
-			the HDK, and the output of those compiles will be placed into the specified
-			target directory. The command line for this is "ant -DHY.HDK=path/to/HDK
-			-DHY.TARGET=path/to/target".</li>
-		</ul>
-		
-		So, for example, 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:
-		<ol>
-			<li>Checkout the luni module</li>
-			<li>cd into the root directory of the module</li>
-			<li>Execute "ant -DHY.HDK=path/to/hdk -DHY.TARGET=path/to/target"</li>
-		</ol>
-		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>
-</subsection>
-</section>
-</body>
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    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
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+
+<document>
+
+ <properties>
+  <title>Harmony Development Kit for the Apache Harmony Class Library</title>
+  <author email="dev@harmony.apache.org">Harmony Documentation Team</author>
+ </properties>
+
+<body>
+
+<section name="Harmony Development Kit for the Apache Harmony Class Library">
+	<p>
+		The Harmony Development Kit (HDK) allows a Harmony developer to 
+		rebuild	any module of the Harmony Classlib in a standalone way by providing all the 
+		necesary supplementary binaries and header files. This document describes the layout 
+		of such an HDK and its contents.
+	</p>
+
+<subsection name="Layout of the HDK">
+	<p>
+		An HDK contains all the header files and binaries, both native and Java, required
+		for a Harmony classlib developer to build against. The directory structure for an
+		HDK is as follows:
+		<blockquote>
+		<pre>
+&lt;hdkbase&gt;
+     |
+     |---build
+     |     |---make
+     |     |---patternsets
+     |     \---test
+     |
+     |---jdk
+     |    |---jre
+     |    \---include
+     |
+     |---include
+     |
+     \---lib
+     
+		</pre>
+		</blockquote>
+		
+		The directories laid out above are used in the following manner:
+		
+		<ul>
+			<li><code>&lt;hdkbase&gt;/build/make</code> - this directory contains include
+			files used by native makefiles.
+			</li>
+			
+			<li><code>&lt;hdkbase&gt;/build/patternsets</code> - this directory contains
+			patternsets describing jar content.
+			</li>
+			
+			<li><code>&lt;hdkbase&gt;/build/test</code> - this directory contains test
+			support classes, bundled up into a jar file.
+			</li>
+			
+			<li><code>&lt;hdkbase&gt;/jdk/jre</code> - this directory contains the standard
+			jre layout, including <code>bin</code> and <code>lib</code> directories.
+			</li>
+			
+			<li><code>&lt;hdkbase&gt;/jdk/include</code> - this directory contains the standard
+			jdk header files. For example, jni.h is held here.
+			</li>
+			
+			<li><code>&lt;hdkbase&gt;/include</code> - this directory contains header files that
+			are Harmony specific and are used across multiple classlib modules.
+			</li>
+			
+			<li><code>&lt;hdkbase&gt;/lib</code> - this directory is used in HDKs on Windows for
+			.lib files and on Linux for .a files necessary for linking during compilation of 
+			classlib natives.
+			</li>
+		</ul>
+	</p>		
+</subsection>
+<subsection name="Building Classlib Against an HDK">
+	<p>
+		<i>Note: The HDK and relevant build system changes are work in progress. 
+		Not all of the Ant targets/properties described	exist yet, and thus not 
+		all of what is described below currently works. This disclaimer will be 
+		removed once work on the HDK is completed.</i><br/>
+		<br/>
+		The Harmony Class Library can be built at the global or modular level.
+		At the modular level, there are three ways to build:
+		<ul>
+			<li><b>Building the default target</b> - An HDK is not required here, and the class
+			library is built against and into the default (deploy) directory. This is the
+			standard way to build, and is what happens when you just run "ant" at the
+			command line.</li>
+			<li><b>Building against an HDK</b> - The location of an HDK must be specified at
+			the Ant command line, and the ouptut will be built into the default (deploy)
+			directory. The command line for this is "ant -DHY.HDK=path/to/HDK".</li>
+			<li><b>Building against an HDK and into a target directory</b> - The location of
+			an HDK and of a target directory must be specified on the Ant command line.
+			The Class Library code will be compiled against the libraries contained in
+			the HDK, and the output of those compiles will be placed into the specified
+			target directory. The command line for this is "ant -DHY.HDK=path/to/HDK
+			-DHY.TARGET=path/to/target".</li>
+		</ul>
+		
+		So, for example, 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:
+		<ol>
+			<li>Checkout the luni module</li>
+			<li>cd into the root directory of the module</li>
+			<li>Execute "ant -DHY.HDK=path/to/hdk -DHY.TARGET=path/to/target"</li>
+		</ol>
+		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>
+</subsection>
+</section>
+</body>
 </document>



Mime
View raw message