Update Royale Nightly Download Links to HTTPS about moonshine-sdk-installer HOT 24 CLOSED

@rat-moonshine Apache Royale has been finally released! Please update version to 0.9.8 -> https://www.apache.org/dyn/closer.lua/royale/0.9.8/binaries/apache-royale-0.9.8-bin-js.tar.gz

Change nighly build download to version 0.9.9 using following location -> https://nightlies.apache.org/Royale/Royale-asjs/
In that case note that whenever I downloaded manually Royale from that location I wasn't able build application on Mac OSX. I'm getting following error:

apache-royale-0.9.9-SNAPSHOT/js/bin/mxmlc: /bin/sh^M: bad interpreter: No such file or directory

When I copy mxmlc file from downloaded SDK from this location and replace in apache-royale-0.9.9-SNAPSHOT/js/bin everything starts working. - Maybe it's the matter of having proper permission to the file.

from moonshine-sdk-installer.

Okay. I'll give a look into the installation problem you've mentioned.

from moonshine-sdk-installer.

My suggestion maybe would be just initially use standard link for Nightly so user won't have any breaks with downloading nightly and next play with my new links. Right now nightly download won't work probably until you change it to 0.9.9.

from moonshine-sdk-installer.

I'm unclear what you meant by standard link for Nightly, are you suggesting to use from the servers as was here - https://github.com/Moonshine-IDE/Moonshine-SDK-Installer/blob/master/InstallerSharedCore/src/helperResources/data/moonshineHelperConfig.xml#L243 ? (URL with http protocol)

from moonshine-sdk-installer.

This link -> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/lastSuccessfulBuild/artifact/out/

Is the one which you are using right now right ?

This one is the one which I'm asking you to use -> https://nightlies.apache.org/Royale/Royale-asjs/

Change links to the one which we are using, push changes, so user can download in current released version of MSDKI Royale nightly and work on changing to new one, along with fixing my issue.

Is it more clear now ?

from moonshine-sdk-installer.

Yeah, the links are same.

from moonshine-sdk-installer.

Yeah, the links are same.

Yeah they are the same, but you are basically need to update Royale Nightly version to 0.9.9.

from moonshine-sdk-installer.

I have updated MSDKI with following changes:

1. Updated Royale SDK download URLs
2. Adjusted necessary Haxe layout fix since Feathers beta.5 update
3. Fixed an exception while changing variant dropdown in Royale SDK

Tested that SDKs have downloaded properly.

from moonshine-sdk-installer.

I have updated MSDKI with following changes:

1. Updated Royale SDK download URLs
2. Adjusted necessary Haxe layout fix since Feathers beta.5 update
3. Fixed an exception while changing variant dropdown in Royale SDK

Tested that SDKs have downloaded properly.

@rat-moonshine Cool, but I don't see these changes in 3.9.0 - Is it possible propagate url changes only to 3.9.0 without release ?

from moonshine-sdk-installer.

If that's not possible we don't have to bother to update our scripts to Nightly -> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/lastSuccessfulBuild/artifact/out/ - let's update it to https://nightlies.apache.org/Royale/Royale-asjs/ and make a release as soon as we can.

from moonshine-sdk-installer.

I have discovered why we have problems with SDK downloaded from here -> https://nightlies.apache.org/Royale/Royale-asjs/. During checkout on Apache server machine (Windows) git is changing line endings from LF to CRLF. I'm not sure how to change it's configuration there yet, but I hope I will get my answer on dev list.

from moonshine-sdk-installer.

It was issue in Maven build in Royale. Josh fixed it. We can switch our download for the next release to new url :)

from moonshine-sdk-installer.

I have updated the nightly URL with https://nightlies.apache.org/Royale/Royale-asjs/. I did a quick test building MyAccount locally on macOS, and I didn't received any compilation error this time.

from moonshine-sdk-installer.

It's working nicely on Mac OSX Big Sur. @Aszusz can you make a quick test on Windows - download nightly build of installer, install Apache Royale 0.9.9 and build some Royale application.

from moonshine-sdk-installer.

download nightly build of installer, install Apache Royale 0.9.9 and build some Royale application.

Eventually, it worked for me but I found two minor issues:

1. Immediatly after I installed Royale SDK the download button looked like this:
   
   but each time I close the installer and open it up again it looks like this:
   
   I think it used to remember your choice in previous versions.
2. After I downloaded Royale SDK it wasn't on the SDK list. I thought it's not working. I had to restart Moonshine twice (maybe first time old instance was hanging or something) for it to show up on the list.

from moonshine-sdk-installer.

I think it used to remember your choice in previous versions

I don't think we had any mechanism to remember this dropdown selection from the last time, though.

After I downloaded Royale SDK it wasn't on the SDK list. I thought it's not working. I had to restart Moonshine twice (maybe first time old instance was hanging or something) for it to show up on the list.

In my test, I able to see v0.9.9 properly listed in the SDK list during MyAccount compilation. But yes, I would like to hear if others also encountered same problem. But one thing yes, the SDK-list parsed during startup of Moonshine.

from moonshine-sdk-installer.

I did a quick test on macOS Catalina using a Moonshine build from earlier in the week. I installed a new nightly build, and it updated in Moonshine.

I created a new Royale Jewel project and chose the 0.9.9 SDK.

However, when I built the project, I got this error:

: Following path(s) are invalid or does not exists:
: Custom SDK: /Users/%user%/Downloads/MoonshineSDKs/Royale_SDK/apache-royale-0.9.9-bin-js/royale-asjs

