[DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[Alex Harui <ah...@adobe.com>]

Please comment on the draft below.  We need Om or someone to publish the
npm module.

-----------

The Apache Flex community is pleased to announce the release of Apache
FlexJS SDK 0.7.0 and Apache Flex FalconJX Compiler 0.7.0.

Apache Flex is a highly productive, open source application framework for
building and maintaining expressive applications that deploy consistently
on all major browsers, desktops and devices (including smartphones,
tablets and tv).

Apache FlexJS is a next-generation Flex SDK that enables developers to use
MXML and ActionScript to not only create SWFs but also cross-compile the
same MXML and ActionScript to HTML/JS/CSS so applications can run natively
in browsers.  The cross-compiled code can also be used in Apache Cordova
(Adobe PhoneGap) mobile applications.

Apache Flex FalconJX is a next-generation MXML and ActionScript
cross-compiler.  It extends the next-generation SWF compiler known as
Falcon.  Both are contained in the release package and are used by the
FlexJS package to compile SWFs or cross-compile to HTML/JS/CSS.

This is the fifth release of FlexJS and FalconJX.  It is ‘beta'
quality.  In this release, all of the compiler JARs and framework SWCs are
also available as Maven artifacts making it the first version of any Flex
SDK to support Maven.  Maven can even be used to build the sources and
examples.  See the various pom.xml files included in the artifacts.

In addition, the JS output also includes source maps so you can see your
ActionScript source in the browser debugger.  Also, there is more support
for using ActionScript to create NodeJS modules, and you can now use a
subset of E4X in your cross-compiled applications.  See the RELEASE_NOTES
files in the artifacts for more information.

The purpose of this release is to gather feedback about the
features and implementation strategies, and recruit new contributors as we
grow these code bases into an SDK and tool chain that delivers the highest
productivity developing applications that can run in the most places.
These releases may not handle production needs.  Expect lots of bugs and
missing features.  Please file bugs at:

https://issues.apache.org/jira/browse/FLEX/

For questions about how to use FlexJS and FalconJX, send email to
users@flex.apache.org.  Please try to prefix the subject with [FlexJS] or
[FalconJX] so it is clear the questions refer to this release and not the
Flex SDK and MXMLC compiler.

For questions and feedback on the development of the source code in these
release, send email to dev@flex.apache.org.  Again, please prefix the
subject with [FlexJS] or [FalconJX].

Apache FlexJS and Apache Flex FalconJX are available in source and binary
form from the following download page:
http://flex.apache.org/download-flexjs.html

When downloading from a mirror site, please remember to verify the
downloads using signatures or MD5 hashes.

A simple way to try these releases is to use the
InstallApacheFlex 3.1 or 3.2 application which is available at the
following url:
http://flex.apache.org/installer.html

Choose Apache FlexJS 0.7.0 and it will create an Adobe Flash
Builder-compatible SDK that uses the Falcon and FalconJX compilers to
generate SWFs and HTML/JS/CSS output.  You can also use FDT as your IDE
for developing FlexJS applications.  Some folks have been successful
using IntelliJ, FlashDevelop as well.  Moonshine is also working on
FlexJS support.

Apache FlexJS 0.7.0 is also available as a npm package. On a system with
npm installed, users can easily install FlexJS with the command: "npm
install flexjs -g".

See the README or the FlexJS wiki for more information.  The FlexJS
section of the wiki is at the following

url:
https://cwiki.apache.org/confluence/display/FLEX/FlexJS

For more information on Apache Flex, visit the project home page:
http://flex.apache.org

Please try FlexJS and become involved in shaping the future of Flex.

The Apache Flex Community

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[Alex Harui <ah...@adobe.com>]

On 9/10/16, 10:04 PM, "omuppi1@gmail.com on behalf of OmPrakash Muppirala"
<omuppi1@gmail.com on behalf of bigosmallm@gmail.com> wrote:

>Which swcs dont match? I can take a look.

If you do a binary compare between what node installs and what we posted
on the mirrors, none of the SWCs compare.

I just checked out Core.swc and found that the code inside is the same,
but the npm version actually came from the nightly build instead of
dist.apache.org or the mirrors.

I don't care enough to check the others and don't really care if you push
out the nightly, but it would be "safer" to push out the exact same bits
we push out through the mirrors.

Thanks,
-Alex

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[OmPrakash Muppirala <bi...@gmail.com>]

Which swcs dont match? I can take a look.

On Sep 10, 2016 9:55 PM, "Alex Harui" <ah...@adobe.com> wrote:

>
>
> On 9/9/16, 10:52 PM, "omuppi1@gmail.com on behalf of OmPrakash Muppirala"
> <omuppi1@gmail.com on behalf of bigosmallm@gmail.com> wrote:
>
> >On Sep 9, 2016 10:46 PM, "Alex Harui" <ah...@adobe.com> wrote:
> >>
> >> The SWCs did not match.  I think they should.  Did you get the SWCs from
> >> the CI server or some other place?
> >
> >Hmm, I thought the swcs came with the binaries?  If yes, it should be
> >loaded from some mirror.
> >
> >Did you have an earlier npm flexjs version installed?  Perhaps you should
> >uninstall that first?
>
> I did uninstall first and checked the node_modules to make sure it is
> gone.  I just tried it again and still the SWCs don't match.  I can build
> stuff a test app, so not sure what to think.  I suppose you can push it.
> We can push another set of files if we figure out what is wrong.
>
> Thanks,
> -Alex
>
>

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[Alex Harui <ah...@adobe.com>]

On 9/9/16, 10:52 PM, "omuppi1@gmail.com on behalf of OmPrakash Muppirala"
<omuppi1@gmail.com on behalf of bigosmallm@gmail.com> wrote:

>On Sep 9, 2016 10:46 PM, "Alex Harui" <ah...@adobe.com> wrote:
>>
>> The SWCs did not match.  I think they should.  Did you get the SWCs from
>> the CI server or some other place?
>
>Hmm, I thought the swcs came with the binaries?  If yes, it should be
>loaded from some mirror.
>
>Did you have an earlier npm flexjs version installed?  Perhaps you should
>uninstall that first?

I did uninstall first and checked the node_modules to make sure it is
gone.  I just tried it again and still the SWCs don't match.  I can build
stuff a test app, so not sure what to think.  I suppose you can push it.
We can push another set of files if we figure out what is wrong.

Thanks,
-Alex

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[OmPrakash Muppirala <bi...@gmail.com>]

On Sep 9, 2016 10:46 PM, "Alex Harui" <ah...@adobe.com> wrote:
>
> The SWCs did not match.  I think they should.  Did you get the SWCs from
> the CI server or some other place?

Hmm, I thought the swcs came with the binaries?  If yes, it should be
loaded from some mirror.

Did you have an earlier npm flexjs version installed?  Perhaps you should
uninstall that first?

>
> -Alex
>
> On 9/9/16, 10:43 PM, "omuppi1@gmail.com on behalf of OmPrakash Muppirala"
> <omuppi1@gmail.com on behalf of bigosmallm@gmail.com> wrote:
>
> >AFAIK the ant build related stuff would be different.   Everything else
> >should match.  But, I’m not 100% sure.
> >
> >Although in my tests, the included apps compiled fine using the npm
> >installed global tools, mxmlc and asjsc.
> >
> >Thanks,
> >Om
> >
> >On Sep 9, 2016 10:01 PM, "Alex Harui" <ah...@adobe.com> wrote:
> >
> >>
> >>
> >> On 9/9/16, 7:08 PM, "omuppi1@gmail.com on behalf of OmPrakash
Muppirala"
> >> <omuppi1@gmail.com on behalf of bigosmallm@gmail.com> wrote:
> >>
> >> >I just pushed flexjs 0.7.0 with a tag 'next'.  If someone can test it
> >>on a
> >> >Mac and give me an all clear, I can go ahead and promote the package
> >>to a
> >> >release.
> >> >
> >> >Run:
> >> >*npm install flexjs@next -g *
> >> >to test flexjs 0.7.0 npm package.
> >>
> >> I tried it and it completed, but the binary files don't match what the
> >> Installer installed.  Should it?
> >>
> >> Thanks,
> >> -Alex
> >>
> >>
>

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[Alex Harui <ah...@adobe.com>]

The SWCs did not match.  I think they should.  Did you get the SWCs from
the CI server or some other place?

-Alex

On 9/9/16, 10:43 PM, "omuppi1@gmail.com on behalf of OmPrakash Muppirala"
<omuppi1@gmail.com on behalf of bigosmallm@gmail.com> wrote:

>AFAIK the ant build related stuff would be different.   Everything else
>should match.  But, I’m not 100% sure.
>
>Although in my tests, the included apps compiled fine using the npm
>installed global tools, mxmlc and asjsc.
>
>Thanks,
>Om
>
>On Sep 9, 2016 10:01 PM, "Alex Harui" <ah...@adobe.com> wrote:
>
>>
>>
>> On 9/9/16, 7:08 PM, "omuppi1@gmail.com on behalf of OmPrakash Muppirala"
>> <omuppi1@gmail.com on behalf of bigosmallm@gmail.com> wrote:
>>
>> >I just pushed flexjs 0.7.0 with a tag 'next'.  If someone can test it
>>on a
>> >Mac and give me an all clear, I can go ahead and promote the package
>>to a
>> >release.
>> >
>> >Run:
>> >*npm install flexjs@next -g *
>> >to test flexjs 0.7.0 npm package.
>>
>> I tried it and it completed, but the binary files don't match what the
>> Installer installed.  Should it?
>>
>> Thanks,
>> -Alex
>>
>>

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[OmPrakash Muppirala <bi...@gmail.com>]

AFAIK the ant build related stuff would be different.   Everything else
should match.  But, I’m not 100% sure.

Although in my tests, the included apps compiled fine using the npm
installed global tools, mxmlc and asjsc.

Thanks,
Om

On Sep 9, 2016 10:01 PM, "Alex Harui" <ah...@adobe.com> wrote:

>
>
> On 9/9/16, 7:08 PM, "omuppi1@gmail.com on behalf of OmPrakash Muppirala"
> <omuppi1@gmail.com on behalf of bigosmallm@gmail.com> wrote:
>
> >I just pushed flexjs 0.7.0 with a tag 'next'.  If someone can test it on a
> >Mac and give me an all clear, I can go ahead and promote the package to a
> >release.
> >
> >Run:
> >*npm install flexjs@next -g *
> >to test flexjs 0.7.0 npm package.
>
> I tried it and it completed, but the binary files don't match what the
> Installer installed.  Should it?
>
> Thanks,
> -Alex
>
>

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[Alex Harui <ah...@adobe.com>]

On 9/9/16, 7:08 PM, "omuppi1@gmail.com on behalf of OmPrakash Muppirala"
<omuppi1@gmail.com on behalf of bigosmallm@gmail.com> wrote:

>I just pushed flexjs 0.7.0 with a tag 'next'.  If someone can test it on a
>Mac and give me an all clear, I can go ahead and promote the package to a
>release.
>
>Run:
>*npm install flexjs@next -g *
>to test flexjs 0.7.0 npm package.

I tried it and it completed, but the binary files don't match what the
Installer installed.  Should it?

Thanks,
-Alex

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[Josh Tynjala <jo...@gmail.com>]

Just tried flexjs@next on Mac. Looks good to me!

- Josh

On Tue, Sep 13, 2016 at 11:55 AM, OmPrakash Muppirala <bi...@gmail.com>
wrote:

> On Mon, Sep 12, 2016 at 4:44 PM, OmPrakash Muppirala <bigosmallm@gmail.com
> >
> wrote:
>
> >
> >
> > On Mon, Sep 12, 2016 at 1:46 PM, Josh Tynjala <jo...@gmail.com>
> > wrote:
> >
> >> Om, can you give my latest changes a try? I tweaked the NPM scripts to
> >> actually run inside Node, which should clear up the cross-platform
> issues,
> >> like requiring Cygwin on Windows. Additionally, I made the NPM scripts
> >> launch the real scripts, so any changes should be picked up
> automatically
> >> from now on.
> >>
> >> I tested on Mac, Windows in PowerShell, and Windows in cmd.exe.
> >>
> >
> > Wow, this is awesome.  Will test soon :-)
> >
>
> Just tested it, everything works as promised on Cygwin, Cmd shell and on
> PowerShell on Windows 7.
> This is huge!  Thanks for getting this done.
>
> I have pushed the new bits as a pre-release to npm.
>
> If someone else wants to test, this is how to install:
>
> *npm install flexjs@next*
>
> I will wait 24 hours before I push this out to npm as a final release
> package.
>
> Thanks,
> Om
>
>
> >
> > Thanks,
> > Om
> >
> >
> >>
> >> - Josh
> >>
> >> On Sun, Sep 11, 2016 at 6:56 PM, Josh Tynjala <jo...@gmail.com>
> >> wrote:
> >>
> >> > I hope to find a way to reuse the existing scripts in the next
> version.
> >> I
> >> > think that tweak I made recently to the NPM versions will help. When I
> >> > expose asnodec, I'll play around with some ideas.
> >> >
> >> > - Josh
> >> >
> >> > On Sep 10, 2016 10:05 PM, "OmPrakash Muppirala" <bigosmallm@gmail.com
> >
> >> > wrote:
> >> >
> >> >> On Sep 10, 2016 9:39 AM, "Josh Tynjala" <jo...@gmail.com>
> wrote:
> >> >> >
> >> >> > Wait! There's one more thing with the NPM versions that need to be
> >> >> changed.
> >> >> > The last lines of asjscnpm, asjscompcnpm, and mxmlcnpm need to be
> >> >> updated
> >> >> > to match the changes in the regular versions.
> >> >> >
> >> >> > For instance, in asjsc:
> >> >> >
> >> >> > -external-library-path="$SCRIPT_HOME/../libs/js.swc"
> >> >> >
> >> >> > is replaced by
> >> >> >
> >> >> > +configname=js
> >> >> >
> >> >> > Exactly the same in asjscompc. It appears that mxmlc may have a
> >> slightly
> >> >> > different change.
> >> >>
> >> >> Gah! We need to figure a way to simply reuse the existing scripts
> >> instead
> >> >> if having to copy everything each time.
> >> >>
> >> >> Are you planning on fixing this?
> >> >>
> >> >> Thanks,
> >> >> Om
> >> >>
> >> >> >
> >> >> > - Josh
> >> >> >
> >> >> > On Sat, Sep 10, 2016 at 9:25 AM, Josh Tynjala <
> joshtynjala@gmail.com
> >> >
> >> >> wrote:
> >> >> >
> >> >> > > After installing flexjs@next from NPM, I can now successfully
> run
> >> >> asjsc,
> >> >> > > asjscompc, and mxmlc from the command line on Mac. The
> end-of-line
> >> fix
> >> >> > > appears to be working correctly.
> >> >> > >
> >> >> > > - Josh
> >> >> > >
> >> >> > > On Fri, Sep 9, 2016 at 7:08 PM, OmPrakash Muppirala <
> >> >> bigosmallm@gmail.com>
> >> >> > > wrote:
> >> >> > >
> >> >> > >> I just pushed flexjs 0.7.0 with a tag 'next'.  If someone can
> >> test it
> >> >> on a
> >> >> > >> Mac and give me an all clear, I can go ahead and promote the
> >> package
> >> >> to a
> >> >> > >> release.
> >> >> > >>
> >> >> > >> Run:
> >> >> > >> *npm install flexjs@next -g *
> >> >> > >> to test flexjs 0.7.0 npm package.
> >> >> > >>
> >> >> > >> Thanks,
> >> >> > >> Om
> >> >> > >>
> >> >> > >> On Fri, Sep 9, 2016 at 2:31 PM, OmPrakash Muppirala <
> >> >> bigosmallm@gmail.com
> >> >> > >> >
> >> >> > >> wrote:
> >> >> > >>
> >> >> > >> >
> >> >> > >> >
> >> >> > >> > On Fri, Sep 9, 2016 at 1:53 PM, Alex Harui <ah...@adobe.com>
> >> >> wrote:
> >> >> > >> >
> >> >> > >> >> Please comment on the draft below.  We need Om or someone to
> >> >> publish
> >> >> > >> the
> >> >> > >> >> npm module.
> >> >> > >> >>
> >> >> > >> >
> >> >> > >> > On it.
> >> >> > >> >
> >> >> > >> > Thanks,
> >> >> > >> > Om
> >> >> > >> >
> >> >> > >> >
> >> >> > >> >>
> >> >> > >> >> -----------
> >> >> > >> >>
> >> >> > >> >> The Apache Flex community is pleased to announce the release
> of
> >> >> Apache
> >> >> > >> >> FlexJS SDK 0.7.0 and Apache Flex FalconJX Compiler 0.7.0.
> >> >> > >> >>
> >> >> > >> >> Apache Flex is a highly productive, open source application
> >> >> framework
> >> >> > >> for
> >> >> > >> >> building and maintaining expressive applications that deploy
> >> >> > >> consistently
> >> >> > >> >> on all major browsers, desktops and devices (including
> >> >> smartphones,
> >> >> > >> >> tablets and tv).
> >> >> > >> >>
> >> >> > >> >> Apache FlexJS is a next-generation Flex SDK that enables
> >> >> developers
> >> >> to
> >> >> > >> use
> >> >> > >> >> MXML and ActionScript to not only create SWFs but also
> >> >> cross-compile
> >> >> > >> the
> >> >> > >> >> same MXML and ActionScript to HTML/JS/CSS so applications can
> >> run
> >> >> > >> natively
> >> >> > >> >> in browsers.  The cross-compiled code can also be used in
> >> Apache
> >> >> > >> Cordova
> >> >> > >> >> (Adobe PhoneGap) mobile applications.
> >> >> > >> >>
> >> >> > >> >> Apache Flex FalconJX is a next-generation MXML and
> ActionScript
> >> >> > >> >> cross-compiler.  It extends the next-generation SWF compiler
> >> known
> >> >> as
> >> >> > >> >> Falcon.  Both are contained in the release package and are
> >> used by
> >> >> the
> >> >> > >> >> FlexJS package to compile SWFs or cross-compile to
> HTML/JS/CSS.
> >> >> > >> >>
> >> >> > >> >> This is the fifth release of FlexJS and FalconJX.  It is
> ‘beta'
> >> >> > >> >> quality.  In this release, all of the compiler JARs and
> >> framework
> >> >> SWCs
> >> >> > >> are
> >> >> > >> >> also available as Maven artifacts making it the first version
> >> of
> >> >> any
> >> >> > >> Flex
> >> >> > >> >> SDK to support Maven.  Maven can even be used to build the
> >> sources
> >> >> and
> >> >> > >> >> examples.  See the various pom.xml files included in the
> >> >> artifacts.
> >> >> > >> >>
> >> >> > >> >> In addition, the JS output also includes source maps so you
> can
> >> >> see
> >> >> > >> your
> >> >> > >> >> ActionScript source in the browser debugger.  Also, there is
> >> more
> >> >> > >> support
> >> >> > >> >> for using ActionScript to create NodeJS modules, and you can
> >> now
> >> >> use a
> >> >> > >> >> subset of E4X in your cross-compiled applications.  See the
> >> >> > >> RELEASE_NOTES
> >> >> > >> >> files in the artifacts for more information.
> >> >> > >> >>
> >> >> > >> >> The purpose of this release is to gather feedback about the
> >> >> > >> >> features and implementation strategies, and recruit new
> >> >> contributors
> >> >> > >> as we
> >> >> > >> >> grow these code bases into an SDK and tool chain that
> delivers
> >> the
> >> >> > >> highest
> >> >> > >> >> productivity developing applications that can run in the most
> >> >> places.
> >> >> > >> >> These releases may not handle production needs.  Expect lots
> of
> >> >> bugs
> >> >> > >> and
> >> >> > >> >> missing features.  Please file bugs at:
> >> >> > >> >>
> >> >> > >> >> https://issues.apache.org/jira/browse/FLEX/
> >> >> > >> >>
> >> >> > >> >> For questions about how to use FlexJS and FalconJX, send
> email
> >> to
> >> >> > >> >> users@flex.apache.org.  Please try to prefix the subject
> with
> >> >> > >> [FlexJS] or
> >> >> > >> >> [FalconJX] so it is clear the questions refer to this release
> >> and
> >> >> not
> >> >> > >> the
> >> >> > >> >> Flex SDK and MXMLC compiler.
> >> >> > >> >>
> >> >> > >> >> For questions and feedback on the development of the source
> >> code
> >> >> in
> >> >> > >> these
> >> >> > >> >> release, send email to dev@flex.apache.org.  Again, please
> >> prefix
> >> >> the
> >> >> > >> >> subject with [FlexJS] or [FalconJX].
> >> >> > >> >>
> >> >> > >> >> Apache FlexJS and Apache Flex FalconJX are available in
> source
> >> and
> >> >> > >> binary
> >> >> > >> >> form from the following download page:
> >> >> > >> >> http://flex.apache.org/download-flexjs.html
> >> >> > >> >>
> >> >> > >> >> When downloading from a mirror site, please remember to
> verify
> >> the
> >> >> > >> >> downloads using signatures or MD5 hashes.
> >> >> > >> >>
> >> >> > >> >> A simple way to try these releases is to use the
> >> >> > >> >> InstallApacheFlex 3.1 or 3.2 application which is available
> at
> >> the
> >> >> > >> >> following url:
> >> >> > >> >> http://flex.apache.org/installer.html
> >> >> > >> >>
> >> >> > >> >> Choose Apache FlexJS 0.7.0 and it will create an Adobe Flash
> >> >> > >> >> Builder-compatible SDK that uses the Falcon and FalconJX
> >> compilers
> >> >> to
> >> >> > >> >> generate SWFs and HTML/JS/CSS output.  You can also use FDT
> as
> >> >> your
> >> >> IDE
> >> >> > >> >> for developing FlexJS applications.  Some folks have been
> >> >> successful
> >> >> > >> >> using IntelliJ, FlashDevelop as well.  Moonshine is also
> >> working
> >> >> on
> >> >> > >> >> FlexJS support.
> >> >> > >> >>
> >> >> > >> >> Apache FlexJS 0.7.0 is also available as a npm package. On a
> >> >> system
> >> >> > >> with
> >> >> > >> >> npm installed, users can easily install FlexJS with the
> >> command:
> >> >> "npm
> >> >> > >> >> install flexjs -g".
> >> >> > >> >>
> >> >> > >> >> See the README or the FlexJS wiki for more information.  The
> >> >> FlexJS
> >> >> > >> >> section of the wiki is at the following
> >> >> > >> >>
> >> >> > >> >> url:
> >> >> > >> >> https://cwiki.apache.org/confluence/display/FLEX/FlexJS
> >> >> > >> >>
> >> >> > >> >> For more information on Apache Flex, visit the project home
> >> page:
> >> >> > >> >> http://flex.apache.org
> >> >> > >> >>
> >> >> > >> >> Please try FlexJS and become involved in shaping the future
> of
> >> >> Flex.
> >> >> > >> >>
> >> >> > >> >> The Apache Flex Community
> >> >> > >> >>
> >> >> > >> >>
> >> >> > >> >>
> >> >> > >> >>
> >> >> > >> >
> >> >> > >>
> >> >> > >
> >> >> > >
> >> >>
> >> >
> >>
> >
> >
>

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[OmPrakash Muppirala <bi...@gmail.com>]

