royale-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aha...@apache.org
Subject [royale-asjs] 01/06: initial attempt at packaging all 3 repos
Date Sat, 09 Dec 2017 00:08:20 GMT
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-asjs.git

commit 0c486b2cc374c0745800dcc04999669a1861fca9
Author: Alex Harui <aharui@apache.org>
AuthorDate: Fri Dec 8 00:19:46 2017 -0800

    initial attempt at packaging all 3 repos
---
 .gitignore               |   1 +
 build.xml                | 109 +++++++++++++++---------
 releasemgr/LICENSE       | 215 +++++++++++++++++++++++++++++++++++++++++++++++
 releasemgr/NOTICE        |  10 +++
 releasemgr/README        | 191 +++++++++++++++++++++++++++++++++++++++++
 releasemgr/RELEASE_NOTES |  20 +++++
 6 files changed, 505 insertions(+), 41 deletions(-)

diff --git a/.gitignore b/.gitignore
index a32c5ce..c40e0f5 100644
--- a/.gitignore
+++ b/.gitignore
@@ -108,6 +108,7 @@ obj/
 [Dd]ebug/
 [Rr]elease*/
 Ankh.NoLoad
+!releasemgr
 
 #Tooling
 _ReSharper*/
diff --git a/build.xml b/build.xml
index 08f1c45..714aca0 100644
--- a/build.xml
+++ b/build.xml
@@ -51,7 +51,8 @@
     <property name="kit.prefix" value="apache-royale-${release.version}"/>
     <property name="source.kit" value="${kit.prefix}-src"/>
     <property name="binary.kit" value="${kit.prefix}-bin"/>
-      
+    <property name="staging-dir" value="${basedir}/temp/royale-asjs" />
+    
     <condition property="isMac" value="mac">
         <os family="mac" />
     </condition>
@@ -148,7 +149,7 @@
     </target>
     
     <target name="release"
-        depends="block-flat-fonts,check-compile-env,check-runtime-env,check-compiler-home,source-release,binary-release,rat-check"
+        depends="block-flat-fonts,source-release,binary-release,rat-check"
         description="Creates source and binary kits for Apache Royale."/>
         
     <target name="release-jenkins" 
@@ -160,7 +161,7 @@
         description="Packages the source release kit which is the official Apache release."/>
         
     <target name="binary-release" 
-        depends="setup-binary-release,main,sample-themes,checkintests,check-goog-home,binary-package"
+        depends="setup-binary-release,set.base.folder,build-all,main,sample-themes,checkintests,check-goog-home,binary-package"
         description="Builds and packages the binary kit which is provided as a convenience."/>
   
 
     <target name="binary-release-jenkins" 
@@ -455,6 +456,8 @@
         
         <!-- generate localized compiler message jars -->
 	    <property name="localized.jars" value="true" />
+        
+        <property name="release.target" value="true" />
     </target>
     
     <!--
@@ -681,16 +684,37 @@
         
         FixMe: clean needs to clean - add code to detect unversioned files
     -->
-    <target name="source-package" depends="stage-source,source-package-zip,source-package-tgz"
+    <target name="source-package" depends="stage-source,stage-compiler,stage-typedefs,stage-top-level,source-package-zip,source-package-tgz"
         description="Package source files required to build in zip and tar-gzip file">
     </target>
 
-    <!-- 
+    <target name="stage-compiler" >
+        <ant dir="${basedir}/../royale-compiler" target="wipe-all" />
+        <ant dir="${basedir}/../royale-compiler" target="stage-all" >
+            <property name="staging-dir" value="${basedir}/temp/royale-compiler" />
+        </ant>
+    </target>
+    
+    <target name="stage-typedefs" >
+        <ant dir="${basedir}/../royale-typedefs" target="wipe" />
+        <mkdir dir="${staging-dir}/../royale-typedefs"/>
+        <copy todir="${staging-dir}/../royale-typedefs" includeEmptyDirs="false" >
+            <fileset dir="${basedir}/../royale-typedefs" includes="**" />
+        </copy>
+    </target>
+    
+    <target name="stage-top-level" >
+        <copy todir="${basedir}/temp" includeEmptyDirs="false">
+            <fileset dir="${basedir}/releasemgr" includes="**" />
+        </copy>
+    </target>
+    
+    <!--
         Packages the source distribution with ZIP.
     -->
     <target name="source-package-zip" unless="no.zip">
         <mkdir dir="${basedir}/out"/>
