Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Yishay Weiss]

Ok, I did that. I will announce the release once @Andrew 
Wetmore<mailto:cottag...@gmail.com> approves the draft.

From: Josh Tynjala 
Sent: Wednesday, May 31, 2023 5:21 PM
To: dev@royale.apache.org 
Subject: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

I think you just replace the contents of the tourdejewel directory with a
new build:

https://github.com/apache/royale-website/tree/master/tourdejewel

--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>


On Wed, May 31, 2023 at 2:40 AM Yishay Weiss  wrote:

> I added a blog post to the docs repo, does it get published automatically?
>
> What needs to be done in TDJ?
> 
> From: Josh Tynjala 
> Sent: Tuesday, May 30, 2023 7:02 PM
> To: dev@royale.apache.org 
> Subject: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
>
> I just updated the source code and downloads pages on the website to link
> to 0.9.10.
>
> In addition to Tour de Jewel, we'll need a 9.10.0 blog post. As with
> previous releases, it can simply be based on the changelogs.
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Sun, May 28, 2023 at 10:54 PM Piotr Zarzycki  >
> wrote:
>
> > I agree on a point where we need more people who can easily do a release.
> > Let’s have 2 more releases with someone else than you and discuss 1.0
> than.
> >
> > In case of announcing I think it should happen once all release related
> > stuff is fully done. We need to update website and Tour de Jewel build
> > maybe. Do you know how to do that ?
> >
> > On Sun, 28 May 2023 at 14:31, Yishay Weiss 
> wrote:
> >
> > > I think it's a good idea to bump the next version, maybe to 0.9.12.
> Going
> > > to 1.0 now does not seem like a good idea to me, because it would
> involve
> > > some overhead and my aim now is to get somebody else in the team
> involved
> > > in the next release and I want to keep it simple for him or her.
> > >
> > > I just posted the standard draft announcement, if anybody has
> suggestions
> > > on how to handle the npm version confusion there, please respond to
> that
> > > thread.
> > >
> > > Thanks.
> > > 
> > > From: Piotr Zarzycki 
> > > Sent: Sunday, May 28, 2023 2:20 PM
> > > To: dev@royale.apache.org 
> > > Cc: OmPrakash Muppirala 
> > > Subject: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
> > >
> > > My suggestion is next release 1.0.0 finally and forgot about that minor
> > > stuff.
> > >
> > > The other thing let’s have clear explanation in announcement.
> > >
> > > On Sun, 28 May 2023 at 11:52, Yishay Weiss 
> > wrote:
> > >
> > > > OTOH the release number is incorrect. I published it to 0.9.11
> > > > accidentally. I'm afraid I cannot change that to 0.9.10 because I
> > > > accidentally published to 0.9.10 a year ago. The good news is that I
> > have
> > > > fixed the npm release script so this issue should not happen again.
> The
> > > bad
> > > > news is that when we release 0.9.11 we won't be able to overwrite the
> > > > current 0.9.11 version.
> > > >
> > > > Unpublishing 0.9.10 and 0.9.11 is not an option so long as @OmPrakash
> > > > Muppirala<mailto:bigosma...@gmail.com> is listed as a maintainer and
> > > does
> > > > not explicitly approve.
> > > >
> > > > Not sure what to do here, so any suggestions are welcome.
> > > >
> > > >
> > > >
> > > >
> > > > 
> > > > From: Josh Tynjala 
> > > > Sent: Thursday, May 25, 2023 8:31 PM
> > > > To: dev@royale.apache.org 
> > > > Subject: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
> > > >
> > > > In reference to the npm issue with the 0.9.9 release [1], I just
> wanted
> > > to
> > > > mention that I've confirmed that the published npm packages are
> > > > working correctly for this release. Yay!
> > > >
> > > > [1] https://lists.apache.org/thread/zclk7q1lowsv464797xl5wmxr2skj2ww
> > > >
> > > > --
> > > > Josh Tynjala
> > > > Bowler Hat LLC <https://bowlerhat.dev>
> > > >
> > > >
> > > > On Sat, May 13, 2023 at 10:37 AM Yishay Weiss <
> yishayj...@hotmail.com>
> > > > wrote:
> > > >
> > > > > This is the discussion thread.
> > > > >
> > > >
> > > --
> > >
> > > Piotr Zarzycki
> > >
> > --
> >
> > Piotr Zarzycki
> >
>

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Josh Tynjala]

I think you just replace the contents of the tourdejewel directory with a
new build:

https://github.com/apache/royale-website/tree/master/tourdejewel

--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>


On Wed, May 31, 2023 at 2:40 AM Yishay Weiss  wrote:

> I added a blog post to the docs repo, does it get published automatically?
>
> What needs to be done in TDJ?
> 
> From: Josh Tynjala 
> Sent: Tuesday, May 30, 2023 7:02 PM
> To: dev@royale.apache.org 
> Subject: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
>
> I just updated the source code and downloads pages on the website to link
> to 0.9.10.
>
> In addition to Tour de Jewel, we'll need a 9.10.0 blog post. As with
> previous releases, it can simply be based on the changelogs.
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Sun, May 28, 2023 at 10:54 PM Piotr Zarzycki  >
> wrote:
>
> > I agree on a point where we need more people who can easily do a release.
> > Let’s have 2 more releases with someone else than you and discuss 1.0
> than.
> >
> > In case of announcing I think it should happen once all release related
> > stuff is fully done. We need to update website and Tour de Jewel build
> > maybe. Do you know how to do that ?
> >
> > On Sun, 28 May 2023 at 14:31, Yishay Weiss 
> wrote:
> >
> > > I think it's a good idea to bump the next version, maybe to 0.9.12.
> Going
> > > to 1.0 now does not seem like a good idea to me, because it would
> involve
> > > some overhead and my aim now is to get somebody else in the team
> involved
> > > in the next release and I want to keep it simple for him or her.
> > >
> > > I just posted the standard draft announcement, if anybody has
> suggestions
> > > on how to handle the npm version confusion there, please respond to
> that
> > > thread.
> > >
> > > Thanks.
> > > 
> > > From: Piotr Zarzycki 
> > > Sent: Sunday, May 28, 2023 2:20 PM
> > > To: dev@royale.apache.org 
> > > Cc: OmPrakash Muppirala 
> > > Subject: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
> > >
> > > My suggestion is next release 1.0.0 finally and forgot about that minor
> > > stuff.
> > >
> > > The other thing let’s have clear explanation in announcement.
> > >
> > > On Sun, 28 May 2023 at 11:52, Yishay Weiss 
> > wrote:
> > >
> > > > OTOH the release number is incorrect. I published it to 0.9.11
> > > > accidentally. I'm afraid I cannot change that to 0.9.10 because I
> > > > accidentally published to 0.9.10 a year ago. The good news is that I
> > have
> > > > fixed the npm release script so this issue should not happen again.
> The
> > > bad
> > > > news is that when we release 0.9.11 we won't be able to overwrite the
> > > > current 0.9.11 version.
> > > >
> > > > Unpublishing 0.9.10 and 0.9.11 is not an option so long as @OmPrakash
> > > > Muppirala<mailto:bigosma...@gmail.com> is listed as a maintainer and
> > > does
> > > > not explicitly approve.
> > > >
> > > > Not sure what to do here, so any suggestions are welcome.
> > > >
> > > >
> > > >
> > > >
> > > > 
> > > > From: Josh Tynjala 
> > > > Sent: Thursday, May 25, 2023 8:31 PM
> > > > To: dev@royale.apache.org 
> > > > Subject: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
> > > >
> > > > In reference to the npm issue with the 0.9.9 release [1], I just
> wanted
> > > to
> > > > mention that I've confirmed that the published npm packages are
> > > > working correctly for this release. Yay!
> > > >
> > > > [1] https://lists.apache.org/thread/zclk7q1lowsv464797xl5wmxr2skj2ww
> > > >
> > > > --
> > > > Josh Tynjala
> > > > Bowler Hat LLC <https://bowlerhat.dev>
> > > >
> > > >
> > > > On Sat, May 13, 2023 at 10:37 AM Yishay Weiss <
> yishayj...@hotmail.com>
> > > > wrote:
> > > >
> > > > > This is the discussion thread.
> > > > >
> > > >
> > > --
> > >
> > > Piotr Zarzycki
> > >
> > --
> >
> > Piotr Zarzycki
> >
>

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Yishay Weiss]

I added a blog post to the docs repo, does it get published automatically?

What needs to be done in TDJ?

From: Josh Tynjala 
Sent: Tuesday, May 30, 2023 7:02 PM
To: dev@royale.apache.org 
Subject: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

I just updated the source code and downloads pages on the website to link
to 0.9.10.

In addition to Tour de Jewel, we'll need a 9.10.0 blog post. As with
previous releases, it can simply be based on the changelogs.

--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>


On Sun, May 28, 2023 at 10:54 PM Piotr Zarzycki 
wrote:

> I agree on a point where we need more people who can easily do a release.
> Let’s have 2 more releases with someone else than you and discuss 1.0 than.
>
> In case of announcing I think it should happen once all release related
> stuff is fully done. We need to update website and Tour de Jewel build
> maybe. Do you know how to do that ?
>
> On Sun, 28 May 2023 at 14:31, Yishay Weiss  wrote:
>
> > I think it's a good idea to bump the next version, maybe to 0.9.12. Going
> > to 1.0 now does not seem like a good idea to me, because it would involve
> > some overhead and my aim now is to get somebody else in the team involved
> > in the next release and I want to keep it simple for him or her.
> >
> > I just posted the standard draft announcement, if anybody has suggestions
> > on how to handle the npm version confusion there, please respond to that
> > thread.
> >
> > Thanks.
> > 
> > From: Piotr Zarzycki 
> > Sent: Sunday, May 28, 2023 2:20 PM
> > To: dev@royale.apache.org 
> > Cc: OmPrakash Muppirala 
> > Subject: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
> >
> > My suggestion is next release 1.0.0 finally and forgot about that minor
> > stuff.
> >
> > The other thing let’s have clear explanation in announcement.
> >
> > On Sun, 28 May 2023 at 11:52, Yishay Weiss 
> wrote:
> >
> > > OTOH the release number is incorrect. I published it to 0.9.11
> > > accidentally. I'm afraid I cannot change that to 0.9.10 because I
> > > accidentally published to 0.9.10 a year ago. The good news is that I
> have
> > > fixed the npm release script so this issue should not happen again. The
> > bad
> > > news is that when we release 0.9.11 we won't be able to overwrite the
> > > current 0.9.11 version.
> > >
> > > Unpublishing 0.9.10 and 0.9.11 is not an option so long as @OmPrakash
> > > Muppirala<mailto:bigosma...@gmail.com> is listed as a maintainer and
> > does
> > > not explicitly approve.
> > >
> > > Not sure what to do here, so any suggestions are welcome.
> > >
> > >
> > >
> > >
> > > 
> > > From: Josh Tynjala 
> > > Sent: Thursday, May 25, 2023 8:31 PM
> > > To: dev@royale.apache.org 
> > > Subject: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
> > >
> > > In reference to the npm issue with the 0.9.9 release [1], I just wanted
> > to
> > > mention that I've confirmed that the published npm packages are
> > > working correctly for this release. Yay!
> > >
> > > [1] https://lists.apache.org/thread/zclk7q1lowsv464797xl5wmxr2skj2ww
> > >
> > > --
> > > Josh Tynjala
> > > Bowler Hat LLC <https://bowlerhat.dev>
> > >
> > >
> > > On Sat, May 13, 2023 at 10:37 AM Yishay Weiss 
> > > wrote:
> > >
> > > > This is the discussion thread.
> > > >
> > >
> > --
> >
> > Piotr Zarzycki
> >
> --
>
> Piotr Zarzycki
>

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Josh Tynjala]

I just updated the source code and downloads pages on the website to link
to 0.9.10.

In addition to Tour de Jewel, we'll need a 9.10.0 blog post. As with
previous releases, it can simply be based on the changelogs.

--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>


On Sun, May 28, 2023 at 10:54 PM Piotr Zarzycki 
wrote:

> I agree on a point where we need more people who can easily do a release.
> Let’s have 2 more releases with someone else than you and discuss 1.0 than.
>
> In case of announcing I think it should happen once all release related
> stuff is fully done. We need to update website and Tour de Jewel build
> maybe. Do you know how to do that ?
>
> On Sun, 28 May 2023 at 14:31, Yishay Weiss  wrote:
>
> > I think it's a good idea to bump the next version, maybe to 0.9.12. Going
> > to 1.0 now does not seem like a good idea to me, because it would involve
> > some overhead and my aim now is to get somebody else in the team involved
> > in the next release and I want to keep it simple for him or her.
> >
> > I just posted the standard draft announcement, if anybody has suggestions
> > on how to handle the npm version confusion there, please respond to that
> > thread.
> >
> > Thanks.
> > 
> > From: Piotr Zarzycki 
> > Sent: Sunday, May 28, 2023 2:20 PM
> > To: dev@royale.apache.org 
> > Cc: OmPrakash Muppirala 
> > Subject: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
> >
> > My suggestion is next release 1.0.0 finally and forgot about that minor
> > stuff.
> >
> > The other thing let’s have clear explanation in announcement.
> >
> > On Sun, 28 May 2023 at 11:52, Yishay Weiss 
> wrote:
> >
> > > OTOH the release number is incorrect. I published it to 0.9.11
> > > accidentally. I'm afraid I cannot change that to 0.9.10 because I
> > > accidentally published to 0.9.10 a year ago. The good news is that I
> have
> > > fixed the npm release script so this issue should not happen again. The
> > bad
> > > news is that when we release 0.9.11 we won't be able to overwrite the
> > > current 0.9.11 version.
> > >
> > > Unpublishing 0.9.10 and 0.9.11 is not an option so long as @OmPrakash
> > > Muppirala<mailto:bigosma...@gmail.com> is listed as a maintainer and
> > does
> > > not explicitly approve.
> > >
> > > Not sure what to do here, so any suggestions are welcome.
> > >
> > >
> > >
> > >
> > > 
> > > From: Josh Tynjala 
> > > Sent: Thursday, May 25, 2023 8:31 PM
> > > To: dev@royale.apache.org 
> > > Subject: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
> > >
> > > In reference to the npm issue with the 0.9.9 release [1], I just wanted
> > to
> > > mention that I've confirmed that the published npm packages are
> > > working correctly for this release. Yay!
> > >
> > > [1] https://lists.apache.org/thread/zclk7q1lowsv464797xl5wmxr2skj2ww
> > >
> > > --
> > > Josh Tynjala
> > > Bowler Hat LLC <https://bowlerhat.dev>
> > >
> > >
> > > On Sat, May 13, 2023 at 10:37 AM Yishay Weiss 
> > > wrote:
> > >
> > > > This is the discussion thread.
> > > >
> > >
> > --
> >
> > Piotr Zarzycki
> >
> --
>
> Piotr Zarzycki
>

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Piotr Zarzycki]

I agree on a point where we need more people who can easily do a release.
Let’s have 2 more releases with someone else than you and discuss 1.0 than.

In case of announcing I think it should happen once all release related
stuff is fully done. We need to update website and Tour de Jewel build
maybe. Do you know how to do that ?

On Sun, 28 May 2023 at 14:31, Yishay Weiss  wrote:

> I think it's a good idea to bump the next version, maybe to 0.9.12. Going
> to 1.0 now does not seem like a good idea to me, because it would involve
> some overhead and my aim now is to get somebody else in the team involved
> in the next release and I want to keep it simple for him or her.
>
> I just posted the standard draft announcement, if anybody has suggestions
> on how to handle the npm version confusion there, please respond to that
> thread.
>
> Thanks.
> 
> From: Piotr Zarzycki 
> Sent: Sunday, May 28, 2023 2:20 PM
> To: dev@royale.apache.org 
> Cc: OmPrakash Muppirala 
> Subject: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
>
> My suggestion is next release 1.0.0 finally and forgot about that minor
> stuff.
>
> The other thing let’s have clear explanation in announcement.
>
> On Sun, 28 May 2023 at 11:52, Yishay Weiss  wrote:
>
> > OTOH the release number is incorrect. I published it to 0.9.11
> > accidentally. I'm afraid I cannot change that to 0.9.10 because I
> > accidentally published to 0.9.10 a year ago. The good news is that I have
> > fixed the npm release script so this issue should not happen again. The
> bad
> > news is that when we release 0.9.11 we won't be able to overwrite the
> > current 0.9.11 version.
> >
> > Unpublishing 0.9.10 and 0.9.11 is not an option so long as @OmPrakash
> > Muppirala<mailto:bigosma...@gmail.com> is listed as a maintainer and
> does
> > not explicitly approve.
> >
> > Not sure what to do here, so any suggestions are welcome.
> >
> >
> >
> >
> > 
> > From: Josh Tynjala 
> > Sent: Thursday, May 25, 2023 8:31 PM
> > To: dev@royale.apache.org 
> > Subject: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
> >
> > In reference to the npm issue with the 0.9.9 release [1], I just wanted
> to
> > mention that I've confirmed that the published npm packages are
> > working correctly for this release. Yay!
> >
> > [1] https://lists.apache.org/thread/zclk7q1lowsv464797xl5wmxr2skj2ww
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC <https://bowlerhat.dev>
> >
> >
> > On Sat, May 13, 2023 at 10:37 AM Yishay Weiss 
> > wrote:
> >
> > > This is the discussion thread.
> > >
> >
> --
>
> Piotr Zarzycki
>
-- 

Piotr Zarzycki

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Yishay Weiss]

I think it's a good idea to bump the next version, maybe to 0.9.12. Going to 
1.0 now does not seem like a good idea to me, because it would involve some 
overhead and my aim now is to get somebody else in the team involved in the 
next release and I want to keep it simple for him or her.

I just posted the standard draft announcement, if anybody has suggestions on 
how to handle the npm version confusion there, please respond to that thread.

Thanks.

From: Piotr Zarzycki 
Sent: Sunday, May 28, 2023 2:20 PM
To: dev@royale.apache.org 
Cc: OmPrakash Muppirala 
Subject: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

My suggestion is next release 1.0.0 finally and forgot about that minor
stuff.

The other thing let’s have clear explanation in announcement.

On Sun, 28 May 2023 at 11:52, Yishay Weiss  wrote:

> OTOH the release number is incorrect. I published it to 0.9.11
> accidentally. I'm afraid I cannot change that to 0.9.10 because I
> accidentally published to 0.9.10 a year ago. The good news is that I have
> fixed the npm release script so this issue should not happen again. The bad
> news is that when we release 0.9.11 we won't be able to overwrite the
> current 0.9.11 version.
>
> Unpublishing 0.9.10 and 0.9.11 is not an option so long as @OmPrakash
> Muppirala<mailto:bigosma...@gmail.com> is listed as a maintainer and does
> not explicitly approve.
>
> Not sure what to do here, so any suggestions are welcome.
>
>
>
>
> 
> From: Josh Tynjala 
> Sent: Thursday, May 25, 2023 8:31 PM
> To: dev@royale.apache.org 
> Subject: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
>
> In reference to the npm issue with the 0.9.9 release [1], I just wanted to
> mention that I've confirmed that the published npm packages are
> working correctly for this release. Yay!
>
> [1] https://lists.apache.org/thread/zclk7q1lowsv464797xl5wmxr2skj2ww
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Sat, May 13, 2023 at 10:37 AM Yishay Weiss 
> wrote:
>
> > This is the discussion thread.
> >
>
--

Piotr Zarzycki

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Piotr Zarzycki]

My suggestion is next release 1.0.0 finally and forgot about that minor
stuff.

The other thing let’s have clear explanation in announcement.

On Sun, 28 May 2023 at 11:52, Yishay Weiss  wrote:

> OTOH the release number is incorrect. I published it to 0.9.11
> accidentally. I'm afraid I cannot change that to 0.9.10 because I
> accidentally published to 0.9.10 a year ago. The good news is that I have
> fixed the npm release script so this issue should not happen again. The bad
> news is that when we release 0.9.11 we won't be able to overwrite the
> current 0.9.11 version.
>
> Unpublishing 0.9.10 and 0.9.11 is not an option so long as @OmPrakash
> Muppirala<mailto:bigosma...@gmail.com> is listed as a maintainer and does
> not explicitly approve.
>
> Not sure what to do here, so any suggestions are welcome.
>
>
>
>
> 
> From: Josh Tynjala 
> Sent: Thursday, May 25, 2023 8:31 PM
> To: dev@royale.apache.org 
> Subject: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
>
> In reference to the npm issue with the 0.9.9 release [1], I just wanted to
> mention that I've confirmed that the published npm packages are
> working correctly for this release. Yay!
>
> [1] https://lists.apache.org/thread/zclk7q1lowsv464797xl5wmxr2skj2ww
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Sat, May 13, 2023 at 10:37 AM Yishay Weiss 
> wrote:
>
> > This is the discussion thread.
> >
>
-- 