I confirmed that the royale-asjs subdirectory does not exist.

I restarted Moonshine, and found that the Custom SDK path for this project was reported as not defined. I selected the 0.9.9 SDK again, and that cleared the error.

I tried Project > Build & Run again, and I got this error:

: /Users/%user%/Documents/Flex/temp_workspace/TestRoyale0930/src/MainContent.mxml(2): col: 1 Error: This tag could not be resolved to an ActionScript class. It will be ignored.
: <j:ApplicationResponsiveView xmlns:fx="http://ns.adobe.com/mxml/2009"
: ^
: /Users/%user%/Documents/Flex/temp_workspace/TestRoyale0930/src/TestRoyale0930.mxml(12): col: 2 Error: Cannot parse a value of type 'org.apache.royale.core.IApplicationView' from ''.
: 	<j:initialView>
: 	^
: /Users/%user%/Documents/Flex/temp_workspace/TestRoyale0930/src/TestRoyale0930.mxml(13): col: 3 Error: In initializer for 'j:initialView', type MainContent is not assignable to target type 'org.apache.royale.core.IApplicationView'.
: 		<local:MainContent />
: 		^

Am I forgetting something for my tests?

from moonshine-sdk-installer.

I confirmed that the royale-asjs subdirectory does not exist.

It was true that the earlier nightly distribution, when expands creates a sub-folder named royale-asjs having the SDK files inside it. From this newer distribution (https://nightlies.apache.org/Royale/Royale-asjs/) the royale-asjs sub-folder and other similar directories vanished keeping the SDK files in the root folder - I think this was what mentioned by @piotrzarzycki21 some time back elsewhere.

Any earlier v0.9.9 SDK-link in Moonshine targeting $v0.9.9/royale-asjs so tend to fail.

from moonshine-sdk-installer.

I tried Project > Build & Run again, and I got this error:

: /Users/%user%/Documents/Flex/temp_workspace/TestRoyale0930/src/MainContent.mxml(2): col: 1 Error: This tag could not be resolved to an ActionScript class. It will be ignored.
: <j:ApplicationResponsiveView xmlns:fx="http://ns.adobe.com/mxml/2009"
: ^
: /Users/%user%/Documents/Flex/temp_workspace/TestRoyale0930/src/TestRoyale0930.mxml(12): col: 2 Error: Cannot parse a value of type 'org.apache.royale.core.IApplicationView' from ''.
: 	<j:initialView>
: 	^
: /Users/%user%/Documents/Flex/temp_workspace/TestRoyale0930/src/TestRoyale0930.mxml(13): col: 3 Error: In initializer for 'j:initialView', type MainContent is not assignable to target type 'org.apache.royale.core.IApplicationView'.
: 		<local:MainContent />
: 		^

Am I forgetting something for my tests?

I forgot about that issue. I couldn't resolve that before release Apache Royale 0.9.8 - I just committed fix for that - we should be good with new nightly -> Moonshine-IDE/Moonshine-IDE#778

from moonshine-sdk-installer.

I don't remember configuring that 0.9.9 SDK, and it automatically cleared after I restarted Moonshine. I assumed that this entry was created automatically when the Royale Nightly build installation finished in MSDKI.

I tried to reproduce this with the latest Moonshine nightly build, but I got a different result:

1. Delete or hide the 0.9.9 nightly build
2. Restart Moonshine. Confirm that there is no 0.9.9 SDK in the list
3. Install Royale Nightly with MSDKI
4. When it finishes, Moonshine gains focus
5. Check the SDK list. BUG: the 0.9.9 SDK was not added automatically

from moonshine-sdk-installer.

I assumed that this entry was created automatically when the Royale Nightly build installation finished in MSDKI.

Okay. I need to re-check.

I shall try to reproduce the other error-steps you've described.

from moonshine-sdk-installer.

While testing with earlier MSDKI build distributing nightly with 'http' protocol, I see the v0.9.9 SDK listed below the available SDK-list and off-the visible scroll. This because the collection was not sorted, and this probably will create confusion and may look bad, as well:

I'm now sorting the list to reduce this scenario.

1. Delete or hide the 0.9.9 nightly build
2. Restart Moonshine. Confirm that there is no 0.9.9 SDK in the list
3. Install Royale Nightly with MSDKI
4. When it finishes, Moonshine gains focus
5. Check the SDK list. BUG: the 0.9.9 SDK was not added automatically

I see the newer 'https' distribution of Nightly failed to auto-added in the SDK-list because it was failing to meet the pathValidation path from the config. This pathValidation path is still true for v0.9.8 release, although we'll probably have the newer directory structure without 'royale-asjs' folder inside it from v0.9.9.

Currently, the pathValidation accepts only path, making this accept multiple paths will affect in different locations, but probably that would be the more suitable option in this case. I shall need to spend some more time having these areas changed and properly tested.

from moonshine-sdk-installer.

I made some changes affecting both Moonshine and Moonshine-SDK-Installer repositories to parse and validate multiple paths from its configuration file, and during the new-SDK-notification from MSDKI to Moonshine.

After the changes I can see v0.9.9 properly listed in SDK-list using Moonshine App Store build:

1. Delete or hide the 0.9.9 nightly build
2. Restart Moonshine. Confirm that there is no 0.9.9 SDK in the list
3. Install Royale Nightly with MSDKI
4. When it finishes, Moonshine gains focus
5. Check the SDK list: the 0.9.9 SDK properly listed as a new addition

from moonshine-sdk-installer.

This is working well for me, now. The sorting is a nice improvement!

from moonshine-sdk-installer.