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

[GitHub] [royale-docs] piotrzarzycki21 commented on issue #16: Improve Build Instructions

piotrzarzycki21 commented on issue #16: Improve Build Instructions URL: https://github.com/apache/royale-docs/pull/16#issuecomment-492126369 @Aszusz let's continue improvements towards master - if anyone would like to change something - we can start discussion on dev.

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

See

Jenkins build is back to normal : TourDeFlexMigration #782

See

Build failed in Jenkins: royale-asjs_MXTests #763

See Changes: [yishayjobs] Allow for empty selection. -- [...truncated 2.04 MB...] [mxmlc] using source file:

Problems with Java 12

I’m setting up a new Windows machine and I installed Java 12. I can’t get Royale to compile. I keep getting this error: annotate.class: [javac] Compiling 1 source file to C:\Apache\royale-compiler\compiler-build-tools\target\classes [javac] warning: [options] bootstrap class path not set i

Jenkins build is back to normal : royale-compiler #848

See

[GitHub] [royale-docs] Aszusz opened a new pull request #17: Move Getting Started to Docs

Aszusz opened a new pull request #17: Move Getting Started to Docs URL: https://github.com/apache/royale-docs/pull/17 This feature takes one page of online documentation hosted outside docs: Getting Started (https://royale.apache.org/getting-started/) and merges it with docs: Get s

Build failed in Jenkins: royale-asjs_MXTests #764

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

[GitHub] [royale-docs] Aszusz opened a new pull request #18: Fix instruction of how to set up baseurl in local_config

Aszusz opened a new pull request #18: Fix instruction of how to set up baseurl in local_config URL: https://github.com/apache/royale-docs/pull/18 Let me correct my instructions on how to properly set up baseurl parameter for working locally with docs --

Re: Problems with Java 12

I can't figure out why your build is trying to use 1.5. My build.xml for compiler-build-tools is using 1.6. -Alex On 5/14/19, 3:46 AM, "Harbs" wrote: I’m setting up a new Windows machine and I installed Java 12. I can’t get Royale to compile. I keep getting this error: annotate

Re: Problems with Java 12

Most of the build files were set to 1.6. There was one set to 1.5 (I don’t remember off-hand which one. Changing all of them did not help. I have no idea where this is being picked up from. Is it possible Maven artifacts are coming into play? > On May 14, 2019, at 6:29 PM, Alex Harui wrote: >

Re: Problems with Java 12

I just switched to compiler-build-tools, ran "ant clean" then "ant". The console said "warning: [options] bootstrap class path not set in conjunction with -source 1.6" What do you get? Maybe the main build.xml sets something but I didn't see it. Swfutils sets 1.5. That can probably be chan

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 and run the following commands: git push You will need your Apache/Github username and 2FA token.

Royale_Release_Step_006 - Build # 15 - Failure!

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

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 and run the following commands: git push You will need your Apache/Github username and 2FA token.

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.

[GitHub] [royale-docs] Aszusz closed pull request #18: Fix instruction of how to set up baseurl in local_config

Aszusz closed pull request #18: Fix instruction of how to set up baseurl in local_config URL: https://github.com/apache/royale-docs/pull/18 This is an automated message from the Apache Git Service. To respond to the message,

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.

Release Step 002a Succeeded

Continue on to Release Step 003

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

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 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 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

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

[GitHub] [royale-docs] carlosrovira commented on issue #16: Improve Build Instructions

carlosrovira commented on issue #16: Improve Build Instructions URL: https://github.com/apache/royale-docs/pull/16#issuecomment-492393739 Hi Guys, getting to this now, was very busy this days with other things, seem I don't have to do nothing for now. Let me know in case I'm wrong. Thanks!

Build failed in Jenkins: royale-asjs_MXTests #765

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

Build failed in Jenkins: royale-asjs_MXTests #766

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

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 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

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

Re: Problems with Java 12

Progress. I was building using `ant all` on asjs. When I build using `ant` on royale-compiler, I got a bunch of errors: [javac] warning: [options] bootstrap class path not set in conjunction with -source 6 [javac] error: Source option 6 is no longer supported. Use 7 or later. [javac] er

Re: Problems with Java 12

Looks like royale-asjs/build.xml specifies 1.5. That's probably an accidental copy from Flex. That said, I'm not sure that flex-compiler-oem will work with Flash Builder if the target is not 1.6. If that's true, we'll need some way to not build that jar on Java 12. -Alex On 5/14/19, 11:49