Piotr Zarzycki

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Yishay Weiss]

OTOH the release number is incorrect. I published it to 0.9.11 accidentally. 
I'm afraid I cannot change that to 0.9.10 because I accidentally published to 
0.9.10 a year ago. The good news is that I have fixed the npm release script so 
this issue should not happen again. The bad news is that when we release 0.9.11 
we won't be able to overwrite the current 0.9.11 version.

Unpublishing 0.9.10 and 0.9.11 is not an option so long as @OmPrakash 
Muppirala<mailto:bigosma...@gmail.com> is listed as a maintainer and does not 
explicitly approve.

Not sure what to do here, so any suggestions are welcome.





From: Josh Tynjala 
Sent: Thursday, May 25, 2023 8:31 PM
To: dev@royale.apache.org 
Subject: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

In reference to the npm issue with the 0.9.9 release [1], I just wanted to
mention that I've confirmed that the published npm packages are
working correctly for this release. Yay!

[1] https://lists.apache.org/thread/zclk7q1lowsv464797xl5wmxr2skj2ww

--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>


On Sat, May 13, 2023 at 10:37 AM Yishay Weiss 
wrote:

> This is the discussion thread.
>

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Josh Tynjala]

In reference to the npm issue with the 0.9.9 release [1], I just wanted to
mention that I've confirmed that the published npm packages are
working correctly for this release. Yay!

[1] https://lists.apache.org/thread/zclk7q1lowsv464797xl5wmxr2skj2ww

--
Josh Tynjala
Bowler Hat LLC 


On Sat, May 13, 2023 at 10:37 AM Yishay Weiss 
wrote:

> This is the discussion thread.
>

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Piotr Zarzycki]

It is awaiting. I will be available on slack for the next 3-4h I can
provide you one time password quickly.

wt., 23 maj 2023 o 14:20 Yishay Weiss  napisał(a):

> I think everything is ready, except npm. I have disabled 2FA on npmjs site
> but there is a one-time password being sent to private for each attempt to
> login. @Piotr Zarzycki , can you please check
> if it's awaiting moderation? I think we discussed white-listing these but
> it looks like it's being moderated.
>
> For now, I have removed the ant target that used to publish to npm as it
> is no longer working with new 2FA rules. If anybody wants to take a look
> and suggest a workaround it's in as-js/releasecandidate.xml under
> release.npm target.
>
> Once we're done with npm I will draft an announcement.
>
> --
> *From:* Harbs 
> *Sent:* Tuesday, May 23, 2023 11:25 AM
> *To:* dev@royale.apache.org 
> *Subject:* Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
>
> Ditto...
>
> > On May 23, 2023, at 8:31 AM, Greg Dove  wrote:
> >
> > Sorry Team,
> >
> > I was meaning to get to this, but have been crazy busy.  I will do better
> > next time.
> >
> >
> > On Tue, May 23, 2023 at 5:23 PM Yishay Weiss 
> wrote:
> >
> >> Good point. I had in my head 4 votes at least were necessary, but 3 is
> >> enough.
> >> ____________
> >> From: Piotr Zarzycki 
> >> Sent: Monday, May 22, 2023 10:51 AM
> >> To: dev@royale.apache.org 
> >> Subject: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
> >>
> >> I believe we are good with this release ? Is there something which has
> to
> >> be done more ?
> >>
> >> śr., 17 maj 2023 o 12:16 Yishay Weiss 
> napisał(a):
> >>
> >>> What java version are you using? Try jdk 17/11/8.
> >>> 
> >>> From: Harbs 
> >>> Sent: Wednesday, May 17, 2023 12:03 PM
> >>> To: dev@royale.apache.org 
> >>> Subject: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
> >>>
> >>> I tried running this on my new computer and I’m getting errors with
> >> Maven:
> >>>
> >>> [INFO] Reactor Summary for Apache Royale: Compiler: Parent 0.9.10:
> >>> [INFO]
> >>> [INFO] Apache Royale: Compiler: Parent  SUCCESS [
> >>> 27.630 s]
> >>> [INFO] Apache Royale: Compiler: Compiler-Common ... SUCCESS [
> >>> 2.998 s]
> >>> [INFO] Apache Royale: Compiler: Test Utils  SUCCESS [
> >>> 0.542 s]
> >>> [INFO] Apache Royale: Compiler: Externc ... SUCCESS [
> >>> 10.956 s]
> >>> [INFO] Apache Royale: Compiler: playerglobal.swc support .. SUCCESS [
> >>> 0.756 s]
> >>> [INFO] Apache Royale: Compiler: Compiler .. FAILURE [
> >>> 5.699 s]
> >>> [INFO] Apache Royale: Compiler: Compiler-JX ... SKIPPED
> >>> [INFO] Apache Royale: Compiler: SWFUtils .. SKIPPED
> >>> [INFO] Apache Royale: Compiler: Debugger .. SKIPPED
> >>> [INFO] Apache Royale: Compiler: AS3/MXML Code Formatter ... SKIPPED
> >>> [INFO] Apache Royale: Compiler: AS3/MXML Code Linter .. SKIPPED
> >>> [INFO] Apache Royale: Compiler: OEM Layer . SKIPPED
> >>> [INFO] Apache Royale: Royale Ant Tasks  SKIPPED
> >>> [INFO] Apache Royale: RoyaleUnit Ant Tasks  SKIPPED
> >>> [INFO] Apache Royale: Royale Maven Plugin . SKIPPED
> >>> [INFO]
> >>>
> 
> >>> [INFO] BUILD FAILURE
> >>> [INFO]
> >>>
> 
> >>> [INFO] Total time:  48.749 s
> >>> [INFO] Finished at: 2023-05-17T11:22:53+03:00
> >>> [INFO]
> >>>
> 
> >>> [WARNING]
> >>> [WARNING] Plugin validation issues were detected in 17 plugin(s)
> >>> [WARNING]
> >>> [WARNING]  * org.jacoco:jacoco-maven-plugin:0.8.5
> >>> [WARNING]  * org.apache.maven.plugins:maven-jar-plugin:3.2.0
> >>> [WARNING]  * de.jflex:maven-jflex-plugin:1.4.3
> >>> [WARNING]  * org.apache.maven.plugins:maven-compiler-plugin:3.8.1
> >>> [WARNING]  * org.apac

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Yishay Weiss]

I think everything is ready, except npm. I have disabled 2FA on npmjs site but 
there is a one-time password being sent to private for each attempt to login. 
@Piotr Zarzycki<mailto:piotrzarzyck...@gmail.com>, can you please check if it's 
awaiting moderation? I think we discussed white-listing these but it looks like 
it's being moderated.

For now, I have removed the ant target that used to publish to npm as it is no 
longer working with new 2FA rules. If anybody wants to take a look and suggest 
a workaround it's in as-js/releasecandidate.xml under release.npm target.

Once we're done with npm I will draft an announcement.


From: Harbs 
Sent: Tuesday, May 23, 2023 11:25 AM
To: dev@royale.apache.org 
Subject: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

Ditto...

> On May 23, 2023, at 8:31 AM, Greg Dove  wrote:
>
> Sorry Team,
>
> I was meaning to get to this, but have been crazy busy.  I will do better
> next time.
>
>
> On Tue, May 23, 2023 at 5:23 PM Yishay Weiss  wrote:
>
>> Good point. I had in my head 4 votes at least were necessary, but 3 is
>> enough.
>> 
>> From: Piotr Zarzycki 
>> Sent: Monday, May 22, 2023 10:51 AM
>> To: dev@royale.apache.org 
>> Subject: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
>>
>> I believe we are good with this release ? Is there something which has to
>> be done more ?
>>
>> śr., 17 maj 2023 o 12:16 Yishay Weiss  napisał(a):
>>
>>> What java version are you using? Try jdk 17/11/8.
>>> ________________
>>> From: Harbs 
>>> Sent: Wednesday, May 17, 2023 12:03 PM
>>> To: dev@royale.apache.org 
>>> Subject: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
>>>
>>> I tried running this on my new computer and I’m getting errors with
>> Maven:
>>>
>>> [INFO] Reactor Summary for Apache Royale: Compiler: Parent 0.9.10:
>>> [INFO]
>>> [INFO] Apache Royale: Compiler: Parent  SUCCESS [
>>> 27.630 s]
>>> [INFO] Apache Royale: Compiler: Compiler-Common ... SUCCESS [
>>> 2.998 s]
>>> [INFO] Apache Royale: Compiler: Test Utils  SUCCESS [
>>> 0.542 s]
>>> [INFO] Apache Royale: Compiler: Externc ... SUCCESS [
>>> 10.956 s]
>>> [INFO] Apache Royale: Compiler: playerglobal.swc support .. SUCCESS [
>>> 0.756 s]
>>> [INFO] Apache Royale: Compiler: Compiler .. FAILURE [
>>> 5.699 s]
>>> [INFO] Apache Royale: Compiler: Compiler-JX ... SKIPPED
>>> [INFO] Apache Royale: Compiler: SWFUtils .. SKIPPED
>>> [INFO] Apache Royale: Compiler: Debugger .. SKIPPED
>>> [INFO] Apache Royale: Compiler: AS3/MXML Code Formatter ... SKIPPED
>>> [INFO] Apache Royale: Compiler: AS3/MXML Code Linter .. SKIPPED
>>> [INFO] Apache Royale: Compiler: OEM Layer . SKIPPED
>>> [INFO] Apache Royale: Royale Ant Tasks  SKIPPED
>>> [INFO] Apache Royale: RoyaleUnit Ant Tasks  SKIPPED
>>> [INFO] Apache Royale: Royale Maven Plugin . SKIPPED
>>> [INFO]
>>> 
>>> [INFO] BUILD FAILURE
>>> [INFO]
>>> 
>>> [INFO] Total time:  48.749 s
>>> [INFO] Finished at: 2023-05-17T11:22:53+03:00
>>> [INFO]
>>> 
>>> [WARNING]
>>> [WARNING] Plugin validation issues were detected in 17 plugin(s)
>>> [WARNING]
>>> [WARNING]  * org.jacoco:jacoco-maven-plugin:0.8.5
>>> [WARNING]  * org.apache.maven.plugins:maven-jar-plugin:3.2.0
>>> [WARNING]  * de.jflex:maven-jflex-plugin:1.4.3
>>> [WARNING]  * org.apache.maven.plugins:maven-compiler-plugin:3.8.1
>>> [WARNING]  * org.apache.maven.plugins:maven-clean-plugin:3.1.0
>>> [WARNING]  * org.apache.maven.plugins:maven-failsafe-plugin:2.22.1
>>> [WARNING]  * org.apache.royale.compiler:compiler-build-tools:1.2.1
>>> [WARNING]  * org.apache.maven.plugins:maven-surefire-plugin:2.22.1
>>> [WARNING]  * org.codehaus.mojo:animal-sniffer-maven-plugin:1.18
>>> [WARNING]  * org.apache.maven.plugins:maven-dependency-plugin:3.1.1
>>> [WARNING]  * org.apache.maven.plugins:maven-resources-plugin:3.1.0
>>> [WARNING]  *
>>> com.googlecode.maven-download-plugin:download-maven-plugin:1.5.0
>&g

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Harbs]

Ditto...

> On May 23, 2023, at 8:31 AM, Greg Dove  wrote:
> 
> Sorry Team,
> 
> I was meaning to get to this, but have been crazy busy.  I will do better
> next time.
> 
> 
> On Tue, May 23, 2023 at 5:23 PM Yishay Weiss  wrote:
> 
>> Good point. I had in my head 4 votes at least were necessary, but 3 is
>> enough.
>> 
>> From: Piotr Zarzycki 
>> Sent: Monday, May 22, 2023 10:51 AM
>> To: dev@royale.apache.org 
>> Subject: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
>> 
>> I believe we are good with this release ? Is there something which has to
>> be done more ?
>> 
>> śr., 17 maj 2023 o 12:16 Yishay Weiss  napisał(a):
>> 
>>> What java version are you using? Try jdk 17/11/8.
>>> ________________
>>> From: Harbs 
>>> Sent: Wednesday, May 17, 2023 12:03 PM
>>> To: dev@royale.apache.org 
>>> Subject: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
>>> 
>>> I tried running this on my new computer and I’m getting errors with
>> Maven:
>>> 
>>> [INFO] Reactor Summary for Apache Royale: Compiler: Parent 0.9.10:
>>> [INFO]
>>> [INFO] Apache Royale: Compiler: Parent  SUCCESS [
>>> 27.630 s]
>>> [INFO] Apache Royale: Compiler: Compiler-Common ... SUCCESS [
>>> 2.998 s]
>>> [INFO] Apache Royale: Compiler: Test Utils  SUCCESS [
>>> 0.542 s]
>>> [INFO] Apache Royale: Compiler: Externc ... SUCCESS [
>>> 10.956 s]
>>> [INFO] Apache Royale: Compiler: playerglobal.swc support .. SUCCESS [
>>> 0.756 s]
>>> [INFO] Apache Royale: Compiler: Compiler .. FAILURE [
>>> 5.699 s]
>>> [INFO] Apache Royale: Compiler: Compiler-JX ... SKIPPED
>>> [INFO] Apache Royale: Compiler: SWFUtils .. SKIPPED
>>> [INFO] Apache Royale: Compiler: Debugger .. SKIPPED
>>> [INFO] Apache Royale: Compiler: AS3/MXML Code Formatter ... SKIPPED
>>> [INFO] Apache Royale: Compiler: AS3/MXML Code Linter .. SKIPPED
>>> [INFO] Apache Royale: Compiler: OEM Layer . SKIPPED
>>> [INFO] Apache Royale: Royale Ant Tasks  SKIPPED
>>> [INFO] Apache Royale: RoyaleUnit Ant Tasks  SKIPPED
>>> [INFO] Apache Royale: Royale Maven Plugin . SKIPPED
>>> [INFO]
>>> 
>>> [INFO] BUILD FAILURE
>>> [INFO]
>>> 
>>> [INFO] Total time:  48.749 s
>>> [INFO] Finished at: 2023-05-17T11:22:53+03:00
>>> [INFO]
>>> 
>>> [WARNING]
>>> [WARNING] Plugin validation issues were detected in 17 plugin(s)
>>> [WARNING]
>>> [WARNING]  * org.jacoco:jacoco-maven-plugin:0.8.5
>>> [WARNING]  * org.apache.maven.plugins:maven-jar-plugin:3.2.0
>>> [WARNING]  * de.jflex:maven-jflex-plugin:1.4.3
>>> [WARNING]  * org.apache.maven.plugins:maven-compiler-plugin:3.8.1
>>> [WARNING]  * org.apache.maven.plugins:maven-clean-plugin:3.1.0
>>> [WARNING]  * org.apache.maven.plugins:maven-failsafe-plugin:2.22.1
>>> [WARNING]  * org.apache.royale.compiler:compiler-build-tools:1.2.1
>>> [WARNING]  * org.apache.maven.plugins:maven-surefire-plugin:2.22.1
>>> [WARNING]  * org.codehaus.mojo:animal-sniffer-maven-plugin:1.18
>>> [WARNING]  * org.apache.maven.plugins:maven-dependency-plugin:3.1.1
>>> [WARNING]  * org.apache.maven.plugins:maven-resources-plugin:3.1.0
>>> [WARNING]  *
>>> com.googlecode.maven-download-plugin:download-maven-plugin:1.5.0
>>> [WARNING]  * org.apache.maven.plugins:maven-install-plugin:2.5.2
>>> [WARNING]  * org.apache.maven.plugins:maven-site-plugin:3.8.2
>>> [WARNING]  * org.apache.maven.plugins:maven-remote-resources-plugin:1.7.0
>>> [WARNING]  * org.apache.maven.plugins:maven-enforcer-plugin:1.4.1
>>> [WARNING]  * org.apache.rat:apache-rat-plugin:0.13
>>> [WARNING]
>>> [WARNING] For more or less details, use 'maven.plugin.validation'
>> property
>>> with one of the values (case insensitive): [BRIEF, DEFAULT, VERBOSE]
>>> [WARNING]
>>> [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-antlr-plugin:2.0-beta-1:generate
>>> (generate-as-parser) on project compiler: Execution generate-as-parser of
>

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Greg Dove]

Sorry Team,

I was meaning to get to this, but have been crazy busy.  I will do better
next time.


On Tue, May 23, 2023 at 5:23 PM Yishay Weiss  wrote:

> Good point. I had in my head 4 votes at least were necessary, but 3 is
> enough.
> 
> From: Piotr Zarzycki 
> Sent: Monday, May 22, 2023 10:51 AM
> To: dev@royale.apache.org 
> Subject: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
>
> I believe we are good with this release ? Is there something which has to
> be done more ?
>
> śr., 17 maj 2023 o 12:16 Yishay Weiss  napisał(a):
>
> > What java version are you using? Try jdk 17/11/8.
> > 
> > From: Harbs 
> > Sent: Wednesday, May 17, 2023 12:03 PM
> > To: dev@royale.apache.org 
> > Subject: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
> >
> > I tried running this on my new computer and I’m getting errors with
> Maven:
> >
> > [INFO] Reactor Summary for Apache Royale: Compiler: Parent 0.9.10:
> > [INFO]
> > [INFO] Apache Royale: Compiler: Parent  SUCCESS [
> > 27.630 s]
> > [INFO] Apache Royale: Compiler: Compiler-Common ... SUCCESS [
> > 2.998 s]
> > [INFO] Apache Royale: Compiler: Test Utils  SUCCESS [
> > 0.542 s]
> > [INFO] Apache Royale: Compiler: Externc ... SUCCESS [
> > 10.956 s]
> > [INFO] Apache Royale: Compiler: playerglobal.swc support .. SUCCESS [
> > 0.756 s]
> > [INFO] Apache Royale: Compiler: Compiler .. FAILURE [
> > 5.699 s]
> > [INFO] Apache Royale: Compiler: Compiler-JX ... SKIPPED
> > [INFO] Apache Royale: Compiler: SWFUtils .. SKIPPED
> > [INFO] Apache Royale: Compiler: Debugger .. SKIPPED
> > [INFO] Apache Royale: Compiler: AS3/MXML Code Formatter ... SKIPPED
> > [INFO] Apache Royale: Compiler: AS3/MXML Code Linter .. SKIPPED
> > [INFO] Apache Royale: Compiler: OEM Layer . SKIPPED
> > [INFO] Apache Royale: Royale Ant Tasks  SKIPPED
> > [INFO] Apache Royale: RoyaleUnit Ant Tasks  SKIPPED
> > [INFO] Apache Royale: Royale Maven Plugin . SKIPPED
> > [INFO]
> > 
> > [INFO] BUILD FAILURE
> > [INFO]
> > 
> > [INFO] Total time:  48.749 s
> > [INFO] Finished at: 2023-05-17T11:22:53+03:00
> > [INFO]
> > 
> > [WARNING]
> > [WARNING] Plugin validation issues were detected in 17 plugin(s)
> > [WARNING]
> > [WARNING]  * org.jacoco:jacoco-maven-plugin:0.8.5
> > [WARNING]  * org.apache.maven.plugins:maven-jar-plugin:3.2.0
> > [WARNING]  * de.jflex:maven-jflex-plugin:1.4.3
> > [WARNING]  * org.apache.maven.plugins:maven-compiler-plugin:3.8.1
> > [WARNING]  * org.apache.maven.plugins:maven-clean-plugin:3.1.0
> > [WARNING]  * org.apache.maven.plugins:maven-failsafe-plugin:2.22.1
> > [WARNING]  * org.apache.royale.compiler:compiler-build-tools:1.2.1
> > [WARNING]  * org.apache.maven.plugins:maven-surefire-plugin:2.22.1
> > [WARNING]  * org.codehaus.mojo:animal-sniffer-maven-plugin:1.18
> > [WARNING]  * org.apache.maven.plugins:maven-dependency-plugin:3.1.1
> > [WARNING]  * org.apache.maven.plugins:maven-resources-plugin:3.1.0
> > [WARNING]  *
> > com.googlecode.maven-download-plugin:download-maven-plugin:1.5.0
> > [WARNING]  * org.apache.maven.plugins:maven-install-plugin:2.5.2
> > [WARNING]  * org.apache.maven.plugins:maven-site-plugin:3.8.2
> > [WARNING]  * org.apache.maven.plugins:maven-remote-resources-plugin:1.7.0
> > [WARNING]  * org.apache.maven.plugins:maven-enforcer-plugin:1.4.1
> > [WARNING]  * org.apache.rat:apache-rat-plugin:0.13
> > [WARNING]
> > [WARNING] For more or less details, use 'maven.plugin.validation'
> property
> > with one of the values (case insensitive): [BRIEF, DEFAULT, VERBOSE]
> > [WARNING]
> > [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-antlr-plugin:2.0-beta-1:generate
> > (generate-as-parser) on project compiler: Execution generate-as-parser of
> > goal org.apache.maven.plugins:maven-antlr-plugin:2.0-beta-1:generate
> > failed: The Security Manager is deprecated and will be removed in a
> future
> > release -> [Help 1]
> > [ERROR]
> > [ERROR] To see the full stack trace of the errors, re-run Maven with the
> > -e switch.
> > [ERROR] Re-run Maven using the -X switch to enable

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Yishay Weiss]