I have published flexjs 0.7.0 on the npm repository.

You can install it by running:

npm install flexjs -g

Before publishing, I confirmed that the npm flexjs package does indeed
download from the mirrors:

==================
*Downloading Apache FlexJS from mirror:
http://mirror.symnds.com/software/Apache/flex/flexjs/0.7.0/binaries/apache-flex-flexjs-0.7.0-bin.zip
<http://mirror.symnds.com/software/Apache/flex/flexjs/0.7.0/binaries/apache-flex-flexjs-0.7.0-bin.zip>*
Apache FlexJS download complete
Extracting Apache FlexJS
Apache FlexJS extraction complete
Downloading Apache Flex Falcon Compiler
*Downloading Apache Flex Falcon Compiler from mirror:
http://apache.mirrors.ionfish.org/flex/falcon/0.7.0/binaries/apache-flex-falconjx-0.7.0-bin.zip
<http://apache.mirrors.ionfish.org/flex/falcon/0.7.0/binaries/apache-flex-falconjx-0.7.0-bin.zip>*
Apache Flex Falcon Compiler download complete
Extracting Apache Flex Falcon Compiler
==================

Thanks,
Om

On Wed, Sep 14, 2016 at 11:55 PM, Harbs <ha...@gmail.com> wrote:

> +1.
>
> Let’s keep things positive and keep things rolling.
>
> Like we’ve discussed in the past, let’s try not to read too much intent
> into emails. Email is a bad medium for conveying intent. I didn’t read bad
> intent from anyone here.
>
> Thank you Alex for getting this release out, and thank you Justin for
> helping us find IP issues. :-)
>
> I didn’t see anything which should delay the release announcement. We can
> look into whether there’s a better way of pushing things to npm before our
> next release. Justin, if you have suggestions on that front, I think we’re
> all happy to hear.
>
> Thanks,
> Harbs
>
> On Sep 15, 2016, at 7:15 AM, Alex Harui <ah...@adobe.com> wrote:
>
> >
> >
> > On 9/14/16, 4:27 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
> >
> >>
> >> Perhaps the question we should be asking is why are other PMC members
> are
> >> not finding these issues earlier as well?
> >
> > Well, I can only speak for myself, but I have learned over the years
> that,
> > while we can't say "Community over Policy" since policy is important,
> > community is still more important than trying to nail every last detail
> of
> > the licensing.  For sure, early on, I thought we had to nail every last
> > detail, but senior Apache members have advised us that we can use "trust"
> > and "intent" in approving releases.  So I look at harder at what we are
> > saying is our source, take a trusting, high-level look at what
> > third-parties say we can do and go from there.  Because if we do make a
> > mistake in the details, it isn't the end of the world, we can fix it in
> > the next release, and the best way to guarantee there will be a next
> > release is to make sure the release process is quick and more like a
> > celebration of work completed than a grind through fine print.  If we can
> > do that, we might find more folks will want to be release managers,
> > releases will take less energy so they can happen more often, and the
> > community will grow as a result.  IOW, I am always looking for reasons to
> > ship, not reasons not too, especially late in the game.
> >
> > Now also for sure, there is nobody in the entire foundation (not just
> this
> > project) who is better than you at finding licensing issues, and if you
> > want to help other PMC members find more of these issues, it would be
> > great if you could share your processes with us and the ASF in general.
> >
> > Another way to look at it is that if the ASF truly cared about nailing
> > every last detail, the policy would be that you could use a licensing
> > issue to veto a release.  It puzzled me for a while that it wasn't that
> > way, but I've come to think that the real goal is to build communities
> and
> > share source code without involving lawyers and tons of time.  I think
> the
> > ASF realizes that these communities are almost all non-lawyers trying to
> > make the world better through shared code and they may (as we know) have
> > not nailed their documentation down to the last detail.  And thus, we
> > don't have to look too hard, especially at third-party bundles.  If
> > something comes up, we can deal with it in the next release.  We can
> trust
> > that third-parties are not trying to lay some trap or sneak in a trojan
> > horse.
> >
> > I personally don't enjoy grinding through the details of license and
> > notice stuff.  My sense is that there are several others in our community
> > who feel the same way and wonder if others have left us and what other
> > code we could have done, and contributors we could have attracted if we
> > didn't spend as much time grinding on it.  As long as the right
> > attribution is there at a high-level, I think we are good to go and
> > volunteers can improve it, just like we improve our code, over time.
> >
> > Now let's push the NPM bits, get the announcement out, and get going on
> > the building the future of Flex.
> >
> > Thanks,
> > -Alex
> >
>
>

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[Harbs <ha...@gmail.com>]

+1.

Let’s keep things positive and keep things rolling.

Like we’ve discussed in the past, let’s try not to read too much intent into emails. Email is a bad medium for conveying intent. I didn’t read bad intent from anyone here.

Thank you Alex for getting this release out, and thank you Justin for helping us find IP issues. :-)

I didn’t see anything which should delay the release announcement. We can look into whether there’s a better way of pushing things to npm before our next release. Justin, if you have suggestions on that front, I think we’re all happy to hear.

Thanks,
Harbs

On Sep 15, 2016, at 7:15 AM, Alex Harui <ah...@adobe.com> wrote:

> 
> 
> On 9/14/16, 4:27 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
> 
>> 
>> Perhaps the question we should be asking is why are other PMC members are
>> not finding these issues earlier as well?
> 
> Well, I can only speak for myself, but I have learned over the years that,
> while we can't say "Community over Policy" since policy is important,
> community is still more important than trying to nail every last detail of
> the licensing.  For sure, early on, I thought we had to nail every last
> detail, but senior Apache members have advised us that we can use "trust"
> and "intent" in approving releases.  So I look at harder at what we are
> saying is our source, take a trusting, high-level look at what
> third-parties say we can do and go from there.  Because if we do make a
> mistake in the details, it isn't the end of the world, we can fix it in
> the next release, and the best way to guarantee there will be a next
> release is to make sure the release process is quick and more like a
> celebration of work completed than a grind through fine print.  If we can
> do that, we might find more folks will want to be release managers,
> releases will take less energy so they can happen more often, and the
> community will grow as a result.  IOW, I am always looking for reasons to
> ship, not reasons not too, especially late in the game.
> 
> Now also for sure, there is nobody in the entire foundation (not just this
> project) who is better than you at finding licensing issues, and if you
> want to help other PMC members find more of these issues, it would be
> great if you could share your processes with us and the ASF in general.
> 
> Another way to look at it is that if the ASF truly cared about nailing
> every last detail, the policy would be that you could use a licensing
> issue to veto a release.  It puzzled me for a while that it wasn't that
> way, but I've come to think that the real goal is to build communities and
> share source code without involving lawyers and tons of time.  I think the
> ASF realizes that these communities are almost all non-lawyers trying to
> make the world better through shared code and they may (as we know) have
> not nailed their documentation down to the last detail.  And thus, we
> don't have to look too hard, especially at third-party bundles.  If
> something comes up, we can deal with it in the next release.  We can trust
> that third-parties are not trying to lay some trap or sneak in a trojan
> horse.
> 
> I personally don't enjoy grinding through the details of license and
> notice stuff.  My sense is that there are several others in our community
> who feel the same way and wonder if others have left us and what other
> code we could have done, and contributors we could have attracted if we
> didn't spend as much time grinding on it.  As long as the right
> attribution is there at a high-level, I think we are good to go and
> volunteers can improve it, just like we improve our code, over time.
> 
> Now let's push the NPM bits, get the announcement out, and get going on
> the building the future of Flex.
> 
> Thanks,
> -Alex
> 

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[Justin Mclean <ju...@classsoftware.com>]

Hi,

> Well, I can only speak for myself, but I have learned over the years that,
> while we can't say "Community over Policy" since policy is important,
> community is still more important than trying to nail every last detail of
> the licensing.

If we start making releases that don’t conform to policy we may attract board attention and we really don’t want that.

>  For sure, early on, I thought we had to nail every last
> detail, but senior Apache members have advised us that we can use "trust"
> and "intent" in approving releases.

That have also advised that policy must be followed and issues need to be fixed when they are brought up.

> Because if we do make a mistake in the details, it isn't the end of the world, we can fix it in
> the next release

Or the next RC if needed. Most of these issues are very easily fixed and where there is some doubt on what to do they can be “fixed" so that at worse it’s a documentation error rather than a licensing error.

>  it would be great if you could share your processes with us and the ASF in general.

I’ve shared several times my process for reviewing releases, there’s noting special there. Mostly an understanding of policy and knowing what to look for and a few simple searches of the code. I have submitted a talk to ApacheCon on this subject and if accepted will share here after the event.

> Another way to look at it is that if the ASF truly cared about nailing
> every last detail, the policy would be that you could use a licensing
> issue to veto a release.

You can’t veto a release but it is common for PMC members to vote -1 on a release that contains:
- security software without an export license
- binaries
- bundled or dependancies on category X licensed software
- category B code in source
- licensing errors

Fix in the next release is generally:
- documentation errors in license/notice
- missing headers

The incubator is a little more lenient to projects starting out and the answer is always going to be "it depends” some licensing errors are more serious than others.

It is for example possible to get VP legal to give you permission to release something with GPL licensed software in it.

> And thus, we don't have to look too hard, especially at third-party bundles.

IMO we need look a little harder when we bundled 3rd party stuff as it's easier to make mistakes. But the issues we currently have are due to what we have done not what 3rd parties have done.

Thanks,
Justin

AW: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[Christofer Dutz <ch...@c-ware.de>]

I still have one discussion in mind with the replacing of License Headers in files as part of the Patch process. I guess this isn't resolved yet. I responded more general as the other responses seemed to refer to someone continuously doing something :-)


Chris

________________________________
Von: Harbs <ha...@gmail.com>
Gesendet: Donnerstag, 15. September 2016 10:30:00
An: dev@flex.apache.org
Betreff: Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

I’m confused about which issue you are referring to.

Before the release was cut he brought up some issues related to code which might have not have compatible licensing, We acted on that pretty much immediately.

During the release process, he brought up the fact that the full MIT license wording was not included, and we did not reach a consensus on whether that’s an issue. We did have enough PMC members agree that it’s at the least not a release-blocker. We should come to a consensus on what to do about that before our next release.

Justin now brought up an issue with how artifacts are being pushed to npm. I don’t understand what the issue could be. If Justin could clarify and propose an alternative, we might be able to improve things for the next release.

Am I missing something?

On Sep 15, 2016, at 10:34 AM, Christofer Dutz <ch...@c-ware.de> wrote:

> Justin did bring up the issue. He even brought it when we were first discussing starting a release. The discussion sort of dried out without a resolution, then when it came to the release, he mentioned it again. But again no action was taken. So I too see a complaint about PMCs coming up with such stuff in the last minute as not valid.

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[Justin Mclean <ju...@classsoftware.com>]

Hi,

> Some issues are more controversial than others.  The controversial ones should be decided before committing changes.

So what issues do you consider not to be controversial? Which ones can I fix?

Thanks,
Justin 

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[Alex Harui <ah...@adobe.com>]

Well, we could use JIRA as you suggested, but for starters, a list of issues in a separate email thread might be more efficient.  I've lost track of what the issues are since some, like the npm distro is no longer an issue (I think).

-Alex

From: "omuppi1@gmail.com<ma...@gmail.com>" <om...@gmail.com>> on behalf of OmPrakash Muppirala <bi...@gmail.com>>
Date: Thursday, September 15, 2016 at 6:47 PM
To: Alex Harui <ah...@adobe.com>>
Cc: "dev@flex.apache.org<ma...@flex.apache.org>" <de...@flex.apache.org>>
Subject: Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released



On Thu, Sep 15, 2016 at 6:21 PM, Alex Harui <ah...@adobe.com>> wrote:
Some issues are more controversial than others.  The controversial ones should be decided before committing changes.
Fair enough.  But that said, I do see Justin's point that he does not want to make the changes if there is a threat of a veto.  How can we separate out things so that the easy to fix ones don't end up clubbed together with controversial ones?

In other words, how can we make it easier for Justin to go ahead and JFDI?

Thanks,
Om



Sent from my LG G3, an AT&T 4G LTE smartphone

------ Original message------
From: OmPrakash Muppirala
Date: Thu, Sep 15, 2016 5:41 PM
To: dev@flex.apache.org<ma...@flex.apache.org>;
Subject:Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

On Thu, Sep 15, 2016 at 4:42 PM, Justin Mclean <ju...@classsoftware.com>>
wrote:

> Hi,
>
> > Justin, any reason you did not fix the issues yourself?  Were you
> expecting
> > someone else to fix them?
>
> If I had changed LICENSE/NOTICE without discussion it’s probable that my
> changes would be vetoed.
>

I doubt that would happen.  Maybe you should try fixing them and see what
happens? ;-)

Thanks,
Om


>
> > Also, why were no JIRA tickets filed?
>
> For these exact issue no a sI had expected it to be resolved before the RC
> was made. I usually raise them after the release so it's not forgotten
> about before the next one - for instance [1]
>

I think you should create tickets for each licensing issue you bring up.
 a) It would be easier for anyone else (ex. Legal folks) to come take a
look and quickly give an opinion and b) We have a record that we did
actually discuss this issue and made an effort to resolve the issue.

Thanks,
Om


>
> Thanks,
> Justin
>
> 1. https://issues.apache.org/jira/browse/FLEX-35058

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[OmPrakash Muppirala <bi...@gmail.com>]