-        <zip destfile="${basedir}/out/${source.kit}.zip" basedir="${basedir}/temp"/>
+        <zip destfile="${basedir}/out/${source.kit}.zip" basedir="${staging-dir}"/>
     </target>
 
     <!-- 
@@ -704,9 +728,9 @@
         description="Package source files required to build in zip file" >
         <antcall target="clean-temp"/>
         <sleep seconds="3" />
-        <mkdir dir="${basedir}/temp"/>
+        <mkdir dir="${staging-dir}"/>
        
-        <copy todir="${basedir}/temp" includeEmptyDirs="true">
+        <copy todir="${staging-dir}" includeEmptyDirs="true">
             <fileset dir="${basedir}">
                 <include name="**"/>
                 <exclude name="local.properties"/>
@@ -747,35 +771,35 @@
         
         <!-- now that config xml files are in temp, fix them up for release. -->
         <echo message="Updating config file air-config.xml with version ${build.version}"/>
-        <fix-config-file file="${basedir}/temp/frameworks/air-config-template.xml" version="${build.version}"
/>
+        <fix-config-file file="${staging-dir}/frameworks/air-config-template.xml" version="${build.version}"
/>
         <echo message="Updating config file royale-config.xml with version ${build.version}"/>
-        <fix-config-file file="${basedir}/temp/frameworks/royale-config-template.xml"
version="${build.version}" />
+        <fix-config-file file="${staging-dir}/frameworks/royale-config-template.xml" version="${build.version}"
/>
         <echo message="Updating config file js-config.xml with version ${build.version}"/>
-        <fix-config-file file="${basedir}/temp/frameworks/js-config-template.xml" version="${build.version}"
/>
+        <fix-config-file file="${staging-dir}/frameworks/js-config-template.xml" version="${build.version}"
/>
         <echo message="Updating config file jquery-config.xml with version ${build.version}"/>
-        <fix-config-file file="${basedir}/temp/frameworks/jquery-config-template.xml"
version="${build.version}" />
+        <fix-config-file file="${staging-dir}/frameworks/jquery-config-template.xml" version="${build.version}"
/>
         <echo message="Updating config file createjs-config.xml with version ${build.version}"/>
-        <fix-config-file file="${basedir}/temp/frameworks/createjs-config-template.xml"
version="${build.version}" />
+        <fix-config-file file="${staging-dir}/frameworks/createjs-config-template.xml"
version="${build.version}" />
         <echo message="Updating config file node-config.xml with version ${build.version}"/>
-        <fix-config-file file="${basedir}/temp/frameworks/node-config-template.xml" version="${build.version}"
/>
+        <fix-config-file file="${staging-dir}/frameworks/node-config-template.xml" version="${build.version}"
/>
         
         
-        <fixcrlf srcdir="${basedir}/temp/js/bin" eol="crlf" fixlast="false">
+        <fixcrlf srcdir="${staging-dir}/js/bin" eol="crlf" fixlast="false">
             <include name="**/*.bat"/>
         </fixcrlf>
         
         <!-- Unix shell scripts need the correct line endings. -->
-        <fixcrlf srcdir="${basedir}/temp/js/bin" eol="unix" fixlast="false">
+        <fixcrlf srcdir="${staging-dir}/js/bin" eol="unix" fixlast="false">
             <exclude name="**/*.bat"/>
         </fixcrlf>
         
-        <chmod dir="${basedir}/temp/js/bin" excludes="**/*.bat" perm="+x" />
+        <chmod dir="${staging-dir}/js/bin" excludes="**/*.bat" perm="+x" />
         
         <!--
              Source files have Windows line endings.  Most UNIX editors can handle
              either type of line endings but the converse is often not true.            

         -->
-        <fixcrlf srcdir="${basedir}/temp/frameworks" eol="crlf" fixlast="false">
+        <fixcrlf srcdir="${staging-dir}/frameworks" eol="crlf" fixlast="false">
             <exclude name="bin/**"/>
             <exclude name="**/assets/**"/>
             <exclude name="**/*.fla"/>
@@ -794,14 +818,14 @@
             Unix shell scripts need the correct line endings. 
             The bin directory is handled in stage-bin.
         -->      
-        <fixcrlf srcdir="${basedir}/temp" eol="unix" fixlast="false">  
+        <fixcrlf srcdir="${staging-dir}/" eol="unix" fixlast="false">
             <include name="**.sh"/>
             <exclude name="bin/**"/>
         </fixcrlf>
         
         <!-- delete any left-over empty directories -->
         <delete includeemptydirs="true">
-            <fileset dir="${basedir}/temp/frameworks/projects">
+            <fileset dir="${staging-dir}/frameworks/projects">
                 <and>
                     <size value="0"/>
                     <type type="dir"/>
@@ -809,7 +833,7 @@
             </fileset>
         </delete>
         <delete includeemptydirs="true">
-            <fileset dir="${basedir}/temp/frameworks/js/projects">
+            <fileset dir="${staging-dir}/frameworks/js/projects">
                 <and>
                     <size value="0"/>
                     <type type="dir"/>
@@ -817,7 +841,7 @@
             </fileset>
         </delete>
         <delete includeemptydirs="true">
-            <fileset dir="${basedir}/temp/examples">
+            <fileset dir="${staging-dir}/examples">
                 <and>
                     <size value="0"/>
                     <type type="dir"/>
@@ -833,7 +857,7 @@
         <antcall target="stage-source"/>
                 
         <!-- concat the license file with the binary license file for the 3rd party deps
-->
-        <concat destfile="${basedir}/temp/LICENSE">
+        <concat destfile="${staging-dir}/LICENSE">
             <filelist dir="${basedir}" files="LICENSE,LICENSE.bin"/>
         </concat>
         
@@ -848,7 +872,7 @@
 
 	<target name="copy-gcl-from-goog-home" if="GOOG_HOME">
 		<echo message="Copying GCL from ${GOOG_HOME}"></echo>
-		<copy todir="${basedir}/temp/js/lib/google/closure-library">
+		<copy todir="${staging-dir}/js/lib/google/closure-library">
 			<fileset dir="${GOOG_HOME}" >
                 <include name="**"/>
                 <exclude name="closure/goog/crypt/**" />
@@ -857,15 +881,15 @@
 	</target>
 	
 	<target name="copy-gcl-from-downloaded" unless="GOOG_HOME">
-		<echo message="Copying GCL from ${basedir}/temp/js/lib/google/closure-library"></echo>
-		<copy todir="${basedir}/temp/js/lib/google/closure-library">
+		<echo message="Copying GCL from ${staging-dir}/js/lib/google/closure-library"></echo>
+		<copy todir="${staging-dir}/js/lib/google/closure-library">
 			<fileset dir="${basedir}/js/lib/google/closure-library" >
                 <include name="**"/>
                 <exclude name="closure/goog/crypt/**" />
             </fileset>
 		</copy>
-        <property name="GOOG_HOME" value="${basedir}/temp/js/lib/google/closure-library"
/>
-        <property name="env.GOOG_HOME" value="${basedir}/temp/js/lib/google/closure-library"
/>
+        <property name="GOOG_HOME" value="${staging-dir}/js/lib/google/closure-library"
/>
+        <property name="env.GOOG_HOME" value="${staging-dir}/js/lib/google/closure-library"
/>
 	</target>
 	
     <target name="tweak-for-jsonly" unless="env.AIR_HOME" description="do a few more things
so the JSOnly package works">
@@ -880,7 +904,7 @@
         description="Zips up the files in the temp directory into the binary zipfile.">
         
         <mkdir dir="${basedir}/out"/>
-        <zip destfile="${basedir}/out/${binary.kit}.zip" basedir="${basedir}/temp"/>
+        <zip destfile="${basedir}/out/${binary.kit}.zip" basedir="${staging-dir}"/>
     </target>
        
     <!-- 
@@ -921,15 +945,15 @@
                 <tar destfile="${basedir}/out/@{name}.tar.gz" 
                     compression="gzip"
                     longfile="gnu">
-                    <tarfileset dir="${basedir}/temp" prefix="@{name}">
+                    <tarfileset dir="${staging-dir}" prefix="@{name}">
                         <include name="**" />
                         <exclude name="bin/**" />
                         <exclude name="**/*.sh" />
                     </tarfileset>
-                    <tarfileset dir="${basedir}/temp" prefix="@{name}">
+                    <tarfileset dir="${staging-dir}" prefix="@{name}">
                         <include name="bin/*.bat" />
                     </tarfileset>
