harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ndbe...@apache.org
Subject svn commit: r446344 [1/2] - in /incubator/harmony/enhanced/classlib/trunk: COPYRIGHT LICENSE NOTICE README.txt RUNNING-TESTS.txt THIRD_PARTY_NOTICES.txt build.xml
Date Fri, 15 Sep 2006 01:57:02 GMT
Author: ndbeyer
Date: Thu Sep 14 18:57:01 2006
New Revision: 446344

URL: http://svn.apache.org/viewvc?view=rev&rev=446344
Log:
Set eol-style = native for root files.

Modified:
    incubator/harmony/enhanced/classlib/trunk/COPYRIGHT   (contents, props changed)
    incubator/harmony/enhanced/classlib/trunk/LICENSE   (contents, props changed)
    incubator/harmony/enhanced/classlib/trunk/NOTICE   (contents, props changed)
    incubator/harmony/enhanced/classlib/trunk/README.txt   (contents, props changed)
    incubator/harmony/enhanced/classlib/trunk/RUNNING-TESTS.txt   (contents, props changed)
    incubator/harmony/enhanced/classlib/trunk/THIRD_PARTY_NOTICES.txt   (contents, props changed)
    incubator/harmony/enhanced/classlib/trunk/build.xml   (contents, props changed)

Modified: incubator/harmony/enhanced/classlib/trunk/COPYRIGHT
URL: http://svn.apache.org/viewvc/incubator/harmony/enhanced/classlib/trunk/COPYRIGHT?view=diff&rev=446344&r1=446343&r2=446344
==============================================================================
--- incubator/harmony/enhanced/classlib/trunk/COPYRIGHT (original)
+++ incubator/harmony/enhanced/classlib/trunk/COPYRIGHT Thu Sep 14 18:57:01 2006
@@ -1,5 +1,5 @@
-    The following copyright notice(s) were affixed to portions of the
-    code with which this file is now or was at one time distributed and
-    are placed here unaltered.
-
-         (C) Copyright 2005 Intel Corporation
+    The following copyright notice(s) were affixed to portions of the
+    code with which this file is now or was at one time distributed and
+    are placed here unaltered.
+
+         (C) Copyright 2005 Intel Corporation

