Trying abstract classes in Jewel

2019-08-23 Thread Carlos Rovira
Hi Josh, after cleaning Jewel TextInput classes, I tried to change TextInputBase from public to abstract class. The reason is that while Simple** classes (like Jewel SimpleButton or SimpleRemoteObject), are a reduced case of a class named without "Simple" (in the example "Button", and most users

Release Step 001 Succeeded

2019-08-23 Thread 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.

Release Step 001a Succeeded

2019-08-23 Thread 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 002 Succeeded

2019-08-23 Thread 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.

Royale_Release_Step_002a_If_Utils - Build # 28 - Failure!

2019-08-23 Thread Apache Royale CI Server
Royale_Release_Step_002a_If_Utils - Build # 28 - Failure: Check console output at http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_002a_If_Utils/28/ to view the results.

Release Step 002a Succeeded

2019-08-23 Thread Apache Royale CI Server
Continue on to Release Step 003

Royale_Release_Step_003 - Build # 40 - Failure!

2019-08-23 Thread Apache Royale CI Server
Royale_Release_Step_003 - Build # 40 - Failure: Check console output at http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_003/40/ to view the results.

Release Step 003 Succeeded

2019-08-23 Thread Apache Royale CI Server
>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

2019-08-23 Thread 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 005 Succeeded

2019-08-23 Thread 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 005a Succeeded

2019-08-23 Thread Apache Royale CI Server
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

2019-08-23 Thread 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

2019-08-23 Thread Apache Royale CI Server
>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

Re: Sub-Menu in royale-docs: "Fundamental Concepts", "Core Concepts" or "Technology features"

2019-08-23 Thread Chris Velevitch
As a Flex developer exploring Royale, I've come across the terms "beads", "strands" and "pay as you go" (PAYG), but I can't find any details, documentation or tutorials on them. How do these map into existing Flex concepts? As for PAYG, as far as I can tell, this is just another name for the concep

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

2019-08-23 Thread Apache Royale CI Server
See

Build failed in Jenkins: Royale_ASDoc_Example #2371

2019-08-23 Thread Apache Royale CI Server
See -- [...truncated 26.09 KB...] [mxmlc] scanning for overrides: IListView [mxmlc] scanning for overrides: DataContainerView [mxmlc] scanning