Good point. I had in my head 4 votes at least were necessary, but 3 is enough.

From: Piotr Zarzycki 
Sent: Monday, May 22, 2023 10:51 AM
To: dev@royale.apache.org 
Subject: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

I believe we are good with this release ? Is there something which has to
be done more ?

śr., 17 maj 2023 o 12:16 Yishay Weiss  napisał(a):

> What java version are you using? Try jdk 17/11/8.
> 
> From: Harbs 
> Sent: Wednesday, May 17, 2023 12:03 PM
> To: dev@royale.apache.org 
> Subject: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
>
> I tried running this on my new computer and I’m getting errors with Maven:
>
> [INFO] Reactor Summary for Apache Royale: Compiler: Parent 0.9.10:
> [INFO]
> [INFO] Apache Royale: Compiler: Parent  SUCCESS [
> 27.630 s]
> [INFO] Apache Royale: Compiler: Compiler-Common ... SUCCESS [
> 2.998 s]
> [INFO] Apache Royale: Compiler: Test Utils  SUCCESS [
> 0.542 s]
> [INFO] Apache Royale: Compiler: Externc ... SUCCESS [
> 10.956 s]
> [INFO] Apache Royale: Compiler: playerglobal.swc support .. SUCCESS [
> 0.756 s]
> [INFO] Apache Royale: Compiler: Compiler .. FAILURE [
> 5.699 s]
> [INFO] Apache Royale: Compiler: Compiler-JX ... SKIPPED
> [INFO] Apache Royale: Compiler: SWFUtils .. SKIPPED
> [INFO] Apache Royale: Compiler: Debugger .. SKIPPED
> [INFO] Apache Royale: Compiler: AS3/MXML Code Formatter ... SKIPPED
> [INFO] Apache Royale: Compiler: AS3/MXML Code Linter .. SKIPPED
> [INFO] Apache Royale: Compiler: OEM Layer . SKIPPED
> [INFO] Apache Royale: Royale Ant Tasks  SKIPPED
> [INFO] Apache Royale: RoyaleUnit Ant Tasks  SKIPPED
> [INFO] Apache Royale: Royale Maven Plugin . SKIPPED
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time:  48.749 s
> [INFO] Finished at: 2023-05-17T11:22:53+03:00
> [INFO]
> 
> [WARNING]
> [WARNING] Plugin validation issues were detected in 17 plugin(s)
> [WARNING]
> [WARNING]  * org.jacoco:jacoco-maven-plugin:0.8.5
> [WARNING]  * org.apache.maven.plugins:maven-jar-plugin:3.2.0
> [WARNING]  * de.jflex:maven-jflex-plugin:1.4.3
> [WARNING]  * org.apache.maven.plugins:maven-compiler-plugin:3.8.1
> [WARNING]  * org.apache.maven.plugins:maven-clean-plugin:3.1.0
> [WARNING]  * org.apache.maven.plugins:maven-failsafe-plugin:2.22.1
> [WARNING]  * org.apache.royale.compiler:compiler-build-tools:1.2.1
> [WARNING]  * org.apache.maven.plugins:maven-surefire-plugin:2.22.1
> [WARNING]  * org.codehaus.mojo:animal-sniffer-maven-plugin:1.18
> [WARNING]  * org.apache.maven.plugins:maven-dependency-plugin:3.1.1
> [WARNING]  * org.apache.maven.plugins:maven-resources-plugin:3.1.0
> [WARNING]  *
> com.googlecode.maven-download-plugin:download-maven-plugin:1.5.0
> [WARNING]  * org.apache.maven.plugins:maven-install-plugin:2.5.2
> [WARNING]  * org.apache.maven.plugins:maven-site-plugin:3.8.2
> [WARNING]  * org.apache.maven.plugins:maven-remote-resources-plugin:1.7.0
> [WARNING]  * org.apache.maven.plugins:maven-enforcer-plugin:1.4.1
> [WARNING]  * org.apache.rat:apache-rat-plugin:0.13
> [WARNING]
> [WARNING] For more or less details, use 'maven.plugin.validation' property
> with one of the values (case insensitive): [BRIEF, DEFAULT, VERBOSE]
> [WARNING]
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-antlr-plugin:2.0-beta-1:generate
> (generate-as-parser) on project compiler: Execution generate-as-parser of
> goal org.apache.maven.plugins:maven-antlr-plugin:2.0-beta-1:generate
> failed: The Security Manager is deprecated and will be removed in a future
> release -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn  -rf :compiler
>
>
> > On May 13, 2023, at 8:36 PM, Yishay Weiss 
> wrote:
> >
> > This is the discussion thread.
>
>

--

Piotr Zarzycki

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Piotr Zarzycki]

I believe we are good with this release ? Is there something which has to
be done more ?

śr., 17 maj 2023 o 12:16 Yishay Weiss  napisał(a):

> What java version are you using? Try jdk 17/11/8.
> 
> From: Harbs 
> Sent: Wednesday, May 17, 2023 12:03 PM
> To: dev@royale.apache.org 
> Subject: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
>
> I tried running this on my new computer and I’m getting errors with Maven:
>
> [INFO] Reactor Summary for Apache Royale: Compiler: Parent 0.9.10:
> [INFO]
> [INFO] Apache Royale: Compiler: Parent  SUCCESS [
> 27.630 s]
> [INFO] Apache Royale: Compiler: Compiler-Common ... SUCCESS [
> 2.998 s]
> [INFO] Apache Royale: Compiler: Test Utils  SUCCESS [
> 0.542 s]
> [INFO] Apache Royale: Compiler: Externc ... SUCCESS [
> 10.956 s]
> [INFO] Apache Royale: Compiler: playerglobal.swc support .. SUCCESS [
> 0.756 s]
> [INFO] Apache Royale: Compiler: Compiler .. FAILURE [
> 5.699 s]
> [INFO] Apache Royale: Compiler: Compiler-JX ... SKIPPED
> [INFO] Apache Royale: Compiler: SWFUtils .. SKIPPED
> [INFO] Apache Royale: Compiler: Debugger .. SKIPPED
> [INFO] Apache Royale: Compiler: AS3/MXML Code Formatter ... SKIPPED
> [INFO] Apache Royale: Compiler: AS3/MXML Code Linter .. SKIPPED
> [INFO] Apache Royale: Compiler: OEM Layer . SKIPPED
> [INFO] Apache Royale: Royale Ant Tasks  SKIPPED
> [INFO] Apache Royale: RoyaleUnit Ant Tasks  SKIPPED
> [INFO] Apache Royale: Royale Maven Plugin . SKIPPED
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time:  48.749 s
> [INFO] Finished at: 2023-05-17T11:22:53+03:00
> [INFO]
> 
> [WARNING]
> [WARNING] Plugin validation issues were detected in 17 plugin(s)
> [WARNING]
> [WARNING]  * org.jacoco:jacoco-maven-plugin:0.8.5
> [WARNING]  * org.apache.maven.plugins:maven-jar-plugin:3.2.0
> [WARNING]  * de.jflex:maven-jflex-plugin:1.4.3
> [WARNING]  * org.apache.maven.plugins:maven-compiler-plugin:3.8.1
> [WARNING]  * org.apache.maven.plugins:maven-clean-plugin:3.1.0
> [WARNING]  * org.apache.maven.plugins:maven-failsafe-plugin:2.22.1
> [WARNING]  * org.apache.royale.compiler:compiler-build-tools:1.2.1
> [WARNING]  * org.apache.maven.plugins:maven-surefire-plugin:2.22.1
> [WARNING]  * org.codehaus.mojo:animal-sniffer-maven-plugin:1.18
> [WARNING]  * org.apache.maven.plugins:maven-dependency-plugin:3.1.1
> [WARNING]  * org.apache.maven.plugins:maven-resources-plugin:3.1.0
> [WARNING]  *
> com.googlecode.maven-download-plugin:download-maven-plugin:1.5.0
> [WARNING]  * org.apache.maven.plugins:maven-install-plugin:2.5.2
> [WARNING]  * org.apache.maven.plugins:maven-site-plugin:3.8.2
> [WARNING]  * org.apache.maven.plugins:maven-remote-resources-plugin:1.7.0
> [WARNING]  * org.apache.maven.plugins:maven-enforcer-plugin:1.4.1
> [WARNING]  * org.apache.rat:apache-rat-plugin:0.13
> [WARNING]
> [WARNING] For more or less details, use 'maven.plugin.validation' property
> with one of the values (case insensitive): [BRIEF, DEFAULT, VERBOSE]
> [WARNING]
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-antlr-plugin:2.0-beta-1:generate
> (generate-as-parser) on project compiler: Execution generate-as-parser of
> goal org.apache.maven.plugins:maven-antlr-plugin:2.0-beta-1:generate
> failed: The Security Manager is deprecated and will be removed in a future
> release -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn  -rf :compiler
>
>
> > On May 13, 2023, at 8:36 PM, Yishay Weiss 
> wrote:
> >
> > This is the discussion thread.
>
>

-- 

Piotr Zarzycki

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Yishay Weiss]

What java version are you using? Try jdk 17/11/8.

From: Harbs 
Sent: Wednesday, May 17, 2023 12:03 PM
To: dev@royale.apache.org 
Subject: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

I tried running this on my new computer and I’m getting errors with Maven:

[INFO] Reactor Summary for Apache Royale: Compiler: Parent 0.9.10:
[INFO]
[INFO] Apache Royale: Compiler: Parent  SUCCESS [ 27.630 s]
[INFO] Apache Royale: Compiler: Compiler-Common ... SUCCESS [  2.998 s]
[INFO] Apache Royale: Compiler: Test Utils  SUCCESS [  0.542 s]
[INFO] Apache Royale: Compiler: Externc ... SUCCESS [ 10.956 s]
[INFO] Apache Royale: Compiler: playerglobal.swc support .. SUCCESS [  0.756 s]
[INFO] Apache Royale: Compiler: Compiler .. FAILURE [  5.699 s]
[INFO] Apache Royale: Compiler: Compiler-JX ... SKIPPED
[INFO] Apache Royale: Compiler: SWFUtils .. SKIPPED
[INFO] Apache Royale: Compiler: Debugger .. SKIPPED
[INFO] Apache Royale: Compiler: AS3/MXML Code Formatter ... SKIPPED
[INFO] Apache Royale: Compiler: AS3/MXML Code Linter .. SKIPPED
[INFO] Apache Royale: Compiler: OEM Layer . SKIPPED
[INFO] Apache Royale: Royale Ant Tasks  SKIPPED
[INFO] Apache Royale: RoyaleUnit Ant Tasks  SKIPPED
[INFO] Apache Royale: Royale Maven Plugin . SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time:  48.749 s
[INFO] Finished at: 2023-05-17T11:22:53+03:00
[INFO] 
[WARNING]
[WARNING] Plugin validation issues were detected in 17 plugin(s)
[WARNING]
[WARNING]  * org.jacoco:jacoco-maven-plugin:0.8.5
[WARNING]  * org.apache.maven.plugins:maven-jar-plugin:3.2.0
[WARNING]  * de.jflex:maven-jflex-plugin:1.4.3
[WARNING]  * org.apache.maven.plugins:maven-compiler-plugin:3.8.1
[WARNING]  * org.apache.maven.plugins:maven-clean-plugin:3.1.0
[WARNING]  * org.apache.maven.plugins:maven-failsafe-plugin:2.22.1
[WARNING]  * org.apache.royale.compiler:compiler-build-tools:1.2.1
[WARNING]  * org.apache.maven.plugins:maven-surefire-plugin:2.22.1
[WARNING]  * org.codehaus.mojo:animal-sniffer-maven-plugin:1.18
[WARNING]  * org.apache.maven.plugins:maven-dependency-plugin:3.1.1
[WARNING]  * org.apache.maven.plugins:maven-resources-plugin:3.1.0
[WARNING]  * com.googlecode.maven-download-plugin:download-maven-plugin:1.5.0
[WARNING]  * org.apache.maven.plugins:maven-install-plugin:2.5.2
[WARNING]  * org.apache.maven.plugins:maven-site-plugin:3.8.2
[WARNING]  * org.apache.maven.plugins:maven-remote-resources-plugin:1.7.0
[WARNING]  * org.apache.maven.plugins:maven-enforcer-plugin:1.4.1
[WARNING]  * org.apache.rat:apache-rat-plugin:0.13
[WARNING]
[WARNING] For more or less details, use 'maven.plugin.validation' property with 
one of the values (case insensitive): [BRIEF, DEFAULT, VERBOSE]
[WARNING]
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-antlr-plugin:2.0-beta-1:generate 
(generate-as-parser) on project compiler: Execution generate-as-parser of goal 
org.apache.maven.plugins:maven-antlr-plugin:2.0-beta-1:generate failed: The 
Security Manager is deprecated and will be removed in a future release -> [Help 
1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :compiler


> On May 13, 2023, at 8:36 PM, Yishay Weiss  wrote:
>
> This is the discussion thread.

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Harbs]

I tried running this on my new computer and I’m getting errors with Maven:

[INFO] Reactor Summary for Apache Royale: Compiler: Parent 0.9.10:
[INFO] 
[INFO] Apache Royale: Compiler: Parent  SUCCESS [ 27.630 s]
[INFO] Apache Royale: Compiler: Compiler-Common ... SUCCESS [  2.998 s]
[INFO] Apache Royale: Compiler: Test Utils  SUCCESS [  0.542 s]
[INFO] Apache Royale: Compiler: Externc ... SUCCESS [ 10.956 s]
[INFO] Apache Royale: Compiler: playerglobal.swc support .. SUCCESS [  0.756 s]
[INFO] Apache Royale: Compiler: Compiler .. FAILURE [  5.699 s]
[INFO] Apache Royale: Compiler: Compiler-JX ... SKIPPED
[INFO] Apache Royale: Compiler: SWFUtils .. SKIPPED
[INFO] Apache Royale: Compiler: Debugger .. SKIPPED
[INFO] Apache Royale: Compiler: AS3/MXML Code Formatter ... SKIPPED
[INFO] Apache Royale: Compiler: AS3/MXML Code Linter .. SKIPPED
[INFO] Apache Royale: Compiler: OEM Layer . SKIPPED
[INFO] Apache Royale: Royale Ant Tasks  SKIPPED
[INFO] Apache Royale: RoyaleUnit Ant Tasks  SKIPPED
[INFO] Apache Royale: Royale Maven Plugin . SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time:  48.749 s
[INFO] Finished at: 2023-05-17T11:22:53+03:00
[INFO] 
[WARNING] 
[WARNING] Plugin validation issues were detected in 17 plugin(s)
[WARNING] 
[WARNING]  * org.jacoco:jacoco-maven-plugin:0.8.5
[WARNING]  * org.apache.maven.plugins:maven-jar-plugin:3.2.0
[WARNING]  * de.jflex:maven-jflex-plugin:1.4.3
[WARNING]  * org.apache.maven.plugins:maven-compiler-plugin:3.8.1
[WARNING]  * org.apache.maven.plugins:maven-clean-plugin:3.1.0
[WARNING]  * org.apache.maven.plugins:maven-failsafe-plugin:2.22.1
[WARNING]  * org.apache.royale.compiler:compiler-build-tools:1.2.1
[WARNING]  * org.apache.maven.plugins:maven-surefire-plugin:2.22.1
[WARNING]  * org.codehaus.mojo:animal-sniffer-maven-plugin:1.18
[WARNING]  * org.apache.maven.plugins:maven-dependency-plugin:3.1.1
[WARNING]  * org.apache.maven.plugins:maven-resources-plugin:3.1.0
[WARNING]  * com.googlecode.maven-download-plugin:download-maven-plugin:1.5.0
[WARNING]  * org.apache.maven.plugins:maven-install-plugin:2.5.2
[WARNING]  * org.apache.maven.plugins:maven-site-plugin:3.8.2
[WARNING]  * org.apache.maven.plugins:maven-remote-resources-plugin:1.7.0
[WARNING]  * org.apache.maven.plugins:maven-enforcer-plugin:1.4.1
[WARNING]  * org.apache.rat:apache-rat-plugin:0.13
[WARNING] 
[WARNING] For more or less details, use 'maven.plugin.validation' property with 
one of the values (case insensitive): [BRIEF, DEFAULT, VERBOSE]
[WARNING] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-antlr-plugin:2.0-beta-1:generate 
(generate-as-parser) on project compiler: Execution generate-as-parser of goal 
org.apache.maven.plugins:maven-antlr-plugin:2.0-beta-1:generate failed: The 
Security Manager is deprecated and will be removed in a future release -> [Help 
1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :compiler


> On May 13, 2023, at 8:36 PM, Yishay Weiss  wrote:
> 
> This is the discussion thread.

RE: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Maria Jose Esteve]

Hahahahaha, thanks Yishay, those 40 minutes were ETERNAL 😝
Ok, now when I get back from dinner I will try it.

Hiedra

-Mensaje original-
De: Yishay Weiss  
Enviado el: martes, 16 de mayo de 2023 21:00
Para: dev@royale.apache.org
Asunto: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

First, to debug this you don't need to wait 40 minutes for the whole ant script 
to run before it fails. You can simply specify the offending target like so:

ant -f ApproveRoyale.xml build_maven -Drelease.version=0.9.10

One thing you can try is to set vmlauncher [1] to false in line 810



As I understand it, that should mimic you typing the command from the shell 
which seems to be successful for you.

[1] Exec Task (apache.org)<https://ant.apache.org/manual/Tasks/exec.html>

From: Maria Jose Esteve 
Sent: Tuesday, May 16, 2023 8:53 PM
To: dev@royale.apache.org 
Subject: RE: [DISCUSS] Release Apache Royale 0.9.10 RC4

Nothing, still with error [1]
- I have compiled with the call ant -v -e -f ApproveRoyale.xml 
-Drelease.version=0.9.10 -Drc=4 instruction.
- I modified the ApproveRoyale.xml file in two ways:
 * Putting blank space between the "-P" and the options.
 * By adding the -e -X parameters to the Maven compilation instructions.

Which " ' " are you referring to?

[1]
Current OS is Windows 10
Using input "Yes"
Executing 'mvn.cmd' with arguments:
'clean'
'-P option-with-swf'
'install'
'-e'
'-X'

The ' characters around the executable and arguments are not part of the 
command.
Exiting D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml.

BUILD FAILED
D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:798: The 
following error occurred while executing this line:
D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:811: exec 
returned: 1
at org.apache.tools.ant.taskdefs.ExecTask.runExecute(ExecTask.java:675)
at org.apache.tools.ant.taskdefs.ExecTask.runExec(ExecTask.java:699)
at org.apache.tools.ant.taskdefs.ExecTask.execute(ExecTask.java:527)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:299)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99)
at org.apache.tools.ant.Task.perform(Task.java:350)
at org.apache.tools.ant.Target.execute(Target.java:449)
at org.apache.tools.ant.Target.performTasks(Target.java:470)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1401)
at 
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:36)
at org.apache.tools.ant.Project.executeTargets(Project.java:1264)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:437)
at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:106)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:299)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99)
at org.apache.tools.ant.Task.perform(Task.java:350)
at org.apache.tools.ant.Target.execute(Target.java:449)
at org.apache.tools.ant.Target.performTasks(Target.java:470)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1401)
at org.apache.tools.ant.Project.executeTarget(Project.java:1374)
at 
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1264)
at org.apache.tools.ant.Main.runBuild(Main.java:818)
at org.apache.tools.ant.Main.startAnt(Main.java:223)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:284)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:101)

