Excellent! Very helpful. I am still fixing issues of Dual and the TLF branch. It found some good bugs.
-Alex On 5/30/17, 11:46 AM, "Josh Tynjala" <joshtynj...@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%2FlastSuccessfu >lBuild%2Fartifact%2Fout%2Fapache-flex-flexjs-0.8.0-bin.zip&data=02%7C01%7C >%7C6aae6367bd7e4eaa377d08d4a78c45f2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0 >%7C0%7C636317668292056590&sdata=EZoLyn6I3ZJRvc5oBkopcL%2B6AkHVyMvQ2wcMpWUO >jN0%3D&reserved=0 >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%2Flas >tSuccessfulBuild%2Fartifact%2Fout%2Fapache-flex-falconjx-0.8.0-bin.zip&dat >a=02%7C01%7C%7C6aae6367bd7e4eaa377d08d4a78c45f2%7Cfa7b1b5a7b34438794aed2c1 >78decee1%7C0%7C0%7C636317668292056590&sdata=VEQF%2FOi8%2FJjHregzU9JzAPT7Sv >cG52ZaVd1yaMVstgc%3D&reserved=0 >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 <joshtynj...@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 <aha...@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" <aha...@adobe.com.INVALID> wrote: >>> >>> > >>> > >>> >On 5/26/17, 8:07 AM, "piotrz" <piotrzarzyck...@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 >>> > >>> >>> >>
