Jenkins build is back to normal : royale-asjs #1284

See

Build failed in Jenkins: royale-typedefs #678

See -- Started by timer Building on master in workspace > git.exe rev-parse

Jenkins build is back to normal : royale-asjs_jsonly #1480

See

Re: Ant Build Problem

Interesting. FlexUnit has two similar SWCS: flexunit-4.3.0-20140410-as3_4.12.0.swc flexunit-4.3.0-20140410-flex_4.12.0.swc For some reason your build is picking up the "flex" one, whereas other builds are picking up the "as3" one. The "as3" one is built after the "flex" one, so the classes in

Re: September report

Correct! I'm going to push 0.9.4. On Fri, Sep 7, 2018, 8:50 PM Carlos Rovira wrote: > Hi, > > I think 0.9.3 is not available right and will be 0.9.4 > If I found something else I'll report > > thanks > > > > El vie., 7 sept. 2018 a las 18:38, Alex Harui () > escribió: > > > I just added a

Re: setting left, top styles vía Javascript has no effect on IE11

ok, I'll investigate it and see what I find thanks! El vie., 7 sept. 2018 a las 21:02, Alex Harui () escribió: > I haven't seen a problem like this before. I would recommend writing a > small test case in JSFiddle or locally and trying different ways of setting > the style property. Maybe IE

Re: setting left, top styles vía Javascript has no effect on IE11

I haven't seen a problem like this before. I would recommend writing a small test case in JSFiddle or locally and trying different ways of setting the style property. Maybe IE won't accept left/top if position isn't absolute/relative. HTH, -Alex On 9/7/18, 11:52 AM, "Carlos Rovira" wrote:

Re: setting left, top styles vía Javascript has no effect on IE11

Just to refresh this, if someone knows something about why Royale could be failing to set styles left and top on IE11 let me know so I can fix and make this compatible in IE11 thanks! Carlos El lun., 3 sept. 2018 a las 13:15, Carlos Rovira () escribió: > Hi, > > we have currently 2 bugs in

Re: September report

Hi, I think 0.9.3 is not available right and will be 0.9.4 If I found something else I'll report thanks El vie., 7 sept. 2018 a las 18:38, Alex Harui () escribió: > I just added a September report. I basically copied June and updated > numbers. IMO, what we need to report really hasn't

Re: [royale-typedefs] branch develop updated: try removing patch step now that royale-extras has been updated

Hi, I can confirm now maven typedefs builds right thanks! :) El vie., 7 sept. 2018 a las 17:59, Alex Harui () escribió: > Looks like the download plugin doesn't check for updates on files. I > thought it was just my local setup and deleted the cached file, but it > looks like we should skip the

Re: Ant Build Problem

Hi Alex this is the full output: - first is the ant all - then is the swfdump https://www.dropbox.com/s/ewyekwoes40k1ce/swfdump-FlexUnitRoyaleApplication.swf.txt?dl=0 Hope you find the issue Thanks Carlos El vie., 7 sept. 2018 a las 20:42, Alex Harui () escribió: > Yes, use swfdump -abc

Re: Ant Build Problem

Yes, use swfdump -abc on that file. But don't send the results in an email. Post a link to it. Thanks, -Alex On 9/7/18, 11:38 AM, "Carlos Rovira" wrote: Hi Alex, pointing to flex-sdk repo source folder does not change and Flash Player Debugger continues showing:

Re: Ant Build Problem

Hi Alex, pointing to flex-sdk repo source folder does not change and Flash Player Debugger continues showing: VerifyError: Error #1014: Class IResponder could not be found. To do the SWFDump, I understand that I must do it over this file right? [flexunit]

Re: Ant Build Problem

Hmm. One difference I noticed was that my FLEX_HOME points to the flex-sdk repo instead of a full installed Flex SDK. You can try changing that to see if that is causing a problem. Otherwise, SWFDump the SWF (with the -abc option) and post the results. -Alex On 9/7/18, 11:03 AM, "Carlos

Re: Ant Build Problem

Hi, I'm finding this problem trying to build with ANT. It seems it never was addressed, but is clear that we have a problem somewhere that make flex unit test run with not the expected code. I have all required environment vars declared: JAVA_HOME to 1.8.0_181-b13 ANT_HOME to 1.10.5

Build failed in Jenkins: royale-compiler #420

See Changes: [harbs] Worked around bug were rest param causes RTE in closure compiler -- [...truncated 89.13 KB...] [mkdir] Created dir:

Build failed in Jenkins: royale-asjs_jsonly #1479

