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/13 13:17:45 UTC
svn commit: r517663 [9/14] - in /harmony/standard/site: docs/
docs/documentation/ docs/subcomponents/classlibrary/
docs/subcomponents/drlvm/ xdocs/ xdocs/documentation/ xdocs/stylesheets/
xdocs/subcomponents/classlibrary/ xdocs/subcomponents/drlvm/
Modified: harmony/standard/site/xdocs/auth_cont_quest.txt
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/auth_cont_quest.txt?view=diff&rev=517663&r1=517662&r2=517663
==============================================================================
--- harmony/standard/site/xdocs/auth_cont_quest.txt (original)
+++ harmony/standard/site/xdocs/auth_cont_quest.txt Tue Mar 13 05:17:43 2007
@@ -1,288 +1,288 @@
- The Apache Software Foundation
- Apache Harmony Project
- Authorized Contributor Questionnaire
- v1.0
-
-
-Please Note : This document and your answers are considered public information,
-and shall be part of the Apache Harmony project public records.
-
-Part I : Identification
-
- Please provide the following information
-
- Name : ___________________________________________
- E-mail : ___________________________________________
-
- Mailing address :
- ___________________________________________
- ___________________________________________
- ___________________________________________
- ___________________________________________
-
- Employer : ___________________________________________
-
-Part II: Access to Repositories
-
- The Project is committed to producing an implementation of Java that
- can be licensed freely under the Apache License. To do this,
- we wish to know what, if any, previous exposure you have had
- to the source for any of the parts of a Java implementation
- including virtual machines, class libraries, tooling, etc.
-
- The following activities are not considered "accessing the
- source code" and would not generally disqualify you from
- committing to the related repository here at Apache Harmony
-
- a) Having a copy of src.jar (or equivalent) on a computer as long as you
- never viewed or edited the contents of the file.
-
- b) While running a debugger on a Java language program, having
- had occasion to step into the source code for the implementation
- as long as you did not attempt to understand or debug the
- implementation code itself.
-
- c) Having implemented "plug-ins" or other component software which
- interact with an implementation, but doing so only with reference
- to the published service provider interfaces.
-
- d) Have written or executed test cases that probed the behavior
- of an implementation as long as you did so with reference
- only to published specifications and interfaces.
-
- The following is a list of the components of the project each
- labeled with an ID (ex. JVM-1):
-
- VM
- --
- VM-1 VM core (including JVMPI, JVMDI, JDWP, JVMTI, JNI,
- JIT, Memory Management/GC, OS Portabillity,
- Threading, etc)
- VM-X other ____________________________________________
-
-
- Classlibrary
- ------------
- CL-1 Applet (java.applet)
- CL-2 Archive (java.util.zip, java.util.jar)
- CL-3 Beans (java.beans)
- CL-4 Core (incl. lang, util, net, io, annotation, concurrent,
- NIO-channels, NIO-charset, text, javax.net
- where not covered elsewhere in list)
- CL-5 Image IO (javax.imageio)
- CL-6 Instrument (java.lang.instrument)
- CL-7 JMX (javax.management)
- CL-8 Lang-management (java.lang.management)
- CL-9 Logging (java.util.logging)
- CL-10 Math (java.math)
- CL-11 ORB (javax.activity, javax.rmi.*, javax.transaction.*, org.omg.*)
- CL-12 Prefs (java.util.prefs)
- CL-13 Print (javax.print.*)
- CL-14 Regex (java.util.regex)
- CL-15 RMI (java.rmi.*)
- CL-16 Security (java.security.*, javax.security.*, org.ietf.jgss,
- javax.crypto)
- CL-17 Sound (javax.sound)
- CL-18 SQL (java.sql, javax.sql.*)
- CL-19 Swing / AWT (java.awt.*, javax.swing.*, javax.accessibility)
- CL-20 XML (javax.xml.*, org.w3c.*, org.xml.*)
- CL-21 JNDI (javax.naming.*)
- CL-X other ____________________________________________
-
- Tools & Misc
- ------------
- T-1 launcher (e.g. java.exe)
- T-2 javah
- T-3 javap
- T-4 javac
- T-5 jdb
- T-6 javadoc
- T-7 jar
- T-8 browser plugins
- T-X other ____________________________________________
-
-
-Part III : General Exposure
-
- With the above activities a)-d) in mind, have you done any of the following
- to an implementation of one or more of the components listed above. If the
- question doesn't apply to you, please write "N/A". If it does, please list
- the components by the above-listed IDs, and provide details :
-
- 1. Read some or all the source code for an implementation?
-
- [ ] Yes [ ] No
-
- Components : ________________________________________________________
- Details : ___________________________________________________________
- _____________________________________________________________________
-
- 2. Fixed defects or performed other maintenance activity on an
- implementation?
-
- [ ] Yes [ ] No
-
- Components : ________________________________________________________
- Details : ___________________________________________________________
- _____________________________________________________________________
-
-
- 3. Enhanced the source code for an implementation with additional function,
- performance or other qualities of service?
-
- [ ] Yes [ ] No
-
- Components : ________________________________________________________
- Details : ___________________________________________________________
- _____________________________________________________________________
-
-
- 4. Ported an implementation to a different operating system or hardware
- platform?
-
- [ ] Yes [ ] No
-
- Components : ________________________________________________________
- Details : ___________________________________________________________
- _____________________________________________________________________
-
- 5. Reverse compiled or otherwise reverse engineered an implementation?
-
- [ ] Yes [ ] No
-
- Components : ________________________________________________________
- Details : ___________________________________________________________
- _____________________________________________________________________
-
-
- If you have answered yes to any question above, and that implementation is
- not available under a recognized Open Source license, you may not be an
- contributor to the related component of Apache Harmony unless the
- copyright owner of that implementation either:
-
- a) submits the implementation to this project under the Software Grant or
- the Corporate Contribution License Agreement (the CCLA);
-
- b) if the copyright owner is your current employer, signs a CCLA and
- lists you as a designated employee; or
-
- c) if the copyright owner is not your current employer, submits
- a written authorization disclaiming any copyright or confidentiality
- interest in your current or future contributions to this project.
-
- 6. For each of the components listed above, please indicate either that you
- will not be an Authorized Contributor for those components at Apache
- Harmony, or indicate how you will resolve the issue of previous
- exposure :
-
- _____________________________________________________________________
- _____________________________________________________________________
- _____________________________________________________________________
- _____________________________________________________________________
- _____________________________________________________________________
- _____________________________________________________________________
- _____________________________________________________________________
- _____________________________________________________________________
- _____________________________________________________________________
- _____________________________________________________________________
- _____________________________________________________________________
- _____________________________________________________________________
- _____________________________________________________________________
-
-
-Part IV : Confidential Exposure
-
- 1. Have you had access to any information regarding a proprietary
- implementation of a component that could be considered
- confidential?
-
- [ ] Yes [ ] No
-
- If so, you may be a Authorized Contributor for that component only
- if the owner of that potential confidential information submits
- a written authorization disclaiming any confidentiality interest
- in your current or future contributions to this project.
-
- 2. For each of the components listed above for which you have had access
- to such information, please indicate either that you will not
- be an Authorized Contributor for those components at Apache Harmony, or
- indicate how you will resolve the issue :
-
- _____________________________________________________________________
- _____________________________________________________________________
- _____________________________________________________________________
- _____________________________________________________________________
- _____________________________________________________________________
- _____________________________________________________________________
- _____________________________________________________________________
- _____________________________________________________________________
- _____________________________________________________________________
- _____________________________________________________________________
- _____________________________________________________________________
- _____________________________________________________________________
- _____________________________________________________________________
-
-
-Part V : Non-Compete Restrictions
-
- 1. Are you subject to a non-compete agreement that covers the
- development of software?
-
- [ ] Yes [ ] No
-
- 2. Would the restrictions of that non-compete agreement prevent
- you from working on any of the technology in or potentially
- in Apache Harmomy? If yes, please provide details.
-
- [ ] Yes [ ] No
-
- _____________________________________________________________________
- _____________________________________________________________________
- _____________________________________________________________________
-
- If so, you may be an Authorized Contributor for those areas
- only if the other party submits a written authorization acknowledging that
- your participation in the project is not in conflict with the
- non-compete agreement.
-
- 3. Please indicate either that you will not be an Authorized Contributor for
- those applicable components at Apache Harmony, or indicate how you will
- resolve the issue :
-
- _____________________________________________________________________
- _____________________________________________________________________
- _____________________________________________________________________
- _____________________________________________________________________
- _____________________________________________________________________
-
-Part VI : ICLA
-
- 1. Please execute a Individual Contributor License Agreement (ICLA).
-
- [ ] Yes, I have executed an ICLA
-
-Part VII : Employment Limitations
-
- 2. Are you employed as a programmer, systems analyst, or other
- IT professional?
-
- [ ] Yes [ ] No
-
- If so, we encourage you to have your employer either :
-
- a) sign a Corporate Contribution License Agreement with Apache
- and lists you as a designated employee or
-
- b) submits a written authorization for your participation in this
- project and disclaims any copyright or confidentiality interest
- in your current or future contributions to this project.
-
-
-
-
- Signature : ___________________________________________
-Print Name : ___________________________________________
- Date : ___________________________________________
-
-
-v1.0 20060622
+ The Apache Software Foundation
+ Apache Harmony Project
+ Authorized Contributor Questionnaire
+ v1.0
+
+
+Please Note : This document and your answers are considered public information,
+and shall be part of the Apache Harmony project public records.
+
+Part I : Identification
+
+ Please provide the following information
+
+ Name : ___________________________________________
+ E-mail : ___________________________________________
+
+ Mailing address :
+ ___________________________________________
+ ___________________________________________
+ ___________________________________________
+ ___________________________________________
+
+ Employer : ___________________________________________
+
+Part II: Access to Repositories
+
+ The Project is committed to producing an implementation of Java that
+ can be licensed freely under the Apache License. To do this,
+ we wish to know what, if any, previous exposure you have had
+ to the source for any of the parts of a Java implementation
+ including virtual machines, class libraries, tooling, etc.
+
+ The following activities are not considered "accessing the
+ source code" and would not generally disqualify you from
+ committing to the related repository here at Apache Harmony
+
+ a) Having a copy of src.jar (or equivalent) on a computer as long as you
+ never viewed or edited the contents of the file.
+
+ b) While running a debugger on a Java language program, having
+ had occasion to step into the source code for the implementation
+ as long as you did not attempt to understand or debug the
+ implementation code itself.
+
+ c) Having implemented "plug-ins" or other component software which
+ interact with an implementation, but doing so only with reference
+ to the published service provider interfaces.
+
+ d) Have written or executed test cases that probed the behavior
+ of an implementation as long as you did so with reference
+ only to published specifications and interfaces.
+
+ The following is a list of the components of the project each
+ labeled with an ID (ex. JVM-1):
+
+ VM
+ --
+ VM-1 VM core (including JVMPI, JVMDI, JDWP, JVMTI, JNI,
+ JIT, Memory Management/GC, OS Portabillity,
+ Threading, etc)
+ VM-X other ____________________________________________
+
+
+ Classlibrary
+ ------------
+ CL-1 Applet (java.applet)
+ CL-2 Archive (java.util.zip, java.util.jar)
+ CL-3 Beans (java.beans)
+ CL-4 Core (incl. lang, util, net, io, annotation, concurrent,
+ NIO-channels, NIO-charset, text, javax.net
+ where not covered elsewhere in list)
+ CL-5 Image IO (javax.imageio)
+ CL-6 Instrument (java.lang.instrument)
+ CL-7 JMX (javax.management)
+ CL-8 Lang-management (java.lang.management)
+ CL-9 Logging (java.util.logging)
+ CL-10 Math (java.math)
+ CL-11 ORB (javax.activity, javax.rmi.*, javax.transaction.*, org.omg.*)
+ CL-12 Prefs (java.util.prefs)
+ CL-13 Print (javax.print.*)
+ CL-14 Regex (java.util.regex)
+ CL-15 RMI (java.rmi.*)
+ CL-16 Security (java.security.*, javax.security.*, org.ietf.jgss,
+ javax.crypto)
+ CL-17 Sound (javax.sound)
+ CL-18 SQL (java.sql, javax.sql.*)
+ CL-19 Swing / AWT (java.awt.*, javax.swing.*, javax.accessibility)
+ CL-20 XML (javax.xml.*, org.w3c.*, org.xml.*)
+ CL-21 JNDI (javax.naming.*)
+ CL-X other ____________________________________________
+
+ Tools & Misc
+ ------------
+ T-1 launcher (e.g. java.exe)
+ T-2 javah
+ T-3 javap
+ T-4 javac
+ T-5 jdb
+ T-6 javadoc
+ T-7 jar
+ T-8 browser plugins
+ T-X other ____________________________________________
+
+
+Part III : General Exposure
+
+ With the above activities a)-d) in mind, have you done any of the following
+ to an implementation of one or more of the components listed above. If the
+ question doesn't apply to you, please write "N/A". If it does, please list
+ the components by the above-listed IDs, and provide details :
+
+ 1. Read some or all the source code for an implementation?
+
+ [ ] Yes [ ] No
+
+ Components : ________________________________________________________
+ Details : ___________________________________________________________
+ _____________________________________________________________________
+
+ 2. Fixed defects or performed other maintenance activity on an
+ implementation?
+
+ [ ] Yes [ ] No
+
+ Components : ________________________________________________________
+ Details : ___________________________________________________________
+ _____________________________________________________________________
+
+
+ 3. Enhanced the source code for an implementation with additional function,
+ performance or other qualities of service?
+
+ [ ] Yes [ ] No
+
+ Components : ________________________________________________________
+ Details : ___________________________________________________________
+ _____________________________________________________________________
+
+
+ 4. Ported an implementation to a different operating system or hardware
+ platform?
+
+ [ ] Yes [ ] No
+
+ Components : ________________________________________________________
+ Details : ___________________________________________________________
+ _____________________________________________________________________
+
+ 5. Reverse compiled or otherwise reverse engineered an implementation?
+
+ [ ] Yes [ ] No
+
+ Components : ________________________________________________________
+ Details : ___________________________________________________________
+ _____________________________________________________________________
+
+
+ If you have answered yes to any question above, and that implementation is
+ not available under a recognized Open Source license, you may not be an
+ contributor to the related component of Apache Harmony unless the
+ copyright owner of that implementation either:
+
+ a) submits the implementation to this project under the Software Grant or
+ the Corporate Contribution License Agreement (the CCLA);
+
+ b) if the copyright owner is your current employer, signs a CCLA and
+ lists you as a designated employee; or
+
+ c) if the copyright owner is not your current employer, submits
+ a written authorization disclaiming any copyright or confidentiality
+ interest in your current or future contributions to this project.
+
+ 6. For each of the components listed above, please indicate either that you
+ will not be an Authorized Contributor for those components at Apache
+ Harmony, or indicate how you will resolve the issue of previous
+ exposure :
+
+ _____________________________________________________________________
+ _____________________________________________________________________
+ _____________________________________________________________________
+ _____________________________________________________________________
+ _____________________________________________________________________
+ _____________________________________________________________________
+ _____________________________________________________________________
+ _____________________________________________________________________
+ _____________________________________________________________________
+ _____________________________________________________________________
+ _____________________________________________________________________
+ _____________________________________________________________________
+ _____________________________________________________________________
+
+
+Part IV : Confidential Exposure
+
+ 1. Have you had access to any information regarding a proprietary
+ implementation of a component that could be considered
+ confidential?
+
+ [ ] Yes [ ] No
+
+ If so, you may be a Authorized Contributor for that component only
+ if the owner of that potential confidential information submits
+ a written authorization disclaiming any confidentiality interest
+ in your current or future contributions to this project.
+
+ 2. For each of the components listed above for which you have had access
+ to such information, please indicate either that you will not
+ be an Authorized Contributor for those components at Apache Harmony, or
+ indicate how you will resolve the issue :
+
+ _____________________________________________________________________
+ _____________________________________________________________________
+ _____________________________________________________________________
+ _____________________________________________________________________
+ _____________________________________________________________________
+ _____________________________________________________________________
+ _____________________________________________________________________
+ _____________________________________________________________________
+ _____________________________________________________________________
+ _____________________________________________________________________
+ _____________________________________________________________________
+ _____________________________________________________________________
+ _____________________________________________________________________
+
+
+Part V : Non-Compete Restrictions
+
+ 1. Are you subject to a non-compete agreement that covers the
+ development of software?
+
+ [ ] Yes [ ] No
+
+ 2. Would the restrictions of that non-compete agreement prevent
+ you from working on any of the technology in or potentially
+ in Apache Harmomy? If yes, please provide details.
+
+ [ ] Yes [ ] No
+
+ _____________________________________________________________________
+ _____________________________________________________________________
+ _____________________________________________________________________
+
+ If so, you may be an Authorized Contributor for those areas
+ only if the other party submits a written authorization acknowledging that
+ your participation in the project is not in conflict with the
+ non-compete agreement.
+
+ 3. Please indicate either that you will not be an Authorized Contributor for
+ those applicable components at Apache Harmony, or indicate how you will
+ resolve the issue :
+
+ _____________________________________________________________________
+ _____________________________________________________________________
+ _____________________________________________________________________
+ _____________________________________________________________________
+ _____________________________________________________________________
+
+Part VI : ICLA
+
+ 1. Please execute a Individual Contributor License Agreement (ICLA).
+
+ [ ] Yes, I have executed an ICLA
+
+Part VII : Employment Limitations
+
+ 2. Are you employed as a programmer, systems analyst, or other
+ IT professional?
+
+ [ ] Yes [ ] No
+
+ If so, we encourage you to have your employer either :
+
+ a) sign a Corporate Contribution License Agreement with Apache
+ and lists you as a designated employee or
+
+ b) submits a written authorization for your participation in this
+ project and disclaims any copyright or confidentiality interest
+ in your current or future contributions to this project.
+
+
+
+
+ Signature : ___________________________________________
+Print Name : ___________________________________________
+ Date : ___________________________________________
+
+
+v1.0 20060622
Modified: harmony/standard/site/xdocs/bulk_contribution_checklist.txt
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/bulk_contribution_checklist.txt?view=diff&rev=517663&r1=517662&r2=517663
==============================================================================
--- harmony/standard/site/xdocs/bulk_contribution_checklist.txt (original)
+++ harmony/standard/site/xdocs/bulk_contribution_checklist.txt Tue Mar 13 05:17:43 2007
@@ -1,144 +1,144 @@
- The Apache Software Foundation
- Apache Harmony Project
- Bulk Contribution Checklist
- v 1.1 20051114
-
-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 ask the following questions of all contributions
-of software that has been created outside of the project. Our goal is
-to provide clear and consistent oversight of the project codebase, as
-well as encourage our contributors to carefully examine their
-contributions before bringing to the project.
-
-Please Note : This document and your answers are considered public
-information, and shall be part of the Apache Harmony project public
-records.
-
-
-Part I : Identification
-
- Please provide the following information
-
- Name : ___________________________________________
- E-mail : ___________________________________________
-
- Mailing address :
- ___________________________________________
- ___________________________________________
- ___________________________________________
- ___________________________________________
-
- Employer : ___________________________________________
-
-
-Part II : Description
-
- Please describe the contribution :
-
-
-
-
-
-Part III : Statement of Origination
-
-a) Have you personally written all of the code or other material
- that you are intending to contribute to this project, and if so,
- are you an Authorized Contributor for all parts of the contribution?
-
- [ ] Yes
- [ ] No
-
- If "yes", you're done with Part III, skip to Part IV
- If "no" please continue with the rest of Part III
-
-b) Have you verified the development history of the code to
- identify ALL of the authors?
-
- Please list the other authors:
-
-
-c) Do you have a written agreement with all of the authors that
- either gives you ownership of the material or otherwise provides
- you sufficient rights to submit this material to the project
- on their behalf.
-
- Please provide the details of this agreement:
-
-
-d) Are all of the authors Authorized Contributors for the part of
- the contribution written/created by each author?
-
- [ ] Yes Ð if "yes", you're done with Part III, skip to Part IV.
- [ ] No Ð if "no", please continue with the rest of part III
-
-
-e) Was the code written prior to May 2005 (when the Harmony Project
- was initiated)?
-
- [ ] Yes
- [ ] No
-
- (i) If No, you must provide Authorized Contributor Questionnaires
- for the authors of the code created after May 2005 such that
- those authors are classified as Authorized Contributors for
- the portions of the contribution written by them
- after May 2005.
-
-f) Did any of the authors of the code have access to third
- party implementations of similar technology while developing the
- contribution?
-
- [ ] Yes
- [ ] No
-
- If "yes", please give details below :
-
-
-
-
-g) Was the code developed in accordance with a development
- process which was designed to prevent unauthorized inclusion
- of third party intellectual property rights into the code?
- (e.g., does the process require that developers not have
- concurrent access to third party implementations of similar
- technology during development?)
-
- [ ] Yes
- [ ] No
-
- If "no", the code isn't eligible for the Harmony Project.
-
- If "yes", please provide short description of the process,
- focusing on protections related to third party intellectual
- property :
-
-
-
-
-Note : The Apache Harmony project generally performs additional
-scans of it's codebase, including bulk contributions, to help
-confirm code pedigree. Prior to submitting any contribution,
-we strongly encourage you to verify that the contribution is
-acceptable. Please see http://harmony.apache.org/code_scan_tools.html
-for more information.
-
-
-
-
-Part IV : Checklist
-
- [ ] Contribution is licensed under the Apache License v2.0
-
- [ ] Software Grant or Corporate Contributor License Agreement and Software
- Grant executed and submitted
-
-
- Signature : ___________________________________________
-Print Name : ___________________________________________
- Date : ___________________________________________
-
-
-
-v1.1 20051114
-
+ The Apache Software Foundation
+ Apache Harmony Project
+ Bulk Contribution Checklist
+ v 1.1 20051114
+
+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 ask the following questions of all contributions
+of software that has been created outside of the project. Our goal is
+to provide clear and consistent oversight of the project codebase, as
+well as encourage our contributors to carefully examine their
+contributions before bringing to the project.
+
+Please Note : This document and your answers are considered public
+information, and shall be part of the Apache Harmony project public
+records.
+
+
+Part I : Identification
+
+ Please provide the following information
+
+ Name : ___________________________________________
+ E-mail : ___________________________________________
+
+ Mailing address :
+ ___________________________________________
+ ___________________________________________
+ ___________________________________________
+ ___________________________________________
+
+ Employer : ___________________________________________
+
+
+Part II : Description
+
+ Please describe the contribution :
+
+
+
+
+
+Part III : Statement of Origination
+
+a) Have you personally written all of the code or other material
+ that you are intending to contribute to this project, and if so,
+ are you an Authorized Contributor for all parts of the contribution?
+
+ [ ] Yes
+ [ ] No
+
+ If "yes", you're done with Part III, skip to Part IV
+ If "no" please continue with the rest of Part III
+
+b) Have you verified the development history of the code to
+ identify ALL of the authors?
+
+ Please list the other authors:
+
+
+c) Do you have a written agreement with all of the authors that
+ either gives you ownership of the material or otherwise provides
+ you sufficient rights to submit this material to the project
+ on their behalf.
+
+ Please provide the details of this agreement:
+
+
+d) Are all of the authors Authorized Contributors for the part of
+ the contribution written/created by each author?
+
+ [ ] Yes Ð if "yes", you're done with Part III, skip to Part IV.
+ [ ] No Ð if "no", please continue with the rest of part III
+
+
+e) Was the code written prior to May 2005 (when the Harmony Project
+ was initiated)?
+
+ [ ] Yes
+ [ ] No
+
+ (i) If No, you must provide Authorized Contributor Questionnaires
+ for the authors of the code created after May 2005 such that
+ those authors are classified as Authorized Contributors for
+ the portions of the contribution written by them
+ after May 2005.
+
+f) Did any of the authors of the code have access to third
+ party implementations of similar technology while developing the
+ contribution?
+
+ [ ] Yes
+ [ ] No
+
+ If "yes", please give details below :
+
+
+
+
+g) Was the code developed in accordance with a development
+ process which was designed to prevent unauthorized inclusion
+ of third party intellectual property rights into the code?
+ (e.g., does the process require that developers not have
+ concurrent access to third party implementations of similar
+ technology during development?)
+
+ [ ] Yes
+ [ ] No
+
+ If "no", the code isn't eligible for the Harmony Project.
+
+ If "yes", please provide short description of the process,
+ focusing on protections related to third party intellectual
+ property :
+
+
+
+
+Note : The Apache Harmony project generally performs additional
+scans of it's codebase, including bulk contributions, to help
+confirm code pedigree. Prior to submitting any contribution,
+we strongly encourage you to verify that the contribution is
+acceptable. Please see http://harmony.apache.org/code_scan_tools.html
+for more information.
+
+
+
+
+Part IV : Checklist
+
+ [ ] Contribution is licensed under the Apache License v2.0
+
+ [ ] Software Grant or Corporate Contributor License Agreement and Software
+ Grant executed and submitted
+
+
+ Signature : ___________________________________________
+Print Name : ___________________________________________
+ Date : ___________________________________________
+
+
+
+v1.1 20051114
+
Modified: harmony/standard/site/xdocs/documentation/conventions.xml
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/documentation/conventions.xml?view=diff&rev=517663&r1=517662&r2=517663
==============================================================================
--- harmony/standard/site/xdocs/documentation/conventions.xml (original)
+++ harmony/standard/site/xdocs/documentation/conventions.xml Tue Mar 13 05:17:43 2007
@@ -1,109 +1,109 @@
-<?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.
--->
-
-<document>
-
- <properties>
- <title>Conventions</title>
- <author email="dev@harmony.apache.org">Harmony Documentation Team</author>
-
- </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>
- </body>
+<?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.
+-->
+
+<document>
+
+ <properties>
+ <title>Conventions</title>
+ <author email="dev@harmony.apache.org">Harmony Documentation Team</author>
+
+ </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>
+ </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=517663&r1=517662&r2=517663
==============================================================================
--- harmony/standard/site/xdocs/documentation/dev_eclipse.xml (original)
+++ harmony/standard/site/xdocs/documentation/dev_eclipse.xml Tue Mar 13 05:17:43 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> > <b>Preferences</b>:
- </li>
- <ul>
- <li>Change the Java compiler settings:
- <ol>
- <li>In the <b>Java</b> > <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> > <b>Compiler</b> > <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> > <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> > <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> > <b>Preferences</b> > <b>Ant</b> > <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 > 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> > <b>Preferences</b>:
+ </li>
+ <ul>
+ <li>Change the Java compiler settings:
+ <ol>
+ <li>In the <b>Java</b> > <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> > <b>Compiler</b> > <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> > <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> > <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> > <b>Preferences</b> > <b>Ant</b> > <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 > 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/documentation/dev_eclipse_movie.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/documentation/dev_eclipse_movie.html?view=diff&rev=517663&r1=517662&r2=517663
==============================================================================
--- harmony/standard/site/xdocs/documentation/dev_eclipse_movie.html (original)
+++ harmony/standard/site/xdocs/documentation/dev_eclipse_movie.html Tue Mar 13 05:17:43 2007
@@ -1,69 +1,69 @@
-<!--
-
- 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.
--->
-
-<html>
-<body>
- <!-- START lines taken from a generated page to ge the header logos -->
- <table border="0" width="100%" cellspacing="0">
- <!-- TOP IMAGE -->
- <tr>
- <td align='LEFT'>
- <table><tr><td>
- <td align="left">
-<a href="http://harmony.apache.org/"><img src="../../images/harmony-logo.png" alt="Apache Harmony" border="0"/></a>
-</td>
-</td>
- </td></tr></table>
- </td>
- <td align='RIGHT'>
- </td>
- </tr>
- </table>
- <!-- END lines taken from a generated page to ge the header logos -->
-
-<hr/>
-<p/>
-<center>
- <h2>Eclipse-based development : The Movie</h2>
-
- <object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000"
- width="994"
- height="755"
- codebase="http://active.macromedia.com/flash5/cabs/swflash.cab#version=5,0,0,0">
-
- <param name=movie value="../../images/eclipse_movie.swf">
- <param name=play value=true>
- <param name=loop value=false>
- <param name=quality value=low>
-
- <embed src="../../images/eclipse_movie.swf"
- width=994
- height=755
- quality=low
- loop=false
- type="application/x-shockwave-flash"
- pluginspage="http://www.macromedia.com/shockwave/download/index.cgi?P1_Prod_Version=ShockwaveFlash">
- </embed>
- </object>
-</center>
-<hr/>
-<p>
- After watching the movie return to <a href="dev_eclipse.html">the Eclipse-based development page</a>.
-</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.
+-->
+
+<html>
+<body>
+ <!-- START lines taken from a generated page to ge the header logos -->
+ <table border="0" width="100%" cellspacing="0">
+ <!-- TOP IMAGE -->
+ <tr>
+ <td align='LEFT'>
+ <table><tr><td>
+ <td align="left">
+<a href="http://harmony.apache.org/"><img src="../../images/harmony-logo.png" alt="Apache Harmony" border="0"/></a>
+</td>
+</td>
+ </td></tr></table>
+ </td>
+ <td align='RIGHT'>
+ </td>
+ </tr>
+ </table>
+ <!-- END lines taken from a generated page to ge the header logos -->
+
+<hr/>
+<p/>
+<center>
+ <h2>Eclipse-based development : The Movie</h2>
+
+ <object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000"
+ width="994"
+ height="755"
+ codebase="http://active.macromedia.com/flash5/cabs/swflash.cab#version=5,0,0,0">
+
+ <param name=movie value="../../images/eclipse_movie.swf">
+ <param name=play value=true>
+ <param name=loop value=false>
+ <param name=quality value=low>
+
+ <embed src="../../images/eclipse_movie.swf"
+ width=994
+ height=755
+ quality=low
+ loop=false
+ type="application/x-shockwave-flash"
+ pluginspage="http://www.macromedia.com/shockwave/download/index.cgi?P1_Prod_Version=ShockwaveFlash">
+ </embed>
+ </object>
+</center>
+<hr/>
+<p>
+ After watching the movie return to <a href="dev_eclipse.html">the Eclipse-based development page</a>.
+</p>
+</body>
+</html>
Modified: harmony/standard/site/xdocs/hdk.xml
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/hdk.xml?view=diff&rev=517663&r1=517662&r2=517663
==============================================================================
--- harmony/standard/site/xdocs/hdk.xml (original)
+++ harmony/standard/site/xdocs/hdk.xml Tue Mar 13 05:17:43 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>
-<hdkbase>
- |
- |---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><hdkbase>/build/make</code> - this directory contains include
- files used by native makefiles.
- </li>
-
- <li><code><hdkbase>/build/patternsets</code> - this directory contains
- patternsets describing jar content.
- </li>
-
- <li><code><hdkbase>/build/test</code> - this directory contains test
- support classes, bundled up into a jar file.
- </li>
-
- <li><code><hdkbase>/jdk/jre</code> - this directory contains the standard
- jre layout, including <code>bin</code> and <code>lib</code> directories.
- </li>
-
- <li><code><hdkbase>/jdk/include</code> - this directory contains the standard
- jdk header files. For example, jni.h is held here.
- </li>
-
- <li><code><hdkbase>/include</code> - this directory contains header files that
- are Harmony specific and are used across multiple classlib modules.
- </li>
-
- <li><code><hdkbase>/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>
+<hdkbase>
+ |
+ |---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><hdkbase>/build/make</code> - this directory contains include
+ files used by native makefiles.
+ </li>
+
+ <li><code><hdkbase>/build/patternsets</code> - this directory contains
+ patternsets describing jar content.
+ </li>
+
+ <li><code><hdkbase>/build/test</code> - this directory contains test
+ support classes, bundled up into a jar file.
+ </li>
+
+ <li><code><hdkbase>/jdk/jre</code> - this directory contains the standard
+ jre layout, including <code>bin</code> and <code>lib</code> directories.
+ </li>
+
+ <li><code><hdkbase>/jdk/include</code> - this directory contains the standard
+ jdk header files. For example, jni.h is held here.
+ </li>
+
+ <li><code><hdkbase>/include</code> - this directory contains header files that
+ are Harmony specific and are used across multiple classlib modules.
+ </li>
+
+ <li><code><hdkbase>/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>