This is an automated email from the ASF dual-hosted git repository.
aharui pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/royale-typedefs.git
The following commit(s) were added to refs/heads/develop by this push:
new 6cd54e3 prepare for packaging all 3 repos into one source package
6cd54e3 is described below
commit 6cd54e3d84aab66c52aeb13fb85244f1bb173cd3
Author: Alex Harui <[email protected]>
AuthorDate: Fri Dec 8 10:50:34 2017 -0800
prepare for packaging all 3 repos into one source package
---
LICENSE | 222 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
NOTICE | 5 ++
README | 137 ++++++++++++++++++++++++++++++++++++
RELEASE_NOTES | 24 +++++++
4 files changed, 388 insertions(+)
diff --git a/LICENSE b/LICENSE
new file mode 100644
index 0000000..e7789c2
--- /dev/null
+++ b/LICENSE
@@ -0,0 +1,222 @@
+
+ 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 ROYALE COMPILER SUBCOMPONENTS:
+
+The Apache Royale Compiler includes a number of subcomponents with
+separate copyright notices and license terms. Your use of the source
+code for the these subcomponents is subject to the terms and
+conditions of the following licenses.
+
+The Google Closure Library Externs For Common Libraries are available
+under Apache License 2.0. For details see the js folder.
+
+The .as files in GCL/src are derived from the .js files in the
+Google Closure Library which are available under Apache License 2.0.
+
+The createjs.js file in createjs/src/main/javascript is
+a non-copyrightable subset of EaselJS and TweenJS from
+https://github.com/CreateJS
+
diff --git a/NOTICE b/NOTICE
new file mode 100644
index 0000000..40c36eb
--- /dev/null
+++ b/NOTICE
@@ -0,0 +1,5 @@
+Apache Royale Typedefs
+Copyright 2012-2017 The Apache Software Foundation
+
+This product includes software developed at
+The Apache Software Foundation (http://www.apache.org/).
diff --git a/README b/README
new file mode 100644
index 0000000..b5d739c
--- /dev/null
+++ b/README
@@ -0,0 +1,137 @@
+Apache Royale Typedefs
+====================
+
+ These Apache Royale Typedefs are libraries that contain ActionScript class
+ definitions for popular JavaScript Libraries like Google Closure, JQuery
+ and more.
+
+ Many of these libraries are created by starting with what the Google
Closure
+ Compiler refers to as "externs" but are also referred to as "typedefs".
These
+ are custom JavaScript files that don't contain runnable code and instead
contain
+ "JSDOc" and function and variable declarations for an API of a JavaScript
library.
+
+ The Royale Compiler has a compiler called EXTERNC that compiles these
externs
+ into ActionScript, then the Royale Compiler's COMPC compiler turns that
into
+ ActionScript Libraries (SWCs).
+
+Getting the latest sources via git
+==================================
+
+ Getting the source code is the recommended way to get the Apache Royale
Typedefs.
+ The typedefs can also be installed by installing an Apache Royale SDK via
NPM
+ or by unpacking Apache Royale binary distributions available from link on
our
+ website at http://royale.apache.org/.
+
+ You can always checkout the latest source via git using the following
+ command:
+
+ git clone https://github.com/apache/royale-typedefs.git royale-typedefs
+ cd royale-typedefs
+ git checkout develop
+
+Building the Apache Royale Typedefs
+=================================
+
+ The Apache Royale Typedefs require the Apache Royale Compiler.
+
+ You can build the Apache Royale Typedefs with Apache Maven or Apache Ant.
+
+Building the Apache Royale Typedefs with Apache Maven
+-----------------------------------------------------
+
+ Before building the Apache Royale Typedefs with Apache Maven you must
install
+ the following software.
+
+
==================================================================================
+ SOFTWARE
+
==================================================================================
+
+ Java SDK 1.7 or greater (*1)
+
+ Maven 3.3.9 or greater (*1)
+
+
==================================================================================
+
+ *1) The bin directories for Maven and Java should be added to your
+ PATH.
+
+ Then run
+
+ mvn clean install
+
+Building the Apache Royale Typedefs with Ant
+----------------------------------------------
+
+ Before building the Apache Royale Typedefs with Apache Ant you must
install
+ the following software and set the corresponding environment variables
using
+ absolute file paths. Relative file paths will result in build errors.
+
+
==================================================================================
+ SOFTWARE ENVIRONMENT VARIABLE
(absolute paths)
+
==================================================================================
+
+ Java SDK 1.7 or greater (*1) JAVA_HOME
+ (for Java 1.7 see note at (*2))
+
+ Ant 1.7.1 or greater (*1) ANT_HOME
+ (for Java 1.7 see note at (*2))
+
+
==================================================================================
+
+ *1) The bin directories for ANT_HOME and JAVA_HOME should be added to your
+ PATH.
+
+ On Windows, set PATH to
+
+ PATH=%PATH%;%ANT_HOME%\bin;%JAVA_HOME%\bin
+
+ On the Mac (bash), set PATH to
+
+ export PATH="$PATH:$ANT_HOME/bin:$JAVA_HOME/bin"
+
+ On Linux make sure you path include ANT_HOME and JAVA_HOME.
+
+ *2) If you are using Java SDK 1.7 or greater on a Mac you must use Ant 1.8
+ or greater. If you use Java 1.7 with Ant 1.7, ant reports the java
+ version as 1.6 so the JVM args for the data model (-d32/-d64) will not
+ be set correctly and you will get compile errors.
+
+ Once you've done that, use
+
+ ant main (or just ant since the default target is main)
+
+ to download the third-party dependencies and build the source and run
+ some tests. Since the third-party dependencies take a little while to
+ download and they don't change very often, they are not cleaned with
+ the regular clean target.
+
+ To clean the build of everything other than the downloaded third-party
+ dependencies use
+
+ ant clean
+
+ To clean the build, of everything, including the downloaded third-party
+ dependencies use
+
+ ant wipe (which is just thirdparty-clean followed by clean)
+
+ To get a brief listing of all the targets type
+
+ ant -projecthelp
+
+
+Using the Apache Royale Typedefs
+=================================
+
+Because the typedef libraries only contain classes, interfaces, constants,
top-level
+variables and functions, and don't contain runnable code, they must be placed
on the
+external-library-path when compiling a Royale application.
+
+The typedefs libraries are packaged into a Royale SDK and are set on the
+external-librar-path by various config.xml files in a Royale SDK.
+
+
+Thanks for using Apache Royale. Enjoy!
+
+ The Apache Royale Project
+ <http://royale.apache.org>
diff --git a/RELEASE_NOTES b/RELEASE_NOTES
new file mode 100644
index 0000000..e4fa32e
--- /dev/null
+++ b/RELEASE_NOTES
@@ -0,0 +1,24 @@
+Apache Royale Typedefs 0.9.0
+============================
+
+Apache Royale Typedefs 0.9.0 is the first release of libraries that contain
+ActionScript class definitions for popular JavaScript Libraries like Google
Closure,
+JQuery and more.
+
+The typedefs were previously released by the Apache Flex project as part of the
+Apache FlexJS Compiler. You can see RELEASE_NOTES for earlier releases in the
A
+pache Flex releases.
+
+Known Issues
+_____________
+
+No known issues at this time.
+
+
+
+Please report new issues to our bugbase at:
+
+ https://github.com/apache/royale-asjs/issues
+
+ The Apache Royale Project
+ <http://royale.apache.org/>
--
To stop receiving notification emails like this one, please contact
['"[email protected]" <[email protected]>'].
