-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add links for download Apache Royale 0.9.6 #16
Comments
Does Moonshine SDK Installer also deployed to you somewhere in Moonshine website as Moonshine-IDE compilation does (at Bamboo), @piotrzarzycki21 ? |
Nope |
Yeah, I see that.. We probably need to have the deployment added to the plan also. For now, here's the link for your tests: |
Please add that changes to CHANGELOG |
I know that is an enhancement, but I think we should display somewhere version of SDK which we are providing for download. |
It doesn't have to as part of this update of course. |
I have updated the CHANGELOG. I think somewhere in old mockups there were a version figure in layouts. You can open a separate ticket for this, we shall look into that. |
I am getting a lot of errors like this with the Royale Browser Templates in Moonshine after the update:
It looks like this issue is already being discussed: http://apache-royale-development.20373.n8.nabble.com/Broken-royale-config-in-JS-only-build-of-released-Apache-Royale-SDK-0-9-6-td12515.html @piotrzarzycki21's fix worked for me: http://apache-royale-development.20373.n8.nabble.com/Broken-royale-config-in-JS-only-build-of-released-Apache-Royale-SDK-0-9-6-td12515.html#a12543 Do we want to apply this fix automatically with Moonshine SDK Installer, or is there a fix planned for the Royale SDK? |
Well I'm not sure whether from the license perspective we can do such things and provide SDK. I saw commit from Alex - it should be fixed now I nightly. I need to think whether I'm ready for release struggle again ;) |
I don't mean downloading the AIR SDK - I think we have discussed this in the past, but I don't immediately remember what we decided for this. Rather, I mean commenting out the entries in royale-config.xml. Is this a problem when we are providing the JS-only version? |
This is what I mean. I don't know whether we can do that and provide changed SDK. :) I will ask on dev on Sunday. |
What I had in mind was using the official ZIP file, but running a script afterwards to remove the lines that broke the builds (assuming they are not needed for anything else). If this is a problem with the license, then we may want to review the current behavior - I think that are adding executable file permissions to royale-asjs/bin and royale-asjs/js/bin |
Ohh... That's also great idea. @rat-moonshine what do you think about that ? |
@piotrzarzycki21, after talking with @rat-moonshine, there were some points I wanted to clarify:
|
|
Guys Alex suggested similar solution to your @JoelProminic . Let's go with that direction and we will be good with licensing. @rat-moonshine can you look into that ? I think implementation should be on Installer sight. |
Since the purpose of this issue have met, I'm creating a separate issue #17 to follow-up the patch-fix to Royale SDK. Please, let's discuss relevant things to that issue. |
We need to add newest Apache Royale release to our installer. All links for download can be found here
The text was updated successfully, but these errors were encountered: