Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

I recently had a hard drive crash, so I have a new hard drive without many past artifacts, a virgin system. I was using 0.9.4 in Moonshine before the crash without, as far as I know, any Ant or npm magic. Have things changed significantly between that release and this one?

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

That would be fine. I am stuck, evidently, at something in the 0.9.6 release of the JS-only version being broken. Virus-free. www.avast.com

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

Well said Andrew - couldn’t agree more. I am a long time Flex developer (back to the beta) and have tried many times to get started with Royale, so that we can move all our existing apps over,  but have fallen at the first hurdle every time. We have now given up and are moving most over to

Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

Hey Andrew, I recommend you make small workaround. 1) Take again JS only version of Royale 0.9.6 2) Open framework/royale-config.xml 3) Remove everything what is inside tag library-path 4) Try rebuild Thanks, Piotr On Thu, Oct 10, 2019, 12:21 AM Andrew Wetmore wrote: > I recently had a hard

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

Node/npm is pretty normal prerequisite for most JS development these days, but I understand your point. Ideally, we should be encouraging developers to start with the JS-only version, which doesn't require any of those special dependencies (other than Java, which is necessary to run the

Build failed in Jenkins: royale-asjs #10

See Changes: -- [...truncated 2.04 MB...] [java] ^ [java] [java]

Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

Hey Richard, When you were trying Royale - did you ask for help on dev list or in private? I agree that at the beginning earlier it was a problem to start. Now that barrier is a bit lower. If you need any help you can ask here or in private we are happy to help and get you move forward. Thanks,

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

You were probably using the JS-only version of 0.9.4. As I said, the JS-only version does not require Ant or npm. You're not missing any new requirements/dependencies that were added between 0.9.4 and 0.9.6. *The JS-only version of 0.9.6 is simply broken.* Something in the build went wrong, and

Build failed in Jenkins: royale-asjs #11

See Changes: -- [...truncated 2.04 MB...] [java] ^ [java] [java]

[ANNOUNCE] Apache Royale 0.9.6 released!

The Apache Royale community is pleased to announce the release of Apache Royale 0.9.6. The Apache Royale project is the next generation of the Apache Flex SDK. It lets developers use MXML and ActionScript 3 to generate HTML/JS/CSS applications which can run natively in browsers. The

Build failed in Jenkins: royale-asjs #5

See Changes: -- [...truncated 1.34 MB...] [mxmlc] scanning for overrides: IApplicationView [mxmlc] scanning for overrides: IValuesImpl [mxmlc]

Re: How to skin components

My apologies. I'll be more thoughtful and considerate in the future. On Tue, 8 Oct 2019 at 23:32, Carlos Rovira wrote: > > Hi Chris, > before going far beyond, I want that you consider the way you are referring > to the concepts you don't share. Talk about that as "silly" seems not very >

Re: Nightly Build Server going offline

Hi, If we are going to stay for a longer time with nightly build offline we should also update link to nightly build on our website. If it's only for couple of days no problem. Thanks, Piotr wt., 8 paź 2019 o 20:04 Carlos Rovira napisał(a): > 爛 > > :) > > El mar., 8 oct. 2019 a las 18:12,

CI emails

I'd like to suggest a new mailing list be created for all the CI and other build related emails. I'm suggesting this to keep the dev mailing clean from these automated emails. -- Chris -- Chris Velevitch m: 0415 469 095

Re: Release 0.9.6 Announce for web post?

Hi Piotr, ok, I'm waiting for your announcement thanks El mar., 8 oct. 2019 a las 21:49, Piotr Zarzycki () escribió: > Let me make announce. I will do that tomorrow morning. :) > > You can next post social media. > > On Tue, Oct 8, 2019, 8:24 PM Carlos Rovira > wrote: > > > Hi > > > > website

Re: Release 0.9.6 Announce for web post?

Hi Carlos, I will send announce in couple of minutes. In the meantime I have found that one thing seems to be wrong in blog post. Sentence: "Updates to the RELEASE_NOTES made after this file was packaged into the release artifacts can be found at this link

Build failed in Jenkins: royale-asjs #6

See Changes: -- [...truncated 1.35 MB...] [mxmlc] scanning for overrides: IApplicationView [mxmlc] scanning for overrides: IValuesImpl [mxmlc]

Re: How to skin components

Thanks for consider it Chris, about you question, I saw it responded in other of your thread by Alex. Thanks El mié., 9 oct. 2019 a las 9:57, Chris Velevitch () escribió: > My apologies. I'll be more thoughtful and considerate in the future. > > On Tue, 8 Oct 2019 at 23:32, Carlos Rovira >

Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

Hi Guys, It looks like we have broken royale-config in released SDK. Andrew raised in Moonshine GitHub issue that he couldn't build Hello World project. I tried Moonshine and downloaded JS-only version of SDK. I get following error [1]. I downloaded JS-SWF version and tried compile project again

Re: Nightly Build Server going offline

Hope Alex can let us know what he thinks about timing We can do a quick change directly in production if needed and then revert when needed to not mesh with pre for something punctual... El mié., 9 oct. 2019 a las 9:50, Piotr Zarzycki () escribió: > Hi, > > If we are going to stay for a longer

Re: maven fails on build royale-asjs 0.9.7-SNAPSHOT

