Re: NPM for Royale (was Re: Repos and Releases)

I see your point, but I would rather have the package name describe the output format instead of one of the runtimes that can handle that format. If we output web assembly someday, I would want to use -wasm instead of listing one or more of the runtimes that can handle that. My 2 cents, -Alex On

Re: NPM for Royale (was Re: Repos and Releases)

On Dec 17, 2017 9:44 PM, "Alex Harui" wrote: Why "Air" and not "SWF"? Not sure I understand your logic. -Alex SWF is generally associated with Flash Player which is going to go away soon. AIR makes it more obvious that we will support AIR runtimes. Unless of

Re: NPM for Royale (was Re: Repos and Releases)

Why "Air" and not "SWF"? Not sure I understand your logic. -Alex On 12/17/17, 12:25 AM, "omup...@gmail.com on behalf of OmPrakash Muppirala" wrote: >I'm making progress on this front. > >I will get the apache-royale npm package first. Let's

Re: NPM for Royale (was Re: Repos and Releases)

On Sun, Dec 17, 2017 at 12:57 AM, Piotr Zarzycki wrote: > Hi Om, > > In the other thread there is a proposition about package naming. Alex and > me propose something. > > Thanks, > Piotr > I thought that was for naming the binary artifact? This is for naming the npm

Re: NPM for Royale (was Re: Repos and Releases)

Hi Om, In the other thread there is a proposition about package naming. Alex and me propose something. Thanks, Piotr On Sun, Dec 17, 2017, 09:26 OmPrakash Muppirala wrote: > I'm making progress on this front. > > I will get the apache-royale npm package first. Let's

Re: NPM for Royale (was Re: Repos and Releases)

I'm making progress on this front. I will get the apache-royale npm package first. Let's test this out and figure out the next steps for the one with swf version. Would it be better to call it apache-royale-with-air instead of apache-royale-with-swf? Thanks, Om On Tue, Dec 12, 2017 at 1:34

Re: NPM for Royale (was Re: Repos and Releases)

OK, we can stick with two standalone packages. FWIW, the CI build finished and I successfully ran: sudo npm install -g http://apacheflexbuild.cloudapp.net:8080/job/royale-asjs/lastSuccessfulBuil d/artifact/out/apache-royale-jsonly-0.9.0-bin.tar.gz The npm progress bar did not show anything at

Re: NPM for Royale (was Re: Repos and Releases)

FWIW, we also have the option of making the SWF support more of an "add-on" instead of its own package. IOW, right now both packages contain mostly the same files and the SWF support is additional files and some slightly different settings. An add-on package would just contain the additional

Re: NPM for Royale (was Re: Repos and Releases)

I think it would be good if we do: apache-royale-x.x.x and apache-royale-with-swf-x.x.x. That makes it much clearer. Thanks, Om On Tue, Dec 12, 2017 at 11:04 AM, Alex Harui wrote: > OK, I think I got the packaging fixed. The CI server is building it and > should

Re: NPM for Royale (was Re: Repos and Releases)

OK, I think I got the packaging fixed. The CI server is building it and should finish in 90 minutes or so. You can try it out locally if you want by syncing up and running "ant release" and pointing NPM at the tar.gz file in the out folder. I think you need to "npm uninstall flexjs" first. I

Re: NPM for Royale (was Re: Repos and Releases)

The package on the CI server aren't working with NPM. I think I messed up the Ant script. Looking into it now. -Alex On 12/12/17, 10:10 AM, "omup...@gmail.com on behalf of OmPrakash Muppirala" wrote: >On Dec 12, 2017 8:41 AM, "Alex Harui"

Re: NPM for Royale (was Re: Repos and Releases)

On Dec 12, 2017 8:41 AM, "Alex Harui" wrote: On 12/12/17, 3:51 AM, "omup...@gmail.com on behalf of OmPrakash Muppirala" wrote: >On Dec 12, 2017 12:25 AM, "Alex Harui" wrote: > >I just

Re: NPM for Royale (was Re: Repos and Releases)

On Dec 12, 2017 12:25 AM, "Alex Harui" wrote: I did some reading about NPM this evening. I think that we can use NPM as a distribution server. It looked like in FlexJS, we still pulled all of the artifacts from the mirrors, but I don't think that is a requirement.

Re: NPM for Royale (was Re: Repos and Releases)

Hi Alex, that seems good to me, as we have this finished I'll be updating the website with final commands Thanks Carlos 2017-12-12 9:25 GMT+01:00 Alex Harui : > I did some reading about NPM this evening. I think that we can use NPM as > a distribution server. It

NPM for Royale (was Re: Repos and Releases)

I did some reading about NPM this evening. I think that we can use NPM as a distribution server. It looked like in FlexJS, we still pulled all of the artifacts from the mirrors, but I don't think that is a requirement. Now that the current package bundles all 3 repos into a tarball, that