I'm already pointing to a Falcon build (the flex-falcon job). I'm running a copy of the 'release' target, where the only thing I took out is the linting 'compile' step for the JS framework. I can't find a 'package-sdk' target in the main build file... But the 'release' target does depend upon 'binary-release', is that what you mean?
EdB On Mon, Nov 25, 2013 at 6:20 PM, Alex Harui <aha...@adobe.com> wrote: > Excellent, thanks for doing that. > > So yes, the plan is to extends the installer to install FlexJS artifacts. > In fact, the plan is to extend the installer to read and process a subset > of Ant script commands so we don't have to keep releasing the installer as > often. > > BTW, do you think it is worth the trouble to get Jenkins to also build the > package-sdk target? That produces a non-compliant artifact that is what > the deploy scripts use to build out an FB-compatible SDK. It is > non-compliant because it bundles Falcon binaries into the artifacts. The > -bin artifacts are just like the SDK artifacts: you can't just use them in > FB, but you can use them with Ant to make Ant tasks build your SWFs and JS > output. It might be a pain because you have to point to a Falcon build, > and all of this will go away when we get the installer working. > > -Alex > > On 11/25/13 6:44 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote: > >>Also, I've created the Jenkins job to build the artefacts nightly or >>upon a commit: >> >>https://builds.apache.org/job/flex-asjs/lastSuccessfulBuild/artifact/out/ >> >>EdB >> >> >> >>On Mon, Nov 25, 2013 at 2:57 PM, Erik de Bruin <e...@ixsoftware.nl> wrote: >>> This could easily be added to the Installer, correct? Download and >>> build an SDK, download the ApacheFlexJS artefacts and then have the >>> app perform the actions currently done by the scripts? Or am I missing >>> something, like a step in the scripts that cannot be done in AIR (I >>> only gave them a glance)? >>> >>> Having the ability to fetch a working FlexJS SDK with the installer >>> will IMHO greatly increase the available pool of testers and eyes on >>> the alpha. >>> >>> EdB >>> >>> >>> >>> On Mon, Nov 25, 2013 at 8:10 AM, Alex Harui <aha...@adobe.com> wrote: >>>> Hi, >>>> >>>> I just checked in some changes to flex-falcon and flex-asjs to allow >>>>for a >>>> build script in flex-asjs. The main target will build the SWCs. The >>>> examples target will build all of the examples. The release target >>>>will >>>> build apache-compliant release packages. The package-sdk target will >>>> package a new version of FlexJSOverlay.zip called ApacheFlexJS.zip and >>>> ApacheFlexJS.tar.gz. FlexJSOverlay.zip is now obsolete as we have >>>>enough >>>> pieces in flex-asjs to no longer need to overlay files on top of an >>>> existing Flex SDK. Now you unzip or untar the ApacheFlexJS artifact >>>>and >>>> run a deploy script that copies a few missing pieces from an existing >>>>Flex >>>> SDK. Eventually, the deploy script will be replaced by a installer. >>>> >>>> The main target does run jshint and gjslint. I've set >>>>failonerror=false >>>> on jshint for now as it is still spitting warnings. You'll also see >>>> warnings when running the examples target. Volunteers are welcome to >>>> clean all of that up. >>>> >>>> I've posted the latest ApacheFlexJS.zip and ApacheFlexJS.tar.gz at [1]. >>>> I'll remove FlexJSOverlay.zip once I get confirmation that these >>>>artifacts >>>> worked for others. >>>> >>>> Next step for me is to try to get the next Adobe donation to legal for >>>> review. Then work on the installer. >>>> >>>> As always, feedback and contributions welcome. >>>> >>>> Thanks, >>>> -Alex >>>> >>>> [1] http://people.apache.org/~aharui/FlexJS/ >>>> >>> >>> >>> >>> -- >>> 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