Many thanks Greg, your change worked for me and I can rely on it in the meanwhile. Thanks! :) El mar., 8 oct. 2019 a las 21:11, Greg Dove () escribió: > Carlos, you need: > > mvn clean install -Pmain,generate-swcs-for-swf -Dgenerate.swf.swcs=true > > But I think that could be avoided. I hope

Re: Nightly Build Server going offline

I sent an email to private@ with the new credentials and URL. I don't know how to get the old URL back at this point in time. The JSOnly build succeeded. I'm trying to get the JS-SWF build to succeed. http://apacheroyaleci2.westus2.cloudapp.azure.com:8080 We should update all links to use

Build failed in Jenkins: royale-asjs #7

See Changes: -- [...truncated 1.34 MB...] [mxmlc] scanning for overrides: ITextItemRenderer [mxmlc] scanning for overrides: UIItemRendererBase [mxmlc]

Re: Nightly Build Server going offline

Well, the build made it a bit further after I set the default app for .swf files. However, it seems that Flash Player is not picking up the trust file that the RoyaleUnit Ant Task is creating. Based on the console log, the Jenkins job seems to be creating it here:

Re: Nightly Build Server going offline

I logged into the server and discovered that js-swf build was failing because there was no default program for .swf files. I set the flashplayerdebugger.exe that you downloaded as the default, and I was able to successfully run the tests in a PowerShell window. I started a new build in Jenkins, so

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

I just installed @apache-royale/royale-js from npm, and I'm seeing the same errors. -- Josh Tynjala Bowler Hat LLC On Wed, Oct 9, 2019 at 6:52 AM Piotr Zarzycki wrote: > Hi Guys, > > It looks like we have broken royale-config in released SDK. Andrew raised > in

Build failed in Jenkins: royale-asjs #8

See Changes: -- [...truncated 1.34 MB...] [mxmlc] scanning for overrides: ITextItemRenderer [mxmlc] scanning for overrides: UIItemRendererBase [mxmlc]

Re: CI emails

IOM, we need the committers to see these in order to fix broken builds. You might be better off filtering out email from apacheroyal...@gmail.com HTH, -Alex On 10/9/19, 1:11 AM, "Chris Velevitch" wrote: I'd like to suggest a new mailing list be created for all the CI and other build

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

When you build with AIR_HOME (which is required to create release artifacts, since we want to produce both jsonly and js-swf in one run), a different target called "jsonly-package" run and tries to muck with some files before packaging the js-only artifacts. It could be that the jsonly-package

RoyaleUnit testing - swf player version used for testing

This is partly for general input, but also for Josh specifically in relation to RoyaleUnit Background I am continuing to add unit tests, mostly language level stuff. It is rare, but there can be some things to account for in terms of differences caused by the player being used for testing (and

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

It looks like the Ant target that updates the library-path for the JS-only build is called tweak-for-jsonly. Copied here for convenience: https://paste.apache.org/asn0i I see that it has unless="env.AIR_HOME", which means that this target is skipped if the AIR_HOME environment variable is set.

Re: Nightly Build Server going offline

OK, I will switch the service to use the ApacheRoyaleCI account and see what happens. -ALex On 10/9/19, 9:12 AM, "Josh Tynjala" wrote: Well, the build made it a bit further after I set the default app for .swf files. However, it seems that Flash Player is not picking up the trust

Re: RoyaleUnit testing - swf player version used for testing

Yeah, I think it would make a lot of sense to update our build scripts to use this environment variable when launching RoyaleUnit tests. I'm pretty sure that it is already set on the CI server for Mustella tests, so we should have the build consistently use the same version for everything. As a

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

I wiped out the previous project and tried again with the Royale JS-SWF version. When I try to compile the project in Moonshine for either JS or Flash, I see this error message: "This SDK does not contains playerglobal.swc in frameworks\libs\player\11.7\playerglobal.swc. Download playerglobal

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

If you downloaded the js-swf binary distribution, you need to add the Adobe dependencies manually. We cannot distribute them. The playerglobal.swc in the js-only version is not the real one from Adobe. It's just a placeholder to make certain IDEs happy. I think it's just a copy of js.swc. --

Re: RoyaleUnit testing - swf player version used for testing

The RoyaleUnit Ant task has a "command" parameter where we can pass in the path of a specific executable. I don't think the Ant task should try to read a magic environment variable. Instead, we can reference the environment variable inside the Ant script. Something like this should probably work:

Build failed in Jenkins: royale-asjs #9

See Changes: -- [...truncated 2.04 MB...] [java] ^ [java] [java]

Re: RoyaleUnit testing - swf player version used for testing

Thanks Josh, that definitely sounds like a better option. I will give that a try for that side of things locally. Maybe we can also use this on the CI server to specify the version that is used? On Thu, Oct 10, 2019 at 7:30 AM Josh Tynjala wrote: > The RoyaleUnit Ant task has a "command"

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

Thanks @Josh Tynjala . Do we say that anywhere in the instructions where a new user would run into it? Virus-free. www.avast.com

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

The main royale-asjs README mentions the Adobe stuff as optional dependencies, but the instructions seem to be aimed at contributors: https://github.com/apache/royale-asjs#additional-prerequisites-for-swf-output What a non-contributor user is expected to do appears to be mentioned on this page