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" <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 http://apacheflexbuild.cloudapp.net:8080/job/flex-asjs_release_branch/ lastSuccessfulBuild/artifact/out/apache-flex-flexjs-0.8.0-bin.zip npm config set flexjs:falcon_custom_url http://apacheflexbuild.cloudapp.net:8080/job/flex-falcon%20release%20branch/ 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 <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 >> > >> >> >
