You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by na...@apache.org on 2007/03/19 15:12:08 UTC
svn commit: r519951 [1/5] - in /harmony/standard/site: docs/
docs/subcomponents/classlibrary/ docs/subcomponents/drlvm/ xdocs/
xdocs/subcomponents/classlibrary/ xdocs/subcomponents/drlvm/
Author: nadinem
Date: Mon Mar 19 07:12:06 2007
New Revision: 519951
URL: http://svn.apache.org/viewvc?view=rev&rev=519951
Log:
HARMONY-3364: applying patches 3 and 6
Modified:
harmony/standard/site/docs/code_scan_tools.html
harmony/standard/site/docs/contribution_policy.html
harmony/standard/site/docs/downloads.html
harmony/standard/site/docs/guidelines.html
harmony/standard/site/docs/hdk.html
harmony/standard/site/docs/index.html
harmony/standard/site/docs/issue_resolution_guideline.html
harmony/standard/site/docs/mailing.html
harmony/standard/site/docs/newshistory.html
harmony/standard/site/docs/quickhelp_users.html
harmony/standard/site/docs/related.html
harmony/standard/site/docs/roadmap.html
harmony/standard/site/docs/sitemap.html
harmony/standard/site/docs/subcomponents/classlibrary/agreements.html
harmony/standard/site/docs/subcomponents/classlibrary/asn1_framework.html
harmony/standard/site/docs/subcomponents/classlibrary/compat.html
harmony/standard/site/docs/subcomponents/classlibrary/pkgnaming.html
harmony/standard/site/docs/subcomponents/classlibrary/ser_testing.html
harmony/standard/site/docs/subcomponents/classlibrary/testing.html
harmony/standard/site/docs/subcomponents/drlvm/DoxygenStart.html
harmony/standard/site/docs/subcomponents/drlvm/TM.html
harmony/standard/site/docs/subcomponents/drlvm/debugging_VM_and_JIT.html
harmony/standard/site/docs/subcomponents/drlvm/emguide.html
harmony/standard/site/docs/subcomponents/drlvm/encoder_library.html
harmony/standard/site/xdocs/code_scan_tools.xml
harmony/standard/site/xdocs/contribution_policy.xml
harmony/standard/site/xdocs/downloads.xml
harmony/standard/site/xdocs/guidelines.xml
harmony/standard/site/xdocs/hdk.xml
harmony/standard/site/xdocs/index.xml
harmony/standard/site/xdocs/issue_resolution_guideline.xml
harmony/standard/site/xdocs/mailing.xml
harmony/standard/site/xdocs/newshistory.xml
harmony/standard/site/xdocs/quickhelp_users.xml
harmony/standard/site/xdocs/related.xml
harmony/standard/site/xdocs/roadmap.xml
harmony/standard/site/xdocs/sitemap.xml
harmony/standard/site/xdocs/subcomponents/classlibrary/ASN1Framework.html
harmony/standard/site/xdocs/subcomponents/classlibrary/AWT.html
harmony/standard/site/xdocs/subcomponents/classlibrary/agreements.xml
harmony/standard/site/xdocs/subcomponents/classlibrary/asn1_framework.xml
harmony/standard/site/xdocs/subcomponents/classlibrary/compat.xml
harmony/standard/site/xdocs/subcomponents/classlibrary/pkgnaming.xml
harmony/standard/site/xdocs/subcomponents/classlibrary/ser_testing.xml
harmony/standard/site/xdocs/subcomponents/classlibrary/testing.xml
harmony/standard/site/xdocs/subcomponents/drlvm/TM.xml
harmony/standard/site/xdocs/subcomponents/drlvm/ThreadManager.html
harmony/standard/site/xdocs/subcomponents/drlvm/debugging_VM_and_JIT.html
harmony/standard/site/xdocs/subcomponents/drlvm/debugging_VM_and_JIT.xml
harmony/standard/site/xdocs/subcomponents/drlvm/emguide.xml
harmony/standard/site/xdocs/subcomponents/drlvm/encoder_library.xml
Modified: harmony/standard/site/docs/code_scan_tools.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/code_scan_tools.html?view=diff&rev=519951&r1=519950&r2=519951
==============================================================================
--- harmony/standard/site/docs/code_scan_tools.html (original)
+++ harmony/standard/site/docs/code_scan_tools.html Mon Mar 19 07:12:06 2007
@@ -192,40 +192,40 @@
<a name="Apache Harmony Code Scanning Tools">Apache Harmony Code Scanning Tools</a>
</h1>
<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>
+ 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>
<h2>
<a name="Apache Harmony Keyword Scanner">Apache Harmony Keyword Scanner</a>
</h2>
<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>
+ 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>
+ 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>
+ <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>
+ We welcome any feedback and further contributions to this or other code-provenance
+ utilities and tools.
+ </p>
<p><a href="#top">Back to top</a></p>
Modified: harmony/standard/site/docs/contribution_policy.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/contribution_policy.html?view=diff&rev=519951&r1=519950&r2=519951
==============================================================================
--- harmony/standard/site/docs/contribution_policy.html (original)
+++ harmony/standard/site/docs/contribution_policy.html Mon Mar 19 07:12:06 2007
@@ -192,54 +192,53 @@
<a name="Apache Harmony Contribution Policy">Apache Harmony Contribution Policy</a>
</h1>
<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>
+ 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>
+ 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>
+ <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>
<h2>
<a name="Division of Repository">Division of Repository</a>
</h2>
<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>
+ 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
@@ -268,14 +267,14 @@
/...
</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>
+ 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>
<h2>
@@ -283,19 +282,19 @@
</h2>
<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>
+ 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>
<h2>
@@ -303,23 +302,23 @@
</h2>
<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>
+ 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>
<h2>
@@ -327,39 +326,40 @@
</h2>
<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>
+ 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>
+ <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>
+ 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>
+ <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>
<p><a href="#top">Back to top</a></p>
Modified: harmony/standard/site/docs/downloads.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/downloads.html?view=diff&rev=519951&r1=519950&r2=519951
==============================================================================
--- harmony/standard/site/docs/downloads.html (original)
+++ harmony/standard/site/docs/downloads.html Mon Mar 19 07:12:06 2007
@@ -225,13 +225,16 @@
have not been tested, and are not official releases of the Apache Harmony project or
the Apache Software Foundation.
</p>
- <h3>Java Development Kit (JDK)</h3>
- <p>
+ <dl>
+ <dt>Java Development Kit (JDK)</dt>
+
+ <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>
- <ul>
+</dd>
+
+<ul>
<li>
<a href="http://people.apache.org/builds/harmony/snapshots/latest-harmony-jdk-linux-x86.tar.gz">Latest 32-bit Linux JDK (tar.gz)</a>
<a href="http://people.apache.org/builds/harmony/snapshots/latest-harmony-jdk-linux-x86.tar.gz.md5">(MD5)</a>
@@ -248,12 +251,15 @@
<a href="http://people.apache.org/builds/harmony/snapshots/latest-harmony-jdk-windows-x86.zip.sha">(SHA)</a>
</li>
</ul>
- <h3>Java Runtime Environment (JRE)</h3>
- <p>
+
+<dt>Java Runtime Environment (JRE)</dt>
+
+<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>
- <ul>
+ </dd>
+
+ <ul>
<li>
<a href="http://people.apache.org/builds/harmony/snapshots/latest-harmony-jre-linux-x86.tar.gz">Latest 32-bit Linux JRE (tar.gz)</a>
<a href="http://people.apache.org/builds/harmony/snapshots/latest-harmony-jre-linux-x86.tar.gz.md5">(MD5)</a>
@@ -270,12 +276,15 @@
<a href="http://people.apache.org/builds/harmony/snapshots/latest-harmony-jre-windows-x86.zip.sha">(SHA)</a>
</li>
</ul>
- <h3>Harmony Development Kit (HDK)</h3>
- <p>
+
+ <dt>Harmony Development Kit (HDK)</dt>
+
+ <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>
- <ul>
+ </dd>
+
+ <ul>
<li>
<a href="http://people.apache.org/builds/harmony/snapshots/latest-harmony-hdk-linux-x86.tar.gz">Latest 32-bit Linux HDK (tar.gz)</a>
<a href="http://people.apache.org/builds/harmony/snapshots/latest-harmony-hdk-linux-x86.tar.gz.md5">(MD5)</a>
@@ -292,6 +301,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
Modified: harmony/standard/site/docs/guidelines.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/guidelines.html?view=diff&rev=519951&r1=519950&r2=519951
==============================================================================
--- harmony/standard/site/docs/guidelines.html (original)
+++ harmony/standard/site/docs/guidelines.html Mon Mar 19 07:12:06 2007
@@ -200,7 +200,7 @@
</p>
<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>
@@ -211,7 +211,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
@@ -220,46 +220,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>
@@ -274,8 +274,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>
@@ -292,18 +292,18 @@
</h1>
<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>
<p><a href="#top">Back to top</a></p>
<h1>
@@ -313,34 +313,34 @@
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,
@@ -352,7 +352,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>
@@ -369,7 +369,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>
@@ -378,7 +378,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>
@@ -387,20 +387,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>
@@ -411,9 +411,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>
@@ -426,7 +426,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>
@@ -442,40 +442,39 @@
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>
<p><a href="#top">Back to top</a></p>
<h1>
@@ -483,25 +482,26 @@
</h1>
<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 >> patchfile.txt</pre>
+file(s).</p>
+ <p class="example">Example</p>
+ <pre>diff -u http_main.c.orig http_main.c >> patchfile.txt</pre>
<p>or</p>
- <pre> cvs diff -u http_main.c >> patchfile.txt</pre>
+ <pre>cvs diff -u http_main.c >> 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 < patchfile</pre>
+ <pre>patch -s < patchfile</pre>
<p>is issued in the target repository.</p>
<p><a href="#top">Back to top</a></p>
<h1>
@@ -512,7 +512,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>
<p><a href="#top">Back to top</a></p>
Modified: harmony/standard/site/docs/hdk.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/hdk.html?view=diff&rev=519951&r1=519950&r2=519951
==============================================================================
--- harmony/standard/site/docs/hdk.html (original)
+++ harmony/standard/site/docs/hdk.html Mon Mar 19 07:12:06 2007
@@ -301,10 +301,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>
@@ -315,7 +316,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>
<p><a href="#top">Back to top</a></p>
Modified: harmony/standard/site/docs/index.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/index.html?view=diff&rev=519951&r1=519950&r2=519951
==============================================================================
--- harmony/standard/site/docs/index.html (original)
+++ harmony/standard/site/docs/index.html Mon Mar 19 07:12:06 2007
@@ -282,16 +282,15 @@
</dd>
</dl>
<p>
- <i>
- Archived articles are <a href="newshistory.html">here</a>
- </i>.
- </p>
+ <i>
+ Archived articles are <a href="newshistory.html">here</a></i>.
+ </p>
<p><a href="#top">Back to top</a></p>
<h1>
<a name="Project Status">Project Status</a>
</h1>
<p>
- How are we doing? We're making steady progress :
+ How are we doing? We're making steady progress:
</p>
<ol>
<li>
Modified: harmony/standard/site/docs/issue_resolution_guideline.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/issue_resolution_guideline.html?view=diff&rev=519951&r1=519950&r2=519951
==============================================================================
--- harmony/standard/site/docs/issue_resolution_guideline.html (original)
+++ harmony/standard/site/docs/issue_resolution_guideline.html Mon Mar 19 07:12:06 2007
@@ -220,16 +220,18 @@
</h2>
<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>
- <p>If <i>the issue is a bug</i>, you should do the following:</p>
- <ol>
+ </dd>
+
+ <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
@@ -257,6 +259,7 @@
<li>If the issue is application-oriented, check the application.</li>
<li>Use issue links if applicable.</li>
</ol>
+ </dd></dl>
<h2>
@@ -264,10 +267,11 @@
</h2>
<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>
@@ -279,6 +283,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>
<p><a href="#top">Back to top</a></p>
Modified: harmony/standard/site/docs/mailing.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/mailing.html?view=diff&rev=519951&r1=519950&r2=519951
==============================================================================
--- harmony/standard/site/docs/mailing.html (original)
+++ harmony/standard/site/docs/mailing.html Mon Mar 19 07:12:06 2007
@@ -192,7 +192,7 @@
<a name="Apache Harmony Mailing Lists">Apache Harmony Mailing Lists</a>
</h1>
<p>
- Apache Harmony mailing lists operate under the following terms :
+ Apache Harmony mailing lists operate under the following terms:
</p>
<ul>
<li>
@@ -232,7 +232,7 @@
</li>
</ul>
<p>
- There are currently three publicly available mailing lists for Harmony :
+ There are currently three publicly available mailing lists for Harmony:
</p>
<h2>
@@ -241,7 +241,7 @@
<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.
@@ -307,15 +307,13 @@
</li>
</ul>
<p>
- Simply add the token to the start of your subject line. For example :
- </p>
+ Simply add the token to the start of your subject line.</p>
+ <p class="example">Example</p>
<pre>
- To : dev@harmony.apache.org
- From : harmony_user@openjava.org
- Subject : [classlib][io] Problem with java.io.OutputSocket
-
- ....
- </pre>
+To: dev@harmony.apache.org
+From: harmony_user@openjava.org
+Subject: [classlib][io] Problem with java.io.OutputSocket
+....</pre>
<h2>
Modified: harmony/standard/site/docs/newshistory.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/newshistory.html?view=diff&rev=519951&r1=519950&r2=519951
==============================================================================
--- harmony/standard/site/docs/newshistory.html (original)
+++ harmony/standard/site/docs/newshistory.html Mon Mar 19 07:12:06 2007
@@ -193,59 +193,34 @@
</h1>
<dl>
<dt>New JRE and HDK Snapshots Posted</dt>
- <dd>
- <p>
- Our <a href="downloads.html">latest snapshots</a> have
+ <dd> Our <a href="downloads.html">latest snapshots</a> have
lots of new fixes and features. The VM has a new GC,
almost complete JVMTI, and now can co-exist with
<a href="http://www.ibm.com/developerworks/java/jdk/harmony">the IBM VME</a> in
the Harmony JRE structure. Our classlibrary continues to grow with new
classes, notably CORBA, thanks to <a href="http://incubator.apache.org/yoko">
- Apache Yoko</a>.
+ Apache Yoko</a>.
Also, the classlibrary includes many new fixes and updates.
Choose the JRE to test your favorite applications, and
<a href="mailing.html">give us feedback</a> on how
we are doing, or use the HDK to enable faster development of the Harmony classlibrary.
(<i>2006-09-28</i>)
- </p>
- </dd>
-
+ </dd>
<dt>Can Apache Harmony Help Sun Open Java?</dt>
- <dd>
- <p>
- We're happy to <a href="http://www.businessreviewonline.com/os/archives/2006/08/open_source_jav.html">help</a>
- (<i>2006-08-16</i>)
- </p>
- </dd>
-
+ <dd>We're happy to <a href="http://www.businessreviewonline.com/os/archives/2006/08/open_source_jav.html">help</a>
+ (<i>2006-08-16</i>)</dd>
<dt>New Snapshot Posted</dt>
- <dd>
- <p>
- Lots of fixes and additions in the latest snapshot. (<i>2006-08-16</i>)
- </p>
- </dd>
-
+ <dd>Lots of fixes and additions in the latest snapshot. (<i>2006-08-16</i>)</dd>
<dt>DRLVM Documentation Update</dt>
- <dd>
- <p>
- Check our new documentation on <a href="subcomponents/drlvm/index.html">DRLVM</a>
+ <dd>Check our new documentation on <a href="subcomponents/drlvm/index.html">DRLVM</a>
including guides for building, using, debugging, GC architecture and execution manager
- architecture. (<i>2006-08-05</i>)
- </p>
- </dd>
-
+ architecture. (<i>2006-08-05</i>)</dd>
<dt>New HDK and JRE Snapshots Available</dt>
- <dd>
- <p>
- New <a href="http://people.apache.org/builds/harmony/snapshots/">snapshots</a>
+ <dd>New <a href="http://people.apache.org/builds/harmony/snapshots/">snapshots</a>
of the HDK and JRE are now available with lots of bugfixes. (<i>2006-08-04</i>)
- </p>
</dd>
-
<dt>HDK and JRE Snapshots Available</dt>
- <dd>
- <p>
- Harmony now <a href="http://people.apache.org/builds/harmony/snapshots/">offers a snapshot</a>
+ <dd>Harmony now <a href="http://people.apache.org/builds/harmony/snapshots/">offers a snapshot</a>
of it's JRE and HDK builds.
The JRE snapshot is our in-progress Java Runtime Environment,
including both the virtual machine and classlibrary. Note that
@@ -255,26 +230,18 @@
to complete the most popular parts of the classlibrary first. The HDK
snapshot is a developers build, complete with classlibrary jars and
native libraries, header files, and build scripts. (<i>2006-07-22</i>)
- </p>
- </dd>
-
+ </dd>
<dt>New class library snapshot build available</dt>
- <dd>
- <p>
- A new stable snapshot of the class libraries code is available
+ <dd>A new stable snapshot of the class libraries code is available
for download from the <a href="downloads.html">Harmony downloads page</a>.
These are made available for people to evaluate and experiment
with the code. This snapshot contains the recently integrated
Swing, AWT, and Java2D code. As always, please report bugs
(and successes!) to the <a href="mailing.html">Harmony developers mailing list</a>.
(<i>2006-06-30</i>)
- </p>
- </dd>
-
+ </dd>
<dt>AWT, Java2D and Swing Code Contribution</dt>
- <dd>
- <p>
- On May 30th, 2006 the Apache Harmony project received a
+ <dd>On May 30th, 2006 the Apache Harmony project received a
<a href="https://issues.apache.org/jira/browse/HARMONY-528">
substantial contribution</a> of class library code into the project.
The code for AWT, Java2D, and Swing implementation has been contributed by Alexey
@@ -282,75 +249,50 @@
on the <a href="mailing.html">Harmony developers mailing list</a>. Thanks to
Alexey and his colleagues in the Intel Middleware Products Division!
(<i>2006-05-31</i>)
- </p>
</dd>
-
<dt>New class library snapshot build available</dt>
- <dd>
- <p>
- A new stable snapshot of the class libraries code is available
+ <dd> A new stable snapshot of the class libraries code is available
for download from the <a href="downloads.html">Harmony downloads page</a>.
There are source and binary downloads available for people to
evaluate and experiment with the code. As always, please report bugs
(and successes!) to the <a href="mailing.html">Harmony developers mailing list</a>.
(<i>2006-05-12</i>)
- </p>
- </dd>
-
+ </dd>
<dt>DRL Virtual Machine Contribution</dt>
- <dd>
- <p>
- On May 3rd, 2006 the Apache Harmony project received a
+ <dd> On May 3rd, 2006 the Apache Harmony project received a
<a href="http://issues.apache.org/jira/browse/HARMONY-438">
substantial contribution </a> of virtual machine (VM) code into the project,
containing a JIT, core VM, GC, bytecode verifier, etc. This was contributed by
Andrey Chernyshev on behalf of Intel Corp. The full announcement can
be found on the <a href="mailing.html">Harmony developers mailing list</a>.
- (<i>2006-05-03</i>)
- </p>
- </dd>
-
+ (<i>2006-05-03</i>)</dd>
<dt>Java Security Code Contribution</dt>
- <dd>
- <p>
- On December 30th, 2005 the Apache Harmony project accepted additional
+ <dd>On December 30th, 2005 the Apache Harmony project accepted additional
class library code into the project. The code had been contributed by
Mikhail Loenko on behalf of Intel corp. The new class library code
includes security, cryptography, javax.net and unit tests. Thanks to
Mikhail and his collegues in the Intel Managed Runtime Division!
(<i>2006-01-16</i>)
- </p>
</dd>
-
<dt>VM Interface and Core Classes Contribution</dt>
- <dd>
- <p>
- IBM has offered the Apache Harmony project a set of core
+ <dd>IBM has offered the Apache Harmony project a set of core
Java classes and an implementation of a VM/class library
- interface. Tim Ellison wrote:
- </p>
- <p>
+ interface. Tim Ellison wrote:<br />
<i>
- I'm delighted to be able to make a code contribution to the
+ "I'm delighted to be able to make a code contribution to the
Harmony project on behalf of IBM. The code comprises a concrete implementation
of the interface between virtual machine and class library that we have
- been discussing recently, together with a set of core Java classes.
- </i>
- </p>
- <p>
+ been discussing recently, together with a set of core Java classes."
+ </i><br />
This contribution is sufficient to run Ant and the Eclipse Java
compiler, to provide a basic self-hosting environment. IBM also
made a version of their J9 VM
<a href="http://www.ibm.com/developerworks/java/jdk/harmony">
available </a> for use by the project in evaluating this contribution.
Thanks Tim and IBM :) (<i>2005-11-08</i>)
- </p>
</dd>
-
<dt>"Bootstrap JVM" Contributed to Apache Harmony</dt>
- <dd>
- <p>
- Daniel Lydickto the Harmony project of a basic Java Virtual Machine entitled
+ <dd> Daniel Lydickto the Harmony project of a basic Java Virtual Machine entitled
the "Apache Harmony Bootstrap JVM." Dan offered the VM with the following goals in mind:
<ul>
<li>Basic platform for learning about VMs</li>
@@ -358,24 +300,15 @@
<li>Help spur architectural discussion about core component designs</li>
</ul>
Thanks Dan! (<i>2005-09-30</i>)
- </p>
</dd>
-
<dt>Source for JCVM Contributed to Apache Harmony</dt>
- <dd>
- <p>
- Archie Cobbs has offered for contribution to the Apache Harmony project
+ <dd>Archie Cobbs has offered for contribution to the Apache Harmony project
a copy of the <a href="http://jcvm.sourceforge.net/">JCVM</a> codebase. Come and
help us build on this interesting VM. Thanks Archie! (<i>2005-09-25</i>)
- </p>
</dd>
-
<dt>Project accepted by Apache Incubator</dt>
- <dd>
- <p>
- The Apache Harmony project was accepted formally accepted for
+ <dd>The Apache Harmony project was accepted formally accepted for
inubation by the Apache Incubator PMC. (<i>2005-05-18</i>)
- </p>
</dd>
</dl>
<p><a href="#top">Back to top</a></p>
Modified: harmony/standard/site/docs/quickhelp_users.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/quickhelp_users.html?view=diff&rev=519951&r1=519950&r2=519951
==============================================================================
--- harmony/standard/site/docs/quickhelp_users.html (original)
+++ harmony/standard/site/docs/quickhelp_users.html Mon Mar 19 07:12:06 2007
@@ -201,8 +201,7 @@
For more information on how to get you machine configured to build and
work with the Apache Harmony source code, refer to
<a href="quickhelp_contributors.html">
- Getting Started For Contributors
- </a>.
+ Getting Started For Contributors</a>.
</p>
<p>
The required dependencies are listed below per platform.
@@ -238,33 +237,32 @@
directory. Further in the document we refer to this directory
as the <i>root directory</i> of the distribution.
</p>
- <strong>Linux Users</strong>
- <p>
+ <dl>
+ <dt>Linux Users</dt>
+
+ <dd>
Use the <code>tar</code> program as follows:
- </p>
- <pre>
-$ tar -tzf latest-harmony-jre-linux.tar.gz
- </pre>
- <p>
+<pre>$ tar -tzf latest-harmony-jre-linux.tar.gz</pre>
+</dd>
+ <dd>
This will unpack the JRE directory tree into the current directory.
- </p>
- <strong>Windows Users</strong>
- <p>
+ </dd>
+ <dt>Windows Users</dt>
+ <dd>
Use one of <code>zip</code> utilities available for Windows to
unpack the distribution. The three popular ones are listed
below, but anything that can handle a <code>zip</code> file
will work:
- </p>
- <ul>
+ <ul>
<li><a href="http://www.info-zip.org/">Info-ZIP</a>
(open source software)</li>
<li><a href="http://www.7-zip.org/">7-Zip</a> (free software)</li>
<li><a href="http://www.winzip.com/">Winzip</a> (commercial)</li>
- </ul>
- <p>
+ </ul></dd>
+ <dd>
To create the JRE directory tree, extract the
distribution <code>zip</code> file using the utility.
- </p>
+ </dd></dl>
<h2>
@@ -281,36 +279,34 @@
environment variables, use the commands appropriate to your
operating system and/or shell you are using.
</p>
- <strong>
- Linux Users</strong>
- <p>
+ <dl>
+ <dt>
+ Linux Users</dt>
+ <dd>
The following command works for the Bash shell:
- </p>
- <pre>
-$ cd jre
+<pre>$ cd jre
$ export JAVA_HOME=`pwd`
$ cd bin
-$ export PATH=`pwd`:$PATH
- </pre>
- <p>
+$ export PATH=`pwd`:$PATH</pre>
+</dd>
+ <dd>
The given command assumes your current directory is the parent
directory of the Harmony JRE.
- </p>
- <p class="note">Note</p>
- <p class="notetext">The <code>`</code> character is a backtick character,
+ </dd>
+ <p class="note">Note</p>
+ <p class="notetext">The <code>`</code> character is a backtick character,
not an apostrophe.</p>
- <strong>Windows Users</strong>
- <p>
+ <dt>Windows Users</dt>
+ <dd>
The following example assumes you unpacked the <code>zip</code>
file into the root directory <code>C:\</code>.
Please adjust as necessary.
- </p>
- <pre>
- C:> cd jre
- C:\jre>set JAVA_HOME=C:\jre
- C:\jre> cd bin
- C:\jre\bin> set PATH=C:\jre\bin;%PATH%
- </pre>
+<pre>C:> cd jre
+C:\jre>set JAVA_HOME=C:\jre
+C:\jre> cd bin
+C:\jre\bin> set PATH=C:\jre\bin;%PATH%</pre>
+</dd>
+ </dl>
<h2>
@@ -323,10 +319,8 @@
<code>javac</code>, so continue to use the compiler from some
other JRE. You should have no problems running programs.
</p>
- <pre>
-$ java Foo
-$ java -jar myjar.jar
- </pre>
+ <pre>$ java Foo
+$ java -jar myjar.jar</pre>
<p><a href="#top">Back to top</a></p>
Modified: harmony/standard/site/docs/related.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/related.html?view=diff&rev=519951&r1=519950&r2=519951
==============================================================================
--- harmony/standard/site/docs/related.html (original)
+++ harmony/standard/site/docs/related.html Mon Mar 19 07:12:06 2007
@@ -193,17 +193,17 @@
</h1>
<p>
Besides our own DRLVM virtual machine, there are also other virtual
- machines that work with the Apache Harmony classlibrary :
+ machines that work with the Apache Harmony class library:
</p>
<ul>
- <li><a href="http://www.ibm.com/developerworks/java/jdk/harmony/">IBM J9</a> : IBM has
+ <li><a href="http://www.ibm.com/developerworks/java/jdk/harmony/">IBM J9</a>: IBM has
made their production-grade virtual machine available for project use under
- a non-open source, evaluation binary license. This VM works with the Harmony
+ a non-open source, evaluation binary license. This VM works with the Harmony
class library.
</li>
- <li><a href="http://dev2dev.bea.com/jrockit/jrockitVM/">BEA JRockit</a> : BEA has
+ <li><a href="http://dev2dev.bea.com/jrockit/jrockitVM/">BEA JRockit</a>: BEA has
made their production-grade virtual machine available for project use under
- a non-open source, evaluation binary license. This VM works with the Harmony
+ a non-open source, evaluation binary license. This VM works with the Harmony
class library.
</li>
</ul>
Modified: harmony/standard/site/docs/roadmap.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/roadmap.html?view=diff&rev=519951&r1=519950&r2=519951
==============================================================================
--- harmony/standard/site/docs/roadmap.html (original)
+++ harmony/standard/site/docs/roadmap.html Mon Mar 19 07:12:06 2007
@@ -193,11 +193,11 @@
</h1>
<p>
Are roadmap and goals are always subject to discussion on the
- <a href="mailing.html">developer's list.</a> As new people join with new focus and
+ <a href="mailing.html">developer's list.</a> As new people join with new focus and
interests, the things we do as a project adapt.
</p>
<p>
- If you have an idea, come join the community and talk about it. Note that you will
+ If you have an idea, come join the community and talk about it. Note that you will
need to subscribe to the <a href="mailing.html">mail list</a>
</p>
<p><a href="#top">Back to top</a></p>
@@ -206,7 +206,7 @@
</h1>
<p>
Our project goal is an open source, compatible implementation of Java SE 5.
- It's a major task being done by a community of volunteers. Thus, the following
+ It's a major task being done by a community of volunteers. Thus, the following
is an approximate roadmap for what the project hopes to achieve in the next year.
</p>
<ul>
@@ -282,9 +282,9 @@
Q4 2007: Apache Harmony SE 6 JDK and JRE released
</li>
<li>
- Q? 2008: Apache Harmony SE 7 JDK and JRE released. Note: The Java SE 7
- JSR has not yet been proposed by Sun. We assume 18
- months from start of JSR to completion. We hope to
+ Q? 2008: Apache Harmony SE 7 JDK and JRE released. Note: The Java SE 7
+ JSR has not yet been proposed by Sun. We assume 18
+ months from start of JSR to completion. We hope to
deliver Harmony's implementation of Java SE 7 at the
same time Sun does.
</li>
@@ -295,7 +295,7 @@
</h1>
<p>
The following is a collection of things that the project community
- has listed as needing to be done. This list is not exhaustive. If
+ has listed as needing to be done. This list is not exhaustive. If
you wish to add an item to this list, or discuss or even volunteer
to work on an item, please join us on the <a href="mailing.html">
Harmony
@@ -342,29 +342,29 @@
<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 portablility, 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
+ code that starts the VM and invokes the tool. Currently, we have
javac completed via the Eclipse compiler, but we need the following:
</p>
<ul>
<li>
- javac (Done), javadoc, apt, appletviewer, jar, jdb, javah, javap, extcheck
- </li>
- <li>
- keytool, jarsigner, policytool, kinit, klist, ktab
- </li>
- <li>
- native2ascii,rmic, rmiregistry, rmid, serialver
- </li>
- <li>
- tnameserv, idlj, orbd, servertool
- </li>
- <li>
- pack200, unpack200
- </li>
- <li>
- htmlconverter, javaws
+ <code>javac (Done), javadoc, apt, appletviewer, jar, jdb, javah, javap, extcheck</code>
+ </li>
+ <li>
+ <code>keytool, jarsigner, policytool, kinit, klist, ktab</code>
+ </li>
+ <li>
+ <code>native2ascii,rmic, rmiregistry, rmid, serialver</code>
+ </li>
+ <li>
+ <code>tnameserv, idlj, orbd, servertool</code>
+ </li>
+ <li>
+ <code>pack200, unpack200</code>
+ </li>
+ <li>
+ <code>htmlconverter, javaws</code>
</li>
</ul>
<p>
@@ -373,7 +373,7 @@
<h3>2. Modularity</h3>
<p>
From the beginning of our project, we've had a strong interest and focus
- on modularity This dedication has paid off in our class library development,
+ on modularity. This dedication has paid off in our class library development,
as we've been able to evaluate competing implementations of RMI and math, as
well as allow developers to isolate development on one module.
</p>
@@ -392,20 +392,20 @@
<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
+ 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
+ to revisit given the differnet toolchains. There are many things to do
in this area, many not listed.
</p>
<p>
Currently, the project has been releasing snapshots of our class library,
but now that we have the DRLVM virtual machine, we can start doing complete
- snapshot builds of a JRE, as well as the HDK
+ snapshot builds of a JRE, as well as the HDK.
</p>
<ul>
<li>
Switch to use system libraries, dynamically where appropriate
- - libz, libpng, libjpeg, liblcms, libicu*, etc.
+ - <code>libz, libpng, libjpeg, liblcms, libicu*,</code> etc.
</li>
<li>
Create regular schedule for snapshots and automate.
@@ -432,7 +432,7 @@
</li>
<li>
Remove assumption in class library build system that all that uses make is
- linux.
+ Linux.
</li>
</ul>
@@ -448,10 +448,8 @@
project codebase on that platform.
</p>
<p>
- There is an
- <a href="http://svn.apache.org/viewvc/harmony/enhanced/buildtest/">
- initial implementation
- </a> in place in SVN, but much more work is needed.
+ There is an <a href="http://svn.apache.org/viewvc/harmony/enhanced/buildtest/">
+ initial implementation</a> in place in SVN, but much more work is needed.
Ideas include:
</p>
<ul>
@@ -460,7 +458,7 @@
</li>
<li>
Create live "status dashboard" with a summary of results from all tested platforms,
- as wella s history for each tested platform.
+ as well as history for each tested platform.
</li>
<li>
Integrate with <a href="http://www.kaffe.org/~stuart/japi/">JAPI</a>
@@ -470,8 +468,8 @@
class library testing
</li>
<li>
- Integrate with test-coverage tool (ex <a href="http://emma.sourceforge.net/">emma</a>
- for auto-generated reports.
+ Integrate with test-coverage tool (for example, <a href="http://emma.sourceforge.net/">emma</a>
+ for auto-generated reports).
</li>
<li>
Externalize local properties into a 'test.properties' file for easy of localization.
@@ -511,27 +509,27 @@
<p>
The class library is an important (and large!) part of the Java SE
- platform. While we have made significant progress so far (~80% at last
- check), there are many, many interesting things remaining to be done
+ platform. While we have made significant progress so far (~80% at last
+ check), there are many, many interesting things remaining to be done.
</p>
<ul>
<li>
<a href="subcomponents/classlibrary/status.html">General package completion</a>
</li>
<li>
- java.util.concurrency: integration of Doug Lea's RI package. Goal is to
+ <code>java.util.concurrency</code>: integration of Doug Lea's RI package. Goal is to
use unmodified code from the 166 expert group and implent whatever
- support is needed by the VM and rest of class library. (in progress)
+ support is needed by the VM and rest of class library. (<i>in progress</i>)
</li>
<li>
CORBA: re-use the Apache Yoko project (currently in incubator)
as the required implementation of CORBA nad related support
- classes (in progress)
+ classes (<i>in progress</i>)
</li>
<li>
JMX: currently we have the standard MX4J jars integrated, but
looking to see what kind of collaboration or unification we can
- achieve with the MX4J project. (in progress)
+ achieve with the MX4J project. (<i>in progress</i>)
</li>
<li>
Test coverage - we need to greatly increase our unit tests (functionaly,
@@ -545,8 +543,8 @@
</h2>
<p>
- VM is a critical part of the Java SE platform. As usual, there are many, many interesting things remaining to be done
- </p>
+ VM is a critical part of the Java SE platform. As usual, there are many, many interesting
+ things remaining to be done.</p>
<ul>
<li>
<a href="http://wiki.apache.org/harmony/CoreVmDevelopmentItems">Core VM Development Items</a>
@@ -579,7 +577,7 @@
<p>
Another motivation of the Harmony project is to provide a
portable implementation that is available on many
- platforms and operating systems. Currently, our interests
+ platforms and operating systems. Currently, our interests
are:
</p>
<table>
@@ -794,16 +792,12 @@
</table>
<p>
<b>Legend</b>
- <dl>
- <dt>"+"</dt>
- <dd>Supported (sure-to-work)</dd>
- <dt>"?"</dt>
- <dd>In progress</dd>
- <dt>"-"</dt>
- <dd>Will Not Support</dd>
- <dt>" " (empty)</dt>
- <dd>N/A or Maybe</dd>
- </dl>
+ <ul>
+ <li>"+" - Supported (sure-to-work)</li>
+ <li>"?" - In progress</li>
+ <li>"-" - Will Not Support</li>
+ <li>" " (empty) - N/A or Maybe</li>
+ </ul>
</p>
@@ -815,10 +809,10 @@
As we now have a fairly usable class library and virtual machine, we wish to
make it easy for the broad Java user community to help us ensure that
the Harmony class library supports the classes necessary for the most popular
- and used applications out there. While we will complete the class library,
+ and used applications out there. While we will complete the class library,
tools like this will help us do it in a way that prioritizes the most useful
first, enabling even more users to test our software and participate in
- the project. So far, there have been a few tools donated, but no concerted
+ the project. So far, there have been a few tools donated, but no concerted
effort to package for ease of use.
</p>
<ul>
@@ -829,8 +823,7 @@
</li>
<li>
<a href="https://issues.apache.org/jira/browse/HARMONY-565">
- Harmony-565
- </a> - another tool for reporting class coverage for applications
+ Harmony-565</a> - another tool for reporting class coverage for applications
</li>
</ul>