On Thu, Sep 15, 2016 at 6:21 PM, Alex Harui <ah...@adobe.com> wrote:

> Some issues are more controversial than others.  The controversial ones
> should be decided before committing changes.
>
Fair enough.  But that said, I do see Justin's point that he does not want
to make the changes if there is a threat of a veto.  How can we separate
out things so that the easy to fix ones don't end up clubbed together with
controversial ones?

In other words, how can we make it easier for Justin to go ahead and JFDI?

Thanks,
Om



>
> Sent from my LG G3, an AT&T 4G LTE smartphone
>
> ------ Original message------
> *From: *OmPrakash Muppirala
> *Date: *Thu, Sep 15, 2016 5:41 PM
> *To: *dev@flex.apache.org;
> *Subject:*Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0
> Released
>
> On Thu, Sep 15, 2016 at 4:42 PM, Justin Mclean <ju...@classsoftware.com>
> wrote:
>
> > Hi,
> >
> > > Justin, any reason you did not fix the issues yourself?  Were you
> > expecting
> > > someone else to fix them?
> >
> > If I had changed LICENSE/NOTICE without discussion it’s probable that my
> > changes would be vetoed.
> >
>
> I doubt that would happen.  Maybe you should try fixing them and see what
> happens? ;-)
>
> Thanks,
> Om
>
>
> >
> > > Also, why were no JIRA tickets filed?
> >
> > For these exact issue no a sI had expected it to be resolved before the
> RC
> > was made. I usually raise them after the release so it's not forgotten
> > about before the next one - for instance [1]
> >
>
> I think you should create tickets for each licensing issue you bring up.
>  a) It would be easier for anyone else (ex. Legal folks) to come take a
> look and quickly give an opinion and b) We have a record that we did
> actually discuss this issue and made an effort to resolve the issue.
>
> Thanks,
> Om
>
>
> >
> > Thanks,
> > Justin
> >
> > 1. https://issues.apache.org/jira/browse/FLEX-35058
>

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[Alex Harui <ah...@adobe.com>]

Some issues are more controversial than others.  The controversial ones should be decided before committing changes.

Sent from my LG G3, an AT&T 4G LTE smartphone

------ Original message------
From: OmPrakash Muppirala
Date: Thu, Sep 15, 2016 5:41 PM
To: dev@flex.apache.org;
Subject:Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

On Thu, Sep 15, 2016 at 4:42 PM, Justin Mclean <ju...@classsoftware.com>
wrote:

> Hi,
>
> > Justin, any reason you did not fix the issues yourself?  Were you
> expecting
> > someone else to fix them?
>
> If I had changed LICENSE/NOTICE without discussion it’s probable that my
> changes would be vetoed.
>

I doubt that would happen.  Maybe you should try fixing them and see what
happens? ;-)

Thanks,
Om


>
> > Also, why were no JIRA tickets filed?
>
> For these exact issue no a sI had expected it to be resolved before the RC
> was made. I usually raise them after the release so it's not forgotten
> about before the next one - for instance [1]
>

I think you should create tickets for each licensing issue you bring up.
 a) It would be easier for anyone else (ex. Legal folks) to come take a
look and quickly give an opinion and b) We have a record that we did
actually discuss this issue and made an effort to resolve the issue.

Thanks,
Om


>
> Thanks,
> Justin
>
> 1. https://issues.apache.org/jira/browse/FLEX-35058

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[OmPrakash Muppirala <bi...@gmail.com>]

On Thu, Sep 15, 2016 at 4:42 PM, Justin Mclean <ju...@classsoftware.com>
wrote:

> Hi,
>
> > Justin, any reason you did not fix the issues yourself?  Were you
> expecting
> > someone else to fix them?
>
> If I had changed LICENSE/NOTICE without discussion it’s probable that my
> changes would be vetoed.
>

I doubt that would happen.  Maybe you should try fixing them and see what
happens? ;-)

Thanks,
Om


>
> > Also, why were no JIRA tickets filed?
>
> For these exact issue no a sI had expected it to be resolved before the RC
> was made. I usually raise them after the release so it's not forgotten
> about before the next one - for instance [1]
>

I think you should create tickets for each licensing issue you bring up.
 a) It would be easier for anyone else (ex. Legal folks) to come take a
look and quickly give an opinion and b) We have a record that we did
actually discuss this issue and made an effort to resolve the issue.

Thanks,
Om


>
> Thanks,
> Justin
>
> 1. https://issues.apache.org/jira/browse/FLEX-35058

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[Justin Mclean <ju...@classsoftware.com>]

Hi,

> Justin, any reason you did not fix the issues yourself?  Were you expecting
> someone else to fix them?

If I had changed LICENSE/NOTICE without discussion it’s probable that my changes would be vetoed.

> Also, why were no JIRA tickets filed?

For these exact issue no a sI had expected it to be resolved before the RC was made. I usually raise them after the release so it's not forgotten about before the next one - for instance [1]

Thanks,
Justin

1. https://issues.apache.org/jira/browse/FLEX-35058

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[OmPrakash Muppirala <bi...@gmail.com>]

Justin, any reason you did not fix the issues yourself?  Were you expecting
someone else to fix them?
Also, why were no JIRA tickets filed?

Thanks,
Om

On Thu, Sep 15, 2016 at 4:19 PM, Justin Mclean <ju...@classsoftware.com>
wrote:

> Hi,
>
> > During the release process, he brought up the fact that the full MIT
> license wording was not included,
>
> I brought this up before before the release process was started [1]. The
> patch header issue was first brought up last in the last release many
> months ago.
>
> Thanks,
> Justin
>
> 1. https://lists.apache.org/thread.html/95ba7d9eb5a83cfa8411b933d00ba6
> fde4c8b982feecc823e7fdbdc4@%3Cdev.flex.apache.org%3E

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[Justin Mclean <ju...@classsoftware.com>]

Hi,

> During the release process, he brought up the fact that the full MIT license wording was not included,

I brought this up before before the release process was started [1]. The patch header issue was first brought up last in the last release many months ago.

Thanks,
Justin

1. https://lists.apache.org/thread.html/95ba7d9eb5a83cfa8411b933d00ba6fde4c8b982feecc823e7fdbdc4@%3Cdev.flex.apache.org%3E

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[Harbs <ha...@gmail.com>]

I’m confused about which issue you are referring to.

Before the release was cut he brought up some issues related to code which might have not have compatible licensing, We acted on that pretty much immediately.

During the release process, he brought up the fact that the full MIT license wording was not included, and we did not reach a consensus on whether that’s an issue. We did have enough PMC members agree that it’s at the least not a release-blocker. We should come to a consensus on what to do about that before our next release.

Justin now brought up an issue with how artifacts are being pushed to npm. I don’t understand what the issue could be. If Justin could clarify and propose an alternative, we might be able to improve things for the next release.

Am I missing something?

On Sep 15, 2016, at 10:34 AM, Christofer Dutz <ch...@c-ware.de> wrote:

> Justin did bring up the issue. He even brought it when we were first discussing starting a release. The discussion sort of dried out without a resolution, then when it came to the release, he mentioned it again. But again no action was taken. So I too see a complaint about PMCs coming up with such stuff in the last minute as not valid.

AW: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[Christofer Dutz <ch...@c-ware.de>]

Just to add my 50ct to this discussion.


Justin did bring up the issue. He even brought it when we were first discussing starting a release. The discussion sort of dried out without a resolution, then when it came to the release, he mentioned it again. But again no action was taken. So I too see a complaint about PMCs coming up with such stuff in the last minute as not valid.


ASF is community over code, but the one thing the ASF deals with is protecting us as developers as well as our users from licensing issues. It's this extra protection and care that distinguishes Apache releases from the typical Github projects. This is why in every bank or insurance company I was working in, there never was a discussion about using ASF software, if it's not ASF however you have to jump quite a lot of obstacles in order to use a library. I remember quite some rounds with legal and quality assurance people.


The ASF has earned that trust because we have people in our communities that care about this sort of stuff. Having some legal caretaker is one of the coolest thing a project can have, cause it lets us coding-monkeys do what we like to do and we can somehow be lazy and trust that someone is taking care of this. I hate legal stuff. To me it's just getting in my way ... sort of as others think working on build-, code-quality or writing documentation should be done by others.


We have a pretty heterogenous community. I know I'm definitely the build-monkey, Justin's the legal-monkey, we have a lot of code-monkeys. Why not use the specialities of each other instead of complaining about it? I know I have to work on my side about not ranting about code-quality, for example, but I'm trying ... hope you guys didn't notice any recent rants from my side ;-)


If we hadn't let the discussion about Justin's findings die when he brought it up and had resolved the problem instead, the problem would have been solved. So how about us addressing the issues Justin has and in case of a "I think this way, you think that way", let's involve legal and have these things settled once and for all?


 Chris




________________________________
Von: Alex Harui <ah...@adobe.com>
Gesendet: Donnerstag, 15. September 2016 06:15
An: dev@flex.apache.org
Betreff: Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released



On 9/14/16, 4:27 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:

>
>Perhaps the question we should be asking is why are other PMC members are
>not finding these issues earlier as well?

Well, I can only speak for myself, but I have learned over the years that,
while we can't say "Community over Policy" since policy is important,
community is still more important than trying to nail every last detail of
the licensing.  For sure, early on, I thought we had to nail every last
detail, but senior Apache members have advised us that we can use "trust"
and "intent" in approving releases.  So I look at harder at what we are
saying is our source, take a trusting, high-level look at what
third-parties say we can do and go from there.  Because if we do make a
mistake in the details, it isn't the end of the world, we can fix it in
the next release, and the best way to guarantee there will be a next
release is to make sure the release process is quick and more like a
celebration of work completed than a grind through fine print.  If we can
do that, we might find more folks will want to be release managers,
releases will take less energy so they can happen more often, and the
community will grow as a result.  IOW, I am always looking for reasons to
ship, not reasons not too, especially late in the game.

Now also for sure, there is nobody in the entire foundation (not just this
project) who is better than you at finding licensing issues, and if you
want to help other PMC members find more of these issues, it would be
great if you could share your processes with us and the ASF in general.

Another way to look at it is that if the ASF truly cared about nailing
every last detail, the policy would be that you could use a licensing
issue to veto a release.  It puzzled me for a while that it wasn't that
way, but I've come to think that the real goal is to build communities and
share source code without involving lawyers and tons of time.  I think the
ASF realizes that these communities are almost all non-lawyers trying to
make the world better through shared code and they may (as we know) have
not nailed their documentation down to the last detail.  And thus, we
don't have to look too hard, especially at third-party bundles.  If
something comes up, we can deal with it in the next release.  We can trust
that third-parties are not trying to lay some trap or sneak in a trojan
horse.

I personally don't enjoy grinding through the details of license and
notice stuff.  My sense is that there are several others in our community
who feel the same way and wonder if others have left us and what other
code we could have done, and contributors we could have attracted if we
didn't spend as much time grinding on it.  As long as the right
attribution is there at a high-level, I think we are good to go and
volunteers can improve it, just like we improve our code, over time.

Now let's push the NPM bits, get the announcement out, and get going on
the building the future of Flex.

Thanks,
-Alex

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[Alex Harui <ah...@adobe.com>]

On 9/14/16, 4:27 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:

>
>Perhaps the question we should be asking is why are other PMC members are
>not finding these issues earlier as well?

Well, I can only speak for myself, but I have learned over the years that,
while we can't say "Community over Policy" since policy is important,
community is still more important than trying to nail every last detail of
the licensing.  For sure, early on, I thought we had to nail every last
detail, but senior Apache members have advised us that we can use "trust"
and "intent" in approving releases.  So I look at harder at what we are
saying is our source, take a trusting, high-level look at what
third-parties say we can do and go from there.  Because if we do make a
mistake in the details, it isn't the end of the world, we can fix it in
the next release, and the best way to guarantee there will be a next
release is to make sure the release process is quick and more like a
celebration of work completed than a grind through fine print.  If we can
do that, we might find more folks will want to be release managers,
releases will take less energy so they can happen more often, and the
community will grow as a result.  IOW, I am always looking for reasons to
ship, not reasons not too, especially late in the game.

Now also for sure, there is nobody in the entire foundation (not just this
project) who is better than you at finding licensing issues, and if you
want to help other PMC members find more of these issues, it would be
great if you could share your processes with us and the ASF in general.

Another way to look at it is that if the ASF truly cared about nailing
every last detail, the policy would be that you could use a licensing
issue to veto a release.  It puzzled me for a while that it wasn't that
way, but I've come to think that the real goal is to build communities and
share source code without involving lawyers and tons of time.  I think the
ASF realizes that these communities are almost all non-lawyers trying to
make the world better through shared code and they may (as we know) have
not nailed their documentation down to the last detail.  And thus, we
don't have to look too hard, especially at third-party bundles.  If
something comes up, we can deal with it in the next release.  We can trust
that third-parties are not trying to lay some trap or sneak in a trojan
horse.

I personally don't enjoy grinding through the details of license and
notice stuff.  My sense is that there are several others in our community
who feel the same way and wonder if others have left us and what other
code we could have done, and contributors we could have attracted if we
didn't spend as much time grinding on it.  As long as the right
attribution is there at a high-level, I think we are good to go and
volunteers can improve it, just like we improve our code, over time.

Now let's push the NPM bits, get the announcement out, and get going on
the building the future of Flex.

Thanks,
-Alex

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[Justin Mclean <ju...@classsoftware.com>]

Hi,

> Justin, regardless of the perceived tone of Alex's message, the content of
> it should not be dismissed. You always seem to raise new licensing issues
> at the last minute before a release

Here the issues were raised well before the RC was made so not really last minute. [1][2]

But it’s true I’m not full time or paid to work on this and so I can’t always review / find everything early. It historically true (for what ever reason) that all PMC members tend to check releases late in the process. Alex had to ask several times for other PMC to review the release after I had done so.

Perhaps the question we should be asking is why are other PMC members are not finding these issues earlier as well? Part of that I would guess is I pay a little more attention to policy/license issues and probably have more experience in knowing what to look for from my work on the incubator PMC. But it is (for instance) slightly concerning that the MIT license issue wasn’t picked up earlier by someone else.

If I hadn’t been reviewing it's likely (IMO) that this realise would of contained GPL licensed/ proprietary IP and would of had more license issues.

Thanks,
Justin

1. https://lists.apache.org/thread.html/db1ec380d40d5685d50fe75430662a7e5c6cf985752f82acf4bec0d1@%3Cdev.flex.apache.org%3E
2. https://lists.apache.org/thread.html/95ba7d9eb5a83cfa8411b933d00ba6fde4c8b982feecc823e7fdbdc4@%3Cdev.flex.apache.org%3E

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[Josh Tynjala <jo...@gmail.com>]

Justin, regardless of the perceived tone of Alex's message, the content of
it should not be dismissed. You always seem to raise new licensing issues
at the last minute before a release. This timing can be extremely
frustrating for the rest of us.

- Josh

On Wed, Sep 14, 2016 at 3:15 PM, Justin Mclean <ju...@classsoftware.com>
wrote:

> Hi,
>
> > I don't think there is a problem.  Let's push npm out so we can push out
> > the announcement.  If there is a problem it can be rectified.
>
> I was suggesting that care be taken. You yourself stated that the npm
> release contained code from the nightly. [1]
>
> > This is another example of why the board and mentors recommend that
> folks who want
> > to be sticklers about policy should be watching the commit lists and
> > raising issues early, not at the last minute where it delays the work of
> > the folks who are actually contributing code to the release.
>
> No it is not. If you referencing to the FlexJS release I did report issues
> before the RC was made. For instance [2] there are also earlier emails.
>
> > "minor" policy issues should be investigated and presented in more detail
> > and in a collaborative fashion
>
> I am acting in a collaborative fashion and providing detail were needed,
> Where there is an issue I suggest a way to fix it, for instance replacing
> content of dubious IP [3] with one of known licensing or with licensing
> issues.[2].
>
> > instead of accusing other PMC members.
>
> On evidence in this public list it seem to me that the only person making
> unfounded accusations is you and I regard this as a person attack. Please
> apologise for your statements.
>
> Justin
>
> 1. https://lists.apache.org/thread.html/a496e2b6595fcf303b13af962f641b
> ec42bf20687f2de07b0df63483@%3Cdev.flex.apache.org%3E
> 2. https://lists.apache.org/thread.html/95ba7d9eb5a83cfa8411b933d00ba6
> fde4c8b982feecc823e7fdbdc4@%3Cdev.flex.apache.org%3E
> 3. https://lists.apache.org/thread.html/92901b973714c6a12853aa8ed2972c
> abb529dfcff065b870e22dbb0a@%3Cdev.flex.apache.org%3E
>
>

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[Justin Mclean <ju...@classsoftware.com>]

Hi,

> I don't think there is a problem.  Let's push npm out so we can push out
> the announcement.  If there is a problem it can be rectified.

I was suggesting that care be taken. You yourself stated that the npm release contained code from the nightly. [1]

> This is another example of why the board and mentors recommend that folks who want
> to be sticklers about policy should be watching the commit lists and
> raising issues early, not at the last minute where it delays the work of
> the folks who are actually contributing code to the release.

No it is not. If you referencing to the FlexJS release I did report issues before the RC was made. For instance [2] there are also earlier emails.

> "minor" policy issues should be investigated and presented in more detail
> and in a collaborative fashion

I am acting in a collaborative fashion and providing detail were needed, Where there is an issue I suggest a way to fix it, for instance replacing content of dubious IP [3] with one of known licensing or with licensing issues.[2].

> instead of accusing other PMC members.

On evidence in this public list it seem to me that the only person making unfounded accusations is you and I regard this as a person attack. Please apologise for your statements.

Justin

1. https://lists.apache.org/thread.html/a496e2b6595fcf303b13af962f641bec42bf20687f2de07b0df63483@%3Cdev.flex.apache.org%3E
2. https://lists.apache.org/thread.html/95ba7d9eb5a83cfa8411b933d00ba6fde4c8b982feecc823e7fdbdc4@%3Cdev.flex.apache.org%3E
3. https://lists.apache.org/thread.html/92901b973714c6a12853aa8ed2972cabb529dfcff065b870e22dbb0a@%3Cdev.flex.apache.org%3E

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[Alex Harui <ah...@adobe.com>]

On 9/13/16, 3:28 PM, "omuppi1@gmail.com on behalf of OmPrakash Muppirala"
<omuppi1@gmail.com on behalf of bigosmallm@gmail.com> wrote:

>The npm flexjs package is a thing on its own which points to only released
>Apache artifacts.  We are not publishing unreleased apache code anywhere.
>
>Still not sure what the violation is.

I don't think there is a problem.  Let's push npm out so we can push out
the announcement.  If there is a problem it can be rectified.  This is
another example of why the board and mentors recommend that folks who want
to be sticklers about policy should be watching the commit lists and
raising issues early, not at the last minute where it delays the work of
the folks who are actually contributing code to the release.

"minor" policy issues should be investigated and presented in more detail
and in a collaborative fashion instead of accusing other PMC members.
There really shouldn't be a "you", it is a "we".

-Alex

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[OmPrakash Muppirala <bi...@gmail.com>]

The npm flexjs package is a thing on its own which points to only released
Apache artifacts.  We are not publishing unreleased apache code anywhere.

Still not sure what the violation is.

Thanks,
Om

On Tue, Sep 13, 2016 at 3:12 PM, Josh Tynjala <jo...@gmail.com> wrote:

> If that's the case, I guess we'll need to switch to using "npm pack" for
> testing NPM builds in the future. It produces an archive that is the same
> as what gets downloaded when a version is published to NPM's servers, but
> you can use it to install locally.
>
> Running the following command in the same directory as package.json creates
> a file like flexjs-0.7.0.tgz:
>
> npm pack
>
> Then you can use the regular npm install command to install it:
>
> npm install -g flexjs-0.7.0.tgz
>
> We'll have to figure out somewhere to upload this TGZ package for testing,
> since the configuration of different computers might accidentally produce
> different output.
>
> - Josh
>
> On Tue, Sep 13, 2016 at 2:52 PM, Justin Mclean <ju...@classsoftware.com>
> wrote:
>
> > Hi,
> >
> > > I have pushed the new bits as a pre-release to npm.
> >
> > Just a word of caution here, by doing this you are probably not in line
> > with ASF policy. I could point you to the usual links about release etc
> but
> > this discussion on the incubator list is recent and relevant. [1]
> >
> > Thanks,
> > Justin
> >
> > 1. https://lists.apache.org/thread.html/e5c17f08f30aa924bdfd50d215b3f4
> > 68269dc9198411b069d035a891@%3Cgeneral.incubator.apache.org%3E
>

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[Justin Mclean <ju...@classsoftware.com>]

Hi,

> If that's the case, I guess we'll need to switch to using "npm pack" for
> testing NPM builds in the future. It produces an archive that is the same
> as what gets downloaded when a version is published to NPM's servers, but
> you can use it to install locally.

That sounds like a good idea that was the package can be voted on at the same time as the other packages rather than after that vote has been taken. That was we also know that he contents will be identical to the voted on release.

Thanks,
Justin

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[Josh Tynjala <jo...@gmail.com>]

If that's the case, I guess we'll need to switch to using "npm pack" for
testing NPM builds in the future. It produces an archive that is the same
as what gets downloaded when a version is published to NPM's servers, but
you can use it to install locally.

Running the following command in the same directory as package.json creates
a file like flexjs-0.7.0.tgz:

npm pack

Then you can use the regular npm install command to install it:

npm install -g flexjs-0.7.0.tgz

We'll have to figure out somewhere to upload this TGZ package for testing,
since the configuration of different computers might accidentally produce
different output.

- Josh

On Tue, Sep 13, 2016 at 2:52 PM, Justin Mclean <ju...@classsoftware.com>
wrote:

> Hi,
>
> > I have pushed the new bits as a pre-release to npm.
>
> Just a word of caution here, by doing this you are probably not in line
> with ASF policy. I could point you to the usual links about release etc but
> this discussion on the incubator list is recent and relevant. [1]
>
> Thanks,
> Justin
>
> 1. https://lists.apache.org/thread.html/e5c17f08f30aa924bdfd50d215b3f4
> 68269dc9198411b069d035a891@%3Cgeneral.incubator.apache.org%3E

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[OmPrakash Muppirala <bi...@gmail.com>]

I read that thread and I don't see any obvious violation.  Can you please
expand on what you think is a violation?  How do you think we should fix
the said violation?

Thanks,
Om

On Tue, Sep 13, 2016 at 2:52 PM, Justin Mclean <ju...@classsoftware.com>
wrote:

> Hi,
>
> > I have pushed the new bits as a pre-release to npm.
>
> Just a word of caution here, by doing this you are probably not in line
> with ASF policy. I could point you to the usual links about release etc but
> this discussion on the incubator list is recent and relevant. [1]
>
> Thanks,
> Justin
>
> 1. https://lists.apache.org/thread.html/e5c17f08f30aa924bdfd50d215b3f4
> 68269dc9198411b069d035a891@%3Cgeneral.incubator.apache.org%3E

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[Justin Mclean <ju...@classsoftware.com>]

Hi,

> I have pushed the new bits as a pre-release to npm.

Just a word of caution here, by doing this you are probably not in line with ASF policy. I could point you to the usual links about release etc but this discussion on the incubator list is recent and relevant. [1]

Thanks,
Justin

1. https://lists.apache.org/thread.html/e5c17f08f30aa924bdfd50d215b3f468269dc9198411b069d035a891@%3Cgeneral.incubator.apache.org%3E

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[OmPrakash Muppirala <bi...@gmail.com>]

On Mon, Sep 12, 2016 at 4:44 PM, OmPrakash Muppirala <bi...@gmail.com>
wrote:

>
>
> On Mon, Sep 12, 2016 at 1:46 PM, Josh Tynjala <jo...@gmail.com>
> wrote:
>
>> Om, can you give my latest changes a try? I tweaked the NPM scripts to
>> actually run inside Node, which should clear up the cross-platform issues,
>> like requiring Cygwin on Windows. Additionally, I made the NPM scripts
>> launch the real scripts, so any changes should be picked up automatically
>> from now on.
>>
>> I tested on Mac, Windows in PowerShell, and Windows in cmd.exe.
>>
>
> Wow, this is awesome.  Will test soon :-)
>

Just tested it, everything works as promised on Cygwin, Cmd shell and on
PowerShell on Windows 7.
This is huge!  Thanks for getting this done.

I have pushed the new bits as a pre-release to npm.

If someone else wants to test, this is how to install:

*npm install flexjs@next*

I will wait 24 hours before I push this out to npm as a final release
package.

Thanks,
Om


>
> Thanks,
> Om
>
>
>>
>> - Josh
>>
>> On Sun, Sep 11, 2016 at 6:56 PM, Josh Tynjala <jo...@gmail.com>
>> wrote:
>>
>> > I hope to find a way to reuse the existing scripts in the next version.
>> I
>> > think that tweak I made recently to the NPM versions will help. When I
>> > expose asnodec, I'll play around with some ideas.
>> >
>> > - Josh
>> >
>> > On Sep 10, 2016 10:05 PM, "OmPrakash Muppirala" <bi...@gmail.com>
>> > wrote:
>> >
>> >> On Sep 10, 2016 9:39 AM, "Josh Tynjala" <jo...@gmail.com> wrote:
>> >> >
>> >> > Wait! There's one more thing with the NPM versions that need to be
>> >> changed.
>> >> > The last lines of asjscnpm, asjscompcnpm, and mxmlcnpm need to be
>> >> updated
>> >> > to match the changes in the regular versions.
>> >> >
>> >> > For instance, in asjsc:
>> >> >
>> >> > -external-library-path="$SCRIPT_HOME/../libs/js.swc"
>> >> >
>> >> > is replaced by
>> >> >
>> >> > +configname=js
>> >> >
>> >> > Exactly the same in asjscompc. It appears that mxmlc may have a
>> slightly
>> >> > different change.
>> >>
>> >> Gah! We need to figure a way to simply reuse the existing scripts
>> instead
>> >> if having to copy everything each time.
>> >>
>> >> Are you planning on fixing this?
>> >>
>> >> Thanks,
>> >> Om
>> >>
>> >> >
>> >> > - Josh
>> >> >
>> >> > On Sat, Sep 10, 2016 at 9:25 AM, Josh Tynjala <joshtynjala@gmail.com
>> >
>> >> wrote:
>> >> >
>> >> > > After installing flexjs@next from NPM, I can now successfully run
>> >> asjsc,
>> >> > > asjscompc, and mxmlc from the command line on Mac. The end-of-line
>> fix
>> >> > > appears to be working correctly.
>> >> > >
>> >> > > - Josh
>> >> > >
>> >> > > On Fri, Sep 9, 2016 at 7:08 PM, OmPrakash Muppirala <
>> >> bigosmallm@gmail.com>
>> >> > > wrote:
>> >> > >
>> >> > >> I just pushed flexjs 0.7.0 with a tag 'next'.  If someone can
>> test it
>> >> on a
>> >> > >> Mac and give me an all clear, I can go ahead and promote the
>> package
>> >> to a
>> >> > >> release.
>> >> > >>
>> >> > >> Run:
>> >> > >> *npm install flexjs@next -g *
>> >> > >> to test flexjs 0.7.0 npm package.
>> >> > >>
>> >> > >> Thanks,
>> >> > >> Om
>> >> > >>
>> >> > >> On Fri, Sep 9, 2016 at 2:31 PM, OmPrakash Muppirala <
>> >> bigosmallm@gmail.com
>> >> > >> >
>> >> > >> wrote:
>> >> > >>
>> >> > >> >
>> >> > >> >
>> >> > >> > On Fri, Sep 9, 2016 at 1:53 PM, Alex Harui <ah...@adobe.com>
>> >> wrote:
>> >> > >> >
>> >> > >> >> Please comment on the draft below.  We need Om or someone to
>> >> publish
>> >> > >> the
>> >> > >> >> npm module.
>> >> > >> >>
>> >> > >> >
>> >> > >> > On it.
>> >> > >> >
>> >> > >> > Thanks,
>> >> > >> > Om
>> >> > >> >
>> >> > >> >
>> >> > >> >>
>> >> > >> >> -----------
>> >> > >> >>
>> >> > >> >> The Apache Flex community is pleased to announce the release of
>> >> Apache
>> >> > >> >> FlexJS SDK 0.7.0 and Apache Flex FalconJX Compiler 0.7.0.
>> >> > >> >>
>> >> > >> >> Apache Flex is a highly productive, open source application
>> >> framework
>> >> > >> for
>> >> > >> >> building and maintaining expressive applications that deploy
>> >> > >> consistently
>> >> > >> >> on all major browsers, desktops and devices (including
>> >> smartphones,
>> >> > >> >> tablets and tv).
>> >> > >> >>
>> >> > >> >> Apache FlexJS is a next-generation Flex SDK that enables
>> >> developers
>> >> to
>> >> > >> use
>> >> > >> >> MXML and ActionScript to not only create SWFs but also
>> >> cross-compile
>> >> > >> the
>> >> > >> >> same MXML and ActionScript to HTML/JS/CSS so applications can
>> run
>> >> > >> natively
>> >> > >> >> in browsers.  The cross-compiled code can also be used in
>> Apache
>> >> > >> Cordova
>> >> > >> >> (Adobe PhoneGap) mobile applications.
>> >> > >> >>
>> >> > >> >> Apache Flex FalconJX is a next-generation MXML and ActionScript
>> >> > >> >> cross-compiler.  It extends the next-generation SWF compiler
>> known
>> >> as
>> >> > >> >> Falcon.  Both are contained in the release package and are
>> used by
>> >> the
>> >> > >> >> FlexJS package to compile SWFs or cross-compile to HTML/JS/CSS.
>> >> > >> >>
>> >> > >> >> This is the fifth release of FlexJS and FalconJX.  It is ‘beta'
>> >> > >> >> quality.  In this release, all of the compiler JARs and
>> framework
>> >> SWCs
>> >> > >> are
>> >> > >> >> also available as Maven artifacts making it the first version
>> of
>> >> any
>> >> > >> Flex
>> >> > >> >> SDK to support Maven.  Maven can even be used to build the
>> sources
>> >> and
>> >> > >> >> examples.  See the various pom.xml files included in the
>> >> artifacts.
>> >> > >> >>
>> >> > >> >> In addition, the JS output also includes source maps so you can
>> >> see
>> >> > >> your
>> >> > >> >> ActionScript source in the browser debugger.  Also, there is
>> more
>> >> > >> support
>> >> > >> >> for using ActionScript to create NodeJS modules, and you can
>> now
>> >> use a
>> >> > >> >> subset of E4X in your cross-compiled applications.  See the
>> >> > >> RELEASE_NOTES
>> >> > >> >> files in the artifacts for more information.
>> >> > >> >>
>> >> > >> >> The purpose of this release is to gather feedback about the
>> >> > >> >> features and implementation strategies, and recruit new
>> >> contributors
>> >> > >> as we
>> >> > >> >> grow these code bases into an SDK and tool chain that delivers
>> the
>> >> > >> highest
>> >> > >> >> productivity developing applications that can run in the most
>> >> places.
>> >> > >> >> These releases may not handle production needs.  Expect lots of
>> >> bugs
>> >> > >> and
>> >> > >> >> missing features.  Please file bugs at:
>> >> > >> >>
>> >> > >> >> https://issues.apache.org/jira/browse/FLEX/
>> >> > >> >>
>> >> > >> >> For questions about how to use FlexJS and FalconJX, send email
>> to
>> >> > >> >> users@flex.apache.org.  Please try to prefix the subject with
>> >> > >> [FlexJS] or
>> >> > >> >> [FalconJX] so it is clear the questions refer to this release
>> and
>> >> not
>> >> > >> the
>> >> > >> >> Flex SDK and MXMLC compiler.
>> >> > >> >>
>> >> > >> >> For questions and feedback on the development of the source
>> code
>> >> in
>> >> > >> these
>> >> > >> >> release, send email to dev@flex.apache.org.  Again, please
>> prefix
>> >> the
>> >> > >> >> subject with [FlexJS] or [FalconJX].
>> >> > >> >>
>> >> > >> >> Apache FlexJS and Apache Flex FalconJX are available in source
>> and
>> >> > >> binary
>> >> > >> >> form from the following download page:
>> >> > >> >> http://flex.apache.org/download-flexjs.html
>> >> > >> >>
>> >> > >> >> When downloading from a mirror site, please remember to verify
>> the
>> >> > >> >> downloads using signatures or MD5 hashes.
>> >> > >> >>
>> >> > >> >> A simple way to try these releases is to use the
>> >> > >> >> InstallApacheFlex 3.1 or 3.2 application which is available at
>> the
>> >> > >> >> following url:
>> >> > >> >> http://flex.apache.org/installer.html
>> >> > >> >>
>> >> > >> >> Choose Apache FlexJS 0.7.0 and it will create an Adobe Flash
>> >> > >> >> Builder-compatible SDK that uses the Falcon and FalconJX
>> compilers
>> >> to
>> >> > >> >> generate SWFs and HTML/JS/CSS output.  You can also use FDT as
>> >> your
>> >> IDE
>> >> > >> >> for developing FlexJS applications.  Some folks have been
>> >> successful
>> >> > >> >> using IntelliJ, FlashDevelop as well.  Moonshine is also
>> working
>> >> on
>> >> > >> >> FlexJS support.
>> >> > >> >>
>> >> > >> >> Apache FlexJS 0.7.0 is also available as a npm package. On a
>> >> system
>> >> > >> with
>> >> > >> >> npm installed, users can easily install FlexJS with the
>> command:
>> >> "npm
>> >> > >> >> install flexjs -g".
>> >> > >> >>
>> >> > >> >> See the README or the FlexJS wiki for more information.  The
>> >> FlexJS
>> >> > >> >> section of the wiki is at the following
>> >> > >> >>
>> >> > >> >> url:
>> >> > >> >> https://cwiki.apache.org/confluence/display/FLEX/FlexJS
>> >> > >> >>
>> >> > >> >> For more information on Apache Flex, visit the project home
>> page:
>> >> > >> >> http://flex.apache.org
>> >> > >> >>
>> >> > >> >> Please try FlexJS and become involved in shaping the future of
>> >> Flex.
>> >> > >> >>
>> >> > >> >> The Apache Flex Community
>> >> > >> >>
>> >> > >> >>
>> >> > >> >>
>> >> > >> >>
>> >> > >> >
>> >> > >>
>> >> > >
>> >> > >
>> >>
>> >
>>
>
>

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[Alex Harui <ah...@adobe.com>]

On 9/13/16, 2:03 AM, "Harbs" <ha...@gmail.com> wrote:

>One thing I noticed is that JIRA has not been updated to the fact that
>there’s a 0.7.0 release.

Thanks for the reminder.  I updated JIRA.

>
>On Sep 13, 2016, at 10:10 AM, Christofer Dutz <ch...@c-ware.de>
>wrote:
>
>> So what's the status on releasing? I would like to start promoting the
>>Maven release ...

AIUI, we are waiting on tuning up the npm module before sending the
announcement.  I don't know of any reason you can't do other promoting, so
feel free to spread the word.

-Alex

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[Harbs <ha...@gmail.com>]

One thing I noticed is that JIRA has not been updated to the fact that there’s a 0.7.0 release.

On Sep 13, 2016, at 10:10 AM, Christofer Dutz <ch...@c-ware.de> wrote:

> So what's the status on releasing? I would like to start promoting the Maven release ...
> 
> 
> Chris
> 
> ________________________________
> Von: omuppi1@gmail.com <om...@gmail.com> im Auftrag von OmPrakash Muppirala <bi...@gmail.com>
> Gesendet: Dienstag, 13. September 2016 01:44:45
> An: dev@flex.apache.org
> Betreff: Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released
> 
> On Mon, Sep 12, 2016 at 1:46 PM, Josh Tynjala <jo...@gmail.com> wrote:
> 
>> Om, can you give my latest changes a try? I tweaked the NPM scripts to
>> actually run inside Node, which should clear up the cross-platform issues,
>> like requiring Cygwin on Windows. Additionally, I made the NPM scripts
>> launch the real scripts, so any changes should be picked up automatically
>> from now on.
>> 
>> I tested on Mac, Windows in PowerShell, and Windows in cmd.exe.
>> 
> 
> Wow, this is awesome.  Will test soon :-)
> 
> Thanks,
> Om
> 
> 
>> 
>> - Josh
>> 
>> On Sun, Sep 11, 2016 at 6:56 PM, Josh Tynjala <jo...@gmail.com>
>> wrote:
>> 
>>> I hope to find a way to reuse the existing scripts in the next version. I
>>> think that tweak I made recently to the NPM versions will help. When I
>>> expose asnodec, I'll play around with some ideas.
>>> 
>>> - Josh
>>> 
>>> On Sep 10, 2016 10:05 PM, "OmPrakash Muppirala" <bi...@gmail.com>
>>> wrote:
>>> 
>>>> On Sep 10, 2016 9:39 AM, "Josh Tynjala" <jo...@gmail.com> wrote:
>>>>> 
>>>>> Wait! There's one more thing with the NPM versions that need to be
>>>> changed.
>>>>> The last lines of asjscnpm, asjscompcnpm, and mxmlcnpm need to be
>>>> updated
>>>>> to match the changes in the regular versions.
>>>>> 
>>>>> For instance, in asjsc:
>>>>> 
>>>>> -external-library-path="$SCRIPT_HOME/../libs/js.swc"
>>>>> 
>>>>> is replaced by
>>>>> 
>>>>> +configname=js
>>>>> 
>>>>> Exactly the same in asjscompc. It appears that mxmlc may have a
>> slightly
>>>>> different change.
>>>> 
>>>> Gah! We need to figure a way to simply reuse the existing scripts
>> instead
>>>> if having to copy everything each time.
>>>> 
>>>> Are you planning on fixing this?
>>>> 
>>>> Thanks,
>>>> Om
>>>> 
>>>>> 
>>>>> - Josh
>>>>> 
>>>>> On Sat, Sep 10, 2016 at 9:25 AM, Josh Tynjala <jo...@gmail.com>
>>>> wrote:
>>>>> 
>>>>>> After installing flexjs@next from NPM, I can now successfully run
>>>> asjsc,
>>>>>> asjscompc, and mxmlc from the command line on Mac. The end-of-line
>> fix
>>>>>> appears to be working correctly.
>>>>>> 
>>>>>> - Josh
>>>>>> 
>>>>>> On Fri, Sep 9, 2016 at 7:08 PM, OmPrakash Muppirala <
>>>> bigosmallm@gmail.com>
>>>>>> wrote:
>>>>>> 
>>>>>>> I just pushed flexjs 0.7.0 with a tag 'next'.  If someone can test
>> it
>>>> on a
>>>>>>> Mac and give me an all clear, I can go ahead and promote the
>> package
>>>> to a
>>>>>>> release.
>>>>>>> 
>>>>>>> Run:
>>>>>>> *npm install flexjs@next -g *
>>>>>>> to test flexjs 0.7.0 npm package.
>>>>>>> 
>>>>>>> Thanks,
>>>>>>> Om
>>>>>>> 
>>>>>>> On Fri, Sep 9, 2016 at 2:31 PM, OmPrakash Muppirala <
>>>> bigosmallm@gmail.com
>>>>>>>> 
>>>>>>> wrote:
>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> On Fri, Sep 9, 2016 at 1:53 PM, Alex Harui <ah...@adobe.com>
>>>> wrote:
>>>>>>>> 
>>>>>>>>> Please comment on the draft below.  We need Om or someone to
>>>> publish
>>>>>>> the
>>>>>>>>> npm module.
>>>>>>>>> 
>>>>>>>> 
>>>>>>>> On it.
>>>>>>>> 
>>>>>>>> Thanks,
>>>>>>>> Om
>>>>>>>> 
>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> -----------
>>>>>>>>> 
>>>>>>>>> The Apache Flex community is pleased to announce the release of
>>>> Apache
>>>>>>>>> FlexJS SDK 0.7.0 and Apache Flex FalconJX Compiler 0.7.0.
>>>>>>>>> 
>>>>>>>>> Apache Flex is a highly productive, open source application
>>>> framework
>>>>>>> for
>>>>>>>>> building and maintaining expressive applications that deploy
>>>>>>> consistently
>>>>>>>>> on all major browsers, desktops and devices (including
>>>> smartphones,
>>>>>>>>> tablets and tv).
>>>>>>>>> 
>>>>>>>>> Apache FlexJS is a next-generation Flex SDK that enables
>>>> developers
>>>> to
>>>>>>> use
>>>>>>>>> MXML and ActionScript to not only create SWFs but also
>>>> cross-compile
>>>>>>> the
>>>>>>>>> same MXML and ActionScript to HTML/JS/CSS so applications can
>> run
>>>>>>> natively
>>>>>>>>> in browsers.  The cross-compiled code can also be used in Apache
>>>>>>> Cordova
>>>>>>>>> (Adobe PhoneGap) mobile applications.
>>>>>>>>> 
>>>>>>>>> Apache Flex FalconJX is a next-generation MXML and ActionScript
>>>>>>>>> cross-compiler.  It extends the next-generation SWF compiler
>> known
>>>> as
>>>>>>>>> Falcon.  Both are contained in the release package and are used
>> by
>>>> the
>>>>>>>>> FlexJS package to compile SWFs or cross-compile to HTML/JS/CSS.
>>>>>>>>> 
>>>>>>>>> This is the fifth release of FlexJS and FalconJX.  It is ‘beta'
>>>>>>>>> quality.  In this release, all of the compiler JARs and
>> framework
>>>> SWCs
>>>>>>> are
>>>>>>>>> also available as Maven artifacts making it the first version of
>>>> any
>>>>>>> Flex
>>>>>>>>> SDK to support Maven.  Maven can even be used to build the
>> sources
>>>> and
>>>>>>>>> examples.  See the various pom.xml files included in the
>>>> artifacts.
>>>>>>>>> 
>>>>>>>>> In addition, the JS output also includes source maps so you can
>>>> see
>>>>>>> your
>>>>>>>>> ActionScript source in the browser debugger.  Also, there is
>> more
>>>>>>> support
>>>>>>>>> for using ActionScript to create NodeJS modules, and you can now
>>>> use a
>>>>>>>>> subset of E4X in your cross-compiled applications.  See the
>>>>>>> RELEASE_NOTES
>>>>>>>>> files in the artifacts for more information.
>>>>>>>>> 
>>>>>>>>> The purpose of this release is to gather feedback about the
>>>>>>>>> features and implementation strategies, and recruit new
>>>> contributors
>>>>>>> as we
>>>>>>>>> grow these code bases into an SDK and tool chain that delivers
>> the
>>>>>>> highest
>>>>>>>>> productivity developing applications that can run in the most
>>>> places.
>>>>>>>>> These releases may not handle production needs.  Expect lots of
>>>> bugs
>>>>>>> and
>>>>>>>>> missing features.  Please file bugs at:
>>>>>>>>> 
>>>>>>>>> https://issues.apache.org/jira/browse/FLEX/
>>>>>>>>> 
>>>>>>>>> For questions about how to use FlexJS and FalconJX, send email
>> to
>>>>>>>>> users@flex.apache.org.  Please try to prefix the subject with
>>>>>>> [FlexJS] or
>>>>>>>>> [FalconJX] so it is clear the questions refer to this release
>> and
>>>> not
>>>>>>> the
>>>>>>>>> Flex SDK and MXMLC compiler.
>>>>>>>>> 
>>>>>>>>> For questions and feedback on the development of the source code
>>>> in
>>>>>>> these
>>>>>>>>> release, send email to dev@flex.apache.org.  Again, please
>> prefix
>>>> the
>>>>>>>>> subject with [FlexJS] or [FalconJX].
>>>>>>>>> 
>>>>>>>>> Apache FlexJS and Apache Flex FalconJX are available in source
>> and
>>>>>>> binary
>>>>>>>>> form from the following download page:
>>>>>>>>> http://flex.apache.org/download-flexjs.html
>>>>>>>>> 
>>>>>>>>> When downloading from a mirror site, please remember to verify
>> the
>>>>>>>>> downloads using signatures or MD5 hashes.
>>>>>>>>> 
>>>>>>>>> A simple way to try these releases is to use the
>>>>>>>>> InstallApacheFlex 3.1 or 3.2 application which is available at
>> the
>>>>>>>>> following url:
>>>>>>>>> http://flex.apache.org/installer.html
>>>>>>>>> 
>>>>>>>>> Choose Apache FlexJS 0.7.0 and it will create an Adobe Flash
>>>>>>>>> Builder-compatible SDK that uses the Falcon and FalconJX
>> compilers
>>>> to
>>>>>>>>> generate SWFs and HTML/JS/CSS output.  You can also use FDT as
>>>> your
>>>> IDE
>>>>>>>>> for developing FlexJS applications.  Some folks have been
>>>> successful
>>>>>>>>> using IntelliJ, FlashDevelop as well.  Moonshine is also working
>>>> on
>>>>>>>>> FlexJS support.
>>>>>>>>> 
>>>>>>>>> Apache FlexJS 0.7.0 is also available as a npm package. On a
>>>> system
>>>>>>> with
>>>>>>>>> npm installed, users can easily install FlexJS with the command:
>>>> "npm
>>>>>>>>> install flexjs -g".
>>>>>>>>> 
>>>>>>>>> See the README or the FlexJS wiki for more information.  The
>>>> FlexJS
>>>>>>>>> section of the wiki is at the following
>>>>>>>>> 
>>>>>>>>> url:
>>>>>>>>> https://cwiki.apache.org/confluence/display/FLEX/FlexJS
>>>>>>>>> 
>>>>>>>>> For more information on Apache Flex, visit the project home
>> page:
>>>>>>>>> http://flex.apache.org
>>>>>>>>> 
>>>>>>>>> Please try FlexJS and become involved in shaping the future of
>>>> Flex.
>>>>>>>>> 
>>>>>>>>> The Apache Flex Community
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>>> 
>>>> 
>>> 
>> 

AW: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[Christofer Dutz <ch...@c-ware.de>]

So what's the status on releasing? I would like to start promoting the Maven release ...


Chris

________________________________
Von: omuppi1@gmail.com <om...@gmail.com> im Auftrag von OmPrakash Muppirala <bi...@gmail.com>
Gesendet: Dienstag, 13. September 2016 01:44:45
An: dev@flex.apache.org
Betreff: Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

On Mon, Sep 12, 2016 at 1:46 PM, Josh Tynjala <jo...@gmail.com> wrote:

> Om, can you give my latest changes a try? I tweaked the NPM scripts to
> actually run inside Node, which should clear up the cross-platform issues,
> like requiring Cygwin on Windows. Additionally, I made the NPM scripts
> launch the real scripts, so any changes should be picked up automatically
> from now on.
>
> I tested on Mac, Windows in PowerShell, and Windows in cmd.exe.
>

Wow, this is awesome.  Will test soon :-)

Thanks,
Om


>
> - Josh
>
> On Sun, Sep 11, 2016 at 6:56 PM, Josh Tynjala <jo...@gmail.com>
> wrote:
>
> > I hope to find a way to reuse the existing scripts in the next version. I
> > think that tweak I made recently to the NPM versions will help. When I
> > expose asnodec, I'll play around with some ideas.
> >
> > - Josh
> >
> > On Sep 10, 2016 10:05 PM, "OmPrakash Muppirala" <bi...@gmail.com>
> > wrote:
> >
> >> On Sep 10, 2016 9:39 AM, "Josh Tynjala" <jo...@gmail.com> wrote:
> >> >
> >> > Wait! There's one more thing with the NPM versions that need to be
> >> changed.
> >> > The last lines of asjscnpm, asjscompcnpm, and mxmlcnpm need to be
> >> updated
> >> > to match the changes in the regular versions.
> >> >
> >> > For instance, in asjsc:
> >> >
> >> > -external-library-path="$SCRIPT_HOME/../libs/js.swc"
> >> >
> >> > is replaced by
> >> >
> >> > +configname=js
> >> >
> >> > Exactly the same in asjscompc. It appears that mxmlc may have a
> slightly
> >> > different change.
> >>
> >> Gah! We need to figure a way to simply reuse the existing scripts
> instead
> >> if having to copy everything each time.
> >>
> >> Are you planning on fixing this?
> >>
> >> Thanks,
> >> Om
> >>
> >> >
> >> > - Josh
> >> >
> >> > On Sat, Sep 10, 2016 at 9:25 AM, Josh Tynjala <jo...@gmail.com>
> >> wrote:
> >> >
> >> > > After installing flexjs@next from NPM, I can now successfully run
> >> asjsc,
> >> > > asjscompc, and mxmlc from the command line on Mac. The end-of-line
> fix
> >> > > appears to be working correctly.
> >> > >
> >> > > - Josh
> >> > >
> >> > > On Fri, Sep 9, 2016 at 7:08 PM, OmPrakash Muppirala <
> >> bigosmallm@gmail.com>
> >> > > wrote:
> >> > >
> >> > >> I just pushed flexjs 0.7.0 with a tag 'next'.  If someone can test
> it
> >> on a
> >> > >> Mac and give me an all clear, I can go ahead and promote the
> package
> >> to a
> >> > >> release.
> >> > >>
> >> > >> Run:
> >> > >> *npm install flexjs@next -g *
> >> > >> to test flexjs 0.7.0 npm package.
> >> > >>
> >> > >> Thanks,
> >> > >> Om
> >> > >>
> >> > >> On Fri, Sep 9, 2016 at 2:31 PM, OmPrakash Muppirala <
> >> bigosmallm@gmail.com
> >> > >> >
> >> > >> wrote:
> >> > >>
> >> > >> >
> >> > >> >
> >> > >> > On Fri, Sep 9, 2016 at 1:53 PM, Alex Harui <ah...@adobe.com>
> >> wrote:
> >> > >> >
> >> > >> >> Please comment on the draft below.  We need Om or someone to
> >> publish
> >> > >> the
> >> > >> >> npm module.
> >> > >> >>
> >> > >> >
> >> > >> > On it.
> >> > >> >
> >> > >> > Thanks,
> >> > >> > Om
> >> > >> >
> >> > >> >
> >> > >> >>
> >> > >> >> -----------
> >> > >> >>
> >> > >> >> The Apache Flex community is pleased to announce the release of
> >> Apache
> >> > >> >> FlexJS SDK 0.7.0 and Apache Flex FalconJX Compiler 0.7.0.
> >> > >> >>
> >> > >> >> Apache Flex is a highly productive, open source application
> >> framework
> >> > >> for
> >> > >> >> building and maintaining expressive applications that deploy
> >> > >> consistently
> >> > >> >> on all major browsers, desktops and devices (including
> >> smartphones,
> >> > >> >> tablets and tv).
> >> > >> >>
> >> > >> >> Apache FlexJS is a next-generation Flex SDK that enables
> >> developers
> >> to
> >> > >> use
> >> > >> >> MXML and ActionScript to not only create SWFs but also
> >> cross-compile
> >> > >> the
> >> > >> >> same MXML and ActionScript to HTML/JS/CSS so applications can
> run
> >> > >> natively
> >> > >> >> in browsers.  The cross-compiled code can also be used in Apache
> >> > >> Cordova
> >> > >> >> (Adobe PhoneGap) mobile applications.
> >> > >> >>
> >> > >> >> Apache Flex FalconJX is a next-generation MXML and ActionScript
> >> > >> >> cross-compiler.  It extends the next-generation SWF compiler
> known
> >> as
> >> > >> >> Falcon.  Both are contained in the release package and are used
> by
> >> the
> >> > >> >> FlexJS package to compile SWFs or cross-compile to HTML/JS/CSS.
> >> > >> >>
> >> > >> >> This is the fifth release of FlexJS and FalconJX.  It is ‘beta'
> >> > >> >> quality.  In this release, all of the compiler JARs and
> framework
> >> SWCs
> >> > >> are
> >> > >> >> also available as Maven artifacts making it the first version of
> >> any
> >> > >> Flex
> >> > >> >> SDK to support Maven.  Maven can even be used to build the
> sources
> >> and
> >> > >> >> examples.  See the various pom.xml files included in the
> >> artifacts.
> >> > >> >>
> >> > >> >> In addition, the JS output also includes source maps so you can
> >> see
> >> > >> your
> >> > >> >> ActionScript source in the browser debugger.  Also, there is
> more
> >> > >> support
> >> > >> >> for using ActionScript to create NodeJS modules, and you can now
> >> use a
> >> > >> >> subset of E4X in your cross-compiled applications.  See the
> >> > >> RELEASE_NOTES
> >> > >> >> files in the artifacts for more information.
> >> > >> >>
> >> > >> >> The purpose of this release is to gather feedback about the
> >> > >> >> features and implementation strategies, and recruit new
> >> contributors
> >> > >> as we
> >> > >> >> grow these code bases into an SDK and tool chain that delivers
> the
> >> > >> highest
> >> > >> >> productivity developing applications that can run in the most
> >> places.
> >> > >> >> These releases may not handle production needs.  Expect lots of
> >> bugs
> >> > >> and
> >> > >> >> missing features.  Please file bugs at:
> >> > >> >>
> >> > >> >> https://issues.apache.org/jira/browse/FLEX/
> >> > >> >>
> >> > >> >> For questions about how to use FlexJS and FalconJX, send email
> to
> >> > >> >> users@flex.apache.org.  Please try to prefix the subject with
> >> > >> [FlexJS] or
> >> > >> >> [FalconJX] so it is clear the questions refer to this release
> and
> >> not
> >> > >> the
> >> > >> >> Flex SDK and MXMLC compiler.
> >> > >> >>
> >> > >> >> For questions and feedback on the development of the source code
> >> in
> >> > >> these
> >> > >> >> release, send email to dev@flex.apache.org.  Again, please
> prefix
> >> the
> >> > >> >> subject with [FlexJS] or [FalconJX].
> >> > >> >>
> >> > >> >> Apache FlexJS and Apache Flex FalconJX are available in source
> and
> >> > >> binary
> >> > >> >> form from the following download page:
> >> > >> >> http://flex.apache.org/download-flexjs.html
> >> > >> >>
> >> > >> >> When downloading from a mirror site, please remember to verify
> the
> >> > >> >> downloads using signatures or MD5 hashes.
> >> > >> >>
> >> > >> >> A simple way to try these releases is to use the
> >> > >> >> InstallApacheFlex 3.1 or 3.2 application which is available at
> the
> >> > >> >> following url:
> >> > >> >> http://flex.apache.org/installer.html
> >> > >> >>
> >> > >> >> Choose Apache FlexJS 0.7.0 and it will create an Adobe Flash
> >> > >> >> Builder-compatible SDK that uses the Falcon and FalconJX
> compilers
> >> to
> >> > >> >> generate SWFs and HTML/JS/CSS output.  You can also use FDT as
> >> your
> >> IDE
> >> > >> >> for developing FlexJS applications.  Some folks have been
> >> successful
> >> > >> >> using IntelliJ, FlashDevelop as well.  Moonshine is also working
> >> on
> >> > >> >> FlexJS support.
> >> > >> >>
> >> > >> >> Apache FlexJS 0.7.0 is also available as a npm package. On a
> >> system
> >> > >> with
> >> > >> >> npm installed, users can easily install FlexJS with the command:
> >> "npm
> >> > >> >> install flexjs -g".
> >> > >> >>
> >> > >> >> See the README or the FlexJS wiki for more information.  The
> >> FlexJS
> >> > >> >> section of the wiki is at the following
> >> > >> >>
> >> > >> >> url:
> >> > >> >> https://cwiki.apache.org/confluence/display/FLEX/FlexJS
> >> > >> >>
> >> > >> >> For more information on Apache Flex, visit the project home
> page:
> >> > >> >> http://flex.apache.org
> >> > >> >>
> >> > >> >> Please try FlexJS and become involved in shaping the future of
> >> Flex.
> >> > >> >>
> >> > >> >> The Apache Flex Community
> >> > >> >>
> >> > >> >>
> >> > >> >>
> >> > >> >>
> >> > >> >
> >> > >>
> >> > >
> >> > >
> >>
> >
>

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[OmPrakash Muppirala <bi...@gmail.com>]