Total time: 38 minutes 41 seconds
D:\Develop_Royale\Projects\Royale-SDK\0.9.10

Hiedra

-Mensaje original-----
De: Maria Jose Esteve  Enviado el: martes, 16 de mayo de 
2023 18:48
Para: dev@royale.apache.org
Asunto: RE: [DISCUSS] Release Apache Royale 0.9.10 RC4

No, this was not... (I removed the -v ☹ option, I try again).

Hiedra

-Mensaje original-----
De: Maria Jose Esteve  Enviado el: martes, 16 de mayo de 
2023 18:08
Para: dev@royale.apache.org
Asunto: RE: [DISCUSS] Release Apache Royale 0.9.10 RC4

I ran ant with -v, as suggested by Yishay, and it gave me the error detail:

Current OS is Windows 10
 

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Yishay Weiss]

First, to debug this you don't need to wait 40 minutes for the whole ant script 
to run before it fails. You can simply specify the offending target like so:

ant -f ApproveRoyale.xml build_maven -Drelease.version=0.9.10

One thing you can try is to set vmlauncher [1] to false in line 810



As I understand it, that should mimic you typing the command from the shell 
which seems to be successful for you.

[1] Exec Task (apache.org)<https://ant.apache.org/manual/Tasks/exec.html>

From: Maria Jose Esteve 
Sent: Tuesday, May 16, 2023 8:53 PM
To: dev@royale.apache.org 
Subject: RE: [DISCUSS] Release Apache Royale 0.9.10 RC4

Nothing, still with error [1]
- I have compiled with the call ant -v -e -f ApproveRoyale.xml 
-Drelease.version=0.9.10 -Drc=4 instruction.
- I modified the ApproveRoyale.xml file in two ways:
 * Putting blank space between the "-P" and the options.
 * By adding the -e -X parameters to the Maven compilation instructions.

Which " ' " are you referring to?

[1]
Current OS is Windows 10
Using input "Yes"
Executing 'mvn.cmd' with arguments:
'clean'
'-P option-with-swf'
'install'
'-e'
'-X'

The ' characters around the executable and arguments are
not part of the command.
Exiting D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml.

BUILD FAILED
D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:798: The 
following error occurred while executing this line:
D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:811: exec 
returned: 1
at org.apache.tools.ant.taskdefs.ExecTask.runExecute(ExecTask.java:675)
at org.apache.tools.ant.taskdefs.ExecTask.runExec(ExecTask.java:699)
at org.apache.tools.ant.taskdefs.ExecTask.execute(ExecTask.java:527)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:299)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99)
at org.apache.tools.ant.Task.perform(Task.java:350)
at org.apache.tools.ant.Target.execute(Target.java:449)
at org.apache.tools.ant.Target.performTasks(Target.java:470)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1401)
at 
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:36)
at org.apache.tools.ant.Project.executeTargets(Project.java:1264)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:437)
at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:106)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:299)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99)
at org.apache.tools.ant.Task.perform(Task.java:350)
at org.apache.tools.ant.Target.execute(Target.java:449)
at org.apache.tools.ant.Target.performTasks(Target.java:470)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1401)
at org.apache.tools.ant.Project.executeTarget(Project.java:1374)
at 
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1264)
at org.apache.tools.ant.Main.runBuild(Main.java:818)
at org.apache.tools.ant.Main.startAnt(Main.java:223)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:284)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:101)

Total time: 38 minutes 41 seconds
D:\Develop_Royale\Projects\Royale-SDK\0.9.10

Hiedra

-Mensaje original-----
De: Maria Jose Esteve 
Enviado el: martes, 16 de mayo de 2023 18:48
Para: dev@royale.apache.org
Asunto: RE: [DISCUSS] Release Apache Royale 0.9.10 RC4

No, this was not... (I removed the -v ☹ option, I try again).

Hiedra

-Mensaje original-----
De: Maria Jose Esteve  Enviado el: martes, 16 de mayo de 
2023 18:08
Para: dev@royale.apache.org
Asunto: RE: [DISCUSS] Release Apache Royale 0.9.10 RC4

I ran ant with -v, as suggested by Yishay, and it gave me the error detail:

Current OS is Windows 10
Using input "Yes"
Executing 'mvn.cmd' with arguments:
'clean'
'-Poption-with-swf'
'install'

The ' characters around the executable and arguments are not part of 
the command.
Exiting D:\Deve

RE: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Maria Jose Esteve]

Nothing, still with error [1]
- I have compiled with the call ant -v -e -f ApproveRoyale.xml 
-Drelease.version=0.9.10 -Drc=4 instruction.
- I modified the ApproveRoyale.xml file in two ways:
 * Putting blank space between the "-P" and the options.
 * By adding the -e -X parameters to the Maven compilation instructions.

Which " ' " are you referring to?

[1]
Current OS is Windows 10
Using input "Yes"
Executing 'mvn.cmd' with arguments:
'clean'
'-P option-with-swf'
'install'
'-e'
'-X'

The ' characters around the executable and arguments are
not part of the command.
Exiting D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml.

BUILD FAILED
D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:798: The 
following error occurred while executing this line:
D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:811: exec 
returned: 1
at org.apache.tools.ant.taskdefs.ExecTask.runExecute(ExecTask.java:675)
at org.apache.tools.ant.taskdefs.ExecTask.runExec(ExecTask.java:699)
at org.apache.tools.ant.taskdefs.ExecTask.execute(ExecTask.java:527)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:299)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99)
at org.apache.tools.ant.Task.perform(Task.java:350)
at org.apache.tools.ant.Target.execute(Target.java:449)
at org.apache.tools.ant.Target.performTasks(Target.java:470)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1401)
at 
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:36)
at org.apache.tools.ant.Project.executeTargets(Project.java:1264)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:437)
at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:106)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:299)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99)
at org.apache.tools.ant.Task.perform(Task.java:350)
at org.apache.tools.ant.Target.execute(Target.java:449)
at org.apache.tools.ant.Target.performTasks(Target.java:470)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1401)
at org.apache.tools.ant.Project.executeTarget(Project.java:1374)
at 
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1264)
at org.apache.tools.ant.Main.runBuild(Main.java:818)
at org.apache.tools.ant.Main.startAnt(Main.java:223)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:284)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:101)

Total time: 38 minutes 41 seconds
D:\Develop_Royale\Projects\Royale-SDK\0.9.10

Hiedra

-Mensaje original-
De: Maria Jose Esteve  
Enviado el: martes, 16 de mayo de 2023 18:48
Para: dev@royale.apache.org
Asunto: RE: [DISCUSS] Release Apache Royale 0.9.10 RC4

No, this was not... (I removed the -v ☹ option, I try again).

Hiedra

-Mensaje original-
De: Maria Jose Esteve  Enviado el: martes, 16 de mayo de 
2023 18:08
Para: dev@royale.apache.org
Asunto: RE: [DISCUSS] Release Apache Royale 0.9.10 RC4

I ran ant with -v, as suggested by Yishay, and it gave me the error detail:

Current OS is Windows 10
Using input "Yes"
Executing 'mvn.cmd' with arguments:
'clean'
'-Poption-with-swf'
'install'

The ' characters around the executable and arguments are not part of 
the command.
Exiting D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml.

I remember once I had this problem because a "blank space" was expected between 
"P" and "option-with-swf"
I have included a blank space in all entries and relaunched the compilation [1].

[1] 
https://drive.google.com/file/d/1FyboL0f4NnQswrfkEyk43TeFIpuPX9x9/view?usp=sharing

I have launched the compilation, I will come back here with the result.

Hiedra.

-Mensaje original-
De: Maria Jose Esteve  Enviado el: martes, 16 de mayo de 
2023 14:06
Para: dev@royale.apache.org
Asunto: RE: [DISCUSS] Release Apache Royale 0.9.10 RC4


>Can you say whether you are using mvn or mvn.cm

RE: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Maria Jose Esteve]

No, this was not... (I removed the -v ☹ option, I try again).

Hiedra

-Mensaje original-
De: Maria Jose Esteve  
Enviado el: martes, 16 de mayo de 2023 18:08
Para: dev@royale.apache.org
Asunto: RE: [DISCUSS] Release Apache Royale 0.9.10 RC4

I ran ant with -v, as suggested by Yishay, and it gave me the error detail:

Current OS is Windows 10
Using input "Yes"
Executing 'mvn.cmd' with arguments:
'clean'
'-Poption-with-swf'
'install'

The ' characters around the executable and arguments are not part of 
the command.
Exiting D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml.

I remember once I had this problem because a "blank space" was expected between 
"P" and "option-with-swf"
I have included a blank space in all entries and relaunched the compilation [1].

[1] 
https://drive.google.com/file/d/1FyboL0f4NnQswrfkEyk43TeFIpuPX9x9/view?usp=sharing

I have launched the compilation, I will come back here with the result.

Hiedra.

-Mensaje original-
De: Maria Jose Esteve  Enviado el: martes, 16 de mayo de 
2023 14:06
Para: dev@royale.apache.org
Asunto: RE: [DISCUSS] Release Apache Royale 0.9.10 RC4


>Can you say whether you are using mvn or mvn.cmd in normal mvn builds (you can 
>check by running where mvn in cmd).

Yes, I did, and everywhere I found it specified "mvn.cmd" and I have no 
problem, it is with this script, and I don't know why.

> You can also set ant -v for verbose mode and see if that helps to diagnose 
> the problem.

Ok, I'll give it a try and get back to you with the results.

Thx Yishay.

Hiedra

-Mensaje original-----
De: Yishay Weiss  Enviado el: martes, 16 de mayo de 
2023 12:39
Para: dev@royale.apache.org
Asunto: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

Can you say whether you are using mvn or mvn.cmd in normal mvn builds (you can 
check by running where mvn in cmd). If it's mvn then you can try to simply 
remove lines 72-74 altogether. On my machine both mvn.cmd and mvn seem to work, 
although it's a windows machine and supposedly mvn isn't guaranteed to work on 
windows.

You can also set ant -v for verbose mode and see if that helps to diagnose the 
problem.
________________
From: Maria Jose Esteve 
Sent: Tuesday, May 16, 2023 5:15 AM
To: dev@royale.apache.org 
Subject: RE: [DISCUSS] Release Apache Royale 0.9.10 RC4

I don't have mvn.exe in the /bin directory of Maven... but I tried it and it 
didn't work.
I have restored mvn.cmd (this file does exist) in ApproveRoyale.xml I modified 
my build bat and manually set MAVEN_HOME, in case the system variable was 
getting lost, but the result was the same.
The last test was to put MAVEN_HOME in first position in the path, also, same 
error.

I have run out of ideas ☹

Hiedra

-Mensaje original-
De: Josh Tynjala  Enviado el: lunes, 15 de mayo de 
2023 23:20
Para: dev@royale.apache.org
Asunto: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

It seems to be failing when running Maven, but it's not giving you an error 
message to explain what the issue is.

