Release Step 009 Succeeded

[apacheroyaleci]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_009 and run the following commands:
git push

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

Release Step 008 Succeeded

[apacheroyaleci]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_008 and run the following commands:
git push
git checkout release/0.9.9
git push -u origin refs/heads/release/0.9.9

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

Re: Update of the royale web site for TDJ

[Andrew Wetmore]

We may have to appeal to Carlos for instructions.

On Sun, Mar 6, 2022 at 8:24 PM Maria Jose Esteve  wrote:

> Hi,
> I have not found explicit instructions for upgrading TDJ, but I have
> deduced from the upgrade instructions on the royale website [1] that you
> manually upgrade with a working release:
> - I compiled TDJ (Maven build).
> - I updated the "tourdejewel" folder in the "royale-website/tree/asf-site"
> repository with the updated TDJ build.
>
> Apparently, I am totally wrong and the TDJ site update is not updated this
> way because I don't see the changes on the website and it has been more
> than 5 hours since I did the last commit.
> How should I update?
>
>
> [1] https://github.com/apache/royale-asjs/wiki/Release-Manager-(Web-Site)
>
> Thx
>
> Hiedra
>
>

-- 
Andrew Wetmore

Editor, Moose House Publications 
Editor-Writer, The Apache Software Foundation 

The Jewel ResponsiveSize bead stopped working.

[Maria Jose Esteve]

Hi,
When compiling the TDJ I noticed that the Jewel ResponsiveSize bead has 
"stopped working" and the Apache logo, which is displayed on the main page, is 
displayed with its original dimensions (very large)
I said "stopped working" because the TDJ displayed on the official website 
seems to work correctly (last update January 2021).
The last update of the file in the royale-asjs repository was in July 2020, how 
can it be that it has stopped working?

Could one of you compile the TDJ and verify the anomalous operation I am 
getting?

Thx.

Hiedra

Update of the royale web site for TDJ

[Maria Jose Esteve]

Hi,
I have not found explicit instructions for upgrading TDJ, but I have deduced 
from the upgrade instructions on the royale website [1] that you manually 
upgrade with a working release:
- I compiled TDJ (Maven build).
- I updated the "tourdejewel" folder in the "royale-website/tree/asf-site" 
repository with the updated TDJ build.

Apparently, I am totally wrong and the TDJ site update is not updated this way 
because I don't see the changes on the website and it has been more than 5 
hours since I did the last commit.
How should I update?


[1] https://github.com/apache/royale-asjs/wiki/Release-Manager-(Web-Site)

Thx

Hiedra

Re: Royale_Release_Step_011 - Build # 24 - Failure!

[Greg Dove]

I don't know, but I will look into it today (local time) and see if I can
figure it out.


On Mon, Mar 7, 2022 at 8:19 AM Yishay Weiss  wrote:

> ASDoc is failing which is blocking the build.
>
> Greg, I have found out commit 63c94366f533bc1384401cdd6ba1f20057b4d999
> breaks the ASDoc example, specifically the following line:
>
> import mx.events.ResourceEvent; ResourceEvent;
>
> Do you (or anyone else) have a hunch why that may be?
>
> From: apacheroyal...@gmail.com
> Sent: Sunday, March 6, 2022 1:23 PM
> To: dev@royale.apache.org
> Subject: Royale_Release_Step_011 - Build # 24 - Failure!
>
> Royale_Release_Step_011 - Build # 24 - Failure:
>
> Check console output at
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_011/24/
> to view the results.
>
>

RE: Royale_Release_Step_011 - Build # 24 - Failure!

[Yishay Weiss]

ASDoc is failing which is blocking the build.

Greg, I have found out commit 63c94366f533bc1384401cdd6ba1f20057b4d999 breaks 
the ASDoc example, specifically the following line:

import mx.events.ResourceEvent; ResourceEvent;

Do you (or anyone else) have a hunch why that may be?

From: apacheroyal...@gmail.com
Sent: Sunday, March 6, 2022 1:23 PM
To: dev@royale.apache.org
Subject: Royale_Release_Step_011 - Build # 24 - Failure!