On Mon, Sep 12, 2016 at 1:46 PM, Josh Tynjala <jo...@gmail.com> wrote:

> Om, can you give my latest changes a try? I tweaked the NPM scripts to
> actually run inside Node, which should clear up the cross-platform issues,
> like requiring Cygwin on Windows. Additionally, I made the NPM scripts
> launch the real scripts, so any changes should be picked up automatically
> from now on.
>
> I tested on Mac, Windows in PowerShell, and Windows in cmd.exe.
>

Wow, this is awesome.  Will test soon :-)

Thanks,
Om


>
> - Josh
>
> On Sun, Sep 11, 2016 at 6:56 PM, Josh Tynjala <jo...@gmail.com>
> wrote:
>
> > I hope to find a way to reuse the existing scripts in the next version. I
> > think that tweak I made recently to the NPM versions will help. When I
> > expose asnodec, I'll play around with some ideas.
> >
> > - Josh
> >
> > On Sep 10, 2016 10:05 PM, "OmPrakash Muppirala" <bi...@gmail.com>
> > wrote:
> >
> >> On Sep 10, 2016 9:39 AM, "Josh Tynjala" <jo...@gmail.com> wrote:
> >> >
> >> > Wait! There's one more thing with the NPM versions that need to be
> >> changed.
> >> > The last lines of asjscnpm, asjscompcnpm, and mxmlcnpm need to be
> >> updated
> >> > to match the changes in the regular versions.
> >> >
> >> > For instance, in asjsc:
> >> >
> >> > -external-library-path="$SCRIPT_HOME/../libs/js.swc"
> >> >
> >> > is replaced by
> >> >
> >> > +configname=js
> >> >
> >> > Exactly the same in asjscompc. It appears that mxmlc may have a
> slightly
> >> > different change.
> >>
> >> Gah! We need to figure a way to simply reuse the existing scripts
> instead
> >> if having to copy everything each time.
> >>
> >> Are you planning on fixing this?
> >>
> >> Thanks,
> >> Om
> >>
> >> >
> >> > - Josh
> >> >
> >> > On Sat, Sep 10, 2016 at 9:25 AM, Josh Tynjala <jo...@gmail.com>
> >> wrote:
> >> >
> >> > > After installing flexjs@next from NPM, I can now successfully run
> >> asjsc,
> >> > > asjscompc, and mxmlc from the command line on Mac. The end-of-line
> fix
> >> > > appears to be working correctly.
> >> > >
> >> > > - Josh
> >> > >
> >> > > On Fri, Sep 9, 2016 at 7:08 PM, OmPrakash Muppirala <
> >> bigosmallm@gmail.com>
> >> > > wrote:
> >> > >
> >> > >> I just pushed flexjs 0.7.0 with a tag 'next'.  If someone can test
> it
> >> on a
> >> > >> Mac and give me an all clear, I can go ahead and promote the
> package
> >> to a
> >> > >> release.
> >> > >>
> >> > >> Run:
> >> > >> *npm install flexjs@next -g *
> >> > >> to test flexjs 0.7.0 npm package.
> >> > >>
> >> > >> Thanks,
> >> > >> Om
> >> > >>
> >> > >> On Fri, Sep 9, 2016 at 2:31 PM, OmPrakash Muppirala <
> >> bigosmallm@gmail.com
> >> > >> >
> >> > >> wrote:
> >> > >>
> >> > >> >
> >> > >> >
> >> > >> > On Fri, Sep 9, 2016 at 1:53 PM, Alex Harui <ah...@adobe.com>
> >> wrote:
> >> > >> >
> >> > >> >> Please comment on the draft below.  We need Om or someone to
> >> publish
> >> > >> the
> >> > >> >> npm module.
> >> > >> >>
> >> > >> >
> >> > >> > On it.
> >> > >> >
> >> > >> > Thanks,
> >> > >> > Om
> >> > >> >
> >> > >> >
> >> > >> >>
> >> > >> >> -----------
> >> > >> >>
> >> > >> >> The Apache Flex community is pleased to announce the release of
> >> Apache
> >> > >> >> FlexJS SDK 0.7.0 and Apache Flex FalconJX Compiler 0.7.0.
> >> > >> >>
> >> > >> >> Apache Flex is a highly productive, open source application
> >> framework
> >> > >> for
> >> > >> >> building and maintaining expressive applications that deploy
> >> > >> consistently
> >> > >> >> on all major browsers, desktops and devices (including
> >> smartphones,
> >> > >> >> tablets and tv).
> >> > >> >>
> >> > >> >> Apache FlexJS is a next-generation Flex SDK that enables
> >> developers
> >> to
> >> > >> use
> >> > >> >> MXML and ActionScript to not only create SWFs but also
> >> cross-compile
> >> > >> the
> >> > >> >> same MXML and ActionScript to HTML/JS/CSS so applications can
> run
> >> > >> natively
> >> > >> >> in browsers.  The cross-compiled code can also be used in Apache
> >> > >> Cordova
> >> > >> >> (Adobe PhoneGap) mobile applications.
> >> > >> >>
> >> > >> >> Apache Flex FalconJX is a next-generation MXML and ActionScript
> >> > >> >> cross-compiler.  It extends the next-generation SWF compiler
> known
> >> as
> >> > >> >> Falcon.  Both are contained in the release package and are used
> by
> >> the
> >> > >> >> FlexJS package to compile SWFs or cross-compile to HTML/JS/CSS.
> >> > >> >>
> >> > >> >> This is the fifth release of FlexJS and FalconJX.  It is ‘beta'
> >> > >> >> quality.  In this release, all of the compiler JARs and
> framework
> >> SWCs
> >> > >> are
> >> > >> >> also available as Maven artifacts making it the first version of
> >> any
> >> > >> Flex
> >> > >> >> SDK to support Maven.  Maven can even be used to build the
> sources
> >> and
> >> > >> >> examples.  See the various pom.xml files included in the
> >> artifacts.
> >> > >> >>
> >> > >> >> In addition, the JS output also includes source maps so you can
> >> see
> >> > >> your
> >> > >> >> ActionScript source in the browser debugger.  Also, there is
> more
> >> > >> support
> >> > >> >> for using ActionScript to create NodeJS modules, and you can now
> >> use a
> >> > >> >> subset of E4X in your cross-compiled applications.  See the
> >> > >> RELEASE_NOTES
> >> > >> >> files in the artifacts for more information.
> >> > >> >>
> >> > >> >> The purpose of this release is to gather feedback about the
> >> > >> >> features and implementation strategies, and recruit new
> >> contributors
> >> > >> as we
> >> > >> >> grow these code bases into an SDK and tool chain that delivers
> the
> >> > >> highest
> >> > >> >> productivity developing applications that can run in the most
> >> places.
> >> > >> >> These releases may not handle production needs.  Expect lots of
> >> bugs
> >> > >> and
> >> > >> >> missing features.  Please file bugs at:
> >> > >> >>
> >> > >> >> https://issues.apache.org/jira/browse/FLEX/
> >> > >> >>
> >> > >> >> For questions about how to use FlexJS and FalconJX, send email
> to
> >> > >> >> users@flex.apache.org.  Please try to prefix the subject with
> >> > >> [FlexJS] or
> >> > >> >> [FalconJX] so it is clear the questions refer to this release
> and
> >> not
> >> > >> the
> >> > >> >> Flex SDK and MXMLC compiler.
> >> > >> >>
> >> > >> >> For questions and feedback on the development of the source code
> >> in
> >> > >> these
> >> > >> >> release, send email to dev@flex.apache.org.  Again, please
> prefix
> >> the
> >> > >> >> subject with [FlexJS] or [FalconJX].
> >> > >> >>
> >> > >> >> Apache FlexJS and Apache Flex FalconJX are available in source
> and
> >> > >> binary
> >> > >> >> form from the following download page:
> >> > >> >> http://flex.apache.org/download-flexjs.html
> >> > >> >>
> >> > >> >> When downloading from a mirror site, please remember to verify
> the
> >> > >> >> downloads using signatures or MD5 hashes.
> >> > >> >>
> >> > >> >> A simple way to try these releases is to use the
> >> > >> >> InstallApacheFlex 3.1 or 3.2 application which is available at
> the
> >> > >> >> following url:
> >> > >> >> http://flex.apache.org/installer.html
> >> > >> >>
> >> > >> >> Choose Apache FlexJS 0.7.0 and it will create an Adobe Flash
> >> > >> >> Builder-compatible SDK that uses the Falcon and FalconJX
> compilers
> >> to
> >> > >> >> generate SWFs and HTML/JS/CSS output.  You can also use FDT as
> >> your
> >> IDE
> >> > >> >> for developing FlexJS applications.  Some folks have been
> >> successful
> >> > >> >> using IntelliJ, FlashDevelop as well.  Moonshine is also working
> >> on
> >> > >> >> FlexJS support.
> >> > >> >>
> >> > >> >> Apache FlexJS 0.7.0 is also available as a npm package. On a
> >> system
> >> > >> with
> >> > >> >> npm installed, users can easily install FlexJS with the command:
> >> "npm
> >> > >> >> install flexjs -g".
> >> > >> >>
> >> > >> >> See the README or the FlexJS wiki for more information.  The
> >> FlexJS
> >> > >> >> section of the wiki is at the following
> >> > >> >>
> >> > >> >> url:
> >> > >> >> https://cwiki.apache.org/confluence/display/FLEX/FlexJS
> >> > >> >>
> >> > >> >> For more information on Apache Flex, visit the project home
> page:
> >> > >> >> http://flex.apache.org
> >> > >> >>
> >> > >> >> Please try FlexJS and become involved in shaping the future of
> >> Flex.
> >> > >> >>
> >> > >> >> The Apache Flex Community
> >> > >> >>
> >> > >> >>
> >> > >> >>
> >> > >> >>
> >> > >> >
> >> > >>
> >> > >
> >> > >
> >>
> >
>

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[Josh Tynjala <jo...@gmail.com>]

Om, can you give my latest changes a try? I tweaked the NPM scripts to
actually run inside Node, which should clear up the cross-platform issues,
like requiring Cygwin on Windows. Additionally, I made the NPM scripts
launch the real scripts, so any changes should be picked up automatically
from now on.

I tested on Mac, Windows in PowerShell, and Windows in cmd.exe.

- Josh

On Sun, Sep 11, 2016 at 6:56 PM, Josh Tynjala <jo...@gmail.com> wrote:

> I hope to find a way to reuse the existing scripts in the next version. I
> think that tweak I made recently to the NPM versions will help. When I
> expose asnodec, I'll play around with some ideas.
>
> - Josh
>
> On Sep 10, 2016 10:05 PM, "OmPrakash Muppirala" <bi...@gmail.com>
> wrote:
>
>> On Sep 10, 2016 9:39 AM, "Josh Tynjala" <jo...@gmail.com> wrote:
>> >
>> > Wait! There's one more thing with the NPM versions that need to be
>> changed.
>> > The last lines of asjscnpm, asjscompcnpm, and mxmlcnpm need to be
>> updated
>> > to match the changes in the regular versions.
>> >
>> > For instance, in asjsc:
>> >
>> > -external-library-path="$SCRIPT_HOME/../libs/js.swc"
>> >
>> > is replaced by
>> >
>> > +configname=js
>> >
>> > Exactly the same in asjscompc. It appears that mxmlc may have a slightly
>> > different change.
>>
>> Gah! We need to figure a way to simply reuse the existing scripts instead
>> if having to copy everything each time.
>>
>> Are you planning on fixing this?
>>
>> Thanks,
>> Om
>>
>> >
>> > - Josh
>> >
>> > On Sat, Sep 10, 2016 at 9:25 AM, Josh Tynjala <jo...@gmail.com>
>> wrote:
>> >
>> > > After installing flexjs@next from NPM, I can now successfully run
>> asjsc,
>> > > asjscompc, and mxmlc from the command line on Mac. The end-of-line fix
>> > > appears to be working correctly.
>> > >
>> > > - Josh
>> > >
>> > > On Fri, Sep 9, 2016 at 7:08 PM, OmPrakash Muppirala <
>> bigosmallm@gmail.com>
>> > > wrote:
>> > >
>> > >> I just pushed flexjs 0.7.0 with a tag 'next'.  If someone can test it
>> on a
>> > >> Mac and give me an all clear, I can go ahead and promote the package
>> to a
>> > >> release.
>> > >>
>> > >> Run:
>> > >> *npm install flexjs@next -g *
>> > >> to test flexjs 0.7.0 npm package.
>> > >>
>> > >> Thanks,
>> > >> Om
>> > >>
>> > >> On Fri, Sep 9, 2016 at 2:31 PM, OmPrakash Muppirala <
>> bigosmallm@gmail.com
>> > >> >
>> > >> wrote:
>> > >>
>> > >> >
>> > >> >
>> > >> > On Fri, Sep 9, 2016 at 1:53 PM, Alex Harui <ah...@adobe.com>
>> wrote:
>> > >> >
>> > >> >> Please comment on the draft below.  We need Om or someone to
>> publish
>> > >> the
>> > >> >> npm module.
>> > >> >>
>> > >> >
>> > >> > On it.
>> > >> >
>> > >> > Thanks,
>> > >> > Om
>> > >> >
>> > >> >
>> > >> >>
>> > >> >> -----------
>> > >> >>
>> > >> >> The Apache Flex community is pleased to announce the release of
>> Apache
>> > >> >> FlexJS SDK 0.7.0 and Apache Flex FalconJX Compiler 0.7.0.
>> > >> >>
>> > >> >> Apache Flex is a highly productive, open source application
>> framework
>> > >> for
>> > >> >> building and maintaining expressive applications that deploy
>> > >> consistently
>> > >> >> on all major browsers, desktops and devices (including
>> smartphones,
>> > >> >> tablets and tv).
>> > >> >>
>> > >> >> Apache FlexJS is a next-generation Flex SDK that enables
>> developers
>> to
>> > >> use
>> > >> >> MXML and ActionScript to not only create SWFs but also
>> cross-compile
>> > >> the
>> > >> >> same MXML and ActionScript to HTML/JS/CSS so applications can run
>> > >> natively
>> > >> >> in browsers.  The cross-compiled code can also be used in Apache
>> > >> Cordova
>> > >> >> (Adobe PhoneGap) mobile applications.
>> > >> >>
>> > >> >> Apache Flex FalconJX is a next-generation MXML and ActionScript
>> > >> >> cross-compiler.  It extends the next-generation SWF compiler known
>> as
>> > >> >> Falcon.  Both are contained in the release package and are used by
>> the
>> > >> >> FlexJS package to compile SWFs or cross-compile to HTML/JS/CSS.
>> > >> >>
>> > >> >> This is the fifth release of FlexJS and FalconJX.  It is ‘beta'
>> > >> >> quality.  In this release, all of the compiler JARs and framework
>> SWCs
>> > >> are
>> > >> >> also available as Maven artifacts making it the first version of
>> any
>> > >> Flex
>> > >> >> SDK to support Maven.  Maven can even be used to build the sources
>> and
>> > >> >> examples.  See the various pom.xml files included in the
>> artifacts.
>> > >> >>
>> > >> >> In addition, the JS output also includes source maps so you can
>> see
>> > >> your
>> > >> >> ActionScript source in the browser debugger.  Also, there is more
>> > >> support
>> > >> >> for using ActionScript to create NodeJS modules, and you can now
>> use a
>> > >> >> subset of E4X in your cross-compiled applications.  See the
>> > >> RELEASE_NOTES
>> > >> >> files in the artifacts for more information.
>> > >> >>
>> > >> >> The purpose of this release is to gather feedback about the
>> > >> >> features and implementation strategies, and recruit new
>> contributors
>> > >> as we
>> > >> >> grow these code bases into an SDK and tool chain that delivers the
>> > >> highest
>> > >> >> productivity developing applications that can run in the most
>> places.
>> > >> >> These releases may not handle production needs.  Expect lots of
>> bugs
>> > >> and
>> > >> >> missing features.  Please file bugs at:
>> > >> >>
>> > >> >> https://issues.apache.org/jira/browse/FLEX/
>> > >> >>
>> > >> >> For questions about how to use FlexJS and FalconJX, send email to
>> > >> >> users@flex.apache.org.  Please try to prefix the subject with
>> > >> [FlexJS] or
>> > >> >> [FalconJX] so it is clear the questions refer to this release and
>> not
>> > >> the
>> > >> >> Flex SDK and MXMLC compiler.
>> > >> >>
>> > >> >> For questions and feedback on the development of the source code
>> in
>> > >> these
>> > >> >> release, send email to dev@flex.apache.org.  Again, please prefix
>> the
>> > >> >> subject with [FlexJS] or [FalconJX].
>> > >> >>
>> > >> >> Apache FlexJS and Apache Flex FalconJX are available in source and
>> > >> binary
>> > >> >> form from the following download page:
>> > >> >> http://flex.apache.org/download-flexjs.html
>> > >> >>
>> > >> >> When downloading from a mirror site, please remember to verify the
>> > >> >> downloads using signatures or MD5 hashes.
>> > >> >>
>> > >> >> A simple way to try these releases is to use the
>> > >> >> InstallApacheFlex 3.1 or 3.2 application which is available at the
>> > >> >> following url:
>> > >> >> http://flex.apache.org/installer.html
>> > >> >>
>> > >> >> Choose Apache FlexJS 0.7.0 and it will create an Adobe Flash
>> > >> >> Builder-compatible SDK that uses the Falcon and FalconJX compilers
>> to
>> > >> >> generate SWFs and HTML/JS/CSS output.  You can also use FDT as
>> your
>> IDE
>> > >> >> for developing FlexJS applications.  Some folks have been
>> successful
>> > >> >> using IntelliJ, FlashDevelop as well.  Moonshine is also working
>> on
>> > >> >> FlexJS support.
>> > >> >>
>> > >> >> Apache FlexJS 0.7.0 is also available as a npm package. On a
>> system
>> > >> with
>> > >> >> npm installed, users can easily install FlexJS with the command:
>> "npm
>> > >> >> install flexjs -g".
>> > >> >>
>> > >> >> See the README or the FlexJS wiki for more information.  The
>> FlexJS
>> > >> >> section of the wiki is at the following
>> > >> >>
>> > >> >> url:
>> > >> >> https://cwiki.apache.org/confluence/display/FLEX/FlexJS
>> > >> >>
>> > >> >> For more information on Apache Flex, visit the project home page:
>> > >> >> http://flex.apache.org
>> > >> >>
>> > >> >> Please try FlexJS and become involved in shaping the future of
>> Flex.
>> > >> >>
>> > >> >> The Apache Flex Community
>> > >> >>
>> > >> >>
>> > >> >>
>> > >> >>
>> > >> >
>> > >>
>> > >
>> > >
>>
>

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[Josh Tynjala <jo...@gmail.com>]

