Re: [VOTE] Release Apache Royale 0.9.9 RC4

[Josh Tynjala]

+1
Package
https://dist.apache.org/repos/dist/dev/royale/0.9.9/rc4/apache-royale-0.9.9-src.tar.gz
Java 17
OS: Mac OS X aarch64 12.1
Source kit signatures match: y
Source kit builds: y
README is ok: y
RELEASE_NOTES is ok: y
NOTICE is ok: y
LICENSE is ok: y
No unapproved licenses or archives: y
No unapproved binaries: y

Package
https://dist.apache.org/repos/dist/dev/royale/0.9.9/rc4/binaries/apache-royale-0.9.9-bin-js-swf.tar.gz
Binary kit signatures match: y
NOTICE is ok: y
LICENSE is ok: y
No unapproved licenses or archives in binary package: y
No unapproved binaries in binary package: y

--
Josh Tynjala
Bowler Hat LLC 


On Thu, Mar 17, 2022 at 10:42 AM  wrote:

> Hi,
> This is the vote for the 0.9.9 release of Apache Royale.  The release
> candidate can be found here;
> https://dist.apache.org/repos/dist/dev/royale/0.9.9/rc4/
>
> Before voting please review the section,'What are the ASF requirements on
> approving a release?', at:
> http://www.apache.org/dev/release.html#approving-a-release
>
> At a minimum you would be expected to check that:
> - SHA and signed packages are correct
> - README, RELEASE_NOTES, NOTICE and LICENSE files are all fine
> - That the build script completes successfully
> - That you can compile and crosscompile a simple example using the SDK.
>
> The KEYS file is at https://dist.apache.org/repos/dist/release/royale/KEYS
>
> The source package is a combination of the 3 main Royale repos.
>
> To use the binary package, unzip it into a folder. The -js package is
> ready-to-use in an IDE or command-line. If you need SWF output, use the
> -js-swf package and use Apache Ant to run the InstallAdobeSDKs script via:
> ant -f InstallAdobeSDKs.xml
>
> You may also get the binarypackages via NPM. The -js package can be
> installed via:
> npm install
> https://dist.apache.org/repos/dist/dev/royale/0.9.9/rc4/binaries/apache-royale-0.9.9-bin-js.tar.gz
>
> The full package with SWF support can be installed via:
>
> npm install
> https://dist.apache.org/repos/dist/dev/royale/0.9.9/rc4/binaries/apache-royale-0.9.9-bin-js-swf.tar.gz
>
> Maven artifacts are staged here:
> https://repository.apache.org/content/repositories/orgapacheroyale-1091
>
> Please vote to approve this release:
> +1 Approve the release
> -1 Disapprove the release (please provide specific comments to why)
>
> This vote will be open for 72 hours or until a result can be called.
>
> The vote passes if there is:
> - At least 3 +1 votes from the PMC
> - More positive votes than negative votes
>
> Remember that this is a 'beta-quality' release so expect there will be
> many bugs found. IMO the goal is not to try to find and fix bugs in the RC,
> but to make sure we have the packaging right, and enough functionality that
> folks will have some success trying to use it.  People who are not in PMC
> are also encouraged to test out the release and vote, although their votes
> will not be binding, they can influence how the PMC votes.
>
> When voting please indicate what OS, IDE, Flash Player version and AIR
> version you tested with.
>
> For your convenience, there is an ant script that automates the common
> steps to validate a release.  Instead of individually downloading the
> package and signature files, unzipping, etc, you can instead:
> 1) create an empty folder,
> 2) download into that folder this file:
> https://dist.apache.org/repos/dist/dev/royale/0.9.9/rc4/ApproveRoyale.xml
> 3) run the script:
>ant -e -f ApproveRoyale.xml -Drelease.version=0.9.9 -Drc=4
>If you want to test SWF support during the approval, use:
>ant -e -f ApproveRoyale.xml -Drelease.version=0.9.9 -Drc=4
> -Duse-flash=true
>
> You are not required to use this script, and more testing of the packages
> and build results are always encouraged.
>
> Please put all discussion about this release in the DISCUSSION thread not
> this VOTE thread.
>
> Thanks,
> Yishay Weiss

Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC4

[Josh Tynjala]

Hmmm... In RC4, I have now reproduced the ASDoc build issue that I
mentioned previously, both with -Duse-flash=true and without it. Even
without AIR_HOME being specified in the case of the JS-only build. However,
it doesn't seem to reproduce every time. I guess that I just got unlucky
when I was testing RC3, where it seemed to consistently affect the JS-only
SDK. This time around, it seems to affect the JS+SWF SDK just as frequently
on the same machine.

Anyway, I agree with Alex that this issue doesn't need to block the
release. I'm going to comment out the ASDoc example from the build, and if
the approval script gets through everything else, I'm happy. I plan to vote
+1, assuming that my remaining manual tests in VSCode and elsewhere all
look good too.

--
Josh Tynjala
Bowler Hat LLC 


On Thu, Mar 17, 2022 at 10:43 AM  wrote:

> This is the discussion thread.
>
> Thanks,
> Yishay Weiss

RE: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC3

[Yishay Weiss]

I agree in retrospect that an example that compiles in Maven, but not in Ant, 
and is not critical for users, should not hold a release. It was good to spot 
the regression, but ideally that should be spotted on CI.

From: Alex Harui
Sent: Thursday, March 17, 2022 6:18 PM
To: dev@royale.apache.org; Josh 
Tynjala
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC3

IMO, the release does not have to be bug free.  If the Maven and Ant build 
scripts can build the source package, there are no unintended compiled code in 
the source package, LICENSE and NOTICE are correct, and a few other Apache 
policy requirements are met, and folks can use the results of the built source 
package to be successful in their work, I would still vote for release.

-Alex

On 3/17/22, 6:30 AM, "Yishay Weiss"  wrote:

> The ant examples are only built after release approval.

Actually, I think I misread the scripts. I don’t think examples are built 
with ant anywhere in the release process except upon approval. If somebody 
wants to inform otherwise please do.

From: Yishay Weiss
Sent: Thursday, March 17, 2022 9:12 AM
To: Josh Tynjala; 
dev@royale.apache.org
Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC3

The examples are run as part of the step 11, but mvn only. The ant examples 
are only built after release approval. For some reason MenuExample was working 
in mvn but not in ant. That’s why the release steps did not fail prior to 
approval script. For anybody curious to find out why these differences between 
mvn and ant exist, this is the maven output [2] taken from the CI logs [1]. You 
can compare it to Josh’s ant output upthread.

Unrelated, I scheduled a daily job for ASDocs example so we can track 
ASDocs errors, as they seem to be pretty common.

I will see if I can figure out if I can continue the release from the 
existing release branch after cherry-picking Josh’s pick.

Thanks.

[1] Royale_Release_Step_011 #26 Console [Jenkins] 
(azure.com)


[2] [INFO] [INFO] ---< org.apache.royale.examples:MenuExample 
>---

[INFO] [INFO] Building Apache Royale: Examples: Royale: MenuExample 0.9.9   
 [195/265]

[INFO] [INFO] [ swf 
]-

[INFO] [INFO]

[INFO] [INFO] --- maven-enforcer-plugin:1.4.1:enforce 
(enforce-maven-version) @ MenuExample ---

[INFO] [INFO]

[INFO] [INFO] --- maven-resources-plugin:3.1.0:copy-resources 
(copy-resources-debug) @ MenuExample ---

[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.

[INFO] [INFO] skip non existing resourceDirectory 
C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\src\main\resources

[INFO] [INFO]

[INFO] [INFO] --- maven-resources-plugin:3.1.0:copy-resources 
(copy-resources-release) @ MenuExample ---

[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.

[INFO] [INFO] skip non existing resourceDirectory 
C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\src\main\resources\assets

[INFO] [INFO]

[INFO] [INFO] --- maven-remote-resources-plugin:1.7.0:process 
(process-resource-bundles) @ MenuExample ---

[INFO] [INFO] Preparing remote bundle 
org.apache:apache-jar-resource-bundle:1.4

[INFO] [INFO] Copying 3 resources from 1 bundle.

[INFO] [INFO]

[INFO] [INFO] --- maven-resources-plugin:3.1.0:resources 
(default-resources) @ MenuExample ---

[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.

[INFO] [INFO] skip non existing resourceDirectory 
C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\src\main\resources

[INFO] [INFO] Copying 3 resources

[INFO] [INFO]

[INFO] [INFO] --- royale-maven-plugin:0.9.9:compile-app 
(default-compile-app) @ MenuExample ---

[INFO] [INFO] Executing MXMLC in tool group Royale with args: 
[-load-config=C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\target\compile-app-config.xml,
 -metadata.date=2022-03-13T09:39:40Z, 
-metadata.dateFormat=-MM-dd'T'HH:mm:ss'Z', 

[DISCUSS] Discuss Release Apache Royale 0.9.9 RC4

[apacheroyaleci]

This is the discussion thread.

Thanks,
Yishay Weiss

[VOTE] Release Apache Royale 0.9.9 RC4

[apacheroyaleci]

Hi,
This is the vote for the 0.9.9 release of Apache Royale.  The release candidate 
can be found here;
https://dist.apache.org/repos/dist/dev/royale/0.9.9/rc4/

Before voting please review the section,'What are the ASF requirements on 
approving a release?', at: 
http://www.apache.org/dev/release.html#approving-a-release

At a minimum you would be expected to check that:
- SHA and signed packages are correct
- README, RELEASE_NOTES, NOTICE and LICENSE files are all fine
- That the build script completes successfully
- That you can compile and crosscompile a simple example using the SDK.

The KEYS file is at https://dist.apache.org/repos/dist/release/royale/KEYS

The source package is a combination of the 3 main Royale repos.

To use the binary package, unzip it into a folder. The -js package is 
ready-to-use in an IDE or command-line. If you need SWF output, use the
-js-swf package and use Apache Ant to run the InstallAdobeSDKs script via:
ant -f InstallAdobeSDKs.xml

You may also get the binarypackages via NPM. The -js package can be installed 
via:
npm install 
https://dist.apache.org/repos/dist/dev/royale/0.9.9/rc4/binaries/apache-royale-0.9.9-bin-js.tar.gz

The full package with SWF support can be installed via:

npm install 
https://dist.apache.org/repos/dist/dev/royale/0.9.9/rc4/binaries/apache-royale-0.9.9-bin-js-swf.tar.gz

Maven artifacts are staged here: 
https://repository.apache.org/content/repositories/orgapacheroyale-1091

Please vote to approve this release:
+1 Approve the release
-1 Disapprove the release (please provide specific comments to why)

This vote will be open for 72 hours or until a result can be called.

The vote passes if there is:
- At least 3 +1 votes from the PMC
- More positive votes than negative votes

Remember that this is a 'beta-quality' release so expect there will be many 
bugs found. IMO the goal is not to try to find and fix bugs in the RC, but to 
make sure we have the packaging right, and enough functionality that folks will 
have some success trying to use it.  People who are not in PMC are also 
encouraged to test out the release and vote, although their votes will not be 
binding, they can influence how the PMC votes.

When voting please indicate what OS, IDE, Flash Player version and AIR version 
you tested with.  

For your convenience, there is an ant script that automates the common steps to 
validate a release.  Instead of individually downloading the package and 
signature files, unzipping, etc, you can instead:
1) create an empty folder,
2) download into that folder this file:
https://dist.apache.org/repos/dist/dev/royale/0.9.9/rc4/ApproveRoyale.xml
3) run the script:
   ant -e -f ApproveRoyale.xml -Drelease.version=0.9.9 -Drc=4
   If you want to test SWF support during the approval, use:
   ant -e -f ApproveRoyale.xml -Drelease.version=0.9.9 -Drc=4 -Duse-flash=true

You are not required to use this script, and more testing of the packages and 
build results are always encouraged.

Please put all discussion about this release in the DISCUSSION thread not this 
VOTE thread.

Thanks,
Yishay Weiss

Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC3

[Alex Harui]

IMO, the release does not have to be bug free.  If the Maven and Ant build 
scripts can build the source package, there are no unintended compiled code in 
the source package, LICENSE and NOTICE are correct, and a few other Apache 
policy requirements are met, and folks can use the results of the built source 
package to be successful in their work, I would still vote for release.

-Alex

On 3/17/22, 6:30 AM, "Yishay Weiss"  wrote:

> The ant examples are only built after release approval.

Actually, I think I misread the scripts. I don’t think examples are built 
with ant anywhere in the release process except upon approval. If somebody 
wants to inform otherwise please do.

From: Yishay Weiss
Sent: Thursday, March 17, 2022 9:12 AM
To: Josh Tynjala; 
dev@royale.apache.org
Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC3

The examples are run as part of the step 11, but mvn only. The ant examples 
are only built after release approval. For some reason MenuExample was working 
in mvn but not in ant. That’s why the release steps did not fail prior to 
approval script. For anybody curious to find out why these differences between 
mvn and ant exist, this is the maven output [2] taken from the CI logs [1]. You 
can compare it to Josh’s ant output upthread.

Unrelated, I scheduled a daily job for ASDocs example so we can track 
ASDocs errors, as they seem to be pretty common.

I will see if I can figure out if I can continue the release from the 
existing release branch after cherry-picking Josh’s pick.

Thanks.

[1] Royale_Release_Step_011 #26 Console [Jenkins] 
(azure.com)


[2] [INFO] [INFO] ---< org.apache.royale.examples:MenuExample 
>---

[INFO] [INFO] Building Apache Royale: Examples: Royale: MenuExample 0.9.9   
 [195/265]

[INFO] [INFO] [ swf 
]-

[INFO] [INFO]

[INFO] [INFO] --- maven-enforcer-plugin:1.4.1:enforce 
(enforce-maven-version) @ MenuExample ---

[INFO] [INFO]

[INFO] [INFO] --- maven-resources-plugin:3.1.0:copy-resources 
(copy-resources-debug) @ MenuExample ---

[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.

[INFO] [INFO] skip non existing resourceDirectory 
C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\src\main\resources

[INFO] [INFO]

[INFO] [INFO] --- maven-resources-plugin:3.1.0:copy-resources 
(copy-resources-release) @ MenuExample ---

[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.

[INFO] [INFO] skip non existing resourceDirectory 
C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\src\main\resources\assets

[INFO] [INFO]

[INFO] [INFO] --- maven-remote-resources-plugin:1.7.0:process 
(process-resource-bundles) @ MenuExample ---

[INFO] [INFO] Preparing remote bundle 
org.apache:apache-jar-resource-bundle:1.4

[INFO] [INFO] Copying 3 resources from 1 bundle.

[INFO] [INFO]

[INFO] [INFO] --- maven-resources-plugin:3.1.0:resources 
(default-resources) @ MenuExample ---

[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.

[INFO] [INFO] skip non existing resourceDirectory 
C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\src\main\resources

[INFO] [INFO] Copying 3 resources

[INFO] [INFO]

[INFO] [INFO] --- royale-maven-plugin:0.9.9:compile-app 
(default-compile-app) @ MenuExample ---

[INFO] [INFO] Executing MXMLC in tool group Royale with args: 
[-load-config=C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\target\compile-app-config.xml,
 -metadata.date=2022-03-13T09:39:40Z, 
-metadata.dateFormat=-MM-dd'T'HH:mm:ss'Z', 
-js-output=C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\target\javascript,
 -compiler.targets=SWF,JSRoyale, 
C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\src\main\royale\MenuExample.mxml]

[INFO] Loading configuration: 
C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\target\compile-app-config.xml

[INFO]

[INFO] 57676 bytes written to 

RE: Implementing JS renderer from Royale

[Maria Jose Esteve]

Hi Yishay, yes of course,
Right now I have two cases:
- DatePicker, from Mobiscroll
- InspireTree JS

In the DatePicker I have to customize the calendar header (our DateChooser) to 
put a series of options (Labels, buttons,..).
This component allows me to customize the content of this header "DIV", as a 
HTML/DOM string. (" 
Enviado el: jueves, 17 de marzo de 2022 13:54
Para: dev@royale.apache.org
Asunto: RE: Implementing JS renderer from Royale

Do you have a concrete example?

From: Maria Jose Esteve
Sent: Thursday, March 17, 2022 1:27 PM
To: dev@royale.apache.org
Subject: Implementing JS renderer from Royale

Hi, I'm asking for guidance...
Lately I'm actively using several JS libraries in Royale and I find myself with 
a recurring need: custom renderers.
Depending on how the library is made there is the possibility to define the 
view of the component or some part of it.
I would like to be able to define "the renderer" in Royale, get its DOM and 
pass it to the library/component?

Am I crazy or is this feasible to do with Royale?
If it is possible, any example that I can see to guide me?

Thx.

Hiedra

RE: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC3

[Yishay Weiss]

> The ant examples are only built after release approval.

Actually, I think I misread the scripts. I don’t think examples are built with 
ant anywhere in the release process except upon approval. If somebody wants to 
inform otherwise please do.

From: Yishay Weiss
Sent: Thursday, March 17, 2022 9:12 AM
To: Josh Tynjala; 
dev@royale.apache.org
Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC3

The examples are run as part of the step 11, but mvn only. The ant examples are 
only built after release approval. For some reason MenuExample was working in 
mvn but not in ant. That’s why the release steps did not fail prior to approval 
script. For anybody curious to find out why these differences between mvn and 
ant exist, this is the maven output [2] taken from the CI logs [1]. You can 
compare it to Josh’s ant output upthread.

Unrelated, I scheduled a daily job for ASDocs example so we can track ASDocs 
errors, as they seem to be pretty common.

I will see if I can figure out if I can continue the release from the existing 
release branch after cherry-picking Josh’s pick.

Thanks.

[1] Royale_Release_Step_011 #26 Console [Jenkins] 
(azure.com)


[2] [INFO] [INFO] ---< org.apache.royale.examples:MenuExample 
>---

[INFO] [INFO] Building Apache Royale: Examples: Royale: MenuExample 0.9.9
[195/265]

[INFO] [INFO] [ swf 
]-

[INFO] [INFO]

[INFO] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ 
MenuExample ---

[INFO] [INFO]

[INFO] [INFO] --- maven-resources-plugin:3.1.0:copy-resources 
(copy-resources-debug) @ MenuExample ---

[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.

[INFO] [INFO] skip non existing resourceDirectory 
C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\src\main\resources

[INFO] [INFO]

[INFO] [INFO] --- maven-resources-plugin:3.1.0:copy-resources 
(copy-resources-release) @ MenuExample ---

[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.

[INFO] [INFO] skip non existing resourceDirectory 
C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\src\main\resources\assets

[INFO] [INFO]

[INFO] [INFO] --- maven-remote-resources-plugin:1.7.0:process 
(process-resource-bundles) @ MenuExample ---

[INFO] [INFO] Preparing remote bundle org.apache:apache-jar-resource-bundle:1.4

[INFO] [INFO] Copying 3 resources from 1 bundle.

[INFO] [INFO]

[INFO] [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ 
MenuExample ---

[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.

[INFO] [INFO] skip non existing resourceDirectory 
C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\src\main\resources

[INFO] [INFO] Copying 3 resources

[INFO] [INFO]

[INFO] [INFO] --- royale-maven-plugin:0.9.9:compile-app (default-compile-app) @ 
MenuExample ---

[INFO] [INFO] Executing MXMLC in tool group Royale with args: 
[-load-config=C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\target\compile-app-config.xml,
 -metadata.date=2022-03-13T09:39:40Z, 
-metadata.dateFormat=-MM-dd'T'HH:mm:ss'Z', 
-js-output=C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\target\javascript,
 -compiler.targets=SWF,JSRoyale, 
C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\src\main\royale\MenuExample.mxml]

[INFO] Loading configuration: 
C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\target\compile-app-config.xml

[INFO]

[INFO] 57676 bytes written to 
C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\target\MenuExample-0.9.9.swf
 in 0.602 seconds

[INFO] Mar 13, 2022 12:00:56 PM com.google.javascript.jscomp.LoggerErrorManager 
printSummary

[INFO] INFO: 0 error(s), 0 warning(s), 97.8% typed

[INFO] The project 'MenuExample' has been successfully compiled and optimized.


From: Yishay Weiss
Sent: Wednesday, March 16, 2022 7:14 AM
To: Josh Tynjala; 
dev@royale.apache.org
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC3

Thanks, I will see if I can figure out why this didn't fail at an earlier 
stage. I will look into why asdoc example isn't run regularly on CI.

My CLT-L09. On O2.


 Original message 
From: Josh Tynjala 
Date: Tue, 15 Mar 2022, 23:07
To: dev@royale.apache.org
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC3
I ran into two separate issues with the approval script.

The 

Release Step 013 Succeeded

[apacheroyaleci]

Note: before running these steps make sure that PLAYERGLOBAL_HOME is set and 
that you have PlayerGlobal installed under 
/11.7/playerglobal.swc

>From the royale-asjs repo
1. Run ant -f releasesteps.xml Release_Step_013 -Drelease.version=0.9.9 
-Droyale.swc-date="2/10/22 9:06 -0800" -Dplayerglobal.version=11.7 
-Dflat.donot.ask=true -Drc=4 -DskipTests=true
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_013_Sign 
-Drelease.version=0.9.9
This will PGP sign the source and convenience binary packages
4. Then run ant -f releasesteps.xml Release_Step_013_Upload 
-Drelease.version=0.9.9 -Drc=4
This will upload the signed artifacts to dist.apache.org.

RE: Implementing JS renderer from Royale

[Yishay Weiss]

Do you have a concrete example?

From: Maria Jose Esteve
Sent: Thursday, March 17, 2022 1:27 PM
To: dev@royale.apache.org
Subject: Implementing JS renderer from Royale

Hi, I'm asking for guidance...
Lately I'm actively using several JS libraries in Royale and I find myself with 
a recurring need: custom renderers.
Depending on how the library is made there is the possibility to define the 
view of the component or some part of it.
I would like to be able to define "the renderer" in Royale, get its DOM and 
pass it to the library/component?

Am I crazy or is this feasible to do with Royale?
If it is possible, any example that I can see to guide me?

Thx.

Hiedra

Release Step 012 Succeeded

[apacheroyaleci]

Folder 0.9.9 already exists.
Continue to next step.

Implementing JS renderer from Royale

[Maria Jose Esteve]

Hi, I'm asking for guidance...
Lately I'm actively using several JS libraries in Royale and I find myself with 
a recurring need: custom renderers.
Depending on how the library is made there is the possibility to define the 
view of the component or some part of it.
I would like to be able to define "the renderer" in Royale, get its DOM and 
pass it to the library/component?

Am I crazy or is this feasible to do with Royale?
If it is possible, any example that I can see to guide me?

Thx.

Hiedra

Release Step 011 Succeeded

[apacheroyaleci]

Warning: this step requires a secret key, so it should not be performed on the 
CI server. It's probably best to perform it on your PC.

>From the royale-asjs repo:
1. Run ant -f releasesteps.xml Release_Step_011 -Drelease.version=0.9.9 
-DskipTests=true
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_011_Sign 
-Drelease.version=0.9.9
This will PGP sign the source ZIP and compiled JARs
4. Then run ant -f releasesteps.xml Release_Step_011_Upload 
-Drelease.version=0.9.9
This will upload the signed artifacts to Maven Release Staging.  Verify that 
the compiler and typedefs artifacts are there along with the asjs artifacts, 
then hit the close to close the staging repo. (https://repository.apache.org/)

Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC3

[Piotr Zarzycki]

Main Maven build on Jenkins is still failing, but I think it may not be
problem on our sight, but rather something happened with our project in
nightly -> https://nightlies.apache.org/Royale/Royale-asjs/ - it has been
removed for some reason. I think I will contact infrastructure and ask what
has happened.

czw., 17 mar 2022 o 08:22 Yishay Weiss  napisał(a):

> >Josh’s pick
>
> I meant Josh’s fix of course (being picky here).
> From: Yishay Weiss
> Sent: Thursday, March 17, 2022 9:12 AM
> To: Josh Tynjala; dev@royale.apache.org
> 
> Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC3
>
> The examples are run as part of the step 11, but mvn only. The ant
> examples are only built after release approval. For some reason MenuExample
> was working in mvn but not in ant. That’s why the release steps did not
> fail prior to approval script. For anybody curious to find out why these
> differences between mvn and ant exist, this is the maven output [2] taken
> from the CI logs [1]. You can compare it to Josh’s ant output upthread.
>
> Unrelated, I scheduled a daily job for ASDocs example so we can track
> ASDocs errors, as they seem to be pretty common.
>
> I will see if I can figure out if I can continue the release from the
> existing release branch after cherry-picking Josh’s pick.
>
> Thanks.
>
> [1] Royale_Release_Step_011 #26 Console [Jenkins] (azure.com)<
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/view/Royale_Release_Steps/job/Royale_Release_Step_011/26/consoleFull
> >
>
>
> [2] [INFO] [INFO] ---< org.apache.royale.examples:MenuExample
> >---
>
> [INFO] [INFO] Building Apache Royale: Examples: Royale: MenuExample 0.9.9
>   [195/265]
>
> [INFO] [INFO] [ swf
> ]-
>
> [INFO] [INFO]
>
> [INFO] [INFO] --- maven-enforcer-plugin:1.4.1:enforce
> (enforce-maven-version) @ MenuExample ---
>
> [INFO] [INFO]
>
> [INFO] [INFO] --- maven-resources-plugin:3.1.0:copy-resources
> (copy-resources-debug) @ MenuExample ---
>
> [INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
>
> [INFO] [INFO] skip non existing resourceDirectory
> C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\src\main\resources
>
> [INFO] [INFO]
>
> [INFO] [INFO] --- maven-resources-plugin:3.1.0:copy-resources
> (copy-resources-release) @ MenuExample ---
>
> [INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
>
> [INFO] [INFO] skip non existing resourceDirectory
> C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\src\main\resources\assets
>
> [INFO] [INFO]
>
> [INFO] [INFO] --- maven-remote-resources-plugin:1.7.0:process
> (process-resource-bundles) @ MenuExample ---
>
> [INFO] [INFO] Preparing remote bundle
> org.apache:apache-jar-resource-bundle:1.4
>
> [INFO] [INFO] Copying 3 resources from 1 bundle.
>
> [INFO] [INFO]
>
> [INFO] [INFO] --- maven-resources-plugin:3.1.0:resources
> (default-resources) @ MenuExample ---
>
> [INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
>
> [INFO] [INFO] skip non existing resourceDirectory
> C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\src\main\resources
>
> [INFO] [INFO] Copying 3 resources
>
> [INFO] [INFO]
>
> [INFO] [INFO] --- royale-maven-plugin:0.9.9:compile-app
> (default-compile-app) @ MenuExample ---
>
> [INFO] [INFO] Executing MXMLC in tool group Royale with args:
> [-load-config=C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\target\compile-app-config.xml,
> -metadata.date=2022-03-13T09:39:40Z,
> -metadata.dateFormat=-MM-dd'T'HH:mm:ss'Z',
> -js-output=C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\target\javascript,
> -compiler.targets=SWF,JSRoyale,
> C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\src\main\royale\MenuExample.mxml]
>
> [INFO] Loading configuration:
> C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\target\compile-app-config.xml
>
> [INFO]
>
> [INFO] 57676 bytes written to
> C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\target\MenuExample-0.9.9.swf
> in 0.602 seconds
>
> [INFO] Mar 13, 2022 12:00:56 PM
> com.google.javascript.jscomp.LoggerErrorManager printSummary
>
> [INFO] INFO: 0 error(s), 0 warning(s), 97.8% typed
>
> [INFO] The project 'MenuExample' has been successfully compiled and
> optimized.
>
>
> From: Yishay Weiss
> Sent: Wednesday, March 16, 2022 7:14 AM
> To: Josh Tynjala; dev@royale.apache.org
> 
> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC3
>
> Thanks, I will see if I can figure out why this 

Release Step 010 Succeeded

[apacheroyaleci]

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.9-rc4

You will need your Apache/Github username and 2FA token.

[CANCEL] [VOTE] Release Apache Royale 0.9.9 RC3

[Yishay Weiss]

Josh found an issue with MenuExample

From: apacheroyal...@gmail.com
Sent: Monday, March 14, 2022 8:35 AM
To: dev@royale.apache.org
Subject: [VOTE] Release Apache Royale 0.9.9 RC3

Hi,
This is the vote for the 0.9.9 release of Apache Royale.  The release candidate 
can be found here;
https://dist.apache.org/repos/dist/dev/royale/0.9.9/rc3/

Before voting please review the section,'What are the ASF requirements on 
approving a release?', at:
http://www.apache.org/dev/release.html#approving-a-release

At a minimum you would be expected to check that:
- SHA and signed packages are correct
- README, RELEASE_NOTES, NOTICE and LICENSE files are all fine
- That the build script completes successfully
- That you can compile and crosscompile a simple example using the SDK.

The KEYS file is at https://dist.apache.org/repos/dist/release/royale/KEYS

The source package is a combination of the 3 main Royale repos.

To use the binary package, unzip it into a folder. The -js package is 
ready-to-use in an IDE or command-line. If you need SWF output, use the
-js-swf package and use Apache Ant to run the InstallAdobeSDKs script via:
ant -f InstallAdobeSDKs.xml

You may also get the binarypackages via NPM. The -js package can be installed 
via:
npm install 
https://dist.apache.org/repos/dist/dev/royale/0.9.9/rc3/binaries/apache-royale-0.9.9-bin-js.tar.gz

The full package with SWF support can be installed via:

npm install 
https://dist.apache.org/repos/dist/dev/royale/0.9.9/rc3/binaries/apache-royale-0.9.9-bin-js-swf.tar.gz

Maven artifacts are staged here:
https://repository.apache.org/content/repositories/orgapacheroyale-1090

Please vote to approve this release:
+1 Approve the release
-1 Disapprove the release (please provide specific comments to why)

This vote will be open for 72 hours or until a result can be called.

The vote passes if there is:
- At least 3 +1 votes from the PMC
- More positive votes than negative votes

Remember that this is a 'beta-quality' release so expect there will be many 
bugs found. IMO the goal is not to try to find and fix bugs in the RC, but to 
make sure we have the packaging right, and enough functionality that folks will 
have some success trying to use it.  People who are not in PMC are also 
encouraged to test out the release and vote, although their votes will not be 
binding, they can influence how the PMC votes.

When voting please indicate what OS, IDE, Flash Player version and AIR version 
you tested with.

For your convenience, there is an ant script that automates the common steps to 
validate a release.  Instead of individually downloading the package and 
signature files, unzipping, etc, you can instead:
1) create an empty folder,
2) download into that folder this file:
https://dist.apache.org/repos/dist/dev/royale/0.9.9/rc3/ApproveRoyale.xml
3) run the script:
   ant -e -f ApproveRoyale.xml -Drelease.version=0.9.9 -Drc=3
   If you want to test SWF support during the approval, use:
   ant -e -f ApproveRoyale.xml -Drelease.version=0.9.9 -Drc=3 -Duse-flash=true

You are not required to use this script, and more testing of the packages and 
build results are always encouraged.

Please put all discussion about this release in the DISCUSSION thread not this 
VOTE thread.

Thanks,
Yishay Weiss

RE: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC3

[Yishay Weiss]

>Josh’s pick

I meant Josh’s fix of course (being picky here).
From: Yishay Weiss
Sent: Thursday, March 17, 2022 9:12 AM
To: Josh Tynjala; 
dev@royale.apache.org
Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC3

The examples are run as part of the step 11, but mvn only. The ant examples are 
only built after release approval. For some reason MenuExample was working in 
mvn but not in ant. That’s why the release steps did not fail prior to approval 
script. For anybody curious to find out why these differences between mvn and 
ant exist, this is the maven output [2] taken from the CI logs [1]. You can 
compare it to Josh’s ant output upthread.

Unrelated, I scheduled a daily job for ASDocs example so we can track ASDocs 
errors, as they seem to be pretty common.

I will see if I can figure out if I can continue the release from the existing 
release branch after cherry-picking Josh’s pick.

Thanks.

[1] Royale_Release_Step_011 #26 Console [Jenkins] 
(azure.com)


[2] [INFO] [INFO] ---< org.apache.royale.examples:MenuExample 
>---

[INFO] [INFO] Building Apache Royale: Examples: Royale: MenuExample 0.9.9
[195/265]

[INFO] [INFO] [ swf 
]-

[INFO] [INFO]

[INFO] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ 
MenuExample ---

[INFO] [INFO]

[INFO] [INFO] --- maven-resources-plugin:3.1.0:copy-resources 
(copy-resources-debug) @ MenuExample ---

[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.

[INFO] [INFO] skip non existing resourceDirectory 
C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\src\main\resources

[INFO] [INFO]

[INFO] [INFO] --- maven-resources-plugin:3.1.0:copy-resources 
(copy-resources-release) @ MenuExample ---

[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.

[INFO] [INFO] skip non existing resourceDirectory 
C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\src\main\resources\assets

[INFO] [INFO]

[INFO] [INFO] --- maven-remote-resources-plugin:1.7.0:process 
(process-resource-bundles) @ MenuExample ---

[INFO] [INFO] Preparing remote bundle org.apache:apache-jar-resource-bundle:1.4

[INFO] [INFO] Copying 3 resources from 1 bundle.

[INFO] [INFO]

[INFO] [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ 
MenuExample ---

[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.

[INFO] [INFO] skip non existing resourceDirectory 
C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\src\main\resources

[INFO] [INFO] Copying 3 resources

[INFO] [INFO]

[INFO] [INFO] --- royale-maven-plugin:0.9.9:compile-app (default-compile-app) @ 
MenuExample ---

[INFO] [INFO] Executing MXMLC in tool group Royale with args: 
[-load-config=C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\target\compile-app-config.xml,
 -metadata.date=2022-03-13T09:39:40Z, 
-metadata.dateFormat=-MM-dd'T'HH:mm:ss'Z', 
-js-output=C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\target\javascript,
 -compiler.targets=SWF,JSRoyale, 
C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\src\main\royale\MenuExample.mxml]

[INFO] Loading configuration: 
C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\target\compile-app-config.xml

[INFO]

[INFO] 57676 bytes written to 
C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\target\MenuExample-0.9.9.swf
 in 0.602 seconds

[INFO] Mar 13, 2022 12:00:56 PM com.google.javascript.jscomp.LoggerErrorManager 
printSummary

[INFO] INFO: 0 error(s), 0 warning(s), 97.8% typed

[INFO] The project 'MenuExample' has been successfully compiled and optimized.


From: Yishay Weiss
Sent: Wednesday, March 16, 2022 7:14 AM
To: Josh Tynjala; 
dev@royale.apache.org
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC3

Thanks, I will see if I can figure out why this didn't fail at an earlier 
stage. I will look into why asdoc example isn't run regularly on CI.

My CLT-L09. On O2.


 Original message 
From: Josh Tynjala 
Date: Tue, 15 Mar 2022, 23:07
To: dev@royale.apache.org
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC3
I ran into two separate issues with the approval script.

The first issue was the ASDoc example build failing in the JS-only SDK,
which I discovered was happening because I didn't realize that I had an
AIR_HOME environment variable set 

RE: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC3

[Yishay Weiss]

The examples are run as part of the step 11, but mvn only. The ant examples are 
only built after release approval. For some reason MenuExample was working in 
mvn but not in ant. That’s why the release steps did not fail prior to approval 
script. For anybody curious to find out why these differences between mvn and 
ant exist, this is the maven output [2] taken from the CI logs [1]. You can 
compare it to Josh’s ant output upthread.

Unrelated, I scheduled a daily job for ASDocs example so we can track ASDocs 
errors, as they seem to be pretty common.

I will see if I can figure out if I can continue the release from the existing 
release branch after cherry-picking Josh’s pick.

Thanks.

[1] Royale_Release_Step_011 #26 Console [Jenkins] 
(azure.com)


[2] [INFO] [INFO] ---< org.apache.royale.examples:MenuExample 
>---

[INFO] [INFO] Building Apache Royale: Examples: Royale: MenuExample 0.9.9
[195/265]

[INFO] [INFO] [ swf 
]-

[INFO] [INFO]

[INFO] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ 
MenuExample ---

[INFO] [INFO]

[INFO] [INFO] --- maven-resources-plugin:3.1.0:copy-resources 
(copy-resources-debug) @ MenuExample ---

[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.

[INFO] [INFO] skip non existing resourceDirectory 
C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\src\main\resources

[INFO] [INFO]

[INFO] [INFO] --- maven-resources-plugin:3.1.0:copy-resources 
(copy-resources-release) @ MenuExample ---

[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.

[INFO] [INFO] skip non existing resourceDirectory 
C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\src\main\resources\assets

[INFO] [INFO]

[INFO] [INFO] --- maven-remote-resources-plugin:1.7.0:process 
(process-resource-bundles) @ MenuExample ---

[INFO] [INFO] Preparing remote bundle org.apache:apache-jar-resource-bundle:1.4

[INFO] [INFO] Copying 3 resources from 1 bundle.

[INFO] [INFO]

[INFO] [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ 
MenuExample ---

[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.

[INFO] [INFO] skip non existing resourceDirectory 
C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\src\main\resources

[INFO] [INFO] Copying 3 resources

[INFO] [INFO]

[INFO] [INFO] --- royale-maven-plugin:0.9.9:compile-app (default-compile-app) @ 
MenuExample ---

[INFO] [INFO] Executing MXMLC in tool group Royale with args: 
[-load-config=C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\target\compile-app-config.xml,
 -metadata.date=2022-03-13T09:39:40Z, 
-metadata.dateFormat=-MM-dd'T'HH:mm:ss'Z', 
-js-output=C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\target\javascript,
 -compiler.targets=SWF,JSRoyale, 
C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\src\main\royale\MenuExample.mxml]

[INFO] Loading configuration: 
C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\target\compile-app-config.xml

[INFO]

[INFO] 57676 bytes written to 
C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\examples\royale\MenuExample\target\MenuExample-0.9.9.swf
 in 0.602 seconds

[INFO] Mar 13, 2022 12:00:56 PM com.google.javascript.jscomp.LoggerErrorManager 
printSummary

[INFO] INFO: 0 error(s), 0 warning(s), 97.8% typed

[INFO] The project 'MenuExample' has been successfully compiled and optimized.


From: Yishay Weiss
Sent: Wednesday, March 16, 2022 7:14 AM
To: Josh Tynjala; 
dev@royale.apache.org
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC3

Thanks, I will see if I can figure out why this didn't fail at an earlier 
stage. I will look into why asdoc example isn't run regularly on CI.

My CLT-L09. On O2.


 Original message 
From: Josh Tynjala 
Date: Tue, 15 Mar 2022, 23:07
To: dev@royale.apache.org
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.9 RC3
I ran into two separate issues with the approval script.

The first issue was the ASDoc example build failing in the JS-only SDK,
which I discovered was happening because I didn't realize that I had an
AIR_HOME environment variable set externally. I cleared AIR_HOME, and
that's fixed it for me. No RC needed for this.

The second issue was the MenuExample example build failing. My commit today
fixes that. A new RC is needed to resolve this one with my commit.

--
Josh Tynjala
Bowler Hat LLC 


On Tue, Mar 15, 2022 at 1:52 PM Yishay Weiss