harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From hinde...@apache.org
Subject svn commit: r822451 - in /harmony/standard/site/trunk: docs/issue_resolution_guideline.html docs/roadmap.html xdocs/issue_resolution_guideline.xml xdocs/roadmap.xml
Date Tue, 06 Oct 2009 19:28:32 GMT
Author: hindessm
Date: Tue Oct  6 19:28:32 2009
New Revision: 822451

URL: http://svn.apache.org/viewvc?rev=822451&view=rev
Log:
Trivial spelling fixes (and testing harmony.staging.apache.org).

Modified:
    harmony/standard/site/trunk/docs/issue_resolution_guideline.html
    harmony/standard/site/trunk/docs/roadmap.html
    harmony/standard/site/trunk/xdocs/issue_resolution_guideline.xml
    harmony/standard/site/trunk/xdocs/roadmap.xml

Modified: harmony/standard/site/trunk/docs/issue_resolution_guideline.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/trunk/docs/issue_resolution_guideline.html?rev=822451&r1=822450&r2=822451&view=diff
==============================================================================
--- harmony/standard/site/trunk/docs/issue_resolution_guideline.html (original)
+++ harmony/standard/site/trunk/docs/issue_resolution_guideline.html Tue Oct  6 19:28:32 2009
@@ -31,11 +31,8 @@
             <meta name="email" content="dev@harmony.apache.org">
             
            
-            
-            
-            
-            
-            
+                                    
+                        
             <title>Apache Harmony - Good Issue Resolution Guideline</title>
 
                         
@@ -257,7 +254,7 @@
                   Create a patch to fix the issue. If you have any questions,
                   discuss them on the <a href="mailing.html">developer mailing list</a>.
                   Add a link to the discussion as a comment.</li>
-                <li>All pacthes, such as tests and fixes, should be relative to the
directory where 
+                <li>All patches, such as tests and fixes, should be relative to the
directory where 
                 the main <code>build.xml</code> is:<br />
                 <code>http://svn.apache.org/repos/asf/harmony/enhanced/classlib/trunk</code>,<br
/>
                 or to the module root directory.</li>

Modified: harmony/standard/site/trunk/docs/roadmap.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/trunk/docs/roadmap.html?rev=822451&r1=822450&r2=822451&view=diff
==============================================================================
--- harmony/standard/site/trunk/docs/roadmap.html (original)
+++ harmony/standard/site/trunk/docs/roadmap.html Tue Oct  6 19:28:32 2009
@@ -31,11 +31,8 @@
             <meta name="email" content="dev@harmony.apache.org">
             
            
-            
-            
-            
-            
-            
+                                    
+                        
             <title>Apache Harmony - Project Roadmap</title>
 
                         
@@ -374,7 +371,7 @@
                                 <p>
           As part of the JDK that Harmony will distribute, we'll include
           the full set of tools that Java programmers expect to find in
-          any JDK. For maximum portablility, we plan to write all of the
+          any JDK. For maximum portability, we plan to write all of the
           tools in Java, using the Harmony launcher as the portable native
           code that starts the VM and invokes the tool. Currently, we have
           the following completed:
@@ -433,8 +430,8 @@
                         <p>
           Build engineering in Harmony is a complicated subject, as we are building
           on multiple platforms in multiple languages. So far, we have support for
-          our Windows and Linux ports, but our porting plans indiciate that we'll need
-          to revisit given the differnet toolchains. There are many things to do
+          our Windows and Linux ports, but our porting plans indicate that we'll need
+          to revisit given the different toolchains. There are many things to do
           in this area, many not listed.
         </p>
                                 <ul>
@@ -459,7 +456,7 @@
             <b>DONE</b>
           </font>
           <strike>          
-            Federated build - abliity to builds a complete JDK from top level
+            Federated build - ability to builds a complete JDK from top level
             using choice of project VM
           </strike>
           </li>