I hope to find a way to reuse the existing scripts in the next version. I
think that tweak I made recently to the NPM versions will help. When I
expose asnodec, I'll play around with some ideas.

- Josh

On Sep 10, 2016 10:05 PM, "OmPrakash Muppirala" <bi...@gmail.com>
wrote:

> On Sep 10, 2016 9:39 AM, "Josh Tynjala" <jo...@gmail.com> wrote:
> >
> > Wait! There's one more thing with the NPM versions that need to be
> changed.
> > The last lines of asjscnpm, asjscompcnpm, and mxmlcnpm need to be updated
> > to match the changes in the regular versions.
> >
> > For instance, in asjsc:
> >
> > -external-library-path="$SCRIPT_HOME/../libs/js.swc"
> >
> > is replaced by
> >
> > +configname=js
> >
> > Exactly the same in asjscompc. It appears that mxmlc may have a slightly
> > different change.
>
> Gah! We need to figure a way to simply reuse the existing scripts instead
> if having to copy everything each time.
>
> Are you planning on fixing this?
>
> Thanks,
> Om
>
> >
> > - Josh
> >
> > On Sat, Sep 10, 2016 at 9:25 AM, Josh Tynjala <jo...@gmail.com>
> wrote:
> >
> > > After installing flexjs@next from NPM, I can now successfully run
> asjsc,
> > > asjscompc, and mxmlc from the command line on Mac. The end-of-line fix
> > > appears to be working correctly.
> > >
> > > - Josh
> > >
> > > On Fri, Sep 9, 2016 at 7:08 PM, OmPrakash Muppirala <
> bigosmallm@gmail.com>
> > > wrote:
> > >
> > >> I just pushed flexjs 0.7.0 with a tag 'next'.  If someone can test it
> on a
> > >> Mac and give me an all clear, I can go ahead and promote the package
> to a
> > >> release.
> > >>
> > >> Run:
> > >> *npm install flexjs@next -g *
> > >> to test flexjs 0.7.0 npm package.
> > >>
> > >> Thanks,
> > >> Om
> > >>
> > >> On Fri, Sep 9, 2016 at 2:31 PM, OmPrakash Muppirala <
> bigosmallm@gmail.com
> > >> >
> > >> wrote:
> > >>
> > >> >
> > >> >
> > >> > On Fri, Sep 9, 2016 at 1:53 PM, Alex Harui <ah...@adobe.com>
> wrote:
> > >> >
> > >> >> Please comment on the draft below.  We need Om or someone to
> publish
> > >> the
> > >> >> npm module.
> > >> >>
> > >> >
> > >> > On it.
> > >> >
> > >> > Thanks,
> > >> > Om
> > >> >
> > >> >
> > >> >>
> > >> >> -----------
> > >> >>
> > >> >> The Apache Flex community is pleased to announce the release of
> Apache
> > >> >> FlexJS SDK 0.7.0 and Apache Flex FalconJX Compiler 0.7.0.
> > >> >>
> > >> >> Apache Flex is a highly productive, open source application
> framework
> > >> for
> > >> >> building and maintaining expressive applications that deploy
> > >> consistently
> > >> >> on all major browsers, desktops and devices (including smartphones,
> > >> >> tablets and tv).
> > >> >>
> > >> >> Apache FlexJS is a next-generation Flex SDK that enables developers
> to
> > >> use
> > >> >> MXML and ActionScript to not only create SWFs but also
> cross-compile
> > >> the
> > >> >> same MXML and ActionScript to HTML/JS/CSS so applications can run
> > >> natively
> > >> >> in browsers.  The cross-compiled code can also be used in Apache
> > >> Cordova
> > >> >> (Adobe PhoneGap) mobile applications.
> > >> >>
> > >> >> Apache Flex FalconJX is a next-generation MXML and ActionScript
> > >> >> cross-compiler.  It extends the next-generation SWF compiler known
> as
> > >> >> Falcon.  Both are contained in the release package and are used by
> the
> > >> >> FlexJS package to compile SWFs or cross-compile to HTML/JS/CSS.
> > >> >>
> > >> >> This is the fifth release of FlexJS and FalconJX.  It is ‘beta'
> > >> >> quality.  In this release, all of the compiler JARs and framework
> SWCs
> > >> are
> > >> >> also available as Maven artifacts making it the first version of
> any
> > >> Flex
> > >> >> SDK to support Maven.  Maven can even be used to build the sources
> and
> > >> >> examples.  See the various pom.xml files included in the artifacts.
> > >> >>
> > >> >> In addition, the JS output also includes source maps so you can see
> > >> your
> > >> >> ActionScript source in the browser debugger.  Also, there is more
> > >> support
> > >> >> for using ActionScript to create NodeJS modules, and you can now
> use a
> > >> >> subset of E4X in your cross-compiled applications.  See the
> > >> RELEASE_NOTES
> > >> >> files in the artifacts for more information.
> > >> >>
> > >> >> The purpose of this release is to gather feedback about the
> > >> >> features and implementation strategies, and recruit new
> contributors
> > >> as we
> > >> >> grow these code bases into an SDK and tool chain that delivers the
> > >> highest
> > >> >> productivity developing applications that can run in the most
> places.
> > >> >> These releases may not handle production needs.  Expect lots of
> bugs
> > >> and
> > >> >> missing features.  Please file bugs at:
> > >> >>
> > >> >> https://issues.apache.org/jira/browse/FLEX/
> > >> >>
> > >> >> For questions about how to use FlexJS and FalconJX, send email to
> > >> >> users@flex.apache.org.  Please try to prefix the subject with
> > >> [FlexJS] or
> > >> >> [FalconJX] so it is clear the questions refer to this release and
> not
> > >> the
> > >> >> Flex SDK and MXMLC compiler.
> > >> >>
> > >> >> For questions and feedback on the development of the source code in
> > >> these
> > >> >> release, send email to dev@flex.apache.org.  Again, please prefix
> the
> > >> >> subject with [FlexJS] or [FalconJX].
> > >> >>
> > >> >> Apache FlexJS and Apache Flex FalconJX are available in source and
> > >> binary
> > >> >> form from the following download page:
> > >> >> http://flex.apache.org/download-flexjs.html
> > >> >>
> > >> >> When downloading from a mirror site, please remember to verify the
> > >> >> downloads using signatures or MD5 hashes.
> > >> >>
> > >> >> A simple way to try these releases is to use the
> > >> >> InstallApacheFlex 3.1 or 3.2 application which is available at the
> > >> >> following url:
> > >> >> http://flex.apache.org/installer.html
> > >> >>
> > >> >> Choose Apache FlexJS 0.7.0 and it will create an Adobe Flash
> > >> >> Builder-compatible SDK that uses the Falcon and FalconJX compilers
> to
> > >> >> generate SWFs and HTML/JS/CSS output.  You can also use FDT as your
> IDE
> > >> >> for developing FlexJS applications.  Some folks have been
> successful
> > >> >> using IntelliJ, FlashDevelop as well.  Moonshine is also working on
> > >> >> FlexJS support.
> > >> >>
> > >> >> Apache FlexJS 0.7.0 is also available as a npm package. On a system
> > >> with
> > >> >> npm installed, users can easily install FlexJS with the command:
> "npm
> > >> >> install flexjs -g".
> > >> >>
> > >> >> See the README or the FlexJS wiki for more information.  The FlexJS
> > >> >> section of the wiki is at the following
> > >> >>
> > >> >> url:
> > >> >> https://cwiki.apache.org/confluence/display/FLEX/FlexJS
> > >> >>
> > >> >> For more information on Apache Flex, visit the project home page:
> > >> >> http://flex.apache.org
> > >> >>
> > >> >> Please try FlexJS and become involved in shaping the future of
> Flex.
> > >> >>
> > >> >> The Apache Flex Community
> > >> >>
> > >> >>
> > >> >>
> > >> >>
> > >> >
> > >>
> > >
> > >
>

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[OmPrakash Muppirala <bi...@gmail.com>]

On Sep 10, 2016 9:39 AM, "Josh Tynjala" <jo...@gmail.com> wrote:
>
> Wait! There's one more thing with the NPM versions that need to be
changed.
> The last lines of asjscnpm, asjscompcnpm, and mxmlcnpm need to be updated
> to match the changes in the regular versions.
>
> For instance, in asjsc:
>
> -external-library-path="$SCRIPT_HOME/../libs/js.swc"
>
> is replaced by
>
> +configname=js
>
> Exactly the same in asjscompc. It appears that mxmlc may have a slightly
> different change.

Gah! We need to figure a way to simply reuse the existing scripts instead
if having to copy everything each time.

Are you planning on fixing this?

Thanks,
Om

>
> - Josh
>
> On Sat, Sep 10, 2016 at 9:25 AM, Josh Tynjala <jo...@gmail.com>
wrote:
>
> > After installing flexjs@next from NPM, I can now successfully run asjsc,
> > asjscompc, and mxmlc from the command line on Mac. The end-of-line fix
> > appears to be working correctly.
> >
> > - Josh
> >
> > On Fri, Sep 9, 2016 at 7:08 PM, OmPrakash Muppirala <
bigosmallm@gmail.com>
> > wrote:
> >
> >> I just pushed flexjs 0.7.0 with a tag 'next'.  If someone can test it
on a
> >> Mac and give me an all clear, I can go ahead and promote the package
to a
> >> release.
> >>
> >> Run:
> >> *npm install flexjs@next -g *
> >> to test flexjs 0.7.0 npm package.
> >>
> >> Thanks,
> >> Om
> >>
> >> On Fri, Sep 9, 2016 at 2:31 PM, OmPrakash Muppirala <
bigosmallm@gmail.com
> >> >
> >> wrote:
> >>
> >> >
> >> >
> >> > On Fri, Sep 9, 2016 at 1:53 PM, Alex Harui <ah...@adobe.com> wrote:
> >> >
> >> >> Please comment on the draft below.  We need Om or someone to publish
> >> the
> >> >> npm module.
> >> >>
> >> >
> >> > On it.
> >> >
> >> > Thanks,
> >> > Om
> >> >
> >> >
> >> >>
> >> >> -----------
> >> >>
> >> >> The Apache Flex community is pleased to announce the release of
Apache
> >> >> FlexJS SDK 0.7.0 and Apache Flex FalconJX Compiler 0.7.0.
> >> >>
> >> >> Apache Flex is a highly productive, open source application
framework
> >> for
> >> >> building and maintaining expressive applications that deploy
> >> consistently
> >> >> on all major browsers, desktops and devices (including smartphones,
> >> >> tablets and tv).
> >> >>
> >> >> Apache FlexJS is a next-generation Flex SDK that enables developers
to
> >> use
> >> >> MXML and ActionScript to not only create SWFs but also cross-compile
> >> the
> >> >> same MXML and ActionScript to HTML/JS/CSS so applications can run
> >> natively
> >> >> in browsers.  The cross-compiled code can also be used in Apache
> >> Cordova
> >> >> (Adobe PhoneGap) mobile applications.
> >> >>
> >> >> Apache Flex FalconJX is a next-generation MXML and ActionScript
> >> >> cross-compiler.  It extends the next-generation SWF compiler known
as
> >> >> Falcon.  Both are contained in the release package and are used by
the
> >> >> FlexJS package to compile SWFs or cross-compile to HTML/JS/CSS.
> >> >>
> >> >> This is the fifth release of FlexJS and FalconJX.  It is ‘beta'
> >> >> quality.  In this release, all of the compiler JARs and framework
SWCs
> >> are
> >> >> also available as Maven artifacts making it the first version of any
> >> Flex
> >> >> SDK to support Maven.  Maven can even be used to build the sources
and
> >> >> examples.  See the various pom.xml files included in the artifacts.
> >> >>
> >> >> In addition, the JS output also includes source maps so you can see
> >> your
> >> >> ActionScript source in the browser debugger.  Also, there is more
> >> support
> >> >> for using ActionScript to create NodeJS modules, and you can now
use a
> >> >> subset of E4X in your cross-compiled applications.  See the
> >> RELEASE_NOTES
> >> >> files in the artifacts for more information.
> >> >>
> >> >> The purpose of this release is to gather feedback about the
> >> >> features and implementation strategies, and recruit new contributors
> >> as we
> >> >> grow these code bases into an SDK and tool chain that delivers the
> >> highest
> >> >> productivity developing applications that can run in the most
places.
> >> >> These releases may not handle production needs.  Expect lots of bugs
> >> and
> >> >> missing features.  Please file bugs at:
> >> >>
> >> >> https://issues.apache.org/jira/browse/FLEX/
> >> >>
> >> >> For questions about how to use FlexJS and FalconJX, send email to
> >> >> users@flex.apache.org.  Please try to prefix the subject with
> >> [FlexJS] or
> >> >> [FalconJX] so it is clear the questions refer to this release and
not
> >> the
> >> >> Flex SDK and MXMLC compiler.
> >> >>
> >> >> For questions and feedback on the development of the source code in
> >> these
> >> >> release, send email to dev@flex.apache.org.  Again, please prefix
the
> >> >> subject with [FlexJS] or [FalconJX].
> >> >>
> >> >> Apache FlexJS and Apache Flex FalconJX are available in source and
> >> binary
> >> >> form from the following download page:
> >> >> http://flex.apache.org/download-flexjs.html
> >> >>
> >> >> When downloading from a mirror site, please remember to verify the
> >> >> downloads using signatures or MD5 hashes.
> >> >>
> >> >> A simple way to try these releases is to use the
> >> >> InstallApacheFlex 3.1 or 3.2 application which is available at the
> >> >> following url:
> >> >> http://flex.apache.org/installer.html
> >> >>
> >> >> Choose Apache FlexJS 0.7.0 and it will create an Adobe Flash
> >> >> Builder-compatible SDK that uses the Falcon and FalconJX compilers
to
> >> >> generate SWFs and HTML/JS/CSS output.  You can also use FDT as your
IDE
> >> >> for developing FlexJS applications.  Some folks have been successful
> >> >> using IntelliJ, FlashDevelop as well.  Moonshine is also working on
> >> >> FlexJS support.
> >> >>
> >> >> Apache FlexJS 0.7.0 is also available as a npm package. On a system
> >> with
> >> >> npm installed, users can easily install FlexJS with the command:
"npm
> >> >> install flexjs -g".
> >> >>
> >> >> See the README or the FlexJS wiki for more information.  The FlexJS
> >> >> section of the wiki is at the following
> >> >>
> >> >> url:
> >> >> https://cwiki.apache.org/confluence/display/FLEX/FlexJS
> >> >>
> >> >> For more information on Apache Flex, visit the project home page:
> >> >> http://flex.apache.org
> >> >>
> >> >> Please try FlexJS and become involved in shaping the future of Flex.
> >> >>
> >> >> The Apache Flex Community
> >> >>
> >> >>
> >> >>
> >> >>
> >> >
> >>
> >
> >

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[Josh Tynjala <jo...@gmail.com>]

Wait! There's one more thing with the NPM versions that need to be changed.
The last lines of asjscnpm, asjscompcnpm, and mxmlcnpm need to be updated
to match the changes in the regular versions.

For instance, in asjsc:

-external-library-path="$SCRIPT_HOME/../libs/js.swc"

is replaced by

+configname=js

Exactly the same in asjscompc. It appears that mxmlc may have a slightly
different change.

- Josh

On Sat, Sep 10, 2016 at 9:25 AM, Josh Tynjala <jo...@gmail.com> wrote:

> After installing flexjs@next from NPM, I can now successfully run asjsc,
> asjscompc, and mxmlc from the command line on Mac. The end-of-line fix
> appears to be working correctly.
>
> - Josh
>
> On Fri, Sep 9, 2016 at 7:08 PM, OmPrakash Muppirala <bi...@gmail.com>
> wrote:
>
>> I just pushed flexjs 0.7.0 with a tag 'next'.  If someone can test it on a
>> Mac and give me an all clear, I can go ahead and promote the package to a
>> release.
>>
>> Run:
>> *npm install flexjs@next -g *
>> to test flexjs 0.7.0 npm package.
>>
>> Thanks,
>> Om
>>
>> On Fri, Sep 9, 2016 at 2:31 PM, OmPrakash Muppirala <bigosmallm@gmail.com
>> >
>> wrote:
>>
>> >
>> >
>> > On Fri, Sep 9, 2016 at 1:53 PM, Alex Harui <ah...@adobe.com> wrote:
>> >
>> >> Please comment on the draft below.  We need Om or someone to publish
>> the
>> >> npm module.
>> >>
>> >
>> > On it.
>> >
>> > Thanks,
>> > Om
>> >
>> >
>> >>
>> >> -----------
>> >>
>> >> The Apache Flex community is pleased to announce the release of Apache
>> >> FlexJS SDK 0.7.0 and Apache Flex FalconJX Compiler 0.7.0.
>> >>
>> >> Apache Flex is a highly productive, open source application framework
>> for
>> >> building and maintaining expressive applications that deploy
>> consistently
>> >> on all major browsers, desktops and devices (including smartphones,
>> >> tablets and tv).
>> >>
>> >> Apache FlexJS is a next-generation Flex SDK that enables developers to
>> use
>> >> MXML and ActionScript to not only create SWFs but also cross-compile
>> the
>> >> same MXML and ActionScript to HTML/JS/CSS so applications can run
>> natively
>> >> in browsers.  The cross-compiled code can also be used in Apache
>> Cordova
>> >> (Adobe PhoneGap) mobile applications.
>> >>
>> >> Apache Flex FalconJX is a next-generation MXML and ActionScript
>> >> cross-compiler.  It extends the next-generation SWF compiler known as
>> >> Falcon.  Both are contained in the release package and are used by the
>> >> FlexJS package to compile SWFs or cross-compile to HTML/JS/CSS.
>> >>
>> >> This is the fifth release of FlexJS and FalconJX.  It is ‘beta'
>> >> quality.  In this release, all of the compiler JARs and framework SWCs
>> are
>> >> also available as Maven artifacts making it the first version of any
>> Flex
>> >> SDK to support Maven.  Maven can even be used to build the sources and
>> >> examples.  See the various pom.xml files included in the artifacts.
>> >>
>> >> In addition, the JS output also includes source maps so you can see
>> your
>> >> ActionScript source in the browser debugger.  Also, there is more
>> support
>> >> for using ActionScript to create NodeJS modules, and you can now use a
>> >> subset of E4X in your cross-compiled applications.  See the
>> RELEASE_NOTES
>> >> files in the artifacts for more information.
>> >>
>> >> The purpose of this release is to gather feedback about the
>> >> features and implementation strategies, and recruit new contributors
>> as we
>> >> grow these code bases into an SDK and tool chain that delivers the
>> highest
>> >> productivity developing applications that can run in the most places.
>> >> These releases may not handle production needs.  Expect lots of bugs
>> and
>> >> missing features.  Please file bugs at:
>> >>
>> >> https://issues.apache.org/jira/browse/FLEX/
>> >>
>> >> For questions about how to use FlexJS and FalconJX, send email to
>> >> users@flex.apache.org.  Please try to prefix the subject with
>> [FlexJS] or
>> >> [FalconJX] so it is clear the questions refer to this release and not
>> the
>> >> Flex SDK and MXMLC compiler.
>> >>
>> >> For questions and feedback on the development of the source code in
>> these
>> >> release, send email to dev@flex.apache.org.  Again, please prefix the
>> >> subject with [FlexJS] or [FalconJX].
>> >>
>> >> Apache FlexJS and Apache Flex FalconJX are available in source and
>> binary
>> >> form from the following download page:
>> >> http://flex.apache.org/download-flexjs.html
>> >>
>> >> When downloading from a mirror site, please remember to verify the
>> >> downloads using signatures or MD5 hashes.
>> >>
>> >> A simple way to try these releases is to use the
>> >> InstallApacheFlex 3.1 or 3.2 application which is available at the
>> >> following url:
>> >> http://flex.apache.org/installer.html
>> >>
>> >> Choose Apache FlexJS 0.7.0 and it will create an Adobe Flash
>> >> Builder-compatible SDK that uses the Falcon and FalconJX compilers to
>> >> generate SWFs and HTML/JS/CSS output.  You can also use FDT as your IDE
>> >> for developing FlexJS applications.  Some folks have been successful
>> >> using IntelliJ, FlashDevelop as well.  Moonshine is also working on
>> >> FlexJS support.
>> >>
>> >> Apache FlexJS 0.7.0 is also available as a npm package. On a system
>> with
>> >> npm installed, users can easily install FlexJS with the command: "npm
>> >> install flexjs -g".
>> >>
>> >> See the README or the FlexJS wiki for more information.  The FlexJS
>> >> section of the wiki is at the following
>> >>
>> >> url:
>> >> https://cwiki.apache.org/confluence/display/FLEX/FlexJS
>> >>
>> >> For more information on Apache Flex, visit the project home page:
>> >> http://flex.apache.org
>> >>
>> >> Please try FlexJS and become involved in shaping the future of Flex.
>> >>
>> >> The Apache Flex Community
>> >>
>> >>
>> >>
>> >>
>> >
>>
>
>

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[Josh Tynjala <jo...@gmail.com>]

After installing flexjs@next from NPM, I can now successfully run asjsc,
asjscompc, and mxmlc from the command line on Mac. The end-of-line fix
appears to be working correctly.

- Josh

On Fri, Sep 9, 2016 at 7:08 PM, OmPrakash Muppirala <bi...@gmail.com>
wrote:

> I just pushed flexjs 0.7.0 with a tag 'next'.  If someone can test it on a
> Mac and give me an all clear, I can go ahead and promote the package to a
> release.
>
> Run:
> *npm install flexjs@next -g *
> to test flexjs 0.7.0 npm package.
>
> Thanks,
> Om
>
> On Fri, Sep 9, 2016 at 2:31 PM, OmPrakash Muppirala <bi...@gmail.com>
> wrote:
>
> >
> >
> > On Fri, Sep 9, 2016 at 1:53 PM, Alex Harui <ah...@adobe.com> wrote:
> >
> >> Please comment on the draft below.  We need Om or someone to publish the
> >> npm module.
> >>
> >
> > On it.
> >
> > Thanks,
> > Om
> >
> >
> >>
> >> -----------
> >>
> >> The Apache Flex community is pleased to announce the release of Apache
> >> FlexJS SDK 0.7.0 and Apache Flex FalconJX Compiler 0.7.0.
> >>
> >> Apache Flex is a highly productive, open source application framework
> for
> >> building and maintaining expressive applications that deploy
> consistently
> >> on all major browsers, desktops and devices (including smartphones,
> >> tablets and tv).
> >>
> >> Apache FlexJS is a next-generation Flex SDK that enables developers to
> use
> >> MXML and ActionScript to not only create SWFs but also cross-compile the
> >> same MXML and ActionScript to HTML/JS/CSS so applications can run
> natively
> >> in browsers.  The cross-compiled code can also be used in Apache Cordova
> >> (Adobe PhoneGap) mobile applications.
> >>
> >> Apache Flex FalconJX is a next-generation MXML and ActionScript
> >> cross-compiler.  It extends the next-generation SWF compiler known as
> >> Falcon.  Both are contained in the release package and are used by the
> >> FlexJS package to compile SWFs or cross-compile to HTML/JS/CSS.
> >>
> >> This is the fifth release of FlexJS and FalconJX.  It is ‘beta'
> >> quality.  In this release, all of the compiler JARs and framework SWCs
> are
> >> also available as Maven artifacts making it the first version of any
> Flex
> >> SDK to support Maven.  Maven can even be used to build the sources and
> >> examples.  See the various pom.xml files included in the artifacts.
> >>
> >> In addition, the JS output also includes source maps so you can see your
> >> ActionScript source in the browser debugger.  Also, there is more
> support
> >> for using ActionScript to create NodeJS modules, and you can now use a
> >> subset of E4X in your cross-compiled applications.  See the
> RELEASE_NOTES
> >> files in the artifacts for more information.
> >>
> >> The purpose of this release is to gather feedback about the
> >> features and implementation strategies, and recruit new contributors as
> we
> >> grow these code bases into an SDK and tool chain that delivers the
> highest
> >> productivity developing applications that can run in the most places.
> >> These releases may not handle production needs.  Expect lots of bugs and
> >> missing features.  Please file bugs at:
> >>
> >> https://issues.apache.org/jira/browse/FLEX/
> >>
> >> For questions about how to use FlexJS and FalconJX, send email to
> >> users@flex.apache.org.  Please try to prefix the subject with [FlexJS]
> or
> >> [FalconJX] so it is clear the questions refer to this release and not
> the
> >> Flex SDK and MXMLC compiler.
> >>
> >> For questions and feedback on the development of the source code in
> these
> >> release, send email to dev@flex.apache.org.  Again, please prefix the
> >> subject with [FlexJS] or [FalconJX].
> >>
> >> Apache FlexJS and Apache Flex FalconJX are available in source and
> binary
> >> form from the following download page:
> >> http://flex.apache.org/download-flexjs.html
> >>
> >> When downloading from a mirror site, please remember to verify the
> >> downloads using signatures or MD5 hashes.
> >>
> >> A simple way to try these releases is to use the
> >> InstallApacheFlex 3.1 or 3.2 application which is available at the
> >> following url:
> >> http://flex.apache.org/installer.html
> >>
> >> Choose Apache FlexJS 0.7.0 and it will create an Adobe Flash
> >> Builder-compatible SDK that uses the Falcon and FalconJX compilers to
> >> generate SWFs and HTML/JS/CSS output.  You can also use FDT as your IDE
> >> for developing FlexJS applications.  Some folks have been successful
> >> using IntelliJ, FlashDevelop as well.  Moonshine is also working on
> >> FlexJS support.
> >>
> >> Apache FlexJS 0.7.0 is also available as a npm package. On a system with
> >> npm installed, users can easily install FlexJS with the command: "npm
> >> install flexjs -g".
> >>
> >> See the README or the FlexJS wiki for more information.  The FlexJS
> >> section of the wiki is at the following
> >>
> >> url:
> >> https://cwiki.apache.org/confluence/display/FLEX/FlexJS
> >>
> >> For more information on Apache Flex, visit the project home page:
> >> http://flex.apache.org
> >>
> >> Please try FlexJS and become involved in shaping the future of Flex.
> >>
> >> The Apache Flex Community
> >>
> >>
> >>
> >>
> >
>

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[OmPrakash Muppirala <bi...@gmail.com>]

I just pushed flexjs 0.7.0 with a tag 'next'.  If someone can test it on a
Mac and give me an all clear, I can go ahead and promote the package to a
release.

Run:
*npm install flexjs@next -g *
to test flexjs 0.7.0 npm package.

Thanks,
Om

On Fri, Sep 9, 2016 at 2:31 PM, OmPrakash Muppirala <bi...@gmail.com>
wrote:

>
>
> On Fri, Sep 9, 2016 at 1:53 PM, Alex Harui <ah...@adobe.com> wrote:
>
>> Please comment on the draft below.  We need Om or someone to publish the
>> npm module.
>>
>
> On it.
>
> Thanks,
> Om
>
>
>>
>> -----------
>>
>> The Apache Flex community is pleased to announce the release of Apache
>> FlexJS SDK 0.7.0 and Apache Flex FalconJX Compiler 0.7.0.
>>
>> Apache Flex is a highly productive, open source application framework for
>> building and maintaining expressive applications that deploy consistently
>> on all major browsers, desktops and devices (including smartphones,
>> tablets and tv).
>>
>> Apache FlexJS is a next-generation Flex SDK that enables developers to use
>> MXML and ActionScript to not only create SWFs but also cross-compile the
>> same MXML and ActionScript to HTML/JS/CSS so applications can run natively
>> in browsers.  The cross-compiled code can also be used in Apache Cordova
>> (Adobe PhoneGap) mobile applications.
>>
>> Apache Flex FalconJX is a next-generation MXML and ActionScript
>> cross-compiler.  It extends the next-generation SWF compiler known as
>> Falcon.  Both are contained in the release package and are used by the
>> FlexJS package to compile SWFs or cross-compile to HTML/JS/CSS.
>>
>> This is the fifth release of FlexJS and FalconJX.  It is ‘beta'
>> quality.  In this release, all of the compiler JARs and framework SWCs are
>> also available as Maven artifacts making it the first version of any Flex
>> SDK to support Maven.  Maven can even be used to build the sources and
>> examples.  See the various pom.xml files included in the artifacts.
>>
>> In addition, the JS output also includes source maps so you can see your
>> ActionScript source in the browser debugger.  Also, there is more support
>> for using ActionScript to create NodeJS modules, and you can now use a
>> subset of E4X in your cross-compiled applications.  See the RELEASE_NOTES
>> files in the artifacts for more information.
>>
>> The purpose of this release is to gather feedback about the
>> features and implementation strategies, and recruit new contributors as we
>> grow these code bases into an SDK and tool chain that delivers the highest
>> productivity developing applications that can run in the most places.
>> These releases may not handle production needs.  Expect lots of bugs and
>> missing features.  Please file bugs at:
>>
>> https://issues.apache.org/jira/browse/FLEX/
>>
>> For questions about how to use FlexJS and FalconJX, send email to
>> users@flex.apache.org.  Please try to prefix the subject with [FlexJS] or
>> [FalconJX] so it is clear the questions refer to this release and not the
>> Flex SDK and MXMLC compiler.
>>
>> For questions and feedback on the development of the source code in these
>> release, send email to dev@flex.apache.org.  Again, please prefix the
>> subject with [FlexJS] or [FalconJX].
>>
>> Apache FlexJS and Apache Flex FalconJX are available in source and binary
>> form from the following download page:
>> http://flex.apache.org/download-flexjs.html
>>
>> When downloading from a mirror site, please remember to verify the
>> downloads using signatures or MD5 hashes.
>>
>> A simple way to try these releases is to use the
>> InstallApacheFlex 3.1 or 3.2 application which is available at the
>> following url:
>> http://flex.apache.org/installer.html
>>
>> Choose Apache FlexJS 0.7.0 and it will create an Adobe Flash
>> Builder-compatible SDK that uses the Falcon and FalconJX compilers to
>> generate SWFs and HTML/JS/CSS output.  You can also use FDT as your IDE
>> for developing FlexJS applications.  Some folks have been successful
>> using IntelliJ, FlashDevelop as well.  Moonshine is also working on
>> FlexJS support.
>>
>> Apache FlexJS 0.7.0 is also available as a npm package. On a system with
>> npm installed, users can easily install FlexJS with the command: "npm
>> install flexjs -g".
>>
>> See the README or the FlexJS wiki for more information.  The FlexJS
>> section of the wiki is at the following
>>
>> url:
>> https://cwiki.apache.org/confluence/display/FLEX/FlexJS
>>
>> For more information on Apache Flex, visit the project home page:
>> http://flex.apache.org
>>
>> Please try FlexJS and become involved in shaping the future of Flex.
>>
>> The Apache Flex Community
>>
>>
>>
>>
>

Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released

[OmPrakash Muppirala <bi...@gmail.com>]

On Fri, Sep 9, 2016 at 1:53 PM, Alex Harui <ah...@adobe.com> wrote:

> Please comment on the draft below.  We need Om or someone to publish the
> npm module.
>

On it.

Thanks,
Om


>
> -----------
>
> The Apache Flex community is pleased to announce the release of Apache
> FlexJS SDK 0.7.0 and Apache Flex FalconJX Compiler 0.7.0.
>
> Apache Flex is a highly productive, open source application framework for
> building and maintaining expressive applications that deploy consistently
> on all major browsers, desktops and devices (including smartphones,
> tablets and tv).
>
> Apache FlexJS is a next-generation Flex SDK that enables developers to use
> MXML and ActionScript to not only create SWFs but also cross-compile the
> same MXML and ActionScript to HTML/JS/CSS so applications can run natively
> in browsers.  The cross-compiled code can also be used in Apache Cordova
> (Adobe PhoneGap) mobile applications.
>
> Apache Flex FalconJX is a next-generation MXML and ActionScript
> cross-compiler.  It extends the next-generation SWF compiler known as
> Falcon.  Both are contained in the release package and are used by the
> FlexJS package to compile SWFs or cross-compile to HTML/JS/CSS.
>
> This is the fifth release of FlexJS and FalconJX.  It is ‘beta'
> quality.  In this release, all of the compiler JARs and framework SWCs are
> also available as Maven artifacts making it the first version of any Flex
> SDK to support Maven.  Maven can even be used to build the sources and
> examples.  See the various pom.xml files included in the artifacts.
>
> In addition, the JS output also includes source maps so you can see your
> ActionScript source in the browser debugger.  Also, there is more support
> for using ActionScript to create NodeJS modules, and you can now use a
> subset of E4X in your cross-compiled applications.  See the RELEASE_NOTES
> files in the artifacts for more information.
>
> The purpose of this release is to gather feedback about the
> features and implementation strategies, and recruit new contributors as we
> grow these code bases into an SDK and tool chain that delivers the highest
> productivity developing applications that can run in the most places.
> These releases may not handle production needs.  Expect lots of bugs and
> missing features.  Please file bugs at:
>
> https://issues.apache.org/jira/browse/FLEX/
>
> For questions about how to use FlexJS and FalconJX, send email to
> users@flex.apache.org.  Please try to prefix the subject with [FlexJS] or
> [FalconJX] so it is clear the questions refer to this release and not the
> Flex SDK and MXMLC compiler.
>
> For questions and feedback on the development of the source code in these
> release, send email to dev@flex.apache.org.  Again, please prefix the
> subject with [FlexJS] or [FalconJX].
>
> Apache FlexJS and Apache Flex FalconJX are available in source and binary
> form from the following download page:
> http://flex.apache.org/download-flexjs.html
>
> When downloading from a mirror site, please remember to verify the
> downloads using signatures or MD5 hashes.
>
> A simple way to try these releases is to use the
> InstallApacheFlex 3.1 or 3.2 application which is available at the
> following url:
> http://flex.apache.org/installer.html
>
> Choose Apache FlexJS 0.7.0 and it will create an Adobe Flash
> Builder-compatible SDK that uses the Falcon and FalconJX compilers to
> generate SWFs and HTML/JS/CSS output.  You can also use FDT as your IDE
> for developing FlexJS applications.  Some folks have been successful
> using IntelliJ, FlashDevelop as well.  Moonshine is also working on
> FlexJS support.
>
> Apache FlexJS 0.7.0 is also available as a npm package. On a system with
> npm installed, users can easily install FlexJS with the command: "npm
> install flexjs -g".
>
> See the README or the FlexJS wiki for more information.  The FlexJS
> section of the wiki is at the following
>
> url:
> https://cwiki.apache.org/confluence/display/FLEX/FlexJS
>
> For more information on Apache Flex, visit the project home page:
> http://flex.apache.org
>
> Please try FlexJS and become involved in shaping the future of Flex.
>
> The Apache Flex Community
>
>
>
>