I see that you're on Windows. I wonder if you're having a similar issue that I 
had on a previous release of the Royale build tools (I was on Windows at the 
time, but I'm on macOS these days):

https://lists.apache.org/thread/4fw80rsr87h79tofzsfs908plvfghvd4

In this case, a similar workaround would be to change mvn.cmd to mvn.exe on 
line 72 of ApproveRoyale.xml





--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>


On Mon, May 15, 2023 at 2:08 PM Maria Jose Esteve  wrote:

> It has no longer included it as unapproved, but I still can't finish 
> the Maven compilation, same problem but I don't know why, it's in the 
> path. (I can compile the SDK normally with ant and with mvn and it 
> hasn't given me any problems).
> any idea?
> ---
> main:
>
> build_maven:
> Path is C:\Program Files (x86)\Common
> Files\Oracle\Java\javapath;D:\Apache;C:\Program
> Files\Java\jdk1.8.0_281\bin;D:\Apache\apache-ant-1.10.13\bin;D:\Apache
> \apache-maven-3.9.1\bin;D:\app\client\hiedra\product\19.0.0\client_1\b
> in;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\
> System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Progr
> am Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program
> Files\dotnet\;C:\Program
> Files\Git\cmd;C:\Users\hiedra\AppData\Local\Programs\Microsoft VS 
> Code;C:\Program Files\Microsoft SQL Server\Client 
> SDK\ODBC\170\Tools\Binn\;C:\Program
> Files\PowerShell\7-preview\preview;C:\Program Files 
> (x86)\Yarn\bin\;D:\Apache\HaxeToolkit\haxe;D:\Apache\HaxeToolkit\neko;
> C:\Program Files\nodejs\;C:\Progra

RE: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Maria Jose Esteve]

I ran ant with -v, as suggested by Yishay, and it gave me the error detail:

Current OS is Windows 10
Using input "Yes"
Executing 'mvn.cmd' with arguments:
'clean'
'-Poption-with-swf'
'install'

The ' characters around the executable and arguments are not part of 
the command.
Exiting D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml.

I remember once I had this problem because a "blank space" was expected between 
"P" and "option-with-swf"
I have included a blank space in all entries and relaunched the compilation [1].

[1] 
https://drive.google.com/file/d/1FyboL0f4NnQswrfkEyk43TeFIpuPX9x9/view?usp=sharing

I have launched the compilation, I will come back here with the result.

Hiedra.

-Mensaje original-
De: Maria Jose Esteve  
Enviado el: martes, 16 de mayo de 2023 14:06
Para: dev@royale.apache.org
Asunto: RE: [DISCUSS] Release Apache Royale 0.9.10 RC4


>Can you say whether you are using mvn or mvn.cmd in normal mvn builds (you can 
>check by running where mvn in cmd).

Yes, I did, and everywhere I found it specified "mvn.cmd" and I have no 
problem, it is with this script, and I don't know why.

> You can also set ant -v for verbose mode and see if that helps to diagnose 
> the problem.

Ok, I'll give it a try and get back to you with the results.

Thx Yishay.

Hiedra

-Mensaje original-----
De: Yishay Weiss  Enviado el: martes, 16 de mayo de 
2023 12:39
Para: dev@royale.apache.org
Asunto: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

Can you say whether you are using mvn or mvn.cmd in normal mvn builds (you can 
check by running where mvn in cmd). If it's mvn then you can try to simply 
remove lines 72-74 altogether. On my machine both mvn.cmd and mvn seem to work, 
although it's a windows machine and supposedly mvn isn't guaranteed to work on 
windows.

You can also set ant -v for verbose mode and see if that helps to diagnose the 
problem.
________________
From: Maria Jose Esteve 
Sent: Tuesday, May 16, 2023 5:15 AM
To: dev@royale.apache.org 
Subject: RE: [DISCUSS] Release Apache Royale 0.9.10 RC4

I don't have mvn.exe in the /bin directory of Maven... but I tried it and it 
didn't work.
I have restored mvn.cmd (this file does exist) in ApproveRoyale.xml I modified 
my build bat and manually set MAVEN_HOME, in case the system variable was 
getting lost, but the result was the same.
The last test was to put MAVEN_HOME in first position in the path, also, same 
error.

I have run out of ideas ☹

Hiedra

-Mensaje original-
De: Josh Tynjala  Enviado el: lunes, 15 de mayo de 
2023 23:20
Para: dev@royale.apache.org
Asunto: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

It seems to be failing when running Maven, but it's not giving you an error 
message to explain what the issue is.

I see that you're on Windows. I wonder if you're having a similar issue that I 
had on a previous release of the Royale build tools (I was on Windows at the 
time, but I'm on macOS these days):

https://lists.apache.org/thread/4fw80rsr87h79tofzsfs908plvfghvd4

In this case, a similar workaround would be to change mvn.cmd to mvn.exe on 
line 72 of ApproveRoyale.xml





--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>


On Mon, May 15, 2023 at 2:08 PM Maria Jose Esteve  wrote:

> It has no longer included it as unapproved, but I still can't finish 
> the Maven compilation, same problem but I don't know why, it's in the 
> path. (I can compile the SDK normally with ant and with mvn and it 
> hasn't given me any problems).
> any idea?
> ---
> main:
>
> build_maven:
> Path is C:\Program Files (x86)\Common
> Files\Oracle\Java\javapath;D:\Apache;C:\Program
> Files\Java\jdk1.8.0_281\bin;D:\Apache\apache-ant-1.10.13\bin;D:\Apache
> \apache-maven-3.9.1\bin;D:\app\client\hiedra\product\19.0.0\client_1\b
> in;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\
> System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Progr
> am Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program
> Files\dotnet\;C:\Program
> Files\Git\cmd;C:\Users\hiedra\AppData\Local\Programs\Microsoft VS 
> Code;C:\Program Files\Microsoft SQL Server\Client 
> SDK\ODBC\170\Tools\Binn\;C:\Program
> Files\PowerShell\7-preview\preview;C:\Program Files 
> (x86)\Yarn\bin\;D:\Apache\HaxeToolkit\haxe;D:\Apache\HaxeToolkit\neko;
> C:\Program Files\nodejs\;C:\Program Files (x86)\Intel\Intel(R) 
> Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) 
> Management Engine Components\DAL;C:\Program Files (x86)\Pulse 
> Secure\VC142.CRT\X64\;C:\Program Files (x86)\Pulse 
> Secure\VC142.CRT\X86

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Josh Tynjala]

You could try adding -e or -X to the mvn command args. That should make
Maven display more details about errors.








--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>


On Mon, May 15, 2023 at 7:16 PM Maria Jose Esteve  wrote:

> I don't have mvn.exe in the /bin directory of Maven... but I tried it and
> it didn't work.
> I have restored mvn.cmd (this file does exist) in ApproveRoyale.xml
> I modified my build bat and manually set MAVEN_HOME, in case the system
> variable was getting lost, but the result was the same.
> The last test was to put MAVEN_HOME in first position in the path, also,
> same error.
>
> I have run out of ideas ☹
>
> Hiedra
>
> -Mensaje original-
> De: Josh Tynjala 
> Enviado el: lunes, 15 de mayo de 2023 23:20
> Para: dev@royale.apache.org
> Asunto: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
>
> It seems to be failing when running Maven, but it's not giving you an
> error message to explain what the issue is.
>
> I see that you're on Windows. I wonder if you're having a similar issue
> that I had on a previous release of the Royale build tools (I was on
> Windows at the time, but I'm on macOS these days):
>
> https://lists.apache.org/thread/4fw80rsr87h79tofzsfs908plvfghvd4
>
> In this case, a similar workaround would be to change mvn.cmd to mvn.exe
> on line 72 of ApproveRoyale.xml
>
> 
> 
> 
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Mon, May 15, 2023 at 2:08 PM Maria Jose Esteve 
> wrote:
>
> > It has no longer included it as unapproved, but I still can't finish
> > the Maven compilation, same problem but I don't know why, it's in the
> > path. (I can compile the SDK normally with ant and with mvn and it
> > hasn't given me any problems).
> > any idea?
> > ---
> > main:
> >
> > build_maven:
> > Path is C:\Program Files (x86)\Common
> > Files\Oracle\Java\javapath;D:\Apache;C:\Program
> > Files\Java\jdk1.8.0_281\bin;D:\Apache\apache-ant-1.10.13\bin;D:\Apache
> > \apache-maven-3.9.1\bin;D:\app\client\hiedra\product\19.0.0\client_1\b
> > in;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\
> > System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Progr
> > am Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program
> > Files\dotnet\;C:\Program
> > Files\Git\cmd;C:\Users\hiedra\AppData\Local\Programs\Microsoft VS
> > Code;C:\Program Files\Microsoft SQL Server\Client
> > SDK\ODBC\170\Tools\Binn\;C:\Program
> > Files\PowerShell\7-preview\preview;C:\Program Files
> > (x86)\Yarn\bin\;D:\Apache\HaxeToolkit\haxe;D:\Apache\HaxeToolkit\neko;
> > C:\Program Files\nodejs\;C:\Program Files (x86)\Intel\Intel(R)
> > Management Engine Components\DAL;C:\Program Files\Intel\Intel(R)
> > Management Engine Components\DAL;C:\Program Files (x86)\Pulse
> > Secure\VC142.CRT\X64\;C:\Program Files (x86)\Pulse
> > Secure\VC142.CRT\X86\;C:\Program Files\Microsoft SQL
> > Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL
> > Server\130\Tools\Binn\;C:\Program Files
> > (x86)\GnuPG\bin;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:
> > \Users\hiedra\AppData\Local\GitHubDesktop\bin;C:\Users\hiedra\.dotnet\
> > tools;C:\Users\hiedra\AppData\Local\Programs\Microsoft
> > VS
> > Code\bin;C:\Users\hiedra\AppData\Local\Yarn\bin;C:\Users\hiedra\AppDat
> > a\Roaming\npm;C:\Program
> > Files\Microsoft Office\root\Client
> >
> > BUILD FAILED
> > D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:798:
> > The following error occurred while executing this line:
> > D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:811:
> > exec
> > returned: 1
> >
> > Total time: 37 minutes 10 seconds
> >
> > --
> > --
> >
> > Hiedra
> >
> > -Mensaje original-
> > De: Josh Tynjala  Enviado el: lunes, 15 de
> > mayo de 2023 22:16
> > Para: dev@royale.apache.org
> > Asunto: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
> >
> > Yes, as I said, "You should be able to use it with this existing RC,
> > if you'd like."
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC <https://bowlerhat.dev>
> >
> >
> > On Mon, May 15, 2023 at 1:15 PM Maria Jose Esteve 
> > wrote:
> >
> > > can I test this "ApproveRoyale.xml" with RC4 Josh?
> > > Hiedra
> > >

RE: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Maria Jose Esteve]

>Can you say whether you are using mvn or mvn.cmd in normal mvn builds (you can 
>check by running where mvn in cmd).

Yes, I did, and everywhere I found it specified "mvn.cmd" and I have no 
problem, it is with this script, and I don't know why.

> You can also set ant -v for verbose mode and see if that helps to diagnose 
> the problem.

Ok, I'll give it a try and get back to you with the results.

Thx Yishay.

Hiedra

-Mensaje original-
De: Yishay Weiss  
Enviado el: martes, 16 de mayo de 2023 12:39
Para: dev@royale.apache.org
Asunto: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

Can you say whether you are using mvn or mvn.cmd in normal mvn builds (you can 
check by running where mvn in cmd). If it's mvn then you can try to simply 
remove lines 72-74 altogether. On my machine both mvn.cmd and mvn seem to work, 
although it's a windows machine and supposedly mvn isn't guaranteed to work on 
windows.

You can also set ant -v for verbose mode and see if that helps to diagnose the 
problem.

From: Maria Jose Esteve 
Sent: Tuesday, May 16, 2023 5:15 AM
To: dev@royale.apache.org 
Subject: RE: [DISCUSS] Release Apache Royale 0.9.10 RC4

I don't have mvn.exe in the /bin directory of Maven... but I tried it and it 
didn't work.
I have restored mvn.cmd (this file does exist) in ApproveRoyale.xml I modified 
my build bat and manually set MAVEN_HOME, in case the system variable was 
getting lost, but the result was the same.
The last test was to put MAVEN_HOME in first position in the path, also, same 
error.

I have run out of ideas ☹

Hiedra

-Mensaje original-
De: Josh Tynjala  Enviado el: lunes, 15 de mayo de 
2023 23:20
Para: dev@royale.apache.org
Asunto: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

It seems to be failing when running Maven, but it's not giving you an error 
message to explain what the issue is.

I see that you're on Windows. I wonder if you're having a similar issue that I 
had on a previous release of the Royale build tools (I was on Windows at the 
time, but I'm on macOS these days):

https://lists.apache.org/thread/4fw80rsr87h79tofzsfs908plvfghvd4

In this case, a similar workaround would be to change mvn.cmd to mvn.exe on 
line 72 of ApproveRoyale.xml





--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>


On Mon, May 15, 2023 at 2:08 PM Maria Jose Esteve  wrote:

> It has no longer included it as unapproved, but I still can't finish 
> the Maven compilation, same problem but I don't know why, it's in the 
> path. (I can compile the SDK normally with ant and with mvn and it 
> hasn't given me any problems).
> any idea?
> ---
> main:
>
> build_maven:
> Path is C:\Program Files (x86)\Common
> Files\Oracle\Java\javapath;D:\Apache;C:\Program
> Files\Java\jdk1.8.0_281\bin;D:\Apache\apache-ant-1.10.13\bin;D:\Apache
> \apache-maven-3.9.1\bin;D:\app\client\hiedra\product\19.0.0\client_1\b
> in;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\
> System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Progr
> am Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program
> Files\dotnet\;C:\Program
> Files\Git\cmd;C:\Users\hiedra\AppData\Local\Programs\Microsoft VS 
> Code;C:\Program Files\Microsoft SQL Server\Client 
> SDK\ODBC\170\Tools\Binn\;C:\Program
> Files\PowerShell\7-preview\preview;C:\Program Files 
> (x86)\Yarn\bin\;D:\Apache\HaxeToolkit\haxe;D:\Apache\HaxeToolkit\neko;
> C:\Program Files\nodejs\;C:\Program Files (x86)\Intel\Intel(R) 
> Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) 
> Management Engine Components\DAL;C:\Program Files (x86)\Pulse 
> Secure\VC142.CRT\X64\;C:\Program Files (x86)\Pulse 
> Secure\VC142.CRT\X86\;C:\Program Files\Microsoft SQL 
> Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL 
> Server\130\Tools\Binn\;C:\Program Files
> (x86)\GnuPG\bin;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:
> \Users\hiedra\AppData\Local\GitHubDesktop\bin;C:\Users\hiedra\.dotnet\
> tools;C:\Users\hiedra\AppData\Local\Programs\Microsoft
> VS
> Code\bin;C:\Users\hiedra\AppData\Local\Yarn\bin;C:\Users\hiedra\AppDat
> a\Roaming\npm;C:\Program
> Files\Microsoft Office\root\Client
>
> BUILD FAILED
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:798:
> The following error occurred while executing this line:
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:811:
> exec
> returned: 1
>
> Total time: 37 minutes 10 seconds
>
> ------------------
> --
>
> Hiedra
>
> -Mensaje original-
> De: Josh Tynjala  Enviado el: lunes, 15 de 
> mayo de 2023 22:16
> Para: dev

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Piotr Zarzycki]

Josh,

Thank you so much for such detailed analysis of my issue. I will look into
potential solution. I agree it is not a blocker.

Piotr

pon., 15 maj 2023 o 23:05 Josh Tynjala 
napisał(a):

> Based on some further investigation, it looks like the Royale compiler
> knows how to implement the JS IEventDispatcher API in generated .js files
> only. When those .js files are included in a SWC file, the binary part of
> the SWC file that is used for type checking and IDE support will always be
> generated with the SWF IEventDispatcher API. That's where the conflict
> comes from.
>
> This does not appear to me to be a regression, but how it has always
> worked. We may want to provide a way to generate both APIs in SWC binary
> code, but I would say that's for a future release.
>
> In Royale framework code, it looks like there are two ways to manually
> handle bindable beads.
>
> 1) Extend DispatcherBead. It looks like a lot of bead classes do this.
>
> 2) Manually implement IEventDispatcher, with the different signatures
> conditionally compiled with COMPILE::SWF and COMPILE::JS. This is much less
> common, but it is used in a couple of places.
>
> In both cases, the compiler won't generate any IEventDispatcher code for
> bindable properties because the beads will already be event dispatchers.
>
> The first option is most common, but not always possible when another is
> superclass already being used. The second option where the interface is
> manually implemented happens in these two bead:
>
> a) In Jewel, a manual IEventDispatcher implementation is used in
> ArrayListSelectionModel.
> b) In Spark, a manual implementation is used in LayoutBase.
>
> In the case of Jewel's TileHorizontalLayout, if you wanted to avoid
> manually implementing IEventDispatcher, the Core version of LayoutBase
> would need to extend DispatcherBead. However, I don't think this would be
> considered PAYG, which Core is expected to follow more strictly than Jewel,
> so there's no way to use DispatcherBead with Jewel's TileHorizontalLayout.
> TileHorizontalLayout probably needs a manual implementation of
> IEventDispatcher. Or possibly SimpleHorizontalLayout or StyledLayoutBase
> instead, depending on how strict you want to be with PAYG in Jewel. For the
> least impact and most PAYG, you should manually implement IEventDispatcher
> directly on TileHorizontalLayout.
>
> (In my opinion, this is not a release blocker. I'm just letting you know
> what I found in my investigation, and my advice for fixing it.)
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>
>
> On Mon, May 15, 2023 at 1:13 PM Josh Tynjala 
> wrote:
>
> > > Does anyone have any idea what has happened here ? Why
> > TileHorizontalLayout
> > > after compilation to TileHorizontalLayout.js have all of these methods
> ?
> >
> > TileHorizontallayout has [Bindable] metadata on some properties. If
> > anything in a class is marked as [Bindable], and that class (or a
> > superclass) does not already extend EventDispatcher (or implement
> > IEventDispatcher), the compiler will automatically generate an
> > implementation of IEventDispatcher. This is true in Royale, and it was
> also
> > true in Flex.
> >
> > Here are the classes that TileHorizontalLayout is a subclass of:
> > TileHorizontalLayout extends SimpleHorizontalLayout extends
> > StyledLayoutBase extends LayoutBase extends Bead
> >
> > There are also the following interfaces in the type hierarchy:
> > ILayoutStyleProperties, IBeadLayout, IBead
> >
> > Nowhere in this chain of classes is there an EventDispatcher or
> > IEventDispatcher. So the compiler is generating its own implementation of
> > IEventDispatcher.
> >
> > Unfortunately, it seems to be generating an implementation of the methods
> > from the SWF version of IEventDispatcher instead of the methods from the
> JS
> > version of IEventDispatcher. I don't believe that I have worked with the
> > part of the Royale compiler that generates code for bindable
> > classes/properties before, so I don't know why it would be doing that.
> > However, that seems like a bug. Maybe not necessarily in the compiler. It
> > could be that the compiler options used by the JewelJS build are wrong.
> >
> > Note: I don't think that the compiler is incorrectly using the Spark
> > version of LayoutBase instead of the Core version of LayoutBase. This can
> > be explained without the Spark version of LayoutBase being involved in
> any
> > way.
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC 
> >
> >
> > On Mon, May 15, 2023 at 5:14 AM Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> > wrote:
> >
> >> Hi Guys,
> >>
> >> I have voted +1, but I have found one issue which concerns me a little
> >> bit.
> >> I have need of usage in my application
> >> -> org.apache.royale.jewel.beads.layouts.TileHorizontalLayout. I have
> made
> >> my own custom class which extends that one. To my big surprise I got
> >> following compilation error:
> >>
> >>  Error: interface me

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Yishay Weiss]

Can you say whether you are using mvn or mvn.cmd in normal mvn builds (you can 
check by running where mvn in cmd). If it's mvn then you can try to simply 
remove lines 72-74 altogether. On my machine both mvn.cmd and mvn seem to work, 
although it's a windows machine and supposedly mvn isn't guaranteed to work on 
windows.

You can also set ant -v for verbose mode and see if that helps to diagnose the 
problem.

From: Maria Jose Esteve 
Sent: Tuesday, May 16, 2023 5:15 AM
To: dev@royale.apache.org 
Subject: RE: [DISCUSS] Release Apache Royale 0.9.10 RC4

I don't have mvn.exe in the /bin directory of Maven... but I tried it and it 
didn't work.
I have restored mvn.cmd (this file does exist) in ApproveRoyale.xml
I modified my build bat and manually set MAVEN_HOME, in case the system 
variable was getting lost, but the result was the same.
The last test was to put MAVEN_HOME in first position in the path, also, same 
error.

I have run out of ideas ☹

Hiedra

-Mensaje original-
De: Josh Tynjala 
Enviado el: lunes, 15 de mayo de 2023 23:20
Para: dev@royale.apache.org
Asunto: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

It seems to be failing when running Maven, but it's not giving you an error 
message to explain what the issue is.

