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 only tried the -jsonly-
package and it installed for me.  I didn't do any further testing to see
if the command-line scripts worked or not.  If you run against the other
-bin.tar.gz it should try to run the code that downloads Adobe stuff,
which might need tuning.

I'm thinking we should create s.apache.org URLs for the nightly builds so
you could do something like:

  npm install http://s.apache.org/Royale090NightlyBuild

But before we do that, we should decide on the package names.  Right now
it is:

  apache-royale-0.9.0-bin  This contains SWF support.
  apache-royale-jsonly-0.9.0.bin

A while back I suggested:

  apache-royale-flexjs-0.9.0-bin  This contains SWF support.
  apache-royale-0.9.0.bin  The default package is JS only.

Another option is:

  apache-royale-swf-0.9.0-bin This contains SWF support.
  apache-royale-0.9.0.bin  The default package is JS only.

I still think it might be valuable to have 'flexjs' in the package name
for the package with SWF support.


Thoughts?
-Alex



On 12/12/17, 10:18 AM, "Alex Harui" <aha...@adobe.com.INVALID> wrote:

>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" <omup...@gmail.com on behalf of bigosma...@gmail.com> wrote:
>
>>On Dec 12, 2017 8:41 AM, "Alex Harui" <aha...@adobe.com.invalid> wrote:
>>
>>
>>
>>On 12/12/17, 3:51 AM, "omup...@gmail.com on behalf of OmPrakash
>>Muppirala"
>><omup...@gmail.com on behalf of bigosma...@gmail.com> wrote:
>>
>>>On Dec 12, 2017 12:25 AM, "Alex Harui" <aha...@adobe.com.invalid> wrote:
>>>
>>>I just pushed changes to see if it can work.  We'll see after the CI
>>>server builds it.  In theory, you will be able to run:
>>>
>>>    npm install
>>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapachefl
>>>e
>>>x
>>>build.cloudapp.net%3A8080%2Fjob%2Froyale-asjs%2FlastSuccessfulBuil&data=
>>>0
>>>2
>>>%7C01%7Caharui%40adobe.com%7C5d4cb0a761544b1e6dce08d54156c7cb%7Cfa7b1b5a
>>>7
>>>b
>>>34438794aed2c178decee1%7C0%7C0%7C636486763331683835&sdata=99F1YaFJunpkbE
>>>E
>>>Z
>>>WSuZdiO2LJAEHAud55Tq5tx%2FYnM%3D&reserved=0
>>>d/artifact/out/apache-royale-jsonly-0.9.0-bin.tar.gz
>>>
>>>And it should install the JSOnlu package.  Alternatively, you run:
>>>
>>>    npm install
>>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapachefl
>>>e
>>>x
>>>build.cloudapp.net%3A8080%2Fjob%2Froyale-asjs%2FlastSuccessfulBuil&data=
>>>0
>>>2
>>>%7C01%7Caharui%40adobe.com%7C5d4cb0a761544b1e6dce08d54156c7cb%7Cfa7b1b5a
>>>7
>>>b
>>>34438794aed2c178decee1%7C0%7C0%7C636486763331683835&sdata=99F1YaFJunpkbE
>>>E
>>>Z
>>>WSuZdiO2LJAEHAud55Tq5tx%2FYnM%3D&reserved=0
>>>d/artifact/out/apache-royale-0.9.0-bin.tar.gz
>>>
>>>
>>>Does this tarball contain the Adobe dependencies as well?
>>
>>No, it will try to download the Adobe stuff like the earlier npm-flexjs
>>code did.  However, it only need to try to get the Adobe stuff since
>>other
>>things it looks like it used to download are in the package (framework,
>>falcon, swfobject).
>>
>>Thanks,
>>-Alex
>>>
>>
>>Sounds good.  I will start working on this today.
>>
>>Thanks,
>>Om
>

Reply via email to