Build failed in Jenkins: royale-typedefs #1658

2019-10-02 Thread Apache Royale CI Server
See -- Started by timer [EnvInject] - Loading node environment variables. Building on master in workspace

Build failed in Jenkins: royale-asjs #2766

2019-10-02 Thread Apache Royale CI Server
See -- [...truncated 277.06 KB...] [echo] ROYALE_COMPILER_HOME is C:\Program Files (x86)\Jenkins\workspace\royale-compiler\compiler check-dependency:

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

2019-10-02 Thread Apache Royale CI Server
See

Build failed in Jenkins: royale-asjs_jsonly #3627

2019-10-02 Thread Apache Royale CI Server
See -- [...truncated 273.38 KB...] [echo] ROYALE_COMPILER_HOME is C:\Program Files (x86)\Jenkins\workspace\royale-compiler\compiler

Build failed in Jenkins: royale-asjs_MXTests #1211

2019-10-02 Thread Apache Royale CI Server
See Changes: [greg.dove] Consistency between ant and maven. Fixes ASDoc ant build for swf -- [...truncated 1003.11 KB...] [mxmlc]

Jenkins build is back to normal : Royale_ASDoc_Example #2500

2019-10-02 Thread Apache Royale CI Server
See

Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-10-02 Thread Alex Harui
Responses inline... On 10/2/19, 1:37 AM, "Piotr Zarzycki" wrote: Just to understand something. releasecandidate script is using tag instead release branch to whole operation of increase version ? No, the "get_head_of_rc_branches" target should get you the head. > Hi, >

Build failed in Jenkins: royale-asjs_MXTests #1210

2019-10-02 Thread Apache Royale CI Server
See Changes: [piotrzarzycki21] RequireSelection: Fix maximum call stack size exceeded [piotrzarzycki21] RequireSelection should update selection on dataProviderChange as well

Build failed in Jenkins: Royale_ASDoc_Example #2499

2019-10-02 Thread Apache Royale CI Server
See Changes: [piotrzarzycki21] RequireSelection: Fix maximum call stack size exceeded [piotrzarzycki21] RequireSelection should update selection on dataProviderChange as well

Re: Beads and events

2019-10-02 Thread Alex Harui
I agree there is a general problem. In many cases, when you add a bead explicitly, the handler should be specified on the bead itself: In theory, the main scenario when folks run into this is when beads are assigned in CSS. The "simplest" answer is subclassing and adding the event

Build failed in Jenkins: royale-asjs_MXTests #1209

2019-10-02 Thread Apache Royale CI Server
See -- [...truncated 1004.60 KB...] [mxmlc] scanning for overrides: ObjectUtil [mxmlc] scanning for overrides: SolidBorderUtil [mxmlc]

Build failed in Jenkins: Royale_ASDoc_Example #2498

2019-10-02 Thread Apache Royale CI Server
See -- [...truncated 42.32 KB...] [java]^ [java] [java]

Beads and events

2019-10-02 Thread Harbs
BrowserResizeListener dispatches a sizeChanged event on the view when the browser is resized. Someone is struggling with how to use it: https://stackoverflow.com/questions/58128204/how-do-i-get-the-application-width-height-based-on-browser-height-width

Build failed in Jenkins: royale-asjs_MXTests #1208

2019-10-02 Thread Apache Royale CI Server
See Changes: [greg.dove] RoyaleArrayLike support (IArrayList and BinaryData) [greg.dove] Support iteration over keys as well as values (for-in as well as [greg.dove] Baseline XML

Build failed in Jenkins: Royale_ASDoc_Example #2497

2019-10-02 Thread Apache Royale CI Server
See Changes: [greg.dove] RoyaleArrayLike support (IArrayList and BinaryData) [greg.dove] Support iteration over keys as well as values (for-in as well as [greg.dove] Baseline

RoyaleArrayLike - quick summary

2019-10-02 Thread Greg Dove
Just a quick overview of something I added that I was meaning to do for a long time. It makes a huge difference when porting from things like ArrayCollection to Royale ArrayList. It saved me hours of menial stuff on something I had to do recently, and that was also a time-consuming task that both

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

2019-10-02 Thread Apache Royale CI Server
See

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

2019-10-02 Thread Apache Royale CI Server
See

Re: Heads up on XML

2019-10-02 Thread Harbs
OK. I’ll test memory with and without your changes and let you know the differences. :-) Harbs > On Oct 2, 2019, at 11:29 AM, Greg Dove wrote: > > @harbs > > FYI in addition to some other stuff, I am close to pushing my updates to > XML. This should be in the next hour or so. > > I kept

Build failed in Jenkins: royale-asjs_jsonly #3621

2019-10-02 Thread Apache Royale CI Server
See Changes: [greg.dove] RoyaleArrayLike support (IArrayList and BinaryData) [greg.dove] Support iteration over keys as well as values (for-in as well as [greg.dove] Baseline XML

Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-10-02 Thread Piotr Zarzycki
Just to understand something. releasecandidate script is using tag instead release branch to whole operation of increase version ? Cause on release branch I have already version increased, so what's the point of doing anything using tag ? śr., 2 paź 2019 o 10:27 Piotr Zarzycki napisał(a): > Hi,

Re: Heads up on XML

2019-10-02 Thread Greg Dove
@harbs FYI in addition to some other stuff, I am close to pushing my updates to XML. This should be in the next hour or so. I kept the QName caching pretty close to how you had it, with only some minor changes. I tried to do some extra memory optimization, and in theory it should provide better

Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-10-02 Thread Piotr Zarzycki
Hi, I just tried releasecandidate script. It contains following steps. One step previous was move in svn binaries from dev folder to release - I omit that cause I did it already manually. Launching following steps I reached