I see that you're on Windows. I wonder if you're having a similar issue that I 
had on a previous release of the Royale build tools (I was on Windows at the 
time, but I'm on macOS these days):

https://lists.apache.org/thread/4fw80rsr87h79tofzsfs908plvfghvd4

In this case, a similar workaround would be to change mvn.cmd to mvn.exe on 
line 72 of ApproveRoyale.xml





--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>


On Mon, May 15, 2023 at 2:08 PM Maria Jose Esteve  wrote:

> It has no longer included it as unapproved, but I still can't finish
> the Maven compilation, same problem but I don't know why, it's in the
> path. (I can compile the SDK normally with ant and with mvn and it
> hasn't given me any problems).
> any idea?
> ---
> main:
>
> build_maven:
> Path is C:\Program Files (x86)\Common
> Files\Oracle\Java\javapath;D:\Apache;C:\Program
> Files\Java\jdk1.8.0_281\bin;D:\Apache\apache-ant-1.10.13\bin;D:\Apache
> \apache-maven-3.9.1\bin;D:\app\client\hiedra\product\19.0.0\client_1\b
> in;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\
> System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Progr
> am Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program
> Files\dotnet\;C:\Program
> Files\Git\cmd;C:\Users\hiedra\AppData\Local\Programs\Microsoft VS
> Code;C:\Program Files\Microsoft SQL Server\Client
> SDK\ODBC\170\Tools\Binn\;C:\Program
> Files\PowerShell\7-preview\preview;C:\Program Files
> (x86)\Yarn\bin\;D:\Apache\HaxeToolkit\haxe;D:\Apache\HaxeToolkit\neko;
> C:\Program Files\nodejs\;C:\Program Files (x86)\Intel\Intel(R)
> Management Engine Components\DAL;C:\Program Files\Intel\Intel(R)
> Management Engine Components\DAL;C:\Program Files (x86)\Pulse
> Secure\VC142.CRT\X64\;C:\Program Files (x86)\Pulse
> Secure\VC142.CRT\X86\;C:\Program Files\Microsoft SQL
> Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL
> Server\130\Tools\Binn\;C:\Program Files
> (x86)\GnuPG\bin;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:
> \Users\hiedra\AppData\Local\GitHubDesktop\bin;C:\Users\hiedra\.dotnet\
> tools;C:\Users\hiedra\AppData\Local\Programs\Microsoft
> VS
> Code\bin;C:\Users\hiedra\AppData\Local\Yarn\bin;C:\Users\hiedra\AppDat
> a\Roaming\npm;C:\Program
> Files\Microsoft Office\root\Client
>
> BUILD FAILED
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:798:
> The following error occurred while executing this line:
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:811:
> exec
> returned: 1
>
> Total time: 37 minutes 10 seconds
>
> --------------------------
> --
>
> Hiedra
>
> -Mensaje original-
> De: Josh Tynjala  Enviado el: lunes, 15 de
> mayo de 2023 22:16
> Para: dev@royale.apache.org
> Asunto: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
>
> Yes, as I said, "You should be able to use it with this existing RC,
> if you'd like."
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Mon, May 15, 2023 at 1:15 PM Maria Jose Esteve 
> wrote:
>
> > can I test this "ApproveRoyale.xml" with RC4 Josh?
> > Hiedra
> >
> > -Mensaje original-
> > De: Josh Tynjala  Enviado el: lunes, 15
> > de mayo de 2023 20:04
> > Para: dev@royale.apache.org
> > Asunto: Re: [

RE: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Maria Jose Esteve]

I don't have mvn.exe in the /bin directory of Maven... but I tried it and it 
didn't work.
I have restored mvn.cmd (this file does exist) in ApproveRoyale.xml
I modified my build bat and manually set MAVEN_HOME, in case the system 
variable was getting lost, but the result was the same.
The last test was to put MAVEN_HOME in first position in the path, also, same 
error.

I have run out of ideas ☹

Hiedra

-Mensaje original-
De: Josh Tynjala  
Enviado el: lunes, 15 de mayo de 2023 23:20
Para: dev@royale.apache.org
Asunto: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

It seems to be failing when running Maven, but it's not giving you an error 
message to explain what the issue is.

I see that you're on Windows. I wonder if you're having a similar issue that I 
had on a previous release of the Royale build tools (I was on Windows at the 
time, but I'm on macOS these days):

https://lists.apache.org/thread/4fw80rsr87h79tofzsfs908plvfghvd4

In this case, a similar workaround would be to change mvn.cmd to mvn.exe on 
line 72 of ApproveRoyale.xml





--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>


On Mon, May 15, 2023 at 2:08 PM Maria Jose Esteve  wrote:

> It has no longer included it as unapproved, but I still can't finish 
> the Maven compilation, same problem but I don't know why, it's in the 
> path. (I can compile the SDK normally with ant and with mvn and it 
> hasn't given me any problems).
> any idea?
> ---
> main:
>
> build_maven:
> Path is C:\Program Files (x86)\Common
> Files\Oracle\Java\javapath;D:\Apache;C:\Program
> Files\Java\jdk1.8.0_281\bin;D:\Apache\apache-ant-1.10.13\bin;D:\Apache
> \apache-maven-3.9.1\bin;D:\app\client\hiedra\product\19.0.0\client_1\b
> in;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\
> System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Progr
> am Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program
> Files\dotnet\;C:\Program
> Files\Git\cmd;C:\Users\hiedra\AppData\Local\Programs\Microsoft VS 
> Code;C:\Program Files\Microsoft SQL Server\Client 
> SDK\ODBC\170\Tools\Binn\;C:\Program
> Files\PowerShell\7-preview\preview;C:\Program Files 
> (x86)\Yarn\bin\;D:\Apache\HaxeToolkit\haxe;D:\Apache\HaxeToolkit\neko;
> C:\Program Files\nodejs\;C:\Program Files (x86)\Intel\Intel(R) 
> Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) 
> Management Engine Components\DAL;C:\Program Files (x86)\Pulse 
> Secure\VC142.CRT\X64\;C:\Program Files (x86)\Pulse 
> Secure\VC142.CRT\X86\;C:\Program Files\Microsoft SQL 
> Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL 
> Server\130\Tools\Binn\;C:\Program Files 
> (x86)\GnuPG\bin;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:
> \Users\hiedra\AppData\Local\GitHubDesktop\bin;C:\Users\hiedra\.dotnet\
> tools;C:\Users\hiedra\AppData\Local\Programs\Microsoft
> VS
> Code\bin;C:\Users\hiedra\AppData\Local\Yarn\bin;C:\Users\hiedra\AppDat
> a\Roaming\npm;C:\Program
> Files\Microsoft Office\root\Client
>
> BUILD FAILED
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:798: 
> The following error occurred while executing this line:
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:811: 
> exec
> returned: 1
>
> Total time: 37 minutes 10 seconds
>
> ----------------------
> --
>
> Hiedra
>
> -Mensaje original-
> De: Josh Tynjala  Enviado el: lunes, 15 de 
> mayo de 2023 22:16
> Para: dev@royale.apache.org
> Asunto: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
>
> Yes, as I said, "You should be able to use it with this existing RC, 
> if you'd like."
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Mon, May 15, 2023 at 1:15 PM Maria Jose Esteve 
> wrote:
>
> > can I test this "ApproveRoyale.xml" with RC4 Josh?
> > Hiedra
> >
> > -Mensaje original-
> > De: Josh Tynjala  Enviado el: lunes, 15 
> > de mayo de 2023 20:04
> > Para: dev@royale.apache.org
> > Asunto: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
> >
> > That being said, I have updated the approval script in the 
> > royale-asjs Git repo. You should be able to use it with this 
> > existing RC, if you'd
> like.
> >
> > https://github.com/apache/royale-asjs/blob/develop/ApproveRoyale.xml
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC <https://bowlerhat.dev>
> >
> >
> > On Mon, May 15, 2023 at 9:35 AM Josh Tynjala 
> > 
> > wrote:
> >
> > > Now that I've had my morning tea, I rem

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Josh Tynjala]

It seems to be failing when running Maven, but it's not giving you an error
message to explain what the issue is.

I see that you're on Windows. I wonder if you're having a similar issue
that I had on a previous release of the Royale build tools (I was on
Windows at the time, but I'm on macOS these days):

https://lists.apache.org/thread/4fw80rsr87h79tofzsfs908plvfghvd4

In this case, a similar workaround would be to change mvn.cmd to mvn.exe on
line 72 of ApproveRoyale.xml





--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>


On Mon, May 15, 2023 at 2:08 PM Maria Jose Esteve  wrote:

> It has no longer included it as unapproved, but I still can't finish the
> Maven compilation, same problem but I don't know why, it's in the path. (I
> can compile the SDK normally with ant and with mvn and it hasn't given me
> any problems).
> any idea?
> ---
> main:
>
> build_maven:
> Path is C:\Program Files (x86)\Common
> Files\Oracle\Java\javapath;D:\Apache;C:\Program
> Files\Java\jdk1.8.0_281\bin;D:\Apache\apache-ant-1.10.13\bin;D:\Apache\apache-maven-3.9.1\bin;D:\app\client\hiedra\product\19.0.0\client_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program
> Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program
> Files\dotnet\;C:\Program
> Files\Git\cmd;C:\Users\hiedra\AppData\Local\Programs\Microsoft VS
> Code;C:\Program Files\Microsoft SQL Server\Client
> SDK\ODBC\170\Tools\Binn\;C:\Program
> Files\PowerShell\7-preview\preview;C:\Program Files
> (x86)\Yarn\bin\;D:\Apache\HaxeToolkit\haxe;D:\Apache\HaxeToolkit\neko;C:\Program
> Files\nodejs\;C:\Program Files (x86)\Intel\Intel(R) Management Engine
> Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine
> Components\DAL;C:\Program Files (x86)\Pulse
> Secure\VC142.CRT\X64\;C:\Program Files (x86)\Pulse
> Secure\VC142.CRT\X86\;C:\Program Files\Microsoft SQL
> Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL
> Server\130\Tools\Binn\;C:\Program Files
> (x86)\GnuPG\bin;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:\Users\hiedra\AppData\Local\GitHubDesktop\bin;C:\Users\hiedra\.dotnet\tools;C:\Users\hiedra\AppData\Local\Programs\Microsoft
> VS
> Code\bin;C:\Users\hiedra\AppData\Local\Yarn\bin;C:\Users\hiedra\AppData\Roaming\npm;C:\Program
> Files\Microsoft Office\root\Client
>
> BUILD FAILED
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:798: The
> following error occurred while executing this line:
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:811: exec
> returned: 1
>
> Total time: 37 minutes 10 seconds
>
> ----------------
>
> Hiedra
>
> -Mensaje original-
> De: Josh Tynjala 
> Enviado el: lunes, 15 de mayo de 2023 22:16
> Para: dev@royale.apache.org
> Asunto: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
>
> Yes, as I said, "You should be able to use it with this existing RC, if
> you'd like."
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Mon, May 15, 2023 at 1:15 PM Maria Jose Esteve 
> wrote:
>
> > can I test this "ApproveRoyale.xml" with RC4 Josh?
> > Hiedra
> >
> > -Mensaje original-
> > De: Josh Tynjala  Enviado el: lunes, 15 de
> > mayo de 2023 20:04
> > Para: dev@royale.apache.org
> > Asunto: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
> >
> > That being said, I have updated the approval script in the royale-asjs
> > Git repo. You should be able to use it with this existing RC, if you'd
> like.
> >
> > https://github.com/apache/royale-asjs/blob/develop/ApproveRoyale.xml
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC <https://bowlerhat.dev>
> >
> >
> > On Mon, May 15, 2023 at 9:35 AM Josh Tynjala
> > 
> > wrote:
> >
> > > Now that I've had my morning tea, I remember now that I put
> > > RoyaleUnit's dependencies into a separate directory so that they
> > > don't conflict with anything else (and so that they aren't loaded by
> > > the compiler when they aren't needed). I didn't know that I needed
> > > to update ApproveRoyale.xml. I will get that fixed for *future*
> releases.
> > >
> > > For now, this is just a minor issue, and it should not prevent you
> > > from voting in favor of this RC. The license is actually allowed,
> > > but
> > "Rat"
> > > incorrectly flags it. The approval script will

RE: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Maria Jose Esteve]

It has no longer included it as unapproved, but I still can't finish the Maven 
compilation, same problem but I don't know why, it's in the path. (I can 
compile the SDK normally with ant and with mvn and it hasn't given me any 
problems).
any idea?
---
main:

build_maven:
Path is C:\Program Files (x86)\Common 
Files\Oracle\Java\javapath;D:\Apache;C:\Program 
Files\Java\jdk1.8.0_281\bin;D:\Apache\apache-ant-1.10.13\bin;D:\Apache\apache-maven-3.9.1\bin;D:\app\client\hiedra\product\19.0.0\client_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program
 Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program 
Files\dotnet\;C:\Program 
Files\Git\cmd;C:\Users\hiedra\AppData\Local\Programs\Microsoft VS 
Code;C:\Program Files\Microsoft SQL Server\Client 
SDK\ODBC\170\Tools\Binn\;C:\Program 
Files\PowerShell\7-preview\preview;C:\Program Files 
(x86)\Yarn\bin\;D:\Apache\HaxeToolkit\haxe;D:\Apache\HaxeToolkit\neko;C:\Program
 Files\nodejs\;C:\Program Files (x86)\Intel\Intel(R) Management Engine 
Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine 
Components\DAL;C:\Program Files (x86)\Pulse Secure\VC142.CRT\X64\;C:\Program 
Files (x86)\Pulse Secure\VC142.CRT\X86\;C:\Program Files\Microsoft SQL 
Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL 
Server\130\Tools\Binn\;C:\Program Files 
(x86)\GnuPG\bin;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:\Users\hiedra\AppData\Local\GitHubDesktop\bin;C:\Users\hiedra\.dotnet\tools;C:\Users\hiedra\AppData\Local\Programs\Microsoft
 VS 
Code\bin;C:\Users\hiedra\AppData\Local\Yarn\bin;C:\Users\hiedra\AppData\Roaming\npm;C:\Program
 Files\Microsoft Office\root\Client

BUILD FAILED
D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:798: The 
following error occurred while executing this line:
D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:811: exec 
returned: 1

Total time: 37 minutes 10 seconds


Hiedra

-Mensaje original-
De: Josh Tynjala  
Enviado el: lunes, 15 de mayo de 2023 22:16
Para: dev@royale.apache.org
Asunto: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

Yes, as I said, "You should be able to use it with this existing RC, if you'd 
like."

--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>


On Mon, May 15, 2023 at 1:15 PM Maria Jose Esteve  wrote:

> can I test this "ApproveRoyale.xml" with RC4 Josh?
> Hiedra
>
> -Mensaje original-
> De: Josh Tynjala  Enviado el: lunes, 15 de 
> mayo de 2023 20:04
> Para: dev@royale.apache.org
> Asunto: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
>
> That being said, I have updated the approval script in the royale-asjs 
> Git repo. You should be able to use it with this existing RC, if you'd like.
>
> https://github.com/apache/royale-asjs/blob/develop/ApproveRoyale.xml
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Mon, May 15, 2023 at 9:35 AM Josh Tynjala 
> 
> wrote:
>
> > Now that I've had my morning tea, I remember now that I put 
> > RoyaleUnit's dependencies into a separate directory so that they 
> > don't conflict with anything else (and so that they aren't loaded by 
> > the compiler when they aren't needed). I didn't know that I needed 
> > to update ApproveRoyale.xml. I will get that fixed for *future* releases.
> >
> > For now, this is just a minor issue, and it should not prevent you 
> > from voting in favor of this RC. The license is actually allowed, 
> > but
> "Rat"
> > incorrectly flags it. The approval script will not fail when it 
> > mentions this license, so we don't need to do anything to fix it 
> > immediately.
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC <https://bowlerhat.dev>
> >
> >
> > On Mon, May 15, 2023 at 8:55 AM Josh Tynjala 
> > 
> > wrote:
> >
> >> The approval script excludes dom4j-LICENSE.txt at the following
> location:
> >>
> >> 
> >>
> >> But your path is slightly different:
> >>
> >> royale-asjs/js/lib/royaleunit/dom4j-LICENSE.txt
> >>
> >> I think we can just make a minor tweak to the approval script to 
> >> add this path too:
> >>
> >> 
> >>
> >> --
> >> Josh Tynjala
> >> Bowler Hat LLC <https://bowlerhat.dev>
> >>
> >>
> >> On Sat, May 13, 2023 at 6:29 PM Maria Jose Esteve 
> >> 
> >> wrote:
> >>
> >>> Hi,
> >>> I keep t

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Josh Tynjala]

Based on some further investigation, it looks like the Royale compiler
knows how to implement the JS IEventDispatcher API in generated .js files
only. When those .js files are included in a SWC file, the binary part of
the SWC file that is used for type checking and IDE support will always be
generated with the SWF IEventDispatcher API. That's where the conflict
comes from.

This does not appear to me to be a regression, but how it has always
worked. We may want to provide a way to generate both APIs in SWC binary
code, but I would say that's for a future release.

In Royale framework code, it looks like there are two ways to manually
handle bindable beads.

1) Extend DispatcherBead. It looks like a lot of bead classes do this.

2) Manually implement IEventDispatcher, with the different signatures
conditionally compiled with COMPILE::SWF and COMPILE::JS. This is much less
common, but it is used in a couple of places.

In both cases, the compiler won't generate any IEventDispatcher code for
bindable properties because the beads will already be event dispatchers.

The first option is most common, but not always possible when another is
superclass already being used. The second option where the interface is
manually implemented happens in these two bead:

a) In Jewel, a manual IEventDispatcher implementation is used in
ArrayListSelectionModel.
b) In Spark, a manual implementation is used in LayoutBase.

In the case of Jewel's TileHorizontalLayout, if you wanted to avoid
manually implementing IEventDispatcher, the Core version of LayoutBase
would need to extend DispatcherBead. However, I don't think this would be
considered PAYG, which Core is expected to follow more strictly than Jewel,
so there's no way to use DispatcherBead with Jewel's TileHorizontalLayout.
TileHorizontalLayout probably needs a manual implementation of
IEventDispatcher. Or possibly SimpleHorizontalLayout or StyledLayoutBase
instead, depending on how strict you want to be with PAYG in Jewel. For the
least impact and most PAYG, you should manually implement IEventDispatcher
directly on TileHorizontalLayout.

(In my opinion, this is not a release blocker. I'm just letting you know
what I found in my investigation, and my advice for fixing it.)

--
Josh Tynjala
Bowler Hat LLC 


On Mon, May 15, 2023 at 1:13 PM Josh Tynjala 
wrote:

> > Does anyone have any idea what has happened here ? Why
> TileHorizontalLayout
> > after compilation to TileHorizontalLayout.js have all of these methods ?
>
> TileHorizontallayout has [Bindable] metadata on some properties. If
> anything in a class is marked as [Bindable], and that class (or a
> superclass) does not already extend EventDispatcher (or implement
> IEventDispatcher), the compiler will automatically generate an
> implementation of IEventDispatcher. This is true in Royale, and it was also
> true in Flex.
>
> Here are the classes that TileHorizontalLayout is a subclass of:
> TileHorizontalLayout extends SimpleHorizontalLayout extends
> StyledLayoutBase extends LayoutBase extends Bead
>
> There are also the following interfaces in the type hierarchy:
> ILayoutStyleProperties, IBeadLayout, IBead
>
> Nowhere in this chain of classes is there an EventDispatcher or
> IEventDispatcher. So the compiler is generating its own implementation of
> IEventDispatcher.
>
> Unfortunately, it seems to be generating an implementation of the methods
> from the SWF version of IEventDispatcher instead of the methods from the JS
> version of IEventDispatcher. I don't believe that I have worked with the
> part of the Royale compiler that generates code for bindable
> classes/properties before, so I don't know why it would be doing that.
> However, that seems like a bug. Maybe not necessarily in the compiler. It
> could be that the compiler options used by the JewelJS build are wrong.
>
> Note: I don't think that the compiler is incorrectly using the Spark
> version of LayoutBase instead of the Core version of LayoutBase. This can
> be explained without the Spark version of LayoutBase being involved in any
> way.
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>
>
> On Mon, May 15, 2023 at 5:14 AM Piotr Zarzycki 
> wrote:
>
>> Hi Guys,
>>
>> I have voted +1, but I have found one issue which concerns me a little
>> bit.
>> I have need of usage in my application
>> -> org.apache.royale.jewel.beads.layouts.TileHorizontalLayout. I have made
>> my own custom class which extends that one. To my big surprise I got
>> following compilation error:
>>
>>  Error: interface method addEventListener in interface IEventDispatcher is
>> implemented with an incompatible signature in class
>> ExtendedTileHorizontalLayout
>> : Error: interface method removeEventListener in interface
>> IEventDispatcher
>> is implemented with an incompatible signature in class
>> ExtendedTileHorizontalLayout
>> : Error: interface method dispatchEvent in interface IEventDispatcher is
>> implemented with an incompatible signa

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Josh Tynjala]

Yes, as I said, "You should be able to use it with this existing RC, if
you'd like."

--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>


On Mon, May 15, 2023 at 1:15 PM Maria Jose Esteve  wrote:

> can I test this "ApproveRoyale.xml" with RC4 Josh?
> Hiedra
>
> -Mensaje original-
> De: Josh Tynjala 
> Enviado el: lunes, 15 de mayo de 2023 20:04
> Para: dev@royale.apache.org
> Asunto: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
>
> That being said, I have updated the approval script in the royale-asjs Git
> repo. You should be able to use it with this existing RC, if you'd like.
>
> https://github.com/apache/royale-asjs/blob/develop/ApproveRoyale.xml
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Mon, May 15, 2023 at 9:35 AM Josh Tynjala 
> wrote:
>
> > Now that I've had my morning tea, I remember now that I put
> > RoyaleUnit's dependencies into a separate directory so that they don't
> > conflict with anything else (and so that they aren't loaded by the
> > compiler when they aren't needed). I didn't know that I needed to
> > update ApproveRoyale.xml. I will get that fixed for *future* releases.
> >
> > For now, this is just a minor issue, and it should not prevent you
> > from voting in favor of this RC. The license is actually allowed, but
> "Rat"
> > incorrectly flags it. The approval script will not fail when it
> > mentions this license, so we don't need to do anything to fix it
> > immediately.
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC <https://bowlerhat.dev>
> >
> >
> > On Mon, May 15, 2023 at 8:55 AM Josh Tynjala
> > 
> > wrote:
> >
> >> The approval script excludes dom4j-LICENSE.txt at the following
> location:
> >>
> >> 
> >>
> >> But your path is slightly different:
> >>
> >> royale-asjs/js/lib/royaleunit/dom4j-LICENSE.txt
> >>
> >> I think we can just make a minor tweak to the approval script to add
> >> this path too:
> >>
> >> 
> >>
> >> --
> >> Josh Tynjala
> >> Bowler Hat LLC <https://bowlerhat.dev>
> >>
> >>
> >> On Sat, May 13, 2023 at 6:29 PM Maria Jose Esteve 
> >> wrote:
> >>
> >>> Hi,
> >>> I keep testing the automated compilation option [1] the compilation
> >>> gave me error ☹.
> >>> I have left the log of the compilation here [2] but I attach the error:
> >>>
> >>> <<<<<<<
> >>> ...
> >>> main:
> >>> Copying 1 file to
> >>>
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src\royale-asjs\examples\native\USStatesMap\bin\js-debug
> >>> Copying 1 file to
> >>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-sr
> >>> c\royale-asjs\examples\native\USStatesMap\bin\js-release
> >>>
> >>> main:
> >>>
> >>> build_maven:
> >>> Path is C:\Program Files (x86)\Common
> >>> Files\Oracle\Java\javapath;D:\Apache;C:\Program
> >>> Files\Java\jdk1.8.0_281\bin;D:\Apache\apache-ant-1.10.13\bin;D:\Apac
> >>> he\apache-maven-3.9.1\bin;D:\app\client\hiedra\product\19.0.0\client
> >>> _1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Wi
> >>> ndows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;
> >>> C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program
> >>> Files\dotnet\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbe
> >>> m;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\Op
> >>> enSSH\;C:\Program
> >>> Files\Git\cmd;C:\Users\hiedra\AppData\Local\Programs\Microsoft VS
> >>> Code;C:\Program Files\Microsoft SQL Server\Client
> >>> SDK\ODBC\170\Tools\Binn\;C:\Program
> >>> Files\PowerShell\7-preview\preview;C:\Program Files
> >>> (x86)\Yarn\bin\;D:\Apache\HaxeToolkit\haxe;D:\Apache\HaxeToolkit\nek
> >>> o;C:\Program Files\nodejs\;C:\Program Files (x86)\Intel\Intel(R)
> >>> Management Engine Components\DAL;C:\Program Files\Intel\Intel(R)
> >>> Management Engine Components\DAL;C:\Program Files (x86)\Pulse
> >>> Secure\VC142.CRT\X64\;C:\Program Files (x86)\Pulse
> >>> Secure\VC142.CRT\X86\;C:\Program Files\Microsoft SQL
> >

RE: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Maria Jose Esteve]

can I test this "ApproveRoyale.xml" with RC4 Josh?
Hiedra

-Mensaje original-
De: Josh Tynjala  
Enviado el: lunes, 15 de mayo de 2023 20:04
Para: dev@royale.apache.org
Asunto: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

That being said, I have updated the approval script in the royale-asjs Git 
repo. You should be able to use it with this existing RC, if you'd like.

https://github.com/apache/royale-asjs/blob/develop/ApproveRoyale.xml

--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>


On Mon, May 15, 2023 at 9:35 AM Josh Tynjala 
wrote:

> Now that I've had my morning tea, I remember now that I put 
> RoyaleUnit's dependencies into a separate directory so that they don't 
> conflict with anything else (and so that they aren't loaded by the 
> compiler when they aren't needed). I didn't know that I needed to 
> update ApproveRoyale.xml. I will get that fixed for *future* releases.
>
> For now, this is just a minor issue, and it should not prevent you 
> from voting in favor of this RC. The license is actually allowed, but "Rat"
> incorrectly flags it. The approval script will not fail when it 
> mentions this license, so we don't need to do anything to fix it 
> immediately.
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Mon, May 15, 2023 at 8:55 AM Josh Tynjala 
> 
> wrote:
>
>> The approval script excludes dom4j-LICENSE.txt at the following location:
>>
>> 
>>
>> But your path is slightly different:
>>
>> royale-asjs/js/lib/royaleunit/dom4j-LICENSE.txt
>>
>> I think we can just make a minor tweak to the approval script to add 
>> this path too:
>>
>> 
>>
>> --
>> Josh Tynjala
>> Bowler Hat LLC <https://bowlerhat.dev>
>>
>>
>> On Sat, May 13, 2023 at 6:29 PM Maria Jose Esteve 
>> wrote:
>>
>>> Hi,
>>> I keep testing the automated compilation option [1] the compilation 
>>> gave me error ☹.
>>> I have left the log of the compilation here [2] but I attach the error:
>>>
>>> <<<<<<<
>>> ...
>>> main:
>>> Copying 1 file to
>>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src\royale-asjs\examples\native\USStatesMap\bin\js-debug
>>> Copying 1 file to
>>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-sr
>>> c\royale-asjs\examples\native\USStatesMap\bin\js-release
>>>
>>> main:
>>>
>>> build_maven:
>>> Path is C:\Program Files (x86)\Common 
>>> Files\Oracle\Java\javapath;D:\Apache;C:\Program
>>> Files\Java\jdk1.8.0_281\bin;D:\Apache\apache-ant-1.10.13\bin;D:\Apac
>>> he\apache-maven-3.9.1\bin;D:\app\client\hiedra\product\19.0.0\client
>>> _1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Wi
>>> ndows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;
>>> C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program
>>> Files\dotnet\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbe
>>> m;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\Op
>>> enSSH\;C:\Program 
>>> Files\Git\cmd;C:\Users\hiedra\AppData\Local\Programs\Microsoft VS 
>>> Code;C:\Program Files\Microsoft SQL Server\Client 
>>> SDK\ODBC\170\Tools\Binn\;C:\Program
>>> Files\PowerShell\7-preview\preview;C:\Program Files 
>>> (x86)\Yarn\bin\;D:\Apache\HaxeToolkit\haxe;D:\Apache\HaxeToolkit\nek
>>> o;C:\Program Files\nodejs\;C:\Program Files (x86)\Intel\Intel(R) 
>>> Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) 
>>> Management Engine Components\DAL;C:\Program Files (x86)\Pulse 
>>> Secure\VC142.CRT\X64\;C:\Program Files (x86)\Pulse 
>>> Secure\VC142.CRT\X86\;C:\Program Files\Microsoft SQL 
>>> Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL 
>>> Server\130\Tools\Binn\;C:\Program Files 
>>> (x86)\GnuPG\bin;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;
>>> C:\Users\hiedra\AppData\Local\GitHubDesktop\bin;C:\Users\hiedra\.dot
>>> net\tools;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:\Use
>>> rs\hiedra\AppData\Local\Programs\Microsoft
>>> VS
>>> Code\bin;C:\Users\hiedra\AppData\Local\Yarn\bin;C:\Users\hiedra\AppD
>>> ata\Roaming\npm
>>>
>>> BUILD FAILED
>>>
>>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveR

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Josh Tynjala]