rce-path = <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/projects/*/src/main/royale> clean: super-clean: [delete] Deleting directory <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/themes/Spa

Jenkins build is back to normal : royale-typedefs #677

See

Re: September report

I just added a September report. I basically copied June and updated numbers. IMO, what we need to report really hasn't changed much in 3 months, but if I've forgotten something, feel free to add it. https://github.com/apache/royale-asjs/wiki/Board-Report-2018-9 HTH, -Alex On 9/7/18, 3:30

Re: [royale-compiler] branch develop updated: Worked around bug were rest param causes RTE in closure compiler

This does not look right to me. The JSDoc says that a variable number of arguments is supposed to use "...". This change makes it look iike the annotation is one parameter of any type. -Alex On 9/7/18, 1:53 AM, "ha...@apache.org" wrote: This is an automated email from the ASF

Re: GOOG::DEBUG

The fix does not look right to me. Here are a link that indicates that variable number of arguments should be using "...". https://github.com/google/closure-compiler/wiki/Annotating-JavaScript-for-the-Closure-Compiler This link indicates that the annotation for trace should be {...*}

Re: [royale-typedefs] branch develop updated: try removing patch step now that royale-extras has been updated

Looks like the download plugin doesn't check for updates on files. I thought it was just my local setup and deleted the cached file, but it looks like we should skip the cache always if there is a chance the file can change. I just pushed changes for that. -Alex On 9/7/18, 12:43 AM, "Carlos

Re: MXRoyale and VS Code

1. Build royale-asjs using ant. 2. Copy the player folder with the playerglobal.swc structure to the libs folder (it gets cleaned out when you do a full build of ant). I wrote a script to do this for me. Here’s what I use for that:

Re: MXRoyale and VS Code

Hi Harbs, I'm still a bit lost trying to see how to get code intelligence for VS Code. Can you provide a bit of exaplanation about how do you do to get it? (I assume that I will imply some ANT use) If you can share, I'll try this weekend to get up for me and then hopefully try to use the knowledge

September report

We need to put together a report for this month. My availability is very limited this month. It would be very helpful if others could help putting together the report on the wiki. Thanks, Harbs

MXRoyale and VS Code

I just finished setting up MXRoyale for VS Code. We now get code intelligence and the number of errors/warnings is reasonable. It should make it much easier for me (and hopefully others) to work on MXRoyale. I’m not available until Wednesday. Hopefully then I’ll be able to put some more time

Re: GOOG::DEBUG

Hi Harbs, maven if passing right now (the only think that broken now is the latest commit to typedefs, that I have to remove locally). Thanks! El vie., 7 sept. 2018 a las 10:55, Harbs () escribió: > I just committed a fix for this. > > We can discuss further, but at least the build should work…

Re: GOOG::DEBUG

I just committed a fix for this. We can discuss further, but at least the build should work… > On Sep 7, 2018, at 10:55 AM, Carlos Rovira wrote: > > Right, I'm seeing as well JewelExample failing on compile > > thanks > > El vie., 7 sept. 2018 a las 9:13, Harbs () escribió: > >> I’m saying

Re: GOOG::DEBUG

Right, I'm seeing as well JewelExample failing on compile thanks El vie., 7 sept. 2018 a las 9:13, Harbs () escribió: > I’m saying that a param defined as {…} confuses the closure compiler when > you have the rest redefined as an array anywhere but the first line of the > function. It seems

Re: [Discuss] Start release process 0.9.3

Hi, I was thinking that we have debug broken right? I mean, we started a thread about debug (in browsers or in IDEs) and I think nobody here could debug at that time. Was someone successful at that time? if this is broken, I think it would be good to take a look at this issue since this could be

Re: [royale-typedefs] branch develop updated: try removing patch step now that royale-extras has been updated

Hi, this change make maven for typedefs not pass. This is the error SNAPSHOT:generate-extern *(default-generate-extern)* on project royale-typedefs-googlemaps: *Execution default-generate-extern of goal org.apache.royale.compiler:royale-maven-plugin:0.9.3-SNAPSHOT:generate-extern failed: INTERNAL

Re: GOOG::DEBUG

I’m saying that a param defined as {…} confuses the closure compiler when you have the rest redefined as an array anywhere but the first line of the function. It seems like a bug in the closure compiler. Changing: rest = Array.prototype.slice.call(arguments, 0); to: var rest =

Re: GOOG::DEBUG

Are you saying some recent change to the compiler is now generating: @param {...} rest If so, what changed caused that output? If not, why did it not fail before? We should be generating whatever Google says we should generate for rest parameters. Although I did ponder the impact of

Re: GOOG::DEBUG

It looks like the problem is caused by: * @param {...} rest What would happen if we remove the @param or change it to @param {*=} rest? Both of those work. > On Sep 7, 2018, at 8:35 AM, Alex Harui wrote: > > But first, I'm not sure your idea is going to work in all cases. See if you > get

Re: GOOG::DEBUG

OK. I’ll look into it. > On Sep 7, 2018, at 8:35 AM, Alex Harui wrote: > > This seems to be causing problems. The JewelExample is failing. I think it > doesn't like the early exit before the rest parameter is handled. > > I don't think we need to worry about this for SWF output. > > There