Release Step 006 Succeeded

[Apache Royale CI Server]

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

[Apache Royale CI Server]

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

[Apache Royale CI Server]

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

[Apache Royale CI Server]

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.

Build failed in Jenkins: royale-asjs_MXTests #766

[Apache Royale CI Server]

See 


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

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

Build failed in Jenkins: royale-asjs_MXTests #765

[Apache Royale CI Server]

See 


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

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

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

[GitBox]

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!


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Release Step 007 Succeeded

[Apache Royale CI Server]

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 
-Drelease.version=0.9.6
This will PGP sign the source ZIP and compiled JARs
4. Then run ant -f releasesteps.xml Release_Step_007_Upload 
-Drelease.version=0.9.6
This will upload the signed artifacts to Maven Release Staging.  Do not "Close" 
the staging repository until the other repos have been added.

Release Step 006 Succeeded

[Apache Royale CI Server]

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

[Apache Royale CI Server]

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

[Apache Royale CI Server]

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

[Apache Royale CI Server]

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

[Apache Royale CI Server]

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 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_003_Sign 
-Drelease.version=0.9.6
This will PGP sign the source ZIP and compiled JARs
4. Then run ant -f releasesteps.xml Release_Step_003_Upload 
-Drelease.version=0.9.6
This will upload the signed artifacts to Maven Release Staging.  Do not "Close" 
the staging repository until the other repos have been added.

Release Step 002 Succeeded

[Apache Royale CI Server]

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

[Apache Royale CI Server]

Continue on to Release Step 003

Release Step 001a Succeeded

[Apache Royale CI Server]

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

[Apache Royale CI Server]

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.

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

[GitBox]

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, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Release Step 006 Succeeded

[Apache Royale CI Server]

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

[Apache Royale CI Server]

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 
-Drelease.version=0.9.6
This will PGP sign the source ZIP and compiled JARs
4. Then run ant -f releasesteps.xml Release_Step_007_Upload 
-Drelease.version=0.9.6
This will upload the signed artifacts to Maven Release Staging.  Do not "Close" 
the staging repository until the other repos have been added.

Release Step 005a Succeeded

[Apache Royale CI Server]

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

[Apache Royale CI Server]

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

[Apache Royale CI Server]

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.

Royale_Release_Step_006 - Build # 15 - Failure!

[Apache Royale CI Server]

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

[Apache Royale CI Server]

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

[Apache Royale CI Server]

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

[Apache Royale CI Server]

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.

Re: Problems with Java 12

[Alex Harui]

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 changed, but I thought swfutils ran 
after compiler-build-tools.  Maybe you have an environment variable or 
local.properties or env.properties.

-Alex

On 5/14/19, 8:44 AM, "Harbs"  wrote:

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:
> 
> 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.class:
>   [javac] Compiling 1 source file to 
C:\Apache\royale-compiler\compiler-build-tools\target\classes
>   [javac] warning: [options] bootstrap class path not set in 
conjunction with -source 5
>   [javac] error: Source option 5 is no longer supported. Use 7 or 
later.
>   [javac] error: Target option 5 is no longer supported. Use 7 or 
later.
> 
>I tried changing javac.src=1.7 instead of 1.5 in the build.xml files, 
but it had no effect.
> 
>Any suggestions (other than trying to figure out how to download an 
older version of Java)?
> 
>Harbs
> 

Re: Problems with Java 12

[Harbs]

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:
> 
> 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.class:
>   [javac] Compiling 1 source file to 
> C:\Apache\royale-compiler\compiler-build-tools\target\classes
>   [javac] warning: [options] bootstrap class path not set in conjunction 
> with -source 5
>   [javac] error: Source option 5 is no longer supported. Use 7 or later.
>   [javac] error: Target option 5 is no longer supported. Use 7 or later.
> 
>I tried changing javac.src=1.7 instead of 1.5 in the build.xml files, but 
> it had no effect.
> 
>Any suggestions (other than trying to figure out how to download an older 
> version of Java)?
> 
>Harbs
> 

Re: Problems with Java 12

[Alex Harui]

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.class:
   [javac] Compiling 1 source file to 
C:\Apache\royale-compiler\compiler-build-tools\target\classes
   [javac] warning: [options] bootstrap class path not set in conjunction 
with -source 5
   [javac] error: Source option 5 is no longer supported. Use 7 or later.
   [javac] error: Target option 5 is no longer supported. Use 7 or later.

I tried changing javac.src=1.7 instead of 1.5 in the build.xml files, but 
it had no effect.

Any suggestions (other than trying to figure out how to download an older 
version of Java)?

Harbs

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

[GitBox]

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


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Build failed in Jenkins: royale-asjs_MXTests #764

[Apache Royale CI Server]

See 


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

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

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

[GitBox]

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 started with Royale 
(https://apache.github.io/royale-docs/Get%20Started.html)
   
   - The main goal of this feature is to remove duplication. It's confusing to 
have two pages named 'Getting Started". Where do you start?
   - If anyone wants to restructure this page afterward or divide it into parts 
they are very welcome to do so.
   - If this pull request gets accepted it is necessary to make the GET STARTED 
link on webpage point to the new merged location


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

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

[Apache Royale CI Server]

See 

Problems with Java 12

[Harbs]

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 in conjunction with 
-source 5
   [javac] error: Source option 5 is no longer supported. Use 7 or later.
   [javac] error: Target option 5 is no longer supported. Use 7 or later.

I tried changing javac.src=1.7 instead of 1.5 in the build.xml files, but it 
had no effect.

Any suggestions (other than trying to figure out how to download an older 
version of Java)?

Harbs

Build failed in Jenkins: royale-asjs_MXTests #763

[Apache Royale CI Server]

See 


Changes:

[yishayjobs] Allow for empty selection.

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

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

Jenkins build is back to normal : TourDeFlexMigration #782

[Apache Royale CI Server]

See 

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

[Apache Royale CI Server]

See 

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

[GitBox]

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. 


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Release Step 003 Succeeded

[Apache Royale CI Server]

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 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_003_Sign 
-Drelease.version=0.9.6
This will PGP sign the source ZIP and compiled JARs
4. Then run ant -f releasesteps.xml Release_Step_003_Upload 
-Drelease.version=0.9.6
This will upload the signed artifacts to Maven Release Staging.  Do not "Close" 
the staging repository until the other repos have been added.

Royale_Release_Step_003 - Build # 25 - Still Failing!

[Apache Royale CI Server]

Royale_Release_Step_003 - Build # 25 - Still Failing:

Check console output at 
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_003/25/
 to view the results.

Royale_Release_Step_003 - Build # 24 - Failure!

[Apache Royale CI Server]

Royale_Release_Step_003 - Build # 24 - Failure:

Check console output at 
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_003/24/
 to view the results.

Release Step 002 Succeeded

[Apache Royale CI Server]

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

[Apache Royale CI Server]

Continue on to Release Step 003

Release Step 001a Succeeded

[Apache Royale CI Server]

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.