> Does anyone have any idea what has happened here ? Why
TileHorizontalLayout
> after compilation to TileHorizontalLayout.js have all of these methods ?

TileHorizontallayout has [Bindable] metadata on some properties. If
anything in a class is marked as [Bindable], and that class (or a
superclass) does not already extend EventDispatcher (or implement
IEventDispatcher), the compiler will automatically generate an
implementation of IEventDispatcher. This is true in Royale, and it was also
true in Flex.

Here are the classes that TileHorizontalLayout is a subclass of:
TileHorizontalLayout extends SimpleHorizontalLayout extends
StyledLayoutBase extends LayoutBase extends Bead

There are also the following interfaces in the type hierarchy:
ILayoutStyleProperties, IBeadLayout, IBead

Nowhere in this chain of classes is there an EventDispatcher or
IEventDispatcher. So the compiler is generating its own implementation of
IEventDispatcher.

Unfortunately, it seems to be generating an implementation of the methods
from the SWF version of IEventDispatcher instead of the methods from the JS
version of IEventDispatcher. I don't believe that I have worked with the
part of the Royale compiler that generates code for bindable
classes/properties before, so I don't know why it would be doing that.
However, that seems like a bug. Maybe not necessarily in the compiler. It
could be that the compiler options used by the JewelJS build are wrong.

Note: I don't think that the compiler is incorrectly using the Spark
version of LayoutBase instead of the Core version of LayoutBase. This can
be explained without the Spark version of LayoutBase being involved in any
way.

--
Josh Tynjala
Bowler Hat LLC 


On Mon, May 15, 2023 at 5:14 AM Piotr Zarzycki 
wrote:

> Hi Guys,
>
> I have voted +1, but I have found one issue which concerns me a little bit.
> I have need of usage in my application
> -> org.apache.royale.jewel.beads.layouts.TileHorizontalLayout. I have made
> my own custom class which extends that one. To my big surprise I got
> following compilation error:
>
>  Error: interface method addEventListener in interface IEventDispatcher is
> implemented with an incompatible signature in class
> ExtendedTileHorizontalLayout
> : Error: interface method removeEventListener in interface IEventDispatcher
> is implemented with an incompatible signature in class
> ExtendedTileHorizontalLayout
> : Error: interface method dispatchEvent in interface IEventDispatcher is
> implemented with an incompatible signature in class
> ExtendedTileHorizontalLayout
>
> I have looked into TileHorizontalLayout in Moonshine and I see there
> signature methods -> https://prnt.sc/crcNcuFHgu-8
>
> Look int signatures dispatchEvent, hasEventListener, removeEventListener
> and addEventListener - they are all missing fields name. This is definitely
> wrong, but I think all of these methods shouldn't even exists in
> frameworks/js/libs/JewelJS.swc -> TileHorizontalLayout.
>
> TileHorizontalLayout extends several classes, one of them
> is org.apache.royale.core.LayoutBase - non of these classes have anywhere
> inside methods dispatchEvent, hasEventListener etc. However there is
> another class in completely different
> package spark.layouts.supportClasses.LayoutBase - that one have these
> methods implemented exactly in the same way as my TileHorizontalLayout.js
> have.
>
> Does anyone have any idea what has happened here ? Why TileHorizontalLayout
> after compilation to TileHorizontalLayout.js have all of these methods ?
>
> Thanks,
> Piotr
>
>
> niedz., 14 maj 2023 o 03:29 Maria Jose Esteve 
> napisał(a):
>
> > Hi,
> > I keep testing the automated compilation option [1] the compilation gave
> > me error ☹.
> > I have left the log of the compilation here [2] but I attach the error:
> >
> > <<<
> > ...
> > main:
> > Copying 1 file to
> >
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src\royale-asjs\examples\native\USStatesMap\bin\js-debug
> > Copying 1 file to
> >
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src\royale-asjs\examples\native\USStatesMap\bin\js-release
> >
> > main:
> >
> > build_maven:
> > Path is C:\Program Files (x86)\Common
> > Files\Oracle\Java\javapath;D:\Apache;C:\Program
> >
> Files\Java\jdk1.8.0_281\bin;D:\Apache\apache-ant-1.10.13\bin;D:\Apache\apache-maven-3.9.1\bin;D:\app\client\hiedra\product\19.0.0\client_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program
> > Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program
> >
> Files\dotnet\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program
> > Files\Git\cmd;C:\Users\hiedra\AppData\Local\Programs\Microsoft VS
> > Code;C:\Program Files\Microsoft SQL Server\Client
> > SDK\ODBC\170\Tools\Binn\;C:\Pr

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Piotr Zarzycki]

Hi Harbs,

I did my first attempt of implementation in a simple Hello World, so the
answer is no I don't use Spark in my app. This code come to me with
framework. If you download official build 0.9.10 [1] and unpack
frameworks/js/libs/JewelJS.swc you will find in TileHorizontalLayout
unnecessary code.

Why compiler "confuses" all of that.

[1] https://nightlies.apache.org/Royale/Royale-asjs/

pon., 15 maj 2023 o 18:39 Harbs  napisał(a):

> Yes. That is somewhat concerning.
>
> Are you using Spark anywhere in your application?
>
> > On May 15, 2023, at 3:13 PM, Piotr Zarzycki 
> wrote:
> >
> > Hi Guys,
> >
> > I have voted +1, but I have found one issue which concerns me a little
> bit.
> > I have need of usage in my application
> > -> org.apache.royale.jewel.beads.layouts.TileHorizontalLayout. I have
> made
> > my own custom class which extends that one. To my big surprise I got
> > following compilation error:
> >
> > Error: interface method addEventListener in interface IEventDispatcher is
> > implemented with an incompatible signature in class
> > ExtendedTileHorizontalLayout
> > : Error: interface method removeEventListener in interface
> IEventDispatcher
> > is implemented with an incompatible signature in class
> > ExtendedTileHorizontalLayout
> > : Error: interface method dispatchEvent in interface IEventDispatcher is
> > implemented with an incompatible signature in class
> > ExtendedTileHorizontalLayout
> >
> > I have looked into TileHorizontalLayout in Moonshine and I see there
> > signature methods -> https://prnt.sc/crcNcuFHgu-8
> >
> > Look int signatures dispatchEvent, hasEventListener, removeEventListener
> > and addEventListener - they are all missing fields name. This is
> definitely
> > wrong, but I think all of these methods shouldn't even exists in
> > frameworks/js/libs/JewelJS.swc -> TileHorizontalLayout.
> >
> > TileHorizontalLayout extends several classes, one of them
> > is org.apache.royale.core.LayoutBase - non of these classes have anywhere
> > inside methods dispatchEvent, hasEventListener etc. However there is
> > another class in completely different
> > package spark.layouts.supportClasses.LayoutBase - that one have these
> > methods implemented exactly in the same way as my TileHorizontalLayout.js
> > have.
> >
> > Does anyone have any idea what has happened here ? Why
> TileHorizontalLayout
> > after compilation to TileHorizontalLayout.js have all of these methods ?
> >
> > Thanks,
> > Piotr
> >
> >
> > niedz., 14 maj 2023 o 03:29 Maria Jose Esteve 
> > napisał(a):
> >
> >> Hi,
> >> I keep testing the automated compilation option [1] the compilation gave
> >> me error ☹.
> >> I have left the log of the compilation here [2] but I attach the error:
> >>
> >> <<<
> >> ...
> >>main:
> >>Copying 1 file to
> >>
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src\royale-asjs\examples\native\USStatesMap\bin\js-debug
> >>Copying 1 file to
> >>
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src\royale-asjs\examples\native\USStatesMap\bin\js-release
> >>
> >>main:
> >>
> >>build_maven:
> >>Path is C:\Program Files (x86)\Common
> >> Files\Oracle\Java\javapath;D:\Apache;C:\Program
> >>
> Files\Java\jdk1.8.0_281\bin;D:\Apache\apache-ant-1.10.13\bin;D:\Apache\apache-maven-3.9.1\bin;D:\app\client\hiedra\product\19.0.0\client_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program
> >> Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program
> >>
> Files\dotnet\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program
> >> Files\Git\cmd;C:\Users\hiedra\AppData\Local\Programs\Microsoft VS
> >> Code;C:\Program Files\Microsoft SQL Server\Client
> >> SDK\ODBC\170\Tools\Binn\;C:\Program
> >> Files\PowerShell\7-preview\preview;C:\Program Files
> >>
> (x86)\Yarn\bin\;D:\Apache\HaxeToolkit\haxe;D:\Apache\HaxeToolkit\neko;C:\Program
> >> Files\nodejs\;C:\Program Files (x86)\Intel\Intel(R) Management Engine
> >> Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine
> >> Components\DAL;C:\Program Files (x86)\Pulse
> >> Secure\VC142.CRT\X64\;C:\Program Files (x86)\Pulse
> >> Secure\VC142.CRT\X86\;C:\Program Files\Microsoft SQL
> >> Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL
> >> Server\130\Tools\Binn\;C:\Program Files
> >>
> (x86)\GnuPG\bin;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:\Users\hiedra\AppData\Local\GitHubDesktop\bin;C:\Users\hiedra\.dotnet\tools;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:\Users\hiedra\AppData\Local\Programs\Microsoft
> >> VS
> >>
> Code\bin;C:\Users\hiedra\AppData\Local\Yarn\bin;C:\Users\hiedra\AppData\Roaming\npm
> >>
> >>BUILD FAILED
> >>
> >> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:796: The
> >> following error occurred while executing t

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Josh Tynjala]

That being said, I have updated the approval script in the royale-asjs Git
repo. You should be able to use it with this existing RC, if you'd like.

https://github.com/apache/royale-asjs/blob/develop/ApproveRoyale.xml

--
Josh Tynjala
Bowler Hat LLC 


On Mon, May 15, 2023 at 9:35 AM Josh Tynjala 
wrote:

> Now that I've had my morning tea, I remember now that I put
> RoyaleUnit's dependencies into a separate directory so that they don't
> conflict with anything else (and so that they aren't loaded by the compiler
> when they aren't needed). I didn't know that I needed to update
> ApproveRoyale.xml. I will get that fixed for *future* releases.
>
> For now, this is just a minor issue, and it should not prevent you from
> voting in favor of this RC. The license is actually allowed, but "Rat"
> incorrectly flags it. The approval script will not fail when it
> mentions this license, so we don't need to do anything to fix it
> immediately.
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>
>
> On Mon, May 15, 2023 at 8:55 AM Josh Tynjala 
> wrote:
>
>> The approval script excludes dom4j-LICENSE.txt at the following location:
>>
>> 
>>
>> But your path is slightly different:
>>
>> royale-asjs/js/lib/royaleunit/dom4j-LICENSE.txt
>>
>> I think we can just make a minor tweak to the approval script to add this
>> path too:
>>
>> 
>>
>> --
>> Josh Tynjala
>> Bowler Hat LLC 
>>
>>
>> On Sat, May 13, 2023 at 6:29 PM Maria Jose Esteve 
>> wrote:
>>
>>> Hi,
>>> I keep testing the automated compilation option [1] the compilation gave
>>> me error ☹.
>>> I have left the log of the compilation here [2] but I attach the error:
>>>
>>> <<<
>>> ...
>>> main:
>>> Copying 1 file to
>>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src\royale-asjs\examples\native\USStatesMap\bin\js-debug
>>> Copying 1 file to
>>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src\royale-asjs\examples\native\USStatesMap\bin\js-release
>>>
>>> main:
>>>
>>> build_maven:
>>> Path is C:\Program Files (x86)\Common
>>> Files\Oracle\Java\javapath;D:\Apache;C:\Program
>>> Files\Java\jdk1.8.0_281\bin;D:\Apache\apache-ant-1.10.13\bin;D:\Apache\apache-maven-3.9.1\bin;D:\app\client\hiedra\product\19.0.0\client_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program
>>> Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program
>>> Files\dotnet\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program
>>> Files\Git\cmd;C:\Users\hiedra\AppData\Local\Programs\Microsoft VS
>>> Code;C:\Program Files\Microsoft SQL Server\Client
>>> SDK\ODBC\170\Tools\Binn\;C:\Program
>>> Files\PowerShell\7-preview\preview;C:\Program Files
>>> (x86)\Yarn\bin\;D:\Apache\HaxeToolkit\haxe;D:\Apache\HaxeToolkit\neko;C:\Program
>>> Files\nodejs\;C:\Program Files (x86)\Intel\Intel(R) Management Engine
>>> Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine
>>> Components\DAL;C:\Program Files (x86)\Pulse
>>> Secure\VC142.CRT\X64\;C:\Program Files (x86)\Pulse
>>> Secure\VC142.CRT\X86\;C:\Program Files\Microsoft SQL
>>> Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL
>>> Server\130\Tools\Binn\;C:\Program Files
>>> (x86)\GnuPG\bin;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:\Users\hiedra\AppData\Local\GitHubDesktop\bin;C:\Users\hiedra\.dotnet\tools;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:\Users\hiedra\AppData\Local\Programs\Microsoft
>>> VS
>>> Code\bin;C:\Users\hiedra\AppData\Local\Yarn\bin;C:\Users\hiedra\AppData\Roaming\npm
>>>
>>> BUILD FAILED
>>>
>>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:796: The
>>> following error occurred while executing this line:
>>>
>>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:809: exec
>>> returned: 1
>>>
>>> Total time: 39 minutes 52 seconds
>>> >>>
>>>
>>> The error occurs in the Maven compilation task (it's in the path, could
>>> it be because of the maven version?):
>>>
>>> >>>
>>> ...
>>> 
>>> >> value="-Poption-with-swf"
>>> else="-Ddummy=true">
>>> 
>>> 
>>> >> value="-Pwith-examples,with-distribution,option-with-swf"
>>> else="-Pwith-examples,with-distribution">
>>> 
>>> 
>>> Path is ${env.Path}
>>>
>>> -- >>>>> inputstring="Yes">
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> >> inputstring="Yes">
>>> 
>>> 
>>> 
>>> 
>>> 
>>> ...
>>> <<<
>>>
>>> I have a question about licenses... Yishay has no anomalies in this
>>> regard but I have an unapproved license:
>>> Unapproved licenses:
>>>

RE: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Maria Jose Esteve]

Ok Josh, thx

Hiedra

-Mensaje original-
De: Josh Tynjala  
Enviado el: lunes, 15 de mayo de 2023 18:35
Para: dev@royale.apache.org
Asunto: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

Now that I've had my morning tea, I remember now that I put RoyaleUnit's 
dependencies into a separate directory so that they don't conflict with 
anything else (and so that they aren't loaded by the compiler when they aren't 
needed). I didn't know that I needed to update ApproveRoyale.xml. I will get 
that fixed for *future* releases.

For now, this is just a minor issue, and it should not prevent you from voting 
in favor of this RC. The license is actually allowed, but "Rat"
incorrectly flags it. The approval script will not fail when it mentions this 
license, so we don't need to do anything to fix it immediately.

--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>


On Mon, May 15, 2023 at 8:55 AM Josh Tynjala 
wrote:

> The approval script excludes dom4j-LICENSE.txt at the following location:
>
> 
>
> But your path is slightly different:
>
> royale-asjs/js/lib/royaleunit/dom4j-LICENSE.txt
>
> I think we can just make a minor tweak to the approval script to add 
> this path too:
>
> 
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Sat, May 13, 2023 at 6:29 PM Maria Jose Esteve 
> wrote:
>
>> Hi,
>> I keep testing the automated compilation option [1] the compilation 
>> gave me error ☹.
>> I have left the log of the compilation here [2] but I attach the error:
>>
>> <<<<<<<
>> ...
>> main:
>> Copying 1 file to
>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src\royale-asjs\examples\native\USStatesMap\bin\js-debug
>> Copying 1 file to
>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src
>> \royale-asjs\examples\native\USStatesMap\bin\js-release
>>
>> main:
>>
>> build_maven:
>> Path is C:\Program Files (x86)\Common 
>> Files\Oracle\Java\javapath;D:\Apache;C:\Program
>> Files\Java\jdk1.8.0_281\bin;D:\Apache\apache-ant-1.10.13\bin;D:\Apach
>> e\apache-maven-3.9.1\bin;D:\app\client\hiedra\product\19.0.0\client_1
>> \bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windo
>> ws\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\P
>> rogram Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program
>> Files\dotnet\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
>> ;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\Open
>> SSH\;C:\Program 
>> Files\Git\cmd;C:\Users\hiedra\AppData\Local\Programs\Microsoft VS 
>> Code;C:\Program Files\Microsoft SQL Server\Client 
>> SDK\ODBC\170\Tools\Binn\;C:\Program
>> Files\PowerShell\7-preview\preview;C:\Program Files 
>> (x86)\Yarn\bin\;D:\Apache\HaxeToolkit\haxe;D:\Apache\HaxeToolkit\neko
>> ;C:\Program Files\nodejs\;C:\Program Files (x86)\Intel\Intel(R) 
>> Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) 
>> Management Engine Components\DAL;C:\Program Files (x86)\Pulse 
>> Secure\VC142.CRT\X64\;C:\Program Files (x86)\Pulse 
>> Secure\VC142.CRT\X86\;C:\Program Files\Microsoft SQL 
>> Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL 
>> Server\130\Tools\Binn\;C:\Program Files 
>> (x86)\GnuPG\bin;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C
>> :\Users\hiedra\AppData\Local\GitHubDesktop\bin;C:\Users\hiedra\.dotne
>> t\tools;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:\Users\
>> hiedra\AppData\Local\Programs\Microsoft
>> VS
>> Code\bin;C:\Users\hiedra\AppData\Local\Yarn\bin;C:\Users\hiedra\AppDa
>> ta\Roaming\npm
>>
>> BUILD FAILED
>>
>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:796: 
>> The following error occurred while executing this line:
>>
>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:809: 
>> exec
>> returned: 1
>>
>> Total time: 39 minutes 52 seconds
>> >>>>>>>
>>
>> The error occurs in the Maven compilation task (it's in the path, 
>> could it be because of the maven version?):
>>
>> >>>>>>>
>> ...
>> 
>> > value="-Poption-with-swf"
>> else="-Ddummy=true">
>> 
>> 
>> > value="-Pwith-examples,with-distribution,option-with-swf"
>> else="-Pwith-examples,with-distribution">
>> 
>> 

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Harbs]

Yes. That is somewhat concerning.

Are you using Spark anywhere in your application?

