Build failed in Jenkins: royale-asjs_MXTests #1043

See Changes: [yishayjobs] Added controller to mx radio button. [greg.dove] Restoring XML to passing tests (removed [Ignore]s). Fixes #93. Added new [yishayjobs] Let controller ti

Build failed in Jenkins: royale-asjs_MXTests #1044

See -- [...truncated 983.54 KB...] [mxmlc] scanning for overrides: ObjectUtil [mxmlc] scanning for overrides: SolidBorderUtil [mxmlc] scanning

RE: Build failed in Jenkins: royale-asjs_MXTests #1044

This is due to my latest changes. But I’m not sure about the test [1]. This [2] works as expected. Thoughts? [1] [2] https://pas

Build failed in Jenkins: royale-asjs_MXTests #1045

See -- [...truncated 984.83 KB...] [mxmlc] scanning for overrides: ObjectUtil [mxmlc] scanning for overrides: SolidBorderUtil [mxmlc] scanning

Re: Discuss of release steps preparation

Getting back to this. You can start a vote on the results. If we get this process working, it should be relatively easy for others to do releases as well so we will hopefully do releases more often and it won't matter if someone's recent changes made it into the RC or not. Also, the other com

Re: Minification problem with latest build

I've determined that when js-dynamic-access-unknown-members is true, a fully-qualified name is output differently: org["apache"]["royale"]["jewel"]["beads"]["models"].FormItemModel A fully-qualified name should not be considered dynamic access, though, so that's a bug. I'll try to get it fixed.

Re: Minification problem with latest build

Thank you Josh! It will be very helpful for future. pon., 12 sie 2019 o 19:36 Josh Tynjala napisał(a): > I've determined that when js-dynamic-access-unknown-members is true, a > fully-qualified name is output differently: > > org["apache"]["royale"]["jewel"]["beads"]["models"].FormItemModel > >

RE: Build failed in Jenkins: royale-asjs_MXTests #1044

The problem, as I see it, is that click on RadioButton gives event.target.selected == false. I’m not sure why the test passed in the past. So maybe I can rephrase the question: 1. 2. In mustella, what happens between line (a) and line (b)? Is it a simple time out or is there some cl

Build failed in Jenkins: royale-asjs_MXTests #1046

See -- [...truncated 984.82 KB...] [mxmlc] scanning for overrides: ObjectUtil [mxmlc] scanning for overrides: SolidBorderUtil [mxmlc] scanning

Re: Minification problem with latest build

Okay, this should be working correctly now. -- Josh Tynjala Bowler Hat LLC On Mon, Aug 12, 2019 at 10:36 AM Josh Tynjala wrote: > I've determined that when js-dynamic-access-unknown-members is true, a > fully-qualified name is output differently: > > org["apache"]["roya

Release Step 001 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_001 and run the following commands: git push git checkout release/0.9.6 git push -u origin release/0.9.6 You will need your Apache/Github username and 2FA token.

Release Step 001a Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_001a_If_Utils and run the following commands: git push You will need your Apache/Github username and 2FA token.

Build failed in Jenkins: royale-typedefs #1536

See -- Started by timer [EnvInject] - Loading node environment variables. Building on master in workspace

Release Step 002 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_002 and run the following commands: git push git push origin org.apache.royale.compiler-0.9.6-rc1 You will need your Apache/Github username and 2FA token.

Release Step 003 Succeeded

>From the royale-compiler repo: 1. If you are releasing the utils jars (compiler-jburg-types and compiler-build-tools) - you have set in previous step for mentioned projects version ex. 1.1.0 not snapshot, Run: ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.6 Otherw

Release Step 004 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_004 and run the following commands: git push git checkout release/0.9.6 git push -u origin release/0.9.6 You will need your Apache/Github username and 2FA token.

Release Step 005 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_005 and run the following commands: git push You will need your Apache/Github username and 2FA token.

Release Step 005a Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_005a_If_Utils and run the following commands: git push You will need your Apache/Github username and 2FA token.

Release Step 006 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_006 and run the following commands: git push git push origin org.apache.royale.typedefs-0.9.6-rc1 You will need your Apache/Github username and 2FA token.

Release Step 007 Succeeded

>From the royale-typedefs repo: 1. Run ant -f releasesteps.xml Release_Step_007 -Drelease.version=0.9.6 This will download the artifacts then unzip and compile the source artifact. 2. Validate that the compiled artifacts match the downloaded artifacts. 3. If they do, then run ant -f releasesteps.xm

Release Step 008 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_008 and run the following commands: git push git checkout release/0.9.6 git push -u origin release/0.9.6 You will need your Apache/Github username and 2FA token.

Release Step 009 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_009 and run the following commands: git push You will need your Apache/Github username and 2FA token.

Release Step 010 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_010 and run the following commands: git push git push origin org.apache.royale.framework-0.9.6-rc1 You will need your Apache/Github username and 2FA token.

Release Step 011 Succeeded

>From the royale-asjs repo: 1. Run ant -f releasesteps.xml Release_Step_011 -Drelease.version=0.9.6 This will download the artifacts then unzip and compile the source artifact. 2. Validate that the compiled artifacts match the downloaded artifacts. 3. If they do, then run ant -f releasesteps.xml Re