-                    <tarfileset dir="${basedir}/temp" prefix="@{name}" mode="755">
+                    <tarfileset dir="${staging-dir}" prefix="@{name}" mode="755">
                         <include name="bin/*" />
                         <include name="**/*.sh" />
                         <exclude name="bin/*.bat" />
@@ -1014,17 +1038,17 @@
         <antcall target="clean-temp"/>
         <antcall target="asdoc"/>
         <property name="doc_output" value="${basedir}/asdoc-output" />
-        <copy todir="${basedir}/temp/asdoc">
+        <copy todir="${staging-dir}/asdoc">
             <fileset dir="${doc_output}"/>
         </copy>
-        <copy todir="${basedir}/temp/asdoc" file="${basedir}/NOTICE" />
-        <copy tofile="${basedir}/temp/asdoc/LICENSE" file="${basedir}/LICENSE.base" />
-        <zip file="${basedir}/out/${kit.prefix}-asdocs.zip" basedir="${basedir}/temp"/>
+        <copy todir="${staging-dir}/asdoc" file="${basedir}/NOTICE" />
+        <copy tofile="${staging-dir}/asdoc/LICENSE" file="${basedir}/LICENSE.base" />
+        <zip file="${basedir}/out/${kit.prefix}-asdocs.zip" basedir="${staging-dir}"/>
         <antcall target="clean-temp"/>
     </target>
 
     <target name="clean-temp" unless="noclean.temp">
-        <delete dir="${basedir}/temp" failonerror="false" includeEmptyDirs="true"/>
+        <delete dir="${staging-dir}" failonerror="false" includeEmptyDirs="true"/>
     </target>
 
     <!--
@@ -1601,13 +1625,16 @@
 
     <target name="build-all" depends="check-playerglobal-home,check-air-home">
         <property name="font.donot.ask" value="set" />
-        <input
-            message="This script will now download and compile lots of files.  This can take
several minutes.   No interaction should be required.  Press the enter key to continue."
-            />
+        <antcall target="ask-before-build-all" />
         <property name="javadoc.zip.uptodate" value="set" /> <!-- javadoc fails
on windows? -->
         <ant dir="${base.folder.name}/royale-compiler" />
         <ant dir="${base.folder.name}/royale-typedefs" />
     </target>
+    <target name="ask-before-build-all" unless="release.target">
+        <input
+        message="This script will now download and compile lots of files.  This can take
several minutes.   No interaction should be required.  Press the enter key to continue."
+        />
+    </target>
     
     <target name="all" depends="set.base.folder, download-all, main" />
     <target name="set.base.folder" >
@@ -1620,7 +1647,7 @@
             replace="${asfheader}${generated.by.comment}"
             byline="false"
             flags="s">
-            <fileset dir="${basedir}/temp">
+            <fileset dir="${staging-dir}">
                 <include name="**/*.js" />
             </fileset>
         </replaceregexp>
