flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From OmPrakash Muppirala <bigosma...@gmail.com>
Subject Re: [LAST CALL] Release FlexJS/FalconJX 0.8.0
Date Wed, 31 May 2017 16:35:39 GMT
I should have something in the next 12 hours or so.

Thanks,
Om


On May 31, 2017 8:31 AM, "Alex Harui" <aharui@adobe.com.invalid> wrote:

Hi Om,

Command-line sounds great if you can do it.  Let us know when you are done
with the NPM stuff so we can move forward with the release.

Thanks,
-Alex

On 5/30/17, 7:15 PM, "Josh Tynjala" <joshtynjala@gmail.com> wrote:

>I could not find a way to parse extra command line arguments with an npm
>install command. If you could figure that out, that would be better!
>
>- Josh
>
>On May 30, 2017 6:56 PM, "OmPrakash Muppirala" <bigosmallm@gmail.com>
>wrote:
>
>Awesome! I had this as a TODO.  I can at least help with testing this out
>now.
>
>I can also push the bits to the npm registry when we go live with the
>release.
>
>Also, what if we pass them as command line args? Do you mind if I make
>this
>change?
>
>Thanks,
>Om
>
>
>On May 30, 2017 11:47 AM, "Josh Tynjala" <joshtynjala@gmail.com> wrote:
>
>I got the npm version of FlexJS 0.8.0 working with a couple of minor
>fixes.
>It looks good to go for the release!
>
>I also simplified how to test the npm version locally from the
>flex-utilities repo to make it download nightly builds (previously, you
>needed to manually change some JS code):
>
>cd flex-utilities
>npm config set flexjs:flexjs_custom_url
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheflex
>build.cloudapp.net%3A8080%2Fjob%2Fflex-asjs_release_branch%2F&data=02%7C01
>%7C%7C8ea9163b8a4f40e1e30c08d4a7cafb9b%7Cfa7b1b5a7b34438794aed2c178decee1%
>7C0%7C0%7C636317937627432987&sdata=ezcbLDOwjYz3oG3dO8RDtA71Xv%2FfKUgG77enA
>Use3JY%3D&reserved=0
>lastSuccessfulBuild/artifact/out/apache-flex-flexjs-0.8.0-bin.zip
>npm config set flexjs:falcon_custom_url
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheflex
>build.cloudapp.net%3A8080%2Fjob%2Fflex-falcon%2520release%2520branch%2F&da
>ta=02%7C01%7C%7C8ea9163b8a4f40e1e30c08d4a7cafb9b%7Cfa7b1b5a7b34438794aed2c
>178decee1%7C0%7C0%7C636317937627432987&sdata=jiM4u89B6Ea%2F4cRLi0Vw1111SMc
>%2FspYvxcIBFBtsjBw%3D&reserved=0
>lastSuccessfulBuild/artifact/out/apache-flex-falconjx-0.8.0-bin.zip
>npm install -g ./npm-flexjs/
>
>Those are the URLs to the latest builds from the release branches. It
>could
>be used with regular nightly builds from the develop branch and release
>candidate builds too.
>
>When you're done, you should delete the configuration keys:
>
>npm config delete flexjs:flexjs_custom_url
>npm config delete flexjs:falcon_custom_url
>
>- Josh
>
>On Fri, May 26, 2017 at 4:51 PM, Josh Tynjala <joshtynjala@gmail.com>
>wrote:
>
>> I can test installing FlexJS 0.8.0 with NPM early next week, if no one
>> else finds the time. I don't remember the exact process of testing
>>locally
>> with a nightly build of FlexJS, but I think I figured it out pretty
>>easily
>> when I made some tweaks a while back.
>>
>> - Josh
>>
>> On Fri, May 26, 2017 at 2:43 PM, Alex Harui <aharui@adobe.com.invalid>
>> wrote:
>>
>>> I'm still working on the TLF fix.  I saw Josh's commit about Node
>support.
>>> Does someone have time to test out our Node/NPM stuff?  It might need
>some
>>> tuning after this dual-compile feature.
>>>
>>> -Alex
>>>
>>> On 5/26/17, 8:29 AM, "Alex Harui" <aharui@adobe.com.INVALID> wrote:
>>>
>>> >
>>> >
>>> >On 5/26/17, 8:07 AM, "piotrz" <piotrzarzycki21@gmail.com> wrote:
>>> >
>>> >>Alex,
>>> >>
>>> >>That is correct I have FALCON_HOME set up. I will try as fast as I
>>>can
>>> >>run
>>> >>it once again, but there is possibility that will be on Sunday.
>>> >>
>>> >>Any chance to try by you also maven build with command line above ?
>>>I'm
>>> >>wondering if you also experience such issue as Santanu. Personally I
>>> >>didn't
>>> >>have it yesterday.
>>> >
>>> >I will try it when I get through this fix for the TLF branch.  For
>>>me, I
>>> >believe I've always had to separately use the Mavenizer to get
>>>com.adobe
>>> >artifacts.  I'm not sure if that's expected or not.  You might want to
>>> >check the archives to see if there is any mention of how to get
>com.adobe
>>> >artifacts.  I think there maybe issues with not having recent versions
>of
>>> >Maven and/or whether to use settings-template.xml.
>>> >
>>> >I don't want to take the time to help you look into this right now.
>>> >
>>> >Thanks,
>>> >-Alex
>>> >
>>>
>>>
>>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message