@@ -468,7 +465,7 @@
             debug/release flag, structure of artifacts (model after classlib for now) <i>(in
progress)</i>
           </li>
           <li>
-            Common dependency pool for all projet parts to share <i>(in progress)</i>
+            Common dependency pool for all project parts to share <i>(in progress)</i>
           </li>
           <li>
           <font color="green">
@@ -617,7 +614,7 @@
             WebStart and browser plug-in implementation
           </li>
           <li>
-            Test coverage - we need to greatly increase our unit tests (functionaly,
+            Test coverage - we need to greatly increase our unit tests (functional,
             spec, implementation)
           </li>
         </ul>

Modified: harmony/standard/site/trunk/xdocs/issue_resolution_guideline.xml
URL: http://svn.apache.org/viewvc/harmony/standard/site/trunk/xdocs/issue_resolution_guideline.xml?rev=822451&r1=822450&r2=822451&view=diff
==============================================================================
--- harmony/standard/site/trunk/xdocs/issue_resolution_guideline.xml (original)
+++ harmony/standard/site/trunk/xdocs/issue_resolution_guideline.xml Tue Oct  6 19:28:32 2009
@@ -79,7 +79,7 @@
                   Create a patch to fix the issue. If you have any questions,
                   discuss them on the <a href="mailing.html">developer mailing list</a>.
                   Add a link to the discussion as a comment.</li>
-                <li>All pacthes, such as tests and fixes, should be relative to the
directory where 
+                <li>All patches, such as tests and fixes, should be relative to the
directory where 
                 the main <code>build.xml</code> is:<br/>
                 <code>http://svn.apache.org/repos/asf/harmony/enhanced/classlib/trunk</code>,<br/>
                 or to the module root directory.</li>

Modified: harmony/standard/site/trunk/xdocs/roadmap.xml
URL: http://svn.apache.org/viewvc/harmony/standard/site/trunk/xdocs/roadmap.xml?rev=822451&r1=822450&r2=822451&view=diff
==============================================================================
--- harmony/standard/site/trunk/xdocs/roadmap.xml (original)
+++ harmony/standard/site/trunk/xdocs/roadmap.xml Tue Oct  6 19:28:32 2009
@@ -202,7 +202,7 @@
         <p>
           As part of the JDK that Harmony will distribute, we'll include
           the full set of tools that Java programmers expect to find in
-          any JDK. For maximum portablility, we plan to write all of the
+          any JDK. For maximum portability, we plan to write all of the
           tools in Java, using the Harmony launcher as the portable native
           code that starts the VM and invokes the tool. Currently, we have
           the following completed:
@@ -263,8 +263,8 @@
         <p>
           Build engineering in Harmony is a complicated subject, as we are building
           on multiple platforms in multiple languages. So far, we have support for
-          our Windows and Linux ports, but our porting plans indiciate that we'll need
-          to revisit given the differnet toolchains. There are many things to do
+          our Windows and Linux ports, but our porting plans indicate that we'll need
+          to revisit given the different toolchains. There are many things to do
           in this area, many not listed.
         </p>
 
@@ -290,7 +290,7 @@
             <b>DONE</b>
           </font>
           <strike>          
-            Federated build - abliity to builds a complete JDK from top level
+            Federated build - ability to builds a complete JDK from top level
             using choice of project VM
           </strike>
           </li>
@@ -299,7 +299,7 @@
             debug/release flag, structure of artifacts (model after classlib for now) <i>(in
progress)</i>
           </li>
           <li>
-            Common dependency pool for all projet parts to share <i>(in progress)</i>
+            Common dependency pool for all project parts to share <i>(in progress)</i>
           </li>
           <li>
           <font color="green">
@@ -444,7 +444,7 @@
             WebStart and browser plug-in implementation
           </li>
           <li>
-            Test coverage - we need to greatly increase our unit tests (functionaly,
+            Test coverage - we need to greatly increase our unit tests (functional,
             spec, implementation)
           </li>
         </ul>



Mime
View raw message