diff --git a/releasemgr/LICENSE b/releasemgr/LICENSE
new file mode 100644
index 0000000..108108e
--- /dev/null
+++ b/releasemgr/LICENSE
@@ -0,0 +1,215 @@
+
+                                 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 SUBCOMPONENTS:
+
+The Apache Royale SDK 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. 
+
+This LICENSE file is used for the type-level source and binary packages.  The 
+individual folders (royale-compiler, royals-typedefs, royale-asjs) each have their own
+LICENSE file specific to the contents of those folders.
diff --git a/releasemgr/NOTICE b/releasemgr/NOTICE
new file mode 100644
index 0000000..052a388
--- /dev/null
+++ b/releasemgr/NOTICE
@@ -0,0 +1,10 @@
+Apache Royale
+Copyright 2012-2017 The Apache Software Foundation
+
+This product includes software developed at
+The Apache Software Foundation (http://www.apache.org/).
+
+The Initial Developer of some parts of the framework, which are copied from, 
+derived from, or inspired by Adobe Flex (via Apache Flex), is 
+Adobe Systems Incorporated (http://www.adobe.com/).
+Copyright 2003 - 2012 Adobe Systems Incorporated. All Rights Reserved.
diff --git a/releasemgr/README b/releasemgr/README
new file mode 100644
index 0000000..782971b
--- /dev/null
+++ b/releasemgr/README
@@ -0,0 +1,191 @@
+Apache Royale
+=============
+
+Apache Royale is a next-generation of the Apache Flex&trade; SDK: . Royale has the goal
of allowing applications developed in MXML and ActionScript to not only run in the Flash/AIR
runtimes, but also to run natively in the browser without Flash, on mobile devices as a PhoneGap/Cordova
application, and in embedded JS environments such as Chromium Embedded Framework. Royale has
the potential to allow your MXML and ActionScript code to run in even more places than Flash
currently does.
+
+For detailed information about using Royale, visit:
+
+<https://apache.github.io/royale-docs/>
+
+For more information about the Apache Royale project, visit:
+
+<http://royale.apache.org>
+
+Getting Royale
+==============
+
+Official Apache Royale releases are in the form of a source package, which needs to
+be built by Apache Ant or Apache Maven before it can be used to build applications
+that produce JS or SWF output.  Royale also provides pre-built packages (often referred
+to as "binary convenience packages") for users that find it inconvenient to build
+Royale from sources before using.
+
+In addition to that, Royale compiled source is available as Maven artifacts and 
+through Node Package Manager (NPM).  If you want to use NPM, see "Getting Royale with NPM"
+below.
+
+This document is the README for the source and binary convenience packages.
+
+This package contains sources from 3 git repositories.  Royale source code is organized into
these repos as follows:
+
+   royale-compiler:  Java source code for the Royale Compiler that converts 
+                     ActionScript and MXML to JS or SWF output.
+
+   royale-typedefs:  Javascript (and some ActionScript) definitions for common 
+                     JavaScript libraries.
+
+   royale-asjs:      ActionScript source code for a framework of UI and other components.
+
+Each folder has its own README, RELEASE_NOTES, LICENSE and NOTICE with information
+specific to the sources contained within that folder.
+
+Building Royale
+===============
+
+Royale requires Java SDK 1.7 or greater to be installed on your computer. For more information
on installing the Java SDK, see:
+
+    <http://www.oracle.com/technetwork/java/javase/downloads/index.html>
+
+Set the JAVA_HOME environment variable to the Java SDK installation path.
+
+Add the bin directory of **JAVA_HOME** to the PATH.
+
+On Windows, set PATH to
+  PATH=%PATH%;%JAVA_HOME%\bin
+
+On a Mac, set PATH to
+  export PATH="$PATH:$JAVA_HOME/bin"
+
+Once Java is installed and setup, follow the instructions for "Building Royale With 
+Apache Maven" or "Building Royale With Apache Ant".  If you want SWF output, see the
+section on "Additional Prerequisites for SWF Output" before building Royale.
+
+
+Building Royale With Apache Maven
+=================================
+
+Royale requires Maven 3.3.9 or greater to be installed on your computer.
+
+To build Royale with Apache Maven, run Maven in the 3 folders as follows:
+
+royale-compiler:  mvn clean install -P -main,utils
+royale-compiler:  mvn clean install
+royale-typedefs:  mvn clean install
+royale-asjs:      mvn clean install
+
+When complete, you should be able to use the Maven archetypes in royale-asjs/archetypes
+to build Royale applications.
+
+
+Building Royale With Apache Ant
+===============================
+
+Royale requires Ant 1.7.1 or greater to be installed on your computer.
+
+Note: 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 you will get compile errors.
+
+For more information on installing Ant, see:
+
+   <http://ant.apache.org/>
+
+Set the **ANT_HOME** environment variable to the Ant installation path.
+
+Add the bin directory of **ANT_HOME** to the PATH.
+
+On Windows, set PATH to
+  PATH=%PATH%;%ANT_HOME%\bin
+
+On a Mac, set PATH to
+  export PATH="$PATH:$ANT_HOME/bin"
+
+Then, run:
+  cd royale-asjs
+  ant all
+
+This will build all of Royale and when finished the royale-asjs folder will be the
+equivalent of a "binary convenience package".  For instructions on how to use
+the results of the build, see the next section.
+
+Using the Binary Convenience Package
+====================================
+
+A package containing compiled binaries can be used in IDEs that support Royale.  IDEs
+should recognize the royale-asjs as a valid Royale SDK.
+
+You can also compile applications from the command line by running MXMLC to compile ActionScript
and MXML into JS (and SWF) applications.
+
+On Windows, run:
+  royale-asjs\js\bin\mxmlc.bat
+
+On Mac, run: 
+  royale-asjs/js/bin/mxmlc
+
+See documentation for details on how to use mxmlc.  In order to get started using Royale,
you are invited to follow along with the Quick Start Guide at https://github.com/apache/royale-asjs/wiki/Quick-Start.
+
+
+Additional Prerequisites For SWF Output
+=======================================
+
+playerglobal.swc
+----------------
+
+The Adobe Flash Player playerglobal.swc (version 11.1) can be downloaded from:
+
+<http://download.macromedia.com/get/flashplayer/updaters/11/playerglobal11_1.swc>
+
+First, create the following directory structure:
+
+  [some folder]/player/11.1/*
+
+Next, rename the downloaded SWC to 'playerglobal.swc' and place it in the above directory.
+
+Then set the PLAYERGLOBAL_HOME environment variable to the absolute path of the player directory,
not including the version subdirectory (i.e. '[some folder]/player').
+
+Other, more recent versions of Adobe Flash Player 'playerglobal.swc' can be downloaded from
http://download.macromedia.com/get/flashplayer/updaters/[version.major]/playerglobal[version.major]_[version.minor].swc
(e.g. <http://download.macromedia.com/get/flashplayer/updaters/11/playerglobal11_1.swc>).
These versions can be used with Royale, but not all have been fully tested.
+
+
+Flash Player Content Debugger
+-----------------------------
+
+The Flash Player Content Debugger can be found here:
+
+    <http://www.adobe.com/support/flashplayer/downloads.html>
+
+This version of Royale was certified for use with Flash Player 11.1, and is compatible with
version 10.2 and up. It has been tested with version 16.0 on Windows and Mac. It has been
compiled, but not fully tested, with other Flash Player versions. It has not been fully tested
on Linux.
+
+On Windows, set the FLASHPLAYER_DEBUGGER environment variable to the absolute path including
the filename of the Flash Player Projector Content Debugger executable (e.g. 'FlashPlayerDebugger.exe').
Note: the filename of Flash Player Content Debugger can differ slightly between versions.
Adjust your path accordingly.
+
+On the Mac, set the FLASHPLAYER_DEBUGGER environment variable to the absolute path of 'Flash
Player.app/Contents/MacOS/Flash Player Debugger'
+
+On Linux, set the FLASHPLAYER_DEBUGGER environment variable to the absolute path of 'flashplayerdebugger'.
+
+Adobe AIR Integration Kit
+-------------------------
+
+This version of Apache Royale was certified for use with Adobe AIR 16 and is compatible with
version 3.1 and up. The Adobe AIR integration kit can be downloaded from:
+
+Windows: <http://airdownload.adobe.com/air/win/download/16.0/AdobeAIRSDK.zip>
+
+Mac: <http://airdownload.adobe.com/air/mac/download/16.0/AdobeAIRSDK.tbz2>
+
+Linux: <http://airdownload.adobe.com/air/lin/download/2.6/AdobeAIRSDK.tbz2>
+
+After you download the AIR SDK, unzip it and place it in a directory of your choice.
+
+Set the AIR_HOME environment variable to the absolute path of the AIR SDK directory.
+
+
+Getting Royale with NPM
+=======================
+
+You can use NPM to get a pre-built package.  To do so run:
+
+  sudo npm install royale -g
+
+
+
+Thanks for using Apache Royale.  Enjoy!
+
+
+                  The Apache Royale Project
+                  <http://royale.apache.org>
diff --git a/releasemgr/RELEASE_NOTES b/releasemgr/RELEASE_NOTES
new file mode 100644
index 0000000..6a9a64f
--- /dev/null
+++ b/releasemgr/RELEASE_NOTES
@@ -0,0 +1,20 @@
+Apache Royale 0.9.0
+===================
+
+Apache Royale is an SDK that provides the capability to cross-compile MXML 
+and ActionScript applications to HTML/JS/CSS so they can run in a browser
+without Flash.
+
+Apache Royale was previously released by the Apache Flex project.  You can
+see RELEASE_NOTES for earlier releases in the Apache Flex releases.
+
+This RELEASE_NOTES file is used for the top-level source and binary package.  The
+individual folders (royale-compiler, royals-typedefs, royale-asjs) each have their own
+RELEASE_NOTES file specific to the contents of those folders.
+
+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
"commits@royale.apache.org" <commits@royale.apache.org>.

Mime
View raw message