Build failed in Jenkins: royale-asjs_MXTests #770

See -- [...truncated 2.04 MB...] [mxmlc] using source file:

Build failed in Jenkins: royale-asjs_MXTests #769

See -- [...truncated 2.04 MB...] [mxmlc] using source file:

Release Step 007 Succeeded

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.xml Release_Step_007_Sign -Drelea

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 005a Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_005a and run the following commands: git push 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 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 003 Succeeded

1. If you are releasing the utils jars (compiler-jburg-types and compiler-build-tools), Run: ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.6 Otherwise, Run: ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.6 This will download the artifacts then unzip

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 002a Succeeded

Continue on to Release Step 003

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.

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.

Royale_Release_Step_001 - Build # 61 - Failure!

Royale_Release_Step_001 - Build # 61 - Failure: Check console output at http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_001/61/ to view the results.

[GitHub] [royale-docs] piotrzarzycki21 merged pull request #19: Make the logo clickable

piotrzarzycki21 merged pull request #19: Make the logo clickable URL: https://github.com/apache/royale-docs/pull/19 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

[GitHub] [royale-docs] piotrzarzycki21 merged pull request #20: Further improve build instructions

piotrzarzycki21 merged pull request #20: Further improve build instructions URL: https://github.com/apache/royale-docs/pull/20 This is an automated message from the Apache Git Service. To respond to the message, please log on

Re: Problems with Java 12

That's fine, although I think the more common pattern is to require use of env.properties and/or local.properties files. It occurs to me that regarding Flash Builder, the source compatibility is less important than the target compatibility. Does Java 12 have Java 1.6 target compatibility? -Al

[GitHub] [royale-docs] Aszusz opened a new pull request #20: Further improve build instructions

Aszusz opened a new pull request #20: Further improve build instructions URL: https://github.com/apache/royale-docs/pull/20 Let me correct the instructions I provided last time. This method uses a built-in Jekyll server and doesn't require manipulating the baseurl parameter. --

[GitHub] [royale-docs] Aszusz opened a new pull request #19: Make the logo clickable

Aszusz opened a new pull request #19: Make the logo clickable URL: https://github.com/apache/royale-docs/pull/19 This feature makes the Royale logo in docs clickable. It points to Royale main page. This is an automated messag

Build failed in Jenkins: royale-asjs_MXTests #768

See -- [...truncated 2.04 MB...] [mxmlc] using source file:

Build failed in Jenkins: royale-asjs_MXTests #767

See Changes: [yishayjobs] All color models should have Number, so NaN is an option. [yishayjobs] Thumb can disappear when selected color is empty. -

Re: Royale Docs Changes Proposal

My pull request #17: Move Getting Started to Docs URL: https://github.com/apache/royale-docs/pull/17 has just been merged. Now I would like to ask someone with WordPress access to change the link on header's "GET STARTED" button and footer's "Getting Started" from: https://royale.apache.org/gett

[GitHub] [royale-docs] piotrzarzycki21 merged pull request #17: Move Getting Started to Docs

piotrzarzycki21 merged pull request #17: Move Getting Started to Docs URL: https://github.com/apache/royale-docs/pull/17 This is an automated message from the Apache Git Service. To respond to the message, please log on to Gi

Re: Problems with Java 12

Yeah. Looks like the problem. Thanks. Maybe we should keep 1.6 the default, but allow a environment variable to set it higher? > On May 15, 2019, at 9:58 AM, Alex Harui wrote: > > Looks like royale-asjs/build.xml specifies 1.5. That's probably an > accidental copy from Flex. > > That said,

Re: Royale Docs Changes Proposal

Hi Guys, One small thing apart of above changes which are in progress. "Get Started" in the main menu on the website and "Getting Started" in the footer are pointing us to the same page. Words are different - What do you think to align them and have in footer "Get Started" as well? Thanks, Piotr