> On May 15, 2023, at 3:13 PM, Piotr Zarzycki  wrote:
> 
> Hi Guys,
> 
> I have voted +1, but I have found one issue which concerns me a little bit.
> I have need of usage in my application
> -> org.apache.royale.jewel.beads.layouts.TileHorizontalLayout. I have made
> my own custom class which extends that one. To my big surprise I got
> following compilation error:
> 
> Error: interface method addEventListener in interface IEventDispatcher is
> implemented with an incompatible signature in class
> ExtendedTileHorizontalLayout
> : Error: interface method removeEventListener in interface IEventDispatcher
> is implemented with an incompatible signature in class
> ExtendedTileHorizontalLayout
> : Error: interface method dispatchEvent in interface IEventDispatcher is
> implemented with an incompatible signature in class
> ExtendedTileHorizontalLayout
> 
> I have looked into TileHorizontalLayout in Moonshine and I see there
> signature methods -> https://prnt.sc/crcNcuFHgu-8
> 
> Look int signatures dispatchEvent, hasEventListener, removeEventListener
> and addEventListener - they are all missing fields name. This is definitely
> wrong, but I think all of these methods shouldn't even exists in
> frameworks/js/libs/JewelJS.swc -> TileHorizontalLayout.
> 
> TileHorizontalLayout extends several classes, one of them
> is org.apache.royale.core.LayoutBase - non of these classes have anywhere
> inside methods dispatchEvent, hasEventListener etc. However there is
> another class in completely different
> package spark.layouts.supportClasses.LayoutBase - that one have these
> methods implemented exactly in the same way as my TileHorizontalLayout.js
> have.
> 
> Does anyone have any idea what has happened here ? Why TileHorizontalLayout
> after compilation to TileHorizontalLayout.js have all of these methods ?
> 
> Thanks,
> Piotr
> 
> 
> niedz., 14 maj 2023 o 03:29 Maria Jose Esteve 
> napisał(a):
> 
>> Hi,
>> I keep testing the automated compilation option [1] the compilation gave
>> me error ☹.
>> I have left the log of the compilation here [2] but I attach the error:
>> 
>> <<<
>> ...
>>main:
>>Copying 1 file to
>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src\royale-asjs\examples\native\USStatesMap\bin\js-debug
>>Copying 1 file to
>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src\royale-asjs\examples\native\USStatesMap\bin\js-release
>> 
>>main:
>> 
>>build_maven:
>>Path is C:\Program Files (x86)\Common
>> Files\Oracle\Java\javapath;D:\Apache;C:\Program
>> Files\Java\jdk1.8.0_281\bin;D:\Apache\apache-ant-1.10.13\bin;D:\Apache\apache-maven-3.9.1\bin;D:\app\client\hiedra\product\19.0.0\client_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program
>> Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program
>> Files\dotnet\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program
>> Files\Git\cmd;C:\Users\hiedra\AppData\Local\Programs\Microsoft VS
>> Code;C:\Program Files\Microsoft SQL Server\Client
>> SDK\ODBC\170\Tools\Binn\;C:\Program
>> Files\PowerShell\7-preview\preview;C:\Program Files
>> (x86)\Yarn\bin\;D:\Apache\HaxeToolkit\haxe;D:\Apache\HaxeToolkit\neko;C:\Program
>> Files\nodejs\;C:\Program Files (x86)\Intel\Intel(R) Management Engine
>> Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine
>> Components\DAL;C:\Program Files (x86)\Pulse
>> Secure\VC142.CRT\X64\;C:\Program Files (x86)\Pulse
>> Secure\VC142.CRT\X86\;C:\Program Files\Microsoft SQL
>> Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL
>> Server\130\Tools\Binn\;C:\Program Files
>> (x86)\GnuPG\bin;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:\Users\hiedra\AppData\Local\GitHubDesktop\bin;C:\Users\hiedra\.dotnet\tools;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:\Users\hiedra\AppData\Local\Programs\Microsoft
>> VS
>> Code\bin;C:\Users\hiedra\AppData\Local\Yarn\bin;C:\Users\hiedra\AppData\Roaming\npm
>> 
>>BUILD FAILED
>> 
>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:796: The
>> following error occurred while executing this line:
>> 
>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:809: exec
>> returned: 1
>> 
>>Total time: 39 minutes 52 seconds
> 
>> 
>> The error occurs in the Maven compilation task (it's in the path, could it
>> be because of the maven version?):
>> 
> 
>> ...
>>
>>> value="-Poption-with-swf"
>>else="-Ddummy=true">
>>
>>
>>> value="-Pwith-examples,with-distribution,option-with-swf"
>>else="-Pwith-examples,with-distribution">
>>
>>
>>Path is ${env.Path}
>> 
>> -- >>>> inputstring="Ye

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Josh Tynjala]

Now that I've had my morning tea, I remember now that I put
RoyaleUnit's dependencies into a separate directory so that they don't
conflict with anything else (and so that they aren't loaded by the compiler
when they aren't needed). I didn't know that I needed to update
ApproveRoyale.xml. I will get that fixed for *future* releases.

For now, this is just a minor issue, and it should not prevent you from
voting in favor of this RC. The license is actually allowed, but "Rat"
incorrectly flags it. The approval script will not fail when it
mentions this license, so we don't need to do anything to fix it
immediately.

--
Josh Tynjala
Bowler Hat LLC 


On Mon, May 15, 2023 at 8:55 AM Josh Tynjala 
wrote:

> The approval script excludes dom4j-LICENSE.txt at the following location:
>
> 
>
> But your path is slightly different:
>
> royale-asjs/js/lib/royaleunit/dom4j-LICENSE.txt
>
> I think we can just make a minor tweak to the approval script to add this
> path too:
>
> 
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>
>
> On Sat, May 13, 2023 at 6:29 PM Maria Jose Esteve 
> wrote:
>
>> Hi,
>> I keep testing the automated compilation option [1] the compilation gave
>> me error ☹.
>> I have left the log of the compilation here [2] but I attach the error:
>>
>> <<<
>> ...
>> main:
>> Copying 1 file to
>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src\royale-asjs\examples\native\USStatesMap\bin\js-debug
>> Copying 1 file to
>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src\royale-asjs\examples\native\USStatesMap\bin\js-release
>>
>> main:
>>
>> build_maven:
>> Path is C:\Program Files (x86)\Common
>> Files\Oracle\Java\javapath;D:\Apache;C:\Program
>> Files\Java\jdk1.8.0_281\bin;D:\Apache\apache-ant-1.10.13\bin;D:\Apache\apache-maven-3.9.1\bin;D:\app\client\hiedra\product\19.0.0\client_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program
>> Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program
>> Files\dotnet\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program
>> Files\Git\cmd;C:\Users\hiedra\AppData\Local\Programs\Microsoft VS
>> Code;C:\Program Files\Microsoft SQL Server\Client
>> SDK\ODBC\170\Tools\Binn\;C:\Program
>> Files\PowerShell\7-preview\preview;C:\Program Files
>> (x86)\Yarn\bin\;D:\Apache\HaxeToolkit\haxe;D:\Apache\HaxeToolkit\neko;C:\Program
>> Files\nodejs\;C:\Program Files (x86)\Intel\Intel(R) Management Engine
>> Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine
>> Components\DAL;C:\Program Files (x86)\Pulse
>> Secure\VC142.CRT\X64\;C:\Program Files (x86)\Pulse
>> Secure\VC142.CRT\X86\;C:\Program Files\Microsoft SQL
>> Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL
>> Server\130\Tools\Binn\;C:\Program Files
>> (x86)\GnuPG\bin;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:\Users\hiedra\AppData\Local\GitHubDesktop\bin;C:\Users\hiedra\.dotnet\tools;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:\Users\hiedra\AppData\Local\Programs\Microsoft
>> VS
>> Code\bin;C:\Users\hiedra\AppData\Local\Yarn\bin;C:\Users\hiedra\AppData\Roaming\npm
>>
>> BUILD FAILED
>>
>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:796: The
>> following error occurred while executing this line:
>>
>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:809: exec
>> returned: 1
>>
>> Total time: 39 minutes 52 seconds
>> >>>
>>
>> The error occurs in the Maven compilation task (it's in the path, could
>> it be because of the maven version?):
>>
>> >>>
>> ...
>> 
>> > value="-Poption-with-swf"
>> else="-Ddummy=true">
>> 
>> 
>> > value="-Pwith-examples,with-distribution,option-with-swf"
>> else="-Pwith-examples,with-distribution">
>> 
>> 
>> Path is ${env.Path}
>>
>> -- >>>> inputstring="Yes">
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> > inputstring="Yes">
>> 
>> 
>> 
>> 
>> 
>> ...
>> <<<
>>
>> I have a question about licenses... Yishay has no anomalies in this
>> regard but I have an unapproved license:
>> Unapproved licenses:
>>
>>  
>> D:/Develop_Royale/Projects/Royale-SDK/0.9.10/apache-royale-0.9.10-bin-js-swf/royale-asjs/js/lib/royaleunit/dom4j-LICENSE.txt
>> How can I fix it?
>>
>> [1]
>> https://dist.apache.org/repos/dist/dev/royale/0.9.10/rc4/ApproveRoyale.xml
>> y ejecutando el script:
>>ant -e -f ApproveRoyale.xml -Drelease.version=0.9.10 -Drc=4
>> [2]
>> https://drive.google.com/file/d/1jCgS51cgtRSSuh11UJUxzdEaburpDdpF/view?usp=share_link
>>
>> Hiedra
>>
>> -Mensaje original

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Josh Tynjala]

The approval script excludes dom4j-LICENSE.txt at the following location:



But your path is slightly different:

royale-asjs/js/lib/royaleunit/dom4j-LICENSE.txt

I think we can just make a minor tweak to the approval script to add this
path too:



--
Josh Tynjala
Bowler Hat LLC 


On Sat, May 13, 2023 at 6:29 PM Maria Jose Esteve  wrote:

> Hi,
> I keep testing the automated compilation option [1] the compilation gave
> me error ☹.
> I have left the log of the compilation here [2] but I attach the error:
>
> <<<
> ...
> main:
> Copying 1 file to
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src\royale-asjs\examples\native\USStatesMap\bin\js-debug
> Copying 1 file to
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src\royale-asjs\examples\native\USStatesMap\bin\js-release
>
> main:
>
> build_maven:
> Path is C:\Program Files (x86)\Common
> Files\Oracle\Java\javapath;D:\Apache;C:\Program
> Files\Java\jdk1.8.0_281\bin;D:\Apache\apache-ant-1.10.13\bin;D:\Apache\apache-maven-3.9.1\bin;D:\app\client\hiedra\product\19.0.0\client_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program
> Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program
> Files\dotnet\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program
> Files\Git\cmd;C:\Users\hiedra\AppData\Local\Programs\Microsoft VS
> Code;C:\Program Files\Microsoft SQL Server\Client
> SDK\ODBC\170\Tools\Binn\;C:\Program
> Files\PowerShell\7-preview\preview;C:\Program Files
> (x86)\Yarn\bin\;D:\Apache\HaxeToolkit\haxe;D:\Apache\HaxeToolkit\neko;C:\Program
> Files\nodejs\;C:\Program Files (x86)\Intel\Intel(R) Management Engine
> Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine
> Components\DAL;C:\Program Files (x86)\Pulse
> Secure\VC142.CRT\X64\;C:\Program Files (x86)\Pulse
> Secure\VC142.CRT\X86\;C:\Program Files\Microsoft SQL
> Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL
> Server\130\Tools\Binn\;C:\Program Files
> (x86)\GnuPG\bin;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:\Users\hiedra\AppData\Local\GitHubDesktop\bin;C:\Users\hiedra\.dotnet\tools;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:\Users\hiedra\AppData\Local\Programs\Microsoft
> VS
> Code\bin;C:\Users\hiedra\AppData\Local\Yarn\bin;C:\Users\hiedra\AppData\Roaming\npm
>
> BUILD FAILED
>
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:796: The
> following error occurred while executing this line:
>
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:809: exec
> returned: 1
>
> Total time: 39 minutes 52 seconds
> >>>
>
> The error occurs in the Maven compilation task (it's in the path, could it
> be because of the maven version?):
>
> >>>
> ...
> 
>  value="-Poption-with-swf"
> else="-Ddummy=true">
> 
> 
>  value="-Pwith-examples,with-distribution,option-with-swf"
> else="-Pwith-examples,with-distribution">
> 
> 
> Path is ${env.Path}
>
> -- >>> inputstring="Yes">
> 
> 
> 
> 
>  dir="${basedir}/${maven.package.url.name}/royale-typedefs"
> failonerror="true" >
> 
> 
> 
>  dir="${basedir}/${maven.package.url.name}/royale-asjs"
> failonerror="true" inputstring="Yes">
> 
> 
> 
> 
> 
> ...
> <<<
>
> I have a question about licenses... Yishay has no anomalies in this regard
> but I have an unapproved license:
> Unapproved licenses:
>
>  
> D:/Develop_Royale/Projects/Royale-SDK/0.9.10/apache-royale-0.9.10-bin-js-swf/royale-asjs/js/lib/royaleunit/dom4j-LICENSE.txt
> How can I fix it?
>
> [1]
> https://dist.apache.org/repos/dist/dev/royale/0.9.10/rc4/ApproveRoyale.xml
> y ejecutando el script:
>ant -e -f ApproveRoyale.xml -Drelease.version=0.9.10 -Drc=4
> [2]
> https://drive.google.com/file/d/1jCgS51cgtRSSuh11UJUxzdEaburpDdpF/view?usp=share_link
>
> Hiedra
>
> -Mensaje original-
> De: Yishay Weiss 
> Enviado el: sábado, 13 de mayo de 2023 19:36
> Para: dev@royale.apache.org
> Asunto: [DISCUSS] Release Apache Royale 0.9.10 RC4
>
> This is the discussion thread.
>

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Piotr Zarzycki]

Hi Guys,

I have voted +1, but I have found one issue which concerns me a little bit.
I have need of usage in my application
-> org.apache.royale.jewel.beads.layouts.TileHorizontalLayout. I have made
my own custom class which extends that one. To my big surprise I got
following compilation error:

 Error: interface method addEventListener in interface IEventDispatcher is
implemented with an incompatible signature in class
ExtendedTileHorizontalLayout
: Error: interface method removeEventListener in interface IEventDispatcher
is implemented with an incompatible signature in class
ExtendedTileHorizontalLayout
: Error: interface method dispatchEvent in interface IEventDispatcher is
implemented with an incompatible signature in class
ExtendedTileHorizontalLayout

I have looked into TileHorizontalLayout in Moonshine and I see there
signature methods -> https://prnt.sc/crcNcuFHgu-8

Look int signatures dispatchEvent, hasEventListener, removeEventListener
and addEventListener - they are all missing fields name. This is definitely
wrong, but I think all of these methods shouldn't even exists in
frameworks/js/libs/JewelJS.swc -> TileHorizontalLayout.

TileHorizontalLayout extends several classes, one of them
is org.apache.royale.core.LayoutBase - non of these classes have anywhere
inside methods dispatchEvent, hasEventListener etc. However there is
another class in completely different
package spark.layouts.supportClasses.LayoutBase - that one have these
methods implemented exactly in the same way as my TileHorizontalLayout.js
have.

Does anyone have any idea what has happened here ? Why TileHorizontalLayout
after compilation to TileHorizontalLayout.js have all of these methods ?

Thanks,
Piotr


niedz., 14 maj 2023 o 03:29 Maria Jose Esteve 
napisał(a):

> Hi,
> I keep testing the automated compilation option [1] the compilation gave
> me error ☹.
> I have left the log of the compilation here [2] but I attach the error:
>
> <<<
> ...
> main:
> Copying 1 file to
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src\royale-asjs\examples\native\USStatesMap\bin\js-debug
> Copying 1 file to
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src\royale-asjs\examples\native\USStatesMap\bin\js-release
>
> main:
>
> build_maven:
> Path is C:\Program Files (x86)\Common
> Files\Oracle\Java\javapath;D:\Apache;C:\Program
> Files\Java\jdk1.8.0_281\bin;D:\Apache\apache-ant-1.10.13\bin;D:\Apache\apache-maven-3.9.1\bin;D:\app\client\hiedra\product\19.0.0\client_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program
> Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program
> Files\dotnet\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program
> Files\Git\cmd;C:\Users\hiedra\AppData\Local\Programs\Microsoft VS
> Code;C:\Program Files\Microsoft SQL Server\Client
> SDK\ODBC\170\Tools\Binn\;C:\Program
> Files\PowerShell\7-preview\preview;C:\Program Files
> (x86)\Yarn\bin\;D:\Apache\HaxeToolkit\haxe;D:\Apache\HaxeToolkit\neko;C:\Program
> Files\nodejs\;C:\Program Files (x86)\Intel\Intel(R) Management Engine
> Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine
> Components\DAL;C:\Program Files (x86)\Pulse
> Secure\VC142.CRT\X64\;C:\Program Files (x86)\Pulse
> Secure\VC142.CRT\X86\;C:\Program Files\Microsoft SQL
> Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL
> Server\130\Tools\Binn\;C:\Program Files
> (x86)\GnuPG\bin;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:\Users\hiedra\AppData\Local\GitHubDesktop\bin;C:\Users\hiedra\.dotnet\tools;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:\Users\hiedra\AppData\Local\Programs\Microsoft
> VS
> Code\bin;C:\Users\hiedra\AppData\Local\Yarn\bin;C:\Users\hiedra\AppData\Roaming\npm
>
> BUILD FAILED
>
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:796: The
> following error occurred while executing this line:
>
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:809: exec
> returned: 1
>
> Total time: 39 minutes 52 seconds
> >>>
>
> The error occurs in the Maven compilation task (it's in the path, could it
> be because of the maven version?):
>
> >>>
> ...
> 
>  value="-Poption-with-swf"
> else="-Ddummy=true">
> 
> 
>  value="-Pwith-examples,with-distribution,option-with-swf"
> else="-Pwith-examples,with-distribution">
> 
> 
> Path is ${env.Path}
>
> -- >>> inputstring="Yes">
> 
> 
> 
> 
>  dir="${basedir}/${maven.package.url.name}/royale-typedefs"
> failonerror="true" >
> 
> 
> 
>  dir="${basedir}/${maven.package.url.name}/royale-asjs"
> failonerror="true" inputstri

RE: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Maria Jose Esteve]

Hi, 
I keep testing the automated compilation option [1] the compilation gave me 
error ☹.
I have left the log of the compilation here [2] but I attach the error:

<<<
...
main:
Copying 1 file to 
D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src\royale-asjs\examples\native\USStatesMap\bin\js-debug
Copying 1 file to 
D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src\royale-asjs\examples\native\USStatesMap\bin\js-release

main:

build_maven:
Path is C:\Program Files (x86)\Common 
Files\Oracle\Java\javapath;D:\Apache;C:\Program 
Files\Java\jdk1.8.0_281\bin;D:\Apache\apache-ant-1.10.13\bin;D:\Apache\apache-maven-3.9.1\bin;D:\app\client\hiedra\product\19.0.0\client_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program
 Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program 
Files\dotnet\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program
 Files\Git\cmd;C:\Users\hiedra\AppData\Local\Programs\Microsoft VS 
Code;C:\Program Files\Microsoft SQL Server\Client 
SDK\ODBC\170\Tools\Binn\;C:\Program 
Files\PowerShell\7-preview\preview;C:\Program Files 
(x86)\Yarn\bin\;D:\Apache\HaxeToolkit\haxe;D:\Apache\HaxeToolkit\neko;C:\Program
 Files\nodejs\;C:\Program Files (x86)\Intel\Intel(R) Management Engine 
Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine 
Components\DAL;C:\Program Files (x86)\Pulse Secure\VC142.CRT\X64\;C:\Program 
Files (x86)\Pulse Secure\VC142.CRT\X86\;C:\Program Files\Microsoft SQL 
Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL 
Server\130\Tools\Binn\;C:\Program Files 
(x86)\GnuPG\bin;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:\Users\hiedra\AppData\Local\GitHubDesktop\bin;C:\Users\hiedra\.dotnet\tools;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:\Users\hiedra\AppData\Local\Programs\Microsoft
 VS 
Code\bin;C:\Users\hiedra\AppData\Local\Yarn\bin;C:\Users\hiedra\AppData\Roaming\npm

BUILD FAILED
D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:796: The 
following error occurred while executing this line:
D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:809: 
exec returned: 1

Total time: 39 minutes 52 seconds
>>>

The error occurs in the Maven compilation task (it's in the path, could it be 
because of the maven version?):

>>>
...







Path is ${env.Path}

-- >>>














...
<<<

I have a question about licenses... Yishay has no anomalies in this regard but 
I have an unapproved license:
Unapproved licenses:
 
D:/Develop_Royale/Projects/Royale-SDK/0.9.10/apache-royale-0.9.10-bin-js-swf/royale-asjs/js/lib/royaleunit/dom4j-LICENSE.txt
How can I fix it?

[1] https://dist.apache.org/repos/dist/dev/royale/0.9.10/rc4/ApproveRoyale.xml 
y ejecutando el script:
   ant -e -f ApproveRoyale.xml -Drelease.version=0.9.10 -Drc=4
[2] 
https://drive.google.com/file/d/1jCgS51cgtRSSuh11UJUxzdEaburpDdpF/view?usp=share_link

Hiedra

-Mensaje original-
De: Yishay Weiss  
Enviado el: sábado, 13 de mayo de 2023 19:36
Para: dev@royale.apache.org
Asunto: [DISCUSS] Release Apache Royale 0.9.10 RC4

This is the discussion thread.