I've 'fixed' the ES6 issue, so the new version of the GCC is good to go.

That leaves the 'ant_on_air != ant' issue...

EdB




On Fri, Jun 27, 2014 at 9:02 AM, Erik de Bruin <e...@ixsoftware.nl> wrote:

> The checksum requirement makes us go into download.xml when updating
> anyway, and I like to keep some measure of control over the version, so we
> can update at our leisure. For the current update, for example, the
> examples will not readily compile due to some changes into the GC parsers
> for ES6, apparently. If I can't fix that right away, I can now easily roll
> back to the previous version ;-)
>
> Your 'ant_on_air' had me fooled there. Any suggestions? Do I need to
> create an 'exec' task (if possible at all) in 'ant_on_air'?
>
> EdB
>
>
>
>
> On Fri, Jun 27, 2014 at 8:53 AM, Alex Harui <aha...@adobe.com> wrote:
>
>> OK, I thought you automatically wanted to stay up-to-date.  So for GCC, we
>> just have to keep updating the downloads.xml if we notice GCC has been
>> updated?
>>
>> What about GCL?  They only seem to have one zip on their GH site.  I
>> looked and saw that for Jenkins you are pulling the GCL sources via Git,
>> but the installer cannot run Git.
>>
>> -Alex
>>
>>
>> On 6/26/14 11:41 PM, "Erik de Bruin" <e...@ixsoftware.nl> wrote:
>>
>> >We download the compiler source by version number (not "latest"). That
>> way
>> >we keep control over which version is used and when updating, we can add
>> >the correct checksum.
>> >
>> >EdB
>> >
>> >
>> >
>> >
>> >On Fri, Jun 27, 2014 at 8:36 AM, Alex Harui <aha...@adobe.com> wrote:
>> >
>> >> It will be this weekend at the earliest.  Installer is first then SDK
>> >> because it has a related LICENSE/NOTICE change, then FalconJX/FlexJS.
>> >>
>> >> BTW, one concern I have with always using the latest is that we
>> checksum
>> >> these downloads and the checksum is currently burned into the ant
>> >>script.
>> >> How can we be flexible with the checksum as new releases come out?  I
>> >> guess we can have the installer pull a checksum from the -config.xml on
>> >> the website and update that.  Does that make sense?
>> >>
>> >> -Alex
>> >>
>> >> On 6/26/14 11:30 PM, "Erik de Bruin" <e...@ixsoftware.nl> wrote:
>> >>
>> >> >Hold off for a little bit, please. Google just release a new version
>> of
>> >> >the
>> >> >Compiler, and I want to update and test first ;-)
>> >> >
>> >> >Will be done in about an hour, either way.
>> >> >
>> >> >EdB
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >On Fri, Jun 27, 2014 at 7:37 AM, Alex Harui <aha...@adobe.com> wrote:
>> >> >
>> >> >> Thanks Mark.
>> >> >>
>> >> >> Actually, I think I am going to cancel this RC and the FlexJS RC and
>> >> >>make
>> >> >> new ones with Erik's latest upgrades to the most recent GCC and GCL.
>> >> >>
>> >> >> -Alex
>> >> >>
>> >> >> On 6/26/14 3:49 PM, "Mark Kessler" <kesslerconsult...@gmail.com>
>> >>wrote:
>> >> >>
>> >> >> >+1
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> >-Mark
>> >> >> >
>> >> >> >
>> >> >> >On Mon, Jun 23, 2014 at 12:23 PM, Alex Harui <aha...@adobe.com>
>> >>wrote:
>> >> >> >
>> >> >> >> Hi,
>> >> >> >>
>> >> >> >> This is vote for the second (0.0.2) release of the FalconJX (and
>> >> >>Falcon)
>> >> >> >> compilers.  I am not proposing a separate Falcon-only release
>> >> >>package at
>> >> >> >> this time.  The only purpose of the FalconJX packages are to
>> >>serve as
>> >> >> >> upstream packages for the FlexJS release.
>> >> >> >>
>> >> >> >> The release candidate can be found here;
>> >> >> >> https://dist.apache.org/repos/dist/dev/flex/falcon/0.0.2/rc2/
>> >> >> >>
>> >> >> >> Before voting please review the section,"What are the ASF
>> >> >>requirements
>> >> >> >>on
>> >> >> >> approving a release?", at:
>> >> >> >> http://www.apache.org/dev/release.html#approving-a-release
>> >> >> >>
>> >> >> >> At a minimum you would be expected to check that:
>> >> >> >> - MD5 and signed packages are correct
>> >> >> >> - README, RELEASE_NOTES, NOTICE and LICENSE files are all fine
>> >> >> >> - As this is the first release please carefully check the LICENSE
>> >>and
>> >> >> >> NOTICE files
>> >> >> >> - That the build script completes successfully
>> >> >> >> - That you can compile using the results of building the source
>> >> >>package
>> >> >> >>
>> >> >> >> The source package is set up the same way as the repo.  This
>> means
>> >> >>that
>> >> >> >> the results of the build are not the same as the binary package.
>> >>The
>> >> >> >> compiled source package can be used to build FlexJS apps via the
>> >> >>command
>> >> >> >> line and Ant, but not in Flash Builder or other IDEs.  I tested
>> >>the
>> >> >> >>source
>> >> >> >> package by building it, then pointing to it from the source
>> >>package
>> >> >>of
>> >> >> >>the
>> >> >> >> FlexJS release candidate and building the examples in the FlexJS
>> >> >> >>package.
>> >> >> >>
>> >> >> >> The binary package is set up as an upstream package for the
>> FlexJS
>> >> >> >> release.  The most convenient way to use the binary package is to
>> >> >> >>install
>> >> >> >> a FlexJS SDK via Ant or the Installer.
>> >> >> >>
>> >> >> >> Please vote to approve this release:
>> >> >> >> +1 Approve the release
>> >> >> >> -1 Veto the release (please provide specific comments to why)
>> >> >> >>
>> >> >> >> This vote will be open for 72 hours or until a result can be
>> >>called.
>> >> >> >>
>> >> >> >> The vote passes if there is:
>> >> >> >> - At least 3 +1 votes from the PMC
>> >> >> >> - More positive votes than negative votes
>> >> >> >>
>> >> >> >> Remember that this is an initial 'alpha-quality' release so I
>> >>expect
>> >> >> >>there
>> >> >> >> will be many bugs found.  IMO the goal is not to try to find and
>> >>fix
>> >> >> >>bugs
>> >> >> >> in the RC, but to make sure we have the packaging right, and
>> >>enough
>> >> >> >> functionality that folks will have some success trying to use it.
>> >> >> >>
>> >> >> >> People who are not in PMC are also encouraged to test out the
>> >>release
>> >> >> >>and
>> >> >> >> vote, although their votes will not be binding, they can
>> influence
>> >> >>how
>> >> >> >>the
>> >> >> >> PMC votes.
>> >> >> >>
>> >> >> >> When voting please indicate what OS, IDE, Flash Player version
>> and
>> >> >>AIR
>> >> >> >> version you tested FlexUnit with.
>> >> >> >>
>> >> >> >> Please put all discussion about this release in the DISCUSSION
>> >>thread
>> >> >> >>not
>> >> >> >> this VOTE thread.
>> >> >> >>
>> >> >> >> For your convenience there is an ant script that automates the
>> >>common
>> >> >> >> steps to validate a
>> >> >> >> release.  Instead of individually downloading the package and
>> >> >>signature
>> >> >> >> files, unzipping, etc, you can instead:
>> >> >> >> 1) create an empty folder,
>> >> >> >> 2) download into that folder this file:
>> >> >> >>
>> >> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> https://dist.apache.org/repos/dist/dev/flex/falcon/0.0.2/rc2/ApproveFalco
>> >> >> >>n.
>> >> >> >> xml
>> >> >> >> 3) run the script: ant -e -f ApproveFalcon.xml
>> >> >>-Drelease.version=0.0.2
>> >> >> >> -Drc=2
>> >> >> >>
>> >> >> >> You are not required to use this script, and more testing of the
>> >> >> >>packages
>> >> >> >> and build results are always encouraged.
>> >> >> >>
>> >> >> >> Thanks,
>> >> >> >> Alex
>> >> >> >>
>> >> >> >>
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >> >--
>> >> >Ix Multimedia Software
>> >> >
>> >> >Jan Luykenstraat 27
>> >> >3521 VB Utrecht
>> >> >
>> >> >T. 06-51952295
>> >> >I. www.ixsoftware.nl
>> >>
>> >>
>> >
>> >
>> >--
>> >Ix Multimedia Software
>> >
>> >Jan Luykenstraat 27
>> >3521 VB Utrecht
>> >
>> >T. 06-51952295
>> >I. www.ixsoftware.nl
>>
>>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
>



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Reply via email to