Propchange: incubator/harmony/enhanced/classlib/trunk/COPYRIGHT
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: incubator/harmony/enhanced/classlib/trunk/LICENSE
URL: http://svn.apache.org/viewvc/incubator/harmony/enhanced/classlib/trunk/LICENSE?view=diff&rev=446344&r1=446343&r2=446344
==============================================================================
--- incubator/harmony/enhanced/classlib/trunk/LICENSE (original)
+++ incubator/harmony/enhanced/classlib/trunk/LICENSE Thu Sep 14 18:57:01 2006
@@ -1,203 +1,203 @@
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-   1. Definitions.
-
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-
-   END OF TERMS AND CONDITIONS
-
-   APPENDIX: How to apply the Apache License to your work.
-
-      To apply the Apache License to your work, attach the following
-      boilerplate notice, with the fields enclosed by brackets "[]"
-      replaced with your own identifying information. (Don't include
-      the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format. We also recommend that a
-      file or class name and description of purpose be included on the
-      same "printed page" as the copyright notice for easier
-      identification within third-party archives.
-
-   Copyright [yyyy] [name of copyright owner]
-
-   Licensed 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.
-
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed 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.
+
    

Propchange: incubator/harmony/enhanced/classlib/trunk/LICENSE
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: incubator/harmony/enhanced/classlib/trunk/NOTICE
URL: http://svn.apache.org/viewvc/incubator/harmony/enhanced/classlib/trunk/NOTICE?view=diff&rev=446344&r1=446343&r2=446344
==============================================================================
--- incubator/harmony/enhanced/classlib/trunk/NOTICE (original)
+++ incubator/harmony/enhanced/classlib/trunk/NOTICE Thu Sep 14 18:57:01 2006
@@ -1,46 +1,46 @@
-   =========================================================================
-   ==  NOTICE file corresponding to the section 4 d of                    ==
-   ==  the Apache License, Version 2.0,                                   ==
-   ==  in this case for the Apache Harmony distribution.                  ==
-   =========================================================================
-
-This product includes software developed by The Apache Software
-Foundation (http://www.apache.org/).
-
-Portions of Harmony were originally developed by
-Intel Corporation and are licensed to the Apache Software
-Foundation under the "Software Grant and Corporate Contribution
-License Agreement", informally known as the "Intel Harmony CLA".
-
-Portions of Apache Harmony Classlib reference RFC 3280 - "Internet X.509 Public
-Key Infrastructure, Certificate and Certificate Revocation List (CRL) Profile".
-Portions of RFC 3280 are included in Harmony Javadoc for reference, and in
-accordance with the licenssing terms for RFC3280, the license is included here :
-
-   Copyright (C) The Internet Society (2002).  All Rights Reserved.
-
-   This document and translations of it may be copied and furnished to
-   others, and derivative works that comment on or otherwise explain it
-   or assist in its implementation may be prepared, copied, published
-   and distributed, in whole or in part, without restriction of any
-   kind, provided that the above copyright notice and this paragraph are
-   included on all such copies and derivative works.  However, this
-   document itself may not be modified in any way, such as by removing
-   the copyright notice or references to the Internet Society or other
-   Internet organizations, except as needed for the purpose of
-   developing Internet standards in which case the procedures for
-   copyrights defined in the Internet Standards process must be
-   followed, or as required to translate it into languages other than
-   English.
-
-   The limited permissions granted above are perpetual and will not be
-   revoked by the Internet Society or its successors or assigns.
-
-   This document and the information contained herein is provided on an
-   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
-   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
-   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
-   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
-   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
-
-
+   =========================================================================
+   ==  NOTICE file corresponding to the section 4 d of                    ==
+   ==  the Apache License, Version 2.0,                                   ==
+   ==  in this case for the Apache Harmony distribution.                  ==
+   =========================================================================
+
+This product includes software developed by The Apache Software
+Foundation (http://www.apache.org/).
+
+Portions of Harmony were originally developed by
+Intel Corporation and are licensed to the Apache Software
+Foundation under the "Software Grant and Corporate Contribution
+License Agreement", informally known as the "Intel Harmony CLA".
+
+Portions of Apache Harmony Classlib reference RFC 3280 - "Internet X.509 Public
+Key Infrastructure, Certificate and Certificate Revocation List (CRL) Profile".
+Portions of RFC 3280 are included in Harmony Javadoc for reference, and in
+accordance with the licenssing terms for RFC3280, the license is included here :
+
+   Copyright (C) The Internet Society (2002).  All Rights Reserved.
+
+   This document and translations of it may be copied and furnished to
+   others, and derivative works that comment on or otherwise explain it
+   or assist in its implementation may be prepared, copied, published
+   and distributed, in whole or in part, without restriction of any
+   kind, provided that the above copyright notice and this paragraph are
+   included on all such copies and derivative works.  However, this
+   document itself may not be modified in any way, such as by removing
+   the copyright notice or references to the Internet Society or other
+   Internet organizations, except as needed for the purpose of
+   developing Internet standards in which case the procedures for
+   copyrights defined in the Internet Standards process must be
+   followed, or as required to translate it into languages other than
+   English.
+
+   The limited permissions granted above are perpetual and will not be
+   revoked by the Internet Society or its successors or assigns.
+
+   This document and the information contained herein is provided on an
+   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
+   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
+   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
+   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
+   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
+
+

Propchange: incubator/harmony/enhanced/classlib/trunk/NOTICE
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: incubator/harmony/enhanced/classlib/trunk/README.txt
URL: http://svn.apache.org/viewvc/incubator/harmony/enhanced/classlib/trunk/README.txt?view=diff&rev=446344&r1=446343&r2=446344
==============================================================================
--- incubator/harmony/enhanced/classlib/trunk/README.txt (original)
+++ incubator/harmony/enhanced/classlib/trunk/README.txt Thu Sep 14 18:57:01 2006
@@ -1,274 +1,274 @@
-README
-======
-
-
-This directory contain the Apache Harmony class library code.
-
-Apache Harmony is an effort undergoing incubation at the Apache Software
-Foundation (ASF). Incubation is required of all newly accepted projects
-until a further review indicates that the infrastructure, communications,
-and decision making process have stabilized in a manner consistent with
-other successful ASF projects. While incubation status is not necessarily
-a reflection of the completeness or stability of the code, it does indicate
-that the project has yet to be fully endorsed by the ASF.
-
-
-Contents
---------
-After checking out the code onto disk at <EXTRACT_DIR> you should find the
-following directories under <EXTRACT_DIR> :
-
-*  make     - support for building the source code and packaging the results.
-
-*  depends  - support files (both text and binary) that are required to build
-              the class libraries and any native libraries required. Includes
-              several third party source files as detailed in the file
-              Harmony/depends/oss/README.txt.
-               
-*  doc      - configuration files and images that are required to generate
-              HTML documentation of the Java and C source using the Doxygen
-              documentation system. Pre-genenerated HTML is included. 
-               
-*  modules  - Java, C/C++, assembly source files that can be compiled into the
-              class library component files.
-
-*  support  - Java source files used to support test cases across various modules.
-
-
-Pre-requisites for Building
----------------------------
-In order to build the source code contained in the modules and support
-directories, it is necessary to configure the following tools in the user 
-environment. That is, the working environment should be such that the PATH 
-environment variable contains all of the directories where the executables of
-the tools listed below are located and that all of those executables can be 
-successfully invoked from the command line.
-
-
-* C compiler - on Windows, the Microsoft(R) 32-bit C/C++ Compiler and on
-               Linux, the GNU project C/C++ Compiler.
-
-* Java compiler - e.g. as delivered in a Java SDK. The compiler must be 
-                  capable of handling Java 1.5 source.
-                  See http://www.ibm.com/developerworks/java/jdk/index.html
-                  
-                  Although it cannot be invoked through an executable, it is 
-                  also possible to use the JDT compiler as delivered in a
-                  standard Eclipse download to accomplish the compiling of the 
-                  source under the modules directory. See the section on 
-                  "Modifying the Java Build Compiler" for more details. 
-                  
-* Apache Ant - the Java based build tool. See http://ant.apache.org
-
-* Doxygen - the open source documentation system for a variety of programming 
-            languages including C, C++ and Java.
-            See http://www.doxygen.org
-            
-
-The top-level Ant script <EXTRACT_DIR>/build.xml has a default target 
-which builds both the Java source and C source files. It is expected
-therefore that, at a minimum, a C compiler and a Java compiler be available.
-Doxygen is only necessary if generation of HTML documentation from the
-source code is to be carried out by invoking Ant with the "doc" target on
-the <EXTRACT_DIR>/build.xml script. As a convenience, pre-generated
-HTML files are already stored in subversion.
-
-
-
-Building
---------
-The simplest way to get started is to change directory into <EXTRACT_DIR> and
-then type "ant" to run Apache Ant against the default target of the build.xml
-file. Provided that the required compilers are available, Ant will proceed to
-compile all the class library source code .
-
-
-Building Java
--------------
-The class files output from the Java compilation will be assembled into a set
-of JAR files which reflect the components of the class libraries (see
-http://wiki.apache.org/harmony/ClassLibrary for more information). Together with
-the required support files, these JAR files will then be laid out in the boot
-directory of the following directory tree structure ...
-
-<EXTRACT_DIR>
-       |
-       \---deploy
-             |
-             \---jdk
-                  |
-                  \---jre
-                       |
-                       +---bin           <- classlibrary native code & launcher
-                       |   |
-                       |   +---default   <- VM-specific files for launcher's default VM
-                       |   +---vm1       <- VM-specific files for 'vm1'
-                       |   \---vm2       <- VM-specific files for 'vm2', and so on
-                       |
-                       \---lib
-                           |
-                           +---boot      <- common JARs for bootclasspath
-                           | 
-                           +---ext       <- extensions directory
-                           |
-                           \---security
-    
-
-
-Building Natives
-----------------
-Next, the source files contained under <EXTRACT_DIR>/modules will be
-built using the available C/C++/ASM compiler. The output from this stage will be the 
-creation of a launcher executable (java.exe on Windows, java on Linux) in the 
-bin directory of the above layout together with a number of shared libraries
-(with the .dll extension on Windows, and .so on Linux). 
-
-On Windows if the native build exits with the message :
-
-fatal error U1052: file 'ntwin32.mak' not found
-
-this is an indication that the required build environment has not been properly
-configured in the working console window. 
-
-
-
-Build Output
-------------
-The supplied source is built into a set of Java class libraries and the native 
-shared libraries necessary to support their correct functioning. In order to 
-be used to run a compiled Java application the built class libraries still
-require a virtual machine component. 
-
-
-
-Building Documentation
-----------------------
-Two sets of HTML files can be found under the <EXTRACT_DIR>/doc directory. 
-
-* kernel_doc - contains HTML documentation on the set of Java classes called the
-               "kernel classes". These are the set of classes which - under the
-               Harmony class library architecture - are closely tied to
-               the structure of the VM. 
-               Browse <EXTRACT_DIR>/doc/kernel_doc/html/index.html
-
-* vm_doc - contains HTML documentation concerned with how the Java class
-           libraries may be used on different VM implementations. This includes
-           an overview of the external dependencies of the class libraries 
-           and introduces a VM interface through which the class library natives
-           and VM can interoperate with one another.        
-           Browse <EXTRACT_DIR>/doc/vm_doc/html/index.html
-
-Running the "doc" target of the top-level Ant script
-<EXTRACT_DIR>/build.xml will refresh the contents of these directories.
-The target makes use of the doxygen tool and so expects the doxygen executable
-to be available in the current user environment (i.e the user PATH environment
-variable should contain an entry for <DOXYGEN_INSTALL_DIR>/bin ). 
-
-
-
-Modifying the Java Build Compiler
----------------------------------
-When compiling the Java source files the top-level Ant script calls another
-Ant script, <EXTRACT_DIR>/modules/build.xml. By opening up this Ant 
-file for editing and making a small change to the "build.compiler" property
-declared near the top of the file it is possible to specify any Java compiler of
-choice - provided it is capable of handling Java 1.5 source code. For example,
-to use the JDT compiler built into Eclipse this property should be changed to
-use the Eclipse compiler adapter ...
-
-<property name="build.compiler" value="org.eclipse.jdt.core.JDTCompilerAdapter" />
-
-So that Ant can actually locate this Eclipse compiler adapter during a build, 
-the location of the supporting JAR files in the Eclipse distribution need to be
-appended to the CLASSPATH environment variable. For an Eclipse 3.1 distribution
-this amounts to adding <ECLIPSE_INSTALL>/plugins/org.eclipse.jdt.core_3.1.0.jar
-together with the jdtCompilerAdapter.jar it contains. 
-
-Remember that the Java source files located under
-<EXTRACT_DIR>/modules are intended for consumption by a compiler that
-understands Java 1.5 source code.
-
-For further information on this topic please refer to the Eclipse batch compiler
-website, the Ant documentation for the "javac" task and to the Eclipse help system
-contents. 
-
-http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-core-home/howto/batch%20compile/batchCompile.html
-
-
-
-What's Next ?
--------------
-
-The class libraries do not provide the full JSE API. Instead the included source
-is only a subset of the Java 1.5 API.
-
-
-To test out the functionality of the built class library components a compatible
-VM needs to be obtained.  A compatible VM implements the Virtual Machine Interface
-as described in the documentation above.
-
-
-
-Troubleshooting & Known Problems
---------------------------------
-
-The java launcher has a bug which makes it sensitive to the JAVA_HOME
-environment setting. Until this bug is fixed users should be aware that When
-running Java applications with the built class library components on a
-compatible VM the JAVA_HOME variable should either be unset or else explicitly
-set to EXTRACT_DIR>/deploy/jdk/jre. Any other value risks crashing
-the launcher. 
-
-                                  ----------
-
-Linux users may need to install an appropriate libc compatibility patch to their
-operating system if they see the following error message when attempting to run
-a Java application with the built class library components on a compatible VM :
-
-<error: unable to load ICUInterface34 (libstdc++.so.5: cannot open shared object
-file: No such file or directory)>
-
-Where to obtain the required patch and the precise means of applying it will 
-obviously differ according to Linux distribution. On Debian the advanced package
-tool apt-get could be used as follows :
-
-user@server:~$> apt-get install libstdc++5
-
-On a Red Hat Enterprise Linux machine the rpm tool may be used to install the 
-equivalent package thus : 
-
-user@server:~$> rpm -Uvh compat-libstdc++-33-3.2.3-47.3.i386.rpm
-
-Consult the system administration documentation of your particular Linux
-distribution for more information.
-
-                                  ----------
-
-Linux users may need to update the value of their LD_LIBRARY_PATH environment 
-variable if they see the following error message when attempting to run a Java
-application with the built class library components on a compatible VM : 
-
-error while loading shared libraries: libhysig.so: cannot open shared 
-object file: No such file or directory
-
-On some systems this error can occur even when the shared library
-(e.g. <EXTRACT_DIR>/deploy/jdk/jre/bin/libhysig.so) has been built correctly
-and is present in the correct location. This is not a problem with the built
-shared library but instead is dependent on how the operating system locates and 
-loads dynamically linked libraries at runtime. Updating the LD_LIBRARY_PATH 
-environment variable to include the directory
-<EXTRACT_DIR>/deploy/jdk/jre/bin should solve this. An alternative remedy 
-would be to add new entries for each of the shared libraries built from the
-contributed native source code to the local /etc/ld.so.conf file and then 
-running the ldconfig program to rebuild the /etc/ld.so.cache. 
-
-                                  ----------
-
-Linux users may need to update their GNU Make (http://www.gnu.org/software/make/)
-to version 3.80 or later if they see the following error message when attempting
-to build native source:
-
-: No such file or directory
-make: *** [../libvmi.so] Error 1
-
-(The library name may be different)
+README
+======
+
+
+This directory contain the Apache Harmony class library code.
+
+Apache Harmony is an effort undergoing incubation at the Apache Software
+Foundation (ASF). Incubation is required of all newly accepted projects
+until a further review indicates that the infrastructure, communications,
+and decision making process have stabilized in a manner consistent with
+other successful ASF projects. While incubation status is not necessarily
+a reflection of the completeness or stability of the code, it does indicate
+that the project has yet to be fully endorsed by the ASF.
+
+
+Contents
+--------
+After checking out the code onto disk at <EXTRACT_DIR> you should find the
+following directories under <EXTRACT_DIR> :
+
+*  make     - support for building the source code and packaging the results.
+
+*  depends  - support files (both text and binary) that are required to build
+              the class libraries and any native libraries required. Includes
+              several third party source files as detailed in the file
+              Harmony/depends/oss/README.txt.
+               
+*  doc      - configuration files and images that are required to generate
+              HTML documentation of the Java and C source using the Doxygen
+              documentation system. Pre-genenerated HTML is included. 
+               
+*  modules  - Java, C/C++, assembly source files that can be compiled into the
+              class library component files.
+
+*  support  - Java source files used to support test cases across various modules.
+
+
+Pre-requisites for Building
+---------------------------
+In order to build the source code contained in the modules and support
+directories, it is necessary to configure the following tools in the user 
+environment. That is, the working environment should be such that the PATH 
+environment variable contains all of the directories where the executables of
+the tools listed below are located and that all of those executables can be 
+successfully invoked from the command line.
+
+
+* C compiler - on Windows, the Microsoft(R) 32-bit C/C++ Compiler and on
+               Linux, the GNU project C/C++ Compiler.
+
+* Java compiler - e.g. as delivered in a Java SDK. The compiler must be 
+                  capable of handling Java 1.5 source.
+                  See http://www.ibm.com/developerworks/java/jdk/index.html
+                  
+                  Although it cannot be invoked through an executable, it is 
+                  also possible to use the JDT compiler as delivered in a
+                  standard Eclipse download to accomplish the compiling of the 
+                  source under the modules directory. See the section on 
+                  "Modifying the Java Build Compiler" for more details. 
+                  
+* Apache Ant - the Java based build tool. See http://ant.apache.org
+
+* Doxygen - the open source documentation system for a variety of programming 
+            languages including C, C++ and Java.
+            See http://www.doxygen.org
+            
+
+The top-level Ant script <EXTRACT_DIR>/build.xml has a default target 
+which builds both the Java source and C source files. It is expected
+therefore that, at a minimum, a C compiler and a Java compiler be available.
+Doxygen is only necessary if generation of HTML documentation from the
+source code is to be carried out by invoking Ant with the "doc" target on
+the <EXTRACT_DIR>/build.xml script. As a convenience, pre-generated
+HTML files are already stored in subversion.
+
+
+
+Building
+--------
+The simplest way to get started is to change directory into <EXTRACT_DIR> and
+then type "ant" to run Apache Ant against the default target of the build.xml
+file. Provided that the required compilers are available, Ant will proceed to
+compile all the class library source code .
+
+
+Building Java
+-------------
+The class files output from the Java compilation will be assembled into a set
+of JAR files which reflect the components of the class libraries (see
+http://wiki.apache.org/harmony/ClassLibrary for more information). Together with
+the required support files, these JAR files will then be laid out in the boot
+directory of the following directory tree structure ...
+
+<EXTRACT_DIR>
+       |
+       \---deploy
+             |
+             \---jdk
+                  |
+                  \---jre
+                       |
+                       +---bin           <- classlibrary native code & launcher
+                       |   |
+                       |   +---default   <- VM-specific files for launcher's default VM
+                       |   +---vm1       <- VM-specific files for 'vm1'
+                       |   \---vm2       <- VM-specific files for 'vm2', and so on
+                       |
+                       \---lib
+                           |
+                           +---boot      <- common JARs for bootclasspath
+                           | 
+                           +---ext       <- extensions directory
+                           |
+                           \---security
+    
+
+
+Building Natives
+----------------
+Next, the source files contained under <EXTRACT_DIR>/modules will be
+built using the available C/C++/ASM compiler. The output from this stage will be the 
+creation of a launcher executable (java.exe on Windows, java on Linux) in the 
+bin directory of the above layout together with a number of shared libraries
+(with the .dll extension on Windows, and .so on Linux). 
+
+On Windows if the native build exits with the message :
+
+fatal error U1052: file 'ntwin32.mak' not found
+
+this is an indication that the required build environment has not been properly
+configured in the working console window. 
+
+
+
+Build Output
+------------
+The supplied source is built into a set of Java class libraries and the native 
+shared libraries necessary to support their correct functioning. In order to 
+be used to run a compiled Java application the built class libraries still
+require a virtual machine component. 
+
+
+
+Building Documentation
+----------------------
+Two sets of HTML files can be found under the <EXTRACT_DIR>/doc directory. 
+
+* kernel_doc - contains HTML documentation on the set of Java classes called the
+               "kernel classes". These are the set of classes which - under the
+               Harmony class library architecture - are closely tied to
+               the structure of the VM. 
+               Browse <EXTRACT_DIR>/doc/kernel_doc/html/index.html
+
+* vm_doc - contains HTML documentation concerned with how the Java class
+           libraries may be used on different VM implementations. This includes
+           an overview of the external dependencies of the class libraries 
+           and introduces a VM interface through which the class library natives
+           and VM can interoperate with one another.        
+           Browse <EXTRACT_DIR>/doc/vm_doc/html/index.html
+
+Running the "doc" target of the top-level Ant script
+<EXTRACT_DIR>/build.xml will refresh the contents of these directories.
+The target makes use of the doxygen tool and so expects the doxygen executable
+to be available in the current user environment (i.e the user PATH environment
+variable should contain an entry for <DOXYGEN_INSTALL_DIR>/bin ). 
+
+
+
+Modifying the Java Build Compiler
+---------------------------------
+When compiling the Java source files the top-level Ant script calls another
+Ant script, <EXTRACT_DIR>/modules/build.xml. By opening up this Ant 
+file for editing and making a small change to the "build.compiler" property
+declared near the top of the file it is possible to specify any Java compiler of
+choice - provided it is capable of handling Java 1.5 source code. For example,
+to use the JDT compiler built into Eclipse this property should be changed to
+use the Eclipse compiler adapter ...
+
+<property name="build.compiler" value="org.eclipse.jdt.core.JDTCompilerAdapter" />
+
+So that Ant can actually locate this Eclipse compiler adapter during a build, 
+the location of the supporting JAR files in the Eclipse distribution need to be
+appended to the CLASSPATH environment variable. For an Eclipse 3.1 distribution
+this amounts to adding <ECLIPSE_INSTALL>/plugins/org.eclipse.jdt.core_3.1.0.jar
+together with the jdtCompilerAdapter.jar it contains. 
+
+Remember that the Java source files located under
+<EXTRACT_DIR>/modules are intended for consumption by a compiler that
+understands Java 1.5 source code.
+
+For further information on this topic please refer to the Eclipse batch compiler
+website, the Ant documentation for the "javac" task and to the Eclipse help system
+contents. 
+
+http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-core-home/howto/batch%20compile/batchCompile.html
+
+
+
+What's Next ?
+-------------
+
+The class libraries do not provide the full JSE API. Instead the included source
+is only a subset of the Java 1.5 API.
+
+
+To test out the functionality of the built class library components a compatible
+VM needs to be obtained.  A compatible VM implements the Virtual Machine Interface
+as described in the documentation above.
+
+
+
+Troubleshooting & Known Problems
+--------------------------------
+
+The java launcher has a bug which makes it sensitive to the JAVA_HOME
+environment setting. Until this bug is fixed users should be aware that When
+running Java applications with the built class library components on a
+compatible VM the JAVA_HOME variable should either be unset or else explicitly
+set to EXTRACT_DIR>/deploy/jdk/jre. Any other value risks crashing
+the launcher. 
+
+                                  ----------
+
+Linux users may need to install an appropriate libc compatibility patch to their
+operating system if they see the following error message when attempting to run
+a Java application with the built class library components on a compatible VM :
+
+<error: unable to load ICUInterface34 (libstdc++.so.5: cannot open shared object
+file: No such file or directory)>
+
+Where to obtain the required patch and the precise means of applying it will 
+obviously differ according to Linux distribution. On Debian the advanced package
+tool apt-get could be used as follows :
+
+user@server:~$> apt-get install libstdc++5
+
+On a Red Hat Enterprise Linux machine the rpm tool may be used to install the 
+equivalent package thus : 
+
+user@server:~$> rpm -Uvh compat-libstdc++-33-3.2.3-47.3.i386.rpm
+
+Consult the system administration documentation of your particular Linux
+distribution for more information.
+
+                                  ----------
+
+Linux users may need to update the value of their LD_LIBRARY_PATH environment 
+variable if they see the following error message when attempting to run a Java
+application with the built class library components on a compatible VM : 
+
+error while loading shared libraries: libhysig.so: cannot open shared 
+object file: No such file or directory
+
+On some systems this error can occur even when the shared library
+(e.g. <EXTRACT_DIR>/deploy/jdk/jre/bin/libhysig.so) has been built correctly
+and is present in the correct location. This is not a problem with the built
+shared library but instead is dependent on how the operating system locates and 
+loads dynamically linked libraries at runtime. Updating the LD_LIBRARY_PATH 
+environment variable to include the directory
+<EXTRACT_DIR>/deploy/jdk/jre/bin should solve this. An alternative remedy 
+would be to add new entries for each of the shared libraries built from the
+contributed native source code to the local /etc/ld.so.conf file and then 
+running the ldconfig program to rebuild the /etc/ld.so.cache. 
+
+                                  ----------
+
+Linux users may need to update their GNU Make (http://www.gnu.org/software/make/)
+to version 3.80 or later if they see the following error message when attempting
+to build native source:
+
+: No such file or directory
+make: *** [../libvmi.so] Error 1
+
+(The library name may be different)

Propchange: incubator/harmony/enhanced/classlib/trunk/README.txt
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: incubator/harmony/enhanced/classlib/trunk/RUNNING-TESTS.txt
URL: http://svn.apache.org/viewvc/incubator/harmony/enhanced/classlib/trunk/RUNNING-TESTS.txt?view=diff&rev=446344&r1=446343&r2=446344
==============================================================================
--- incubator/harmony/enhanced/classlib/trunk/RUNNING-TESTS.txt (original)
+++ incubator/harmony/enhanced/classlib/trunk/RUNNING-TESTS.txt Thu Sep 14 18:57:01 2006
@@ -1,54 +1,54 @@
-How to Run The Tests
-====================
-
-This is a work in progress.
-
-The objective is to make it easy to run unit tests
-for any part of the classlibrary, and be able to also
-run all the tests and do easy reporting.
-
-Requirements : 
-
-1) JUnit.jar - any modern version. http://www.junit.org
-   
-   Put this on your ant/lib directory.
-   
-2) Ensure you have the build time dependencies installed, these
-   can be downloaded using the following command:
-
-   ant fetch-depends
-
-   Warning: Some of the dependencies are made available under
-            licences other than the ASLv2.
-  
-3) J9 VM from IBM (evaluation)
-    
-      http://www-128.ibm.com/developerworks/java/jdk/harmony/index.html
-      
-   Warning - this is not open source, and you must go through a minor 
-   registration process.
-   
-   This is IBM's VM that works with the Harmony class libraries.
-   We will use this until our own VM efforts come up to speed.
-   
-   Installation - drop into deploy/jdk/jre/bin/default
-   
-
- Once the prereqs are there : 
- 
- 1) Build the classlibrary : 
- 
-    $ ant
-    
-    This should build and install all java and native components
-    
- 2) Test : 
- 
-    
-    $ ant test
-    
-    and wait.  You can find a html report in
-    
-       build/test_report/html/index.html
-       
-   when it's finished.
+How to Run The Tests
+====================
+
+This is a work in progress.
+
+The objective is to make it easy to run unit tests
+for any part of the classlibrary, and be able to also
+run all the tests and do easy reporting.
+
+Requirements : 
+
+1) JUnit.jar - any modern version. http://www.junit.org
+   
+   Put this on your ant/lib directory.
+   
+2) Ensure you have the build time dependencies installed, these
+   can be downloaded using the following command:
+
+   ant fetch-depends
+
+   Warning: Some of the dependencies are made available under
+            licences other than the ASLv2.
+  
+3) J9 VM from IBM (evaluation)
+    
+      http://www-128.ibm.com/developerworks/java/jdk/harmony/index.html
+      
+   Warning - this is not open source, and you must go through a minor 
+   registration process.
+   
+   This is IBM's VM that works with the Harmony class libraries.
+   We will use this until our own VM efforts come up to speed.
+   
+   Installation - drop into deploy/jdk/jre/bin/default
+   
+
+ Once the prereqs are there : 
+ 
+ 1) Build the classlibrary : 
+ 
+    $ ant
+    
+    This should build and install all java and native components
+    
+ 2) Test : 
+ 
+    
+    $ ant test
+    
+    and wait.  You can find a html report in
+    
+       build/test_report/html/index.html
+       
+   when it's finished.

Propchange: incubator/harmony/enhanced/classlib/trunk/RUNNING-TESTS.txt
------------------------------------------------------------------------------
    svn:eol-style = native



Mime
View raw message