Royale_Release_Step_011 - Build # 24 - Failure:

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

RE: [apache/royale-asjs] j:DataGridSort is missing (#1111)

[Maria Jose Esteve]

Following the instructions [1], I access wp-admin but I have no user. I have 
tried to access with my apache user (hie...@apache.org), with the github user 
(hie...@github.com), with the account associated with the regisitro of royale 
(mjest...@iest.com) but I imagine that this will have a separate registration.

Who can register me or tell me how to access?

Thx.

[1] https://github.com/apache/royale-asjs/wiki/Release-Manager-(Web-Site)

Hiedra

-Mensaje original-
De: Maria Jose Esteve  
Enviado el: sábado, 5 de marzo de 2022 14:17
Para: dev@royale.apache.org
Asunto: RE: [apache/royale-asjs] j:DataGridSort is missing (#)

Hi Andrew,
This WordPress site is the one hosted on Carlos' server?
I've never used WordPress but I'm going to investigate it... I imagine that 
with the instructions, even if it's expensive, it can be done.

In any case, I'm with you that we should "lead by example" and make a Royale 
site. Have you dealt with this issue before? Should the current site be 
"cloned" or have you thought about giving it a new look?

Hiedra

-Mensaje original-
De: Andrew Wetmore  Enviado el: sábado, 5 de marzo de 2022 
14:09
Para: Apache Royale Development 
Asunto: Re: [apache/royale-asjs] j:DataGridSort is missing (#)

These are the instructions:
https://github.com/apache/royale-asjs/wiki/Release-Manager-(Web-Site).

The complexity of them is part of what makes me want to have a site built using 
Royale, rather than relying on WordPress.

a

On Sat, Mar 5, 2022 at 9:05 AM Maria Jose Esteve  wrote:

> Hi,
> Maybe it would be good, for this release, to update the Royale and TDJ 
> site.
> The website does not have updated links to the latest versions of the 
> SDK and the TDJ is also outdated.
>
> Is there any script I can follow to update it?
>
> Hiedra
>
> -Mensaje original-
> De: Maria Jose Esteve  Enviado el: sábado, 5 de 
> marzo de 2022 14:04
> Para: dev@royale.apache.org
> Asunto: RE: [apache/royale-asjs] j:DataGridSort is missing (#)
>
> Hola,
> Tal vez sería bueno, para este lanzamiento, actualizar el sitio de 
> Royale y del TDJ.
> El sitio web no tiene actualizados los links a las últimas versiones 
> del SDK y el TDJ también está desactualizado.
>
> ¿Existe algún guion que yo pueda seguir para actualizarlo?
>
> Thx.
> Hiedra
>
> De: Nisaba 
> Enviado el: sábado, 5 de marzo de 2022 10:51
> Para: apache/royale-asjs 
> CC: Subscribed 
> Asunto: Re: [apache/royale-asjs] j:DataGridSort is missing (#)
>
>
> Hi,
>
> I use Royale 0.9.9
>
> I've an issue about Datagrid sort that I could reproduce on the example :
> https://royale.apache.org/tourdejewel/#!datagrid_panel
>
> If we click on the "Load Data" button, the sort does'nt work anymore.
>
> Thank you for your help
>
> —
> Reply to this email directly, view it on GitHub<
> https://github.com/apache/royale-asjs/issues/#issuecomment-1059732
> 221>,
> or unsubscribe<
> https://github.com/notifications/unsubscribe-auth/ANJL3UYX3GRIQWCIPKZF
> HUDU6MU7NANCNFSM45FCJE6Q
> >.
> Triage notifications on the go with GitHub Mobile for iOS< 
> https://apps.apple.com/app/apple-store/id1477376905?ct=notification-em
> ail=8=524675>
> or Android<
> https://play.google.com/store/apps/details?id=com.github.android
> rer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_sourc
> e%3Dgithub
> >.
> You are receiving this because you are subscribed to this 
> thread.Message
> ID: 
>


--
Andrew Wetmore

Editor, Moose House Publications  Editor-Writer, 
The Apache Software Foundation 

Royale_Release_Step_011 - Build # 24 - Failure!

[apacheroyaleci]

Royale_Release_Step_011 - Build # 24 - Failure:

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

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

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

Release Step 009 Succeeded

[apacheroyaleci]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_009 and run the following commands:
git push

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

Release Step 008 Succeeded

[apacheroyaleci]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_008 and run the following commands:
git push
git checkout release/0.9.9
git push -u origin refs/heads/release/0.9.9

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

RE: Swc Compiler Version and Binary Reproducibility

[Yishay Weiss]

I had the following in my settings.xml, not sure why it was there to begin 
with. Sorry for the noise.

  
 
royale-release

   
0.9.8

 
  

From: Yishay Weiss
Sent: Thursday, March 3, 2022 5:39 PM
To: dev@royale.apache.org; Josh 
Tynjala
Subject: RE: Swc Compiler Version and Binary Reproducibility

I’m still not sure what’s going on here. My local effective.pom has a 
dependency on compiler version 0.9.8, whereas the one in CI has 0.9.9.

The problem is on my local machine. I added the verbose option [1] to see how 
pom.effective was generated and saw

  0.9.8  

But when I look in parent pom.xml, line 48, I see

0.9.9

I am guessing that the dependency is resolved elsewhere and that the effective 
pom verbose is misleading, but that’s just a theory.

Any ideas?



[1] Apache Maven Help Plugin – 
help:effective-pom

From: Yishay Weiss
Sent: Thursday, February 24, 2022 11:09 AM
To: dev@royale.apache.org; Josh 
Tynjala
Subject: RE: Swc Compiler Version and Binary Reproducibility

The effective pom for the CI swcs does show server version 0.9.8 which seems 
wrong. It could be I was doing something wrong on the CI.

I also had to update the years on NOTICE files and added my 0.9.9 changes to 
RELEASE_NOTES.md.

I think we need to update the rest of the RELEASE_NOTES files in the all repos, 
and when that’s done we can update the top level RELEASE_NOTES under 
royale-asjs\releasemgr\RELEASE_NOTES.

After that’s done I’ll start a new RC and will keep an eye on server versions 
for typedefs.

Thanks.

From: Yishay Weiss
Sent: Thursday, February 24, 2022 8:14 AM
To: Josh Tynjala; Apache Royale 
Development
Subject: RE: Swc Compiler Version and Binary Reproducibility

Ok, I’ll check that. Thanks for the explanation.

From: Josh Tynjala
Sent: Wednesday, February 23, 2022 8:26 PM
To: Apache Royale Development
Cc: yishayj...@hotmail.com
Subject: Re: Swc Compiler Version and Binary Reproducibility

Could it be that the 8 and 9 are derived from the last part of Royale's recent 
version numbers: 0.9.8 and 0.9.9?

In your tutorialspoint link, it prints 1.6.0_25, so I can see why you think it 
might always be the Java version. However, I suspect that's specifically 
because tutorialspoint is calling getImplementationVersion() on the java.lang 
package, so the result will match whichever JDK it is from, since it is a core 
language class. I think that getImplementationVersion() is based on the version 
of the .jar file where the class/package is located. So, for Royale classes, it 
should return something like 0.9.8 or 0.9.9.

Anyway, it seems like the differing build numbers between CI and your local 
machine means that you have a different version of the compiler checked out 
locally than what the CI has.


--
Josh Tynjala
Bowler Hat LLC


On Wed, Feb 23, 2022 at 10:04 AM Yishay Weiss 
mailto:yishayj...@hotmail.com>> wrote:
The typedef swcs produced on my machine are different to the ones produced on 
CI which breaks the build process. I noticed this difference in the catalog 
(though it’s not the only one)




Can somebody explain why the build# is different?

I had a look at SWCTarget.java in the compiler and it looks like it’s getting 
its information from VersionInfo which ultimately relies on Java’s 
getImplementationVersion() [1].

I checked java -version both on my machine and on the CI and they both output 
1.8.0_201, so I don’t understand why the version is different.

Any clues?

[1] Java.lang.getImplementationVersion() Method 
(tutorialspoint.com)