subject:"RE\: \[DISCUSS\] Discuss Release Apache Royale 0.9.7"

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-13 Thread Alex Harui

In releasecandidate.xml, the "release" target tries to run steps 46-100+.  
Helps me reduce typographical errors and missing steps.

We have always merged the release branch into dev, and the tag into master.  
The releasecandidate.xml does that.

Your experience with build-tools is different because we did not use a release 
branch.  We do not run into the versioning issue that Chris is concerned about 
because Maven takes care of the versioning for us when we use release branches, 
in the following way:

1) Before we cut the release branch, we just had:
Develop: 0.9.7-SNAPSHOT

2) When Maven cuts the release branch we get
Develop: 0.9.8-SNAPSHOT
Release/0.9.7: 0.9.7-SNAPSHOT

3) When Maven runs prepare/perform on the release branch we get:
Develop: 0.9.8-SNAPSHOT
Release Tag: 0.9.7
Release/0.9.7: 0.9.8-SNAPSHOT

And that's why we merge the tag into master and the branch into develop without 
version issue.

-Alex


On 5/13/20, 8:29 AM, "Yishay Weiss"  wrote:

I’m trying to understand the general case. If the version numbers are 
different then we’ll have conflicts which will need to be resolved. Why is that 
a problem?

From: Christofer Dutz<mailto:christofer.d...@c-ware.de>
Sent: Wednesday, May 13, 2020 6:09 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
    Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

I did mention that this issue in your case probably doesn't occur.

"Hope that explains ... in this case it probably wouldn't matter as both 
rel as develop are on the same version (which is not ideal)"

But I thought if you folks are defining the steps for future RMs, then I 
should point this out as this will become an issue as soon as you start using 
real version numbers (not starting at the second level of the version range)

Chris


Am 13.05.20, 16:33 schrieb "Yishay Weiss" :

That email came out muddled. The first sentence should be:

I made a local no-commit merge and looked at your explanation, and I 
don’t see the issue.

From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Wednesday, May 13, 2020 5:01 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
    Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

Hi Chris,

Making a local no-commit merge on and looked at your explanation I 
don’t see the issue. There would be a conflict which needs to be resolved to 
include the develop contents. I was worried that release poms would add the 
wrong version to develop automatically, but from what I see that wouldn’t 
happen without a conflict.

What am I missing?

Thanks.

From: Christofer Dutz<mailto:christofer.d...@c-ware.de>
Sent: Wednesday, May 13, 2020 12:29 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Hi Yishay,

Exactly ... perhaps a little explanation on what would usually happen:

develop is on 1.2.0-SNAPSHOT

When creating the release branch we have this:

develop is on 1.3.0-SNAPSHOT
rel/1.2 is on 1.2.0-SNAPSHOT

Now on "release cutting day" after cutting the release:

develop is on 1.3.0-SNAPSHOT
rel/1.2 is on 1.2.1-SNAPSHOT

As the change to 1.2.1-SNAPSHOT is newer than the 1.3.0-SNAPSHOT 
change, when you merge the release branch back to develop you would make this

develop 1.2.1-SNAPSHOT

Hope that explains ... in this case it probably wouldn't matter as both 
rel as develop are on the same version (which is not ideal)

Chris



Am 13.05.20, 11:21 schrieb "Yishay Weiss" :

So in other words, you’re suggesting to cherry-pick the fixes in 
release, rather than merging? I think that makes sense. Piotr, do you remember 
what your strategy was for 0.9.6?

From: Christofer Dutz<mailto:christofer.d...@c-ware.de>
Sent: Wednesday, May 13, 2020 12:13 PM
        To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Hi Yisahy,

I don’t think you should merge the release branch into dev … this 
will mess up the versions of all modules quite a bit (Even if in this case it 
might probably not matter) but as soon as the 1.0.0 is out it will.

For most projects it’s the usual thing to merge the release tag 
(not the branch) to master and leave the release branch open for future bugfix 
releases without merging back to develop.

Chris


Von: Yishay Weiss 
Antworten an: "dev@royale.apache.org"

RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-13 Thread Yishay Weiss

I’m trying to understand the general case. If the version numbers are different 
then we’ll have conflicts which will need to be resolved. Why is that a problem?

From: Christofer Dutz<mailto:christofer.d...@c-ware.de>
Sent: Wednesday, May 13, 2020 6:09 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

I did mention that this issue in your case probably doesn't occur.

"Hope that explains ... in this case it probably wouldn't matter as both rel as 
develop are on the same version (which is not ideal)"

But I thought if you folks are defining the steps for future RMs, then I should 
point this out as this will become an issue as soon as you start using real 
version numbers (not starting at the second level of the version range)

Chris

Am 13.05.20, 16:33 schrieb "Yishay Weiss" :

That email came out muddled. The first sentence should be:

I made a local no-commit merge and looked at your explanation, and I don’t 
see the issue.

From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Wednesday, May 13, 2020 5:01 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

Hi Chris,

Making a local no-commit merge on and looked at your explanation I don’t 
see the issue. There would be a conflict which needs to be resolved to include 
the develop contents. I was worried that release poms would add the wrong 
version to develop automatically, but from what I see that wouldn’t happen 
without a conflict.

What am I missing?

Thanks.

From: Christofer Dutz<mailto:christofer.d...@c-ware.de>
Sent: Wednesday, May 13, 2020 12:29 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
    Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Hi Yishay,

Exactly ... perhaps a little explanation on what would usually happen:

develop is on 1.2.0-SNAPSHOT

When creating the release branch we have this:

develop is on 1.3.0-SNAPSHOT
rel/1.2 is on 1.2.0-SNAPSHOT

Now on "release cutting day" after cutting the release:

develop is on 1.3.0-SNAPSHOT
rel/1.2 is on 1.2.1-SNAPSHOT

As the change to 1.2.1-SNAPSHOT is newer than the 1.3.0-SNAPSHOT change, 
when you merge the release branch back to develop you would make this

develop 1.2.1-SNAPSHOT

Hope that explains ... in this case it probably wouldn't matter as both rel 
as develop are on the same version (which is not ideal)

Chris

Am 13.05.20, 11:21 schrieb "Yishay Weiss" :

So in other words, you’re suggesting to cherry-pick the fixes in 
release, rather than merging? I think that makes sense. Piotr, do you remember 
what your strategy was for 0.9.6?

From: Christofer Dutz<mailto:christofer.d...@c-ware.de>
Sent: Wednesday, May 13, 2020 12:13 PM
    To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Hi Yisahy,

I don’t think you should merge the release branch into dev … this will 
mess up the versions of all modules quite a bit (Even if in this case it might 
probably not matter) but as soon as the 1.0.0 is out it will.

For most projects it’s the usual thing to merge the release tag (not 
the branch) to master and leave the release branch open for future bugfix 
releases without merging back to develop.

Chris

Von: Yishay Weiss 
Antworten an: "dev@royale.apache.org" 
        Datum: Mittwoch, 13. Mai 2020 um 10:01
    An: "dev@royale.apache.org" 
Betreff: RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

I’ve hit ‘release’ on Nexus and committed 0.9.7 to dist on svn. I 
suppose I should also merge release into dev. Do steps 46-106 [1] need to be 
performed manually?

[1] 
https://github.com/apache/royale-asjs/wiki/Task-List-For-Royale-Releases

From: Carlos Rovira 
    Sent: Wednesday, May 13, 2020 10:14:27 AM
To: Apache Royale Development 
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Hi Yishay

yes, please go ahead and announce.
thanks! :)

El mié., 13 may. 2020 a las 8:32, Yishay Weiss 
()
escribió:

> Carlos, I’d like to announce the vote. Does yours still stand?
>
> 
> From: Carlos Rovira 
        > Sent: Wednesday, May 13, 2020 8:58:19 AM
> To: Apache Royale Development 
> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7
>
> Hi Harbs,
>
> about OpenSans, don't think it was introduced by me. I can see it in
> MXRoyale, ASDoc and TourDeFlex examples, so mayb

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-13 Thread Christofer Dutz

I did mention that this issue in your case probably doesn't occur.

"Hope that explains ... in this case it probably wouldn't matter as both rel as 
develop are on the same version (which is not ideal)"

But I thought if you folks are defining the steps for future RMs, then I should 
point this out as this will become an issue as soon as you start using real 
version numbers (not starting at the second level of the version range)

Chris


Am 13.05.20, 16:33 schrieb "Yishay Weiss" :

That email came out muddled. The first sentence should be:

I made a local no-commit merge and looked at your explanation, and I don’t 
see the issue.

From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Wednesday, May 13, 2020 5:01 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
    Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

Hi Chris,

Making a local no-commit merge on and looked at your explanation I don’t 
see the issue. There would be a conflict which needs to be resolved to include 
the develop contents. I was worried that release poms would add the wrong 
version to develop automatically, but from what I see that wouldn’t happen 
without a conflict.

What am I missing?

Thanks.

From: Christofer Dutz<mailto:christofer.d...@c-ware.de>
Sent: Wednesday, May 13, 2020 12:29 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Hi Yishay,

Exactly ... perhaps a little explanation on what would usually happen:

develop is on 1.2.0-SNAPSHOT

When creating the release branch we have this:

develop is on 1.3.0-SNAPSHOT
rel/1.2 is on 1.2.0-SNAPSHOT

Now on "release cutting day" after cutting the release:

develop is on 1.3.0-SNAPSHOT
rel/1.2 is on 1.2.1-SNAPSHOT

As the change to 1.2.1-SNAPSHOT is newer than the 1.3.0-SNAPSHOT change, 
when you merge the release branch back to develop you would make this

develop 1.2.1-SNAPSHOT

Hope that explains ... in this case it probably wouldn't matter as both rel 
as develop are on the same version (which is not ideal)

Chris



Am 13.05.20, 11:21 schrieb "Yishay Weiss" :

So in other words, you’re suggesting to cherry-pick the fixes in 
release, rather than merging? I think that makes sense. Piotr, do you remember 
what your strategy was for 0.9.6?

From: Christofer Dutz<mailto:christofer.d...@c-ware.de>
Sent: Wednesday, May 13, 2020 12:13 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Hi Yisahy,

I don’t think you should merge the release branch into dev … this will 
mess up the versions of all modules quite a bit (Even if in this case it might 
probably not matter) but as soon as the 1.0.0 is out it will.

For most projects it’s the usual thing to merge the release tag (not 
the branch) to master and leave the release branch open for future bugfix 
releases without merging back to develop.

Chris


Von: Yishay Weiss 
Antworten an: "dev@royale.apache.org" 
Datum: Mittwoch, 13. Mai 2020 um 10:01
    An: "dev@royale.apache.org" 
Betreff: RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

I’ve hit ‘release’ on Nexus and committed 0.9.7 to dist on svn. I 
suppose I should also merge release into dev. Do steps 46-106 [1] need to be 
performed manually?


[1] 
https://github.com/apache/royale-asjs/wiki/Task-List-For-Royale-Releases


From: Carlos Rovira 
Sent: Wednesday, May 13, 2020 10:14:27 AM
    To: Apache Royale Development 
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Hi Yishay

yes, please go ahead and announce.
thanks! :)

El mié., 13 may. 2020 a las 8:32, Yishay Weiss 
()
escribió:

> Carlos, I’d like to announce the vote. Does yours still stand?
>
> 
> From: Carlos Rovira 
        > Sent: Wednesday, May 13, 2020 8:58:19 AM
> To: Apache Royale Development 
> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7
>
> Hi Harbs,
>
> about OpenSans, don't think it was introduced by me. I can see it in
> MXRoyale, ASDoc and TourDeFlex examples, so maybe was Alex? really 
don't
> know. TDJ uses Lato Font instead.
>
> I added both to NOTICE file
>
> Thanks
>
>
>
>
>
>
> El mié., 13 may. 2020 a las 7:28, Carlos Rovira 
( >)
> escribió:
>
> > Hi Harbs,
> >
> > we have Maven

RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-13 Thread Yishay Weiss

Hi Chris,

Making a local no-commit merge on and looked at your explanation I don’t see 
the issue. There would be a conflict which needs to be resolved to include the 
develop contents. I was worried that release poms would add the wrong version 
to develop automatically, but from what I see that wouldn’t happen without a 
conflict.

What am I missing?

Thanks.

From: Christofer Dutz<mailto:christofer.d...@c-ware.de>
Sent: Wednesday, May 13, 2020 12:29 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Hi Yishay,

Exactly ... perhaps a little explanation on what would usually happen:

develop is on 1.2.0-SNAPSHOT

When creating the release branch we have this:

develop is on 1.3.0-SNAPSHOT
rel/1.2 is on 1.2.0-SNAPSHOT

Now on "release cutting day" after cutting the release:

develop is on 1.3.0-SNAPSHOT
rel/1.2 is on 1.2.1-SNAPSHOT

As the change to 1.2.1-SNAPSHOT is newer than the 1.3.0-SNAPSHOT change, when 
you merge the release branch back to develop you would make this

develop 1.2.1-SNAPSHOT

Hope that explains ... in this case it probably wouldn't matter as both rel as 
develop are on the same version (which is not ideal)

Chris

Am 13.05.20, 11:21 schrieb "Yishay Weiss" :

So in other words, you’re suggesting to cherry-pick the fixes in release, 
rather than merging? I think that makes sense. Piotr, do you remember what your 
strategy was for 0.9.6?

From: Christofer Dutz<mailto:christofer.d...@c-ware.de>
Sent: Wednesday, May 13, 2020 12:13 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Hi Yisahy,

I don’t think you should merge the release branch into dev … this will mess 
up the versions of all modules quite a bit (Even if in this case it might 
probably not matter) but as soon as the 1.0.0 is out it will.

For most projects it’s the usual thing to merge the release tag (not the 
branch) to master and leave the release branch open for future bugfix releases 
without merging back to develop.

Chris

Von: Yishay Weiss 
Antworten an: "dev@royale.apache.org" 
Datum: Mittwoch, 13. Mai 2020 um 10:01
An: "dev@royale.apache.org" 
Betreff: RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

I’ve hit ‘release’ on Nexus and committed 0.9.7 to dist on svn. I suppose I 
should also merge release into dev. Do steps 46-106 [1] need to be performed 
manually?

[1] https://github.com/apache/royale-asjs/wiki/Task-List-For-Royale-Releases

From: Carlos Rovira 
Sent: Wednesday, May 13, 2020 10:14:27 AM
To: Apache Royale Development 
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Hi Yishay

yes, please go ahead and announce.
thanks! :)

El mié., 13 may. 2020 a las 8:32, Yishay Weiss ()
escribió:

> Carlos, I’d like to announce the vote. Does yours still stand?
>
> 
> From: Carlos Rovira 
> Sent: Wednesday, May 13, 2020 8:58:19 AM
    > To: Apache Royale Development 
> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7
>
> Hi Harbs,
>
> about OpenSans, don't think it was introduced by me. I can see it in
> MXRoyale, ASDoc and TourDeFlex examples, so maybe was Alex? really don't
> know. TDJ uses Lato Font instead.
>
> I added both to NOTICE file
>
> Thanks
>
>
>
>
>
>
> El mié., 13 may. 2020 a las 7:28, Carlos Rovira ( >)
> escribió:
>
> > Hi Harbs,
> >
> > we have Maven Wrapper in all our repos (mvnw). From the source:
> >
> > "The Maven Wrapper is an easy way to ensure a user of your Maven build
> > has everything necessary to run your Maven build."
> >
> > [1] https://github.com/takari/maven-wrapper
> >
> > El mar., 12 may. 2020 a las 19:26, Harbs ()
> > escribió:
> >
> >> And now I just discovered I never installed Maven on this machine… :-(
> >>
> >> Oy!
> >>
> >> > On May 12, 2020, at 8:09 PM, Harbs  wrote:
> >> >
> >> > and I got past that point...
> >>
> >>
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
    > >
    > >
    >
> --
> Carlos Rovira
> http://about.me/carlosrovira
>

--
Carlos Rovira
http://about.me/carlosrovira
From: Carlos Rovira<mailto:carlosrov...@apache.org>
Sent: Wednesday, May 13, 2020 10:14 AM
To: Apache Royale Development<mailto:dev@royale.apache.org>
Subjec

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-13 Thread Christofer Dutz

Hi Yishay,

Exactly ... perhaps a little explanation on what would usually happen:

develop is on 1.2.0-SNAPSHOT

When creating the release branch we have this:

develop is on 1.3.0-SNAPSHOT
rel/1.2 is on 1.2.0-SNAPSHOT

Now on "release cutting day" after cutting the release:

develop is on 1.3.0-SNAPSHOT
rel/1.2 is on 1.2.1-SNAPSHOT

As the change to 1.2.1-SNAPSHOT is newer than the 1.3.0-SNAPSHOT change, when 
you merge the release branch back to develop you would make this 

develop 1.2.1-SNAPSHOT

Hope that explains ... in this case it probably wouldn't matter as both rel as 
develop are on the same version (which is not ideal)

Chris

Am 13.05.20, 11:21 schrieb "Yishay Weiss" :

So in other words, you’re suggesting to cherry-pick the fixes in release, 
rather than merging? I think that makes sense. Piotr, do you remember what your 
strategy was for 0.9.6?

From: Christofer Dutz<mailto:christofer.d...@c-ware.de>
Sent: Wednesday, May 13, 2020 12:13 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
    Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Hi Yisahy,

I don’t think you should merge the release branch into dev … this will mess 
up the versions of all modules quite a bit (Even if in this case it might 
probably not matter) but as soon as the 1.0.0 is out it will.

For most projects it’s the usual thing to merge the release tag (not the 
branch) to master and leave the release branch open for future bugfix releases 
without merging back to develop.

Chris

Von: Yishay Weiss 
Antworten an: "dev@royale.apache.org" 
Datum: Mittwoch, 13. Mai 2020 um 10:01
An: "dev@royale.apache.org" 
Betreff: RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

I’ve hit ‘release’ on Nexus and committed 0.9.7 to dist on svn. I suppose I 
should also merge release into dev. Do steps 46-106 [1] need to be performed 
manually?

[1] https://github.com/apache/royale-asjs/wiki/Task-List-For-Royale-Releases

From: Carlos Rovira 
Sent: Wednesday, May 13, 2020 10:14:27 AM
    To: Apache Royale Development 
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Hi Yishay

yes, please go ahead and announce.
thanks! :)

El mié., 13 may. 2020 a las 8:32, Yishay Weiss ()
escribió:

> Carlos, I’d like to announce the vote. Does yours still stand?
>
> 
> From: Carlos Rovira 
> Sent: Wednesday, May 13, 2020 8:58:19 AM
> To: Apache Royale Development 
> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7
>
> Hi Harbs,
>
> about OpenSans, don't think it was introduced by me. I can see it in
> MXRoyale, ASDoc and TourDeFlex examples, so maybe was Alex? really don't
> know. TDJ uses Lato Font instead.
>
> I added both to NOTICE file
>
> Thanks
>
>
>
>
>
>
> El mié., 13 may. 2020 a las 7:28, Carlos Rovira ( >)
> escribió:
>
> > Hi Harbs,
> >
> > we have Maven Wrapper in all our repos (mvnw). From the source:
> >
> > "The Maven Wrapper is an easy way to ensure a user of your Maven build
> > has everything necessary to run your Maven build."
> >
> > [1] https://github.com/takari/maven-wrapper
> >
> > El mar., 12 may. 2020 a las 19:26, Harbs ()
> > escribió:
> >
> >> And now I just discovered I never installed Maven on this machine… :-(
> >>
> >> Oy!
> >>
> >> > On May 12, 2020, at 8:09 PM, Harbs  wrote:
> >> >
> >> > and I got past that point...
> >>
> >>
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
    > >
> >
    >
> --
> Carlos Rovira
> http://about.me/carlosrovira
>

--
Carlos Rovira
http://about.me/carlosrovira
From: Carlos Rovira<mailto:carlosrov...@apache.org>
Sent: Wednesday, May 13, 2020 10:14 AM
To: Apache Royale Development<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Hi Yishay

    yes, please go ahead and announce.
    thanks! :)

El mié., 13 may. 2020 a las 8:32, Yishay Weiss ()
escribió:

> Carlos, I’d like to announce the vote. Does yours still stand?
>
> 
> From: Carlos Rovira 
> Sent: Wednesday, May 13, 2020 8:58:19 AM
> To: Apache Royale Development 
> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7
>
> Hi Harbs,
>
> about OpenSans, don't think it was introduced by

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-13 Thread Christofer Dutz

Hi Yisahy,

I don’t think you should merge the release branch into dev … this will mess up 
the versions of all modules quite a bit (Even if in this case it might probably 
not matter) but as soon as the 1.0.0 is out it will.

For most projects it’s the usual thing to merge the release tag (not the 
branch) to master and leave the release branch open for future bugfix releases 
without merging back to develop.

Chris


Von: Yishay Weiss 
Antworten an: "dev@royale.apache.org" 
Datum: Mittwoch, 13. Mai 2020 um 10:01
An: "dev@royale.apache.org" 
Betreff: RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

I’ve hit ‘release’ on Nexus and committed 0.9.7 to dist on svn. I suppose I 
should also merge release into dev. Do steps 46-106 [1] need to be performed 
manually?


[1] https://github.com/apache/royale-asjs/wiki/Task-List-For-Royale-Releases


From: Carlos Rovira 
Sent: Wednesday, May 13, 2020 10:14:27 AM
To: Apache Royale Development 
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Hi Yishay

yes, please go ahead and announce.
thanks! :)

El mié., 13 may. 2020 a las 8:32, Yishay Weiss ()
escribió:

> Carlos, I’d like to announce the vote. Does yours still stand?
>
> 
> From: Carlos Rovira 
> Sent: Wednesday, May 13, 2020 8:58:19 AM
> To: Apache Royale Development 
> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7
>
> Hi Harbs,
>
> about OpenSans, don't think it was introduced by me. I can see it in
> MXRoyale, ASDoc and TourDeFlex examples, so maybe was Alex? really don't
> know. TDJ uses Lato Font instead.
>
> I added both to NOTICE file
>
> Thanks
>
>
>
>
>
>
> El mié., 13 may. 2020 a las 7:28, Carlos Rovira ( >)
> escribió:
>
> > Hi Harbs,
> >
> > we have Maven Wrapper in all our repos (mvnw). From the source:
> >
> > "The Maven Wrapper is an easy way to ensure a user of your Maven build
> > has everything necessary to run your Maven build."
> >
> > [1] https://github.com/takari/maven-wrapper
> >
> > El mar., 12 may. 2020 a las 19:26, Harbs ()
> > escribió:
> >
> >> And now I just discovered I never installed Maven on this machine… :-(
> >>
> >> Oy!
> >>
> >> > On May 12, 2020, at 8:09 PM, Harbs  wrote:
> >> >
> >> > and I got past that point...
> >>
> >>
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


--
Carlos Rovira
http://about.me/carlosrovira
From: Carlos Rovira<mailto:carlosrov...@apache.org>
Sent: Wednesday, May 13, 2020 10:14 AM
To: Apache Royale Development<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Hi Yishay

yes, please go ahead and announce.
thanks! :)

El mié., 13 may. 2020 a las 8:32, Yishay Weiss ()
escribió:

> Carlos, I’d like to announce the vote. Does yours still stand?
>
> 
> From: Carlos Rovira 
> Sent: Wednesday, May 13, 2020 8:58:19 AM
> To: Apache Royale Development 
> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7
>
> Hi Harbs,
>
> about OpenSans, don't think it was introduced by me. I can see it in
> MXRoyale, ASDoc and TourDeFlex examples, so maybe was Alex? really don't
> know. TDJ uses Lato Font instead.
>
> I added both to NOTICE file
>
> Thanks
>
>
>
>
>
>
> El mié., 13 may. 2020 a las 7:28, Carlos Rovira ( >)
> escribió:
>
> > Hi Harbs,
> >
> > we have Maven Wrapper in all our repos (mvnw). From the source:
> >
> > "The Maven Wrapper is an easy way to ensure a user of your Maven build
> > has everything necessary to run your Maven build."
> >
> > [1] https://github.com/takari/maven-wrapper
> >
> > El mar., 12 may. 2020 a las 19:26, Harbs ()
> > escribió:
> >
> >> And now I just discovered I never installed Maven on this machine… :-(
> >>
> >> Oy!
> >>
> >> > On May 12, 2020, at 8:09 PM, Harbs  wrote:
> >> >
> >> > and I got past that point...
> >>
> >>
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


--
Carlos Rovira
http://about.me/carlosrovira

RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-13 Thread Yishay Weiss

I’ve hit ‘release’ on Nexus and committed 0.9.7 to dist on svn. I suppose I 
should also merge release into dev. Do steps 46-106 [1] need to be performed 
manually?


[1] https://github.com/apache/royale-asjs/wiki/Task-List-For-Royale-Releases


From: Carlos Rovira 
Sent: Wednesday, May 13, 2020 10:14:27 AM
To: Apache Royale Development 
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Hi Yishay

yes, please go ahead and announce.
thanks! :)

El mié., 13 may. 2020 a las 8:32, Yishay Weiss ()
escribió:

> Carlos, I’d like to announce the vote. Does yours still stand?
>
> 
> From: Carlos Rovira 
> Sent: Wednesday, May 13, 2020 8:58:19 AM
> To: Apache Royale Development 
> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7
>
> Hi Harbs,
>
> about OpenSans, don't think it was introduced by me. I can see it in
> MXRoyale, ASDoc and TourDeFlex examples, so maybe was Alex? really don't
> know. TDJ uses Lato Font instead.
>
> I added both to NOTICE file
>
> Thanks
>
>
>
>
>
>
> El mié., 13 may. 2020 a las 7:28, Carlos Rovira ( >)
> escribió:
>
> > Hi Harbs,
> >
> > we have Maven Wrapper in all our repos (mvnw). From the source:
> >
> > "The Maven Wrapper is an easy way to ensure a user of your Maven build
> > has everything necessary to run your Maven build."
> >
> > [1] https://github.com/takari/maven-wrapper
> >
> > El mar., 12 may. 2020 a las 19:26, Harbs ()
> > escribió:
> >
> >> And now I just discovered I never installed Maven on this machine… :-(
> >>
> >> Oy!
> >>
> >> > On May 12, 2020, at 8:09 PM, Harbs  wrote:
> >> >
> >> > and I got past that point...
> >>
> >>
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


--
Carlos Rovira
http://about.me/carlosrovira
From: Carlos Rovira<mailto:carlosrov...@apache.org>
Sent: Wednesday, May 13, 2020 10:14 AM
To: Apache Royale Development<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Hi Yishay

yes, please go ahead and announce.
thanks! :)

El mié., 13 may. 2020 a las 8:32, Yishay Weiss ()
escribió:

> Carlos, I’d like to announce the vote. Does yours still stand?
>
> 
> From: Carlos Rovira 
> Sent: Wednesday, May 13, 2020 8:58:19 AM
> To: Apache Royale Development 
> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7
>
> Hi Harbs,
>
> about OpenSans, don't think it was introduced by me. I can see it in
> MXRoyale, ASDoc and TourDeFlex examples, so maybe was Alex? really don't
> know. TDJ uses Lato Font instead.
>
> I added both to NOTICE file
>
> Thanks
>
>
>
>
>
>
> El mié., 13 may. 2020 a las 7:28, Carlos Rovira ( >)
> escribió:
>
> > Hi Harbs,
> >
> > we have Maven Wrapper in all our repos (mvnw). From the source:
> >
> > "The Maven Wrapper is an easy way to ensure a user of your Maven build
> > has everything necessary to run your Maven build."
> >
> > [1] https://github.com/takari/maven-wrapper
> >
> > El mar., 12 may. 2020 a las 19:26, Harbs ()
> > escribió:
> >
> >> And now I just discovered I never installed Maven on this machine… :-(
> >>
> >> Oy!
> >>
> >> > On May 12, 2020, at 8:09 PM, Harbs  wrote:
> >> >
> >> > and I got past that point...
> >>
> >>
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


--
Carlos Rovira
http://about.me/carlosrovira

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-13 Thread Carlos Rovira

Hi Yishay

yes, please go ahead and announce.
thanks! :)

El mié., 13 may. 2020 a las 8:32, Yishay Weiss ()
escribió:

> Carlos, I’d like to announce the vote. Does yours still stand?
>
> 
> From: Carlos Rovira 
> Sent: Wednesday, May 13, 2020 8:58:19 AM
> To: Apache Royale Development 
> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7
>
> Hi Harbs,
>
> about OpenSans, don't think it was introduced by me. I can see it in
> MXRoyale, ASDoc and TourDeFlex examples, so maybe was Alex? really don't
> know. TDJ uses Lato Font instead.
>
> I added both to NOTICE file
>
> Thanks
>
>
>
>
>
>
> El mié., 13 may. 2020 a las 7:28, Carlos Rovira ( >)
> escribió:
>
> > Hi Harbs,
> >
> > we have Maven Wrapper in all our repos (mvnw). From the source:
> >
> > "The Maven Wrapper is an easy way to ensure a user of your Maven build
> > has everything necessary to run your Maven build."
> >
> > [1] https://github.com/takari/maven-wrapper
> >
> > El mar., 12 may. 2020 a las 19:26, Harbs ()
> > escribió:
> >
> >> And now I just discovered I never installed Maven on this machine… :-(
> >>
> >> Oy!
> >>
> >> > On May 12, 2020, at 8:09 PM, Harbs  wrote:
> >> >
> >> > and I got past that point...
> >>
> >>
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 
Carlos Rovira
http://about.me/carlosrovira

RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-13 Thread Yishay Weiss

Carlos, I’d like to announce the vote. Does yours still stand?


From: Carlos Rovira 
Sent: Wednesday, May 13, 2020 8:58:19 AM
To: Apache Royale Development 
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Hi Harbs,

about OpenSans, don't think it was introduced by me. I can see it in
MXRoyale, ASDoc and TourDeFlex examples, so maybe was Alex? really don't
know. TDJ uses Lato Font instead.

I added both to NOTICE file

Thanks






El mié., 13 may. 2020 a las 7:28, Carlos Rovira ()
escribió:

> Hi Harbs,
>
> we have Maven Wrapper in all our repos (mvnw). From the source:
>
> "The Maven Wrapper is an easy way to ensure a user of your Maven build
> has everything necessary to run your Maven build."
>
> [1] https://github.com/takari/maven-wrapper
>
> El mar., 12 may. 2020 a las 19:26, Harbs ()
> escribió:
>
>> And now I just discovered I never installed Maven on this machine… :-(
>>
>> Oy!
>>
>> > On May 12, 2020, at 8:09 PM, Harbs  wrote:
>> >
>> > and I got past that point...
>>
>>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

--
Carlos Rovira
http://about.me/carlosrovira

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-12 Thread Carlos Rovira

Hi Harbs,

about OpenSans, don't think it was introduced by me. I can see it in
MXRoyale, ASDoc and TourDeFlex examples, so maybe was Alex? really don't
know. TDJ uses Lato Font instead.

I added both to NOTICE file

Thanks






El mié., 13 may. 2020 a las 7:28, Carlos Rovira ()
escribió:

> Hi Harbs,
>
> we have Maven Wrapper in all our repos (mvnw). From the source:
>
> "The Maven Wrapper is an easy way to ensure a user of your Maven build
> has everything necessary to run your Maven build."
>
> [1] https://github.com/takari/maven-wrapper
>
> El mar., 12 may. 2020 a las 19:26, Harbs ()
> escribió:
>
>> And now I just discovered I never installed Maven on this machine… :-(
>>
>> Oy!
>>
>> > On May 12, 2020, at 8:09 PM, Harbs  wrote:
>> >
>> > and I got past that point...
>>
>>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

-- 
Carlos Rovira
http://about.me/carlosrovira

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-12 Thread Carlos Rovira

Hi Harbs,

we have Maven Wrapper in all our repos (mvnw). From the source:

"The Maven Wrapper is an easy way to ensure a user of your Maven build has
everything necessary to run your Maven build."

[1] https://github.com/takari/maven-wrapper

El mar., 12 may. 2020 a las 19:26, Harbs () escribió:

> And now I just discovered I never installed Maven on this machine… :-(
>
> Oy!
>
> > On May 12, 2020, at 8:09 PM, Harbs  wrote:
> >
> > and I got past that point...
>
>

-- 
Carlos Rovira
http://about.me/carlosrovira

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-12 Thread Harbs

Scratch that. It does have the fix. PEBKAC...

> On May 12, 2020, at 10:54 PM, Harbs  wrote:
> 
> OK. I got the whole thing to build.
> 
> It looks like the biggest issue is that the XML fix that should be in the 
> release branch does not seem top have made it into the RC.
> 
> I don’t think I can vote +1 with XML broken.
> 
>> On May 12, 2020, at 8:26 PM, Harbs > > wrote:
>> 
>> And now I just discovered I never installed Maven on this machine… :-(
>> 
>> Oy!
>> 
>>> On May 12, 2020, at 8:09 PM, Harbs >> > wrote:
>>> 
>>> and I got past that point...
>> 
>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-12 Thread Harbs

OK. I got the whole thing to build.

It looks like the biggest issue is that the XML fix that should be in the 
release branch does not seem top have made it into the RC.

I don’t think I can vote +1 with XML broken.

> On May 12, 2020, at 8:26 PM, Harbs  wrote:
> 
> And now I just discovered I never installed Maven on this machine… :-(
> 
> Oy!
> 
>> On May 12, 2020, at 8:09 PM, Harbs > > wrote:
>> 
>> and I got past that point...
>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-12 Thread Harbs

I think this was it.

I got rid of most of my env vars and I got past that poi

> On May 12, 2020, at 7:43 PM, Josh Tynjala  wrote:
> 
> That failure could happen if you were accidentally using royale-compiler
> 0.9.8-SNAPSHOT with royale-asjs 0.9.7.

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-12 Thread Harbs

It’s failing on the last line here:

public function testGetDynamicFields():void
{

const emptyArray:Array = [];
const singleDynField:Array = ['test'];
assertTrue( contentStringsMatch(getDynamicFields(Object), 
emptyArray), "dynamic fields should match reference list");
Object['test'] = true;
assertTrue( contentStringsMatch(getDynamicFields(Object), 
singleDynField), "dynamic fields should match reference list");
delete Object['test'];

assertTrue( contentStringsMatch(getDynamicFields(TestClass1), 
emptyArray), "dynamic fields should match reference list");


> On May 12, 2020, at 7:43 PM, Josh Tynjala  wrote:
> 
> That failure could happen if you were accidentally using royale-compiler
> 0.9.8-SNAPSHOT with royale-asjs 0.9.7. I had to tweak one of the asserts in
> the  testGetDynamicFields() test, but that was after the release branches
> were made.
> 
> I guess it's possible that a different assert in that test is failing,
> though.
> 
> --
> Josh Tynjala
> Bowler Hat LLC 
> 
> 
> On Tue, May 12, 2020 at 8:50 AM Harbs  wrote:
> 
>> I think ant. Here’s more output:
>> 
>> Executing '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome'
>> with arguments:
>> 
>> '/Apache/approve_ant/apache-royale-0.9.7-src/royale-asjs/frameworks/js/projects/ReflectionJS/src/test/royale/target/bin/js-release/index.html'
>> 
>> The ' characters around the executable and arguments are
>> not part of the command.
>> 
>> Client connected.
>> Receiving data ...
>> Sending acknowledgement to player to start sending test data ...
>> 
>> RoyaleUnit test testGetDynamicFields in suite
>> flexUnitTests.reflection.ReflectionTesterTestDynamic failed.
>> 
>> Stopping server ...
>> End of test data reached, sending acknowledgement to player ...
>> Analyzing reports ...
>> 
>> Suite: flexUnitTests.reflection.ReflectionTesterTest
>> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.738 sec
>> Suite: flexUnitTests.reflection.ReflectionTesterNativeTypes
>> Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.476 sec
>> Suite: flexUnitTests.reflection.ReflectionTesterTestEdgeCases
>> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.615 sec
>> Suite: flexUnitTests.reflection.ReflectionTesterTestUseCache
>> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.123 sec
>> Suite: flexUnitTests.reflection.ReflectionTesterTestDynamic
>> Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.369 sec
>> Suite: flexUnitTests.reflection.ReflectionTesterTestAlias
>> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.123 sec
>> 
>> Results :
>> 
>> Tests run: 28, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.444 sec
>> 
>> JS-RELEASE TESTS FAILED
>> Running backup tests in js-debug build, because release build tests failed
>> OS: [Mac]
>> Local path to SWF was given and SWF property will be used.
>> Validating task attributes ...
>> Generating default values ...
>> Using the following settings for the test run:
>>ROYALE_HOME:
>> [/Apache/approve_ant/apache-royale-0.9.7-src/royale-asjs]
>>haltonfailure: [false]
>>headless: [false]
>>display: [99]
>>localTrusted: [true]
>>player: [html]
>>command: [/Applications/Google Chrome.app/Contents/MacOS/Google
>> Chrome]
>>port: [1024]
>>swf:
>> [/Apache/approve_ant/apache-royale-0.9.7-src/royale-asjs/frameworks/js/projects/ReflectionJS/src/test/royale/target/bin/js-debug/index.html]
>>timeout: [9ms]
>>toDir:
>> [/Apache/approve_ant/apache-royale-0.9.7-src/royale-asjs/frameworks/js/projects/ReflectionJS/src/test/royale/out]
>> Setting up server process ...
>> Entry
>> [/Apache/approve_ant/apache-royale-0.9.7-src/royale-asjs/frameworks/js/projects/ReflectionJS/src/test/royale/target/bin/js-debug]
>> already available in local trust file at
>> [/Users/harbs/Library/Preferences/Macromedia/Flash
>> Player/#Security/FlashPlayerTrust/royaleUnit.cfg].
>> Executing '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome'
>> with arguments:
>> 
>> '/Apache/approve_ant/apache-royale-0.9.7-src/royale-asjs/frameworks/js/projects/ReflectionJS/src/test/royale/target/bin/js-debug/index.html'
>> 
>> The ' characters around the executable and arguments are
>> not part of the command.
>> 
>> Starting server ...
>> Waiting for client connection ...
>> Client connected.
>> Receiving data ...
>> Sending acknowledgement to player to start sending test data ...
>> 
>> 
>> Stopping server ...
>> End of test data reached, sending acknowledgement to player ...
>> Analyzing reports ...
>> 
>> Suite: flexUnitTests.reflection.ReflectionTesterTest
>> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.738 sec
>> Suite: flexUnitTests.reflection.ReflectionTesterNativeTypes
>> Tests run: 12,

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-12 Thread Josh Tynjala

That failure could happen if you were accidentally using royale-compiler
0.9.8-SNAPSHOT with royale-asjs 0.9.7. I had to tweak one of the asserts in
the  testGetDynamicFields() test, but that was after the release branches
were made.

I guess it's possible that a different assert in that test is failing,
though.

--
Josh Tynjala
Bowler Hat LLC 


On Tue, May 12, 2020 at 8:50 AM Harbs  wrote:

> I think ant. Here’s more output:
>
> Executing '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome'
> with arguments:
>
> '/Apache/approve_ant/apache-royale-0.9.7-src/royale-asjs/frameworks/js/projects/ReflectionJS/src/test/royale/target/bin/js-release/index.html'
>
> The ' characters around the executable and arguments are
> not part of the command.
>
> Client connected.
> Receiving data ...
> Sending acknowledgement to player to start sending test data ...
>
> RoyaleUnit test testGetDynamicFields in suite
> flexUnitTests.reflection.ReflectionTesterTestDynamic failed.
>
> Stopping server ...
> End of test data reached, sending acknowledgement to player ...
> Analyzing reports ...
>
> Suite: flexUnitTests.reflection.ReflectionTesterTest
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.738 sec
> Suite: flexUnitTests.reflection.ReflectionTesterNativeTypes
> Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.476 sec
> Suite: flexUnitTests.reflection.ReflectionTesterTestEdgeCases
> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.615 sec
> Suite: flexUnitTests.reflection.ReflectionTesterTestUseCache
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.123 sec
> Suite: flexUnitTests.reflection.ReflectionTesterTestDynamic
> Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.369 sec
> Suite: flexUnitTests.reflection.ReflectionTesterTestAlias
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.123 sec
>
> Results :
>
> Tests run: 28, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.444 sec
>
> JS-RELEASE TESTS FAILED
> Running backup tests in js-debug build, because release build tests failed
> OS: [Mac]
> Local path to SWF was given and SWF property will be used.
> Validating task attributes ...
> Generating default values ...
> Using the following settings for the test run:
> ROYALE_HOME:
> [/Apache/approve_ant/apache-royale-0.9.7-src/royale-asjs]
> haltonfailure: [false]
> headless: [false]
> display: [99]
> localTrusted: [true]
> player: [html]
> command: [/Applications/Google Chrome.app/Contents/MacOS/Google
> Chrome]
> port: [1024]
> swf:
> [/Apache/approve_ant/apache-royale-0.9.7-src/royale-asjs/frameworks/js/projects/ReflectionJS/src/test/royale/target/bin/js-debug/index.html]
> timeout: [9ms]
> toDir:
> [/Apache/approve_ant/apache-royale-0.9.7-src/royale-asjs/frameworks/js/projects/ReflectionJS/src/test/royale/out]
> Setting up server process ...
> Entry
> [/Apache/approve_ant/apache-royale-0.9.7-src/royale-asjs/frameworks/js/projects/ReflectionJS/src/test/royale/target/bin/js-debug]
> already available in local trust file at
> [/Users/harbs/Library/Preferences/Macromedia/Flash
> Player/#Security/FlashPlayerTrust/royaleUnit.cfg].
> Executing '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome'
> with arguments:
>
> '/Apache/approve_ant/apache-royale-0.9.7-src/royale-asjs/frameworks/js/projects/ReflectionJS/src/test/royale/target/bin/js-debug/index.html'
>
> The ' characters around the executable and arguments are
> not part of the command.
>
> Starting server ...
> Waiting for client connection ...
> Client connected.
> Receiving data ...
> Sending acknowledgement to player to start sending test data ...
>
>
> Stopping server ...
> End of test data reached, sending acknowledgement to player ...
> Analyzing reports ...
>
> Suite: flexUnitTests.reflection.ReflectionTesterTest
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.738 sec
> Suite: flexUnitTests.reflection.ReflectionTesterNativeTypes
> Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.476 sec
> Suite: flexUnitTests.reflection.ReflectionTesterTestEdgeCases
> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.615 sec
> Suite: flexUnitTests.reflection.ReflectionTesterTestUseCache
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.123 sec
> Suite: flexUnitTests.reflection.ReflectionTesterTestDynamic
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.369 sec
> Suite: flexUnitTests.reflection.ReflectionTesterTestAlias
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.123 sec
>
> Results :
>
> Tests run: 28, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.444 sec
>
> Processing
> /Apache/approve_ant/apache-royale-0.9.7-src/royale-asjs/frameworks/js/projects/ReflectionJS/src/test/royale/out/TESTS-TestSuites.xml
> to

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-12 Thread Alex Harui

If you saved the output on the other machine, you can compare the output.  I 
don't know the order the tests are run, but I have plenty of .xml files in 
various "out" folders in the frameworks/projects.  If the release build didn't 
do the right thing ever, then it might be some issue with closure compiler.

HTH,
-Alex

On 5/12/20, 9:14 AM, "Harbs"  wrote:

I looked and I don’t see anything there. Not sure how the debug and release 
tests step on each other...

> On May 12, 2020, at 7:01 PM, Alex Harui  wrote:
> 
> I don't know RoyaleUnit that well, but I assume there are test results 
stored in a file to review.
> I have some in frameworks/projects/Reflection/src/test/royale/out

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-12 Thread Harbs

I looked and I don’t see anything there. Not sure how the debug and release 
tests step on each other...

> On May 12, 2020, at 7:01 PM, Alex Harui  wrote:
> 
> I don't know RoyaleUnit that well, but I assume there are test results stored 
> in a file to review.
> I have some in frameworks/projects/Reflection/src/test/royale/out

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-12 Thread Harbs

This is on a different machine.

I’m going to start from scratch again.

> On May 12, 2020, at 7:01 PM, Alex Harui  wrote:
> 
> Yes, that's the "ant all" build.  I'm a bit puzzled because if you were 
> running into issues building maven yesterday, you would have gotten past this 
> point.  The maven build comes after "ant all" and using ant to build 
> examples.  Are you starting over so that there aren't any pre-existing 
> compile outputs?
> 
> I don't know RoyaleUnit that well, but I assume there are test results stored 
> in a file to review.
> I have some in frameworks/projects/Reflection/src/test/royale/out
> 
> HTH,
> -Alex
> 
> On 5/12/20, 8:50 AM, "Harbs"  wrote:
> 
>I think ant. Here’s more output:
> 
>Executing '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome' 
> with arguments:
>
> '/Apache/approve_ant/apache-royale-0.9.7-src/royale-asjs/frameworks/js/projects/ReflectionJS/src/test/royale/target/bin/js-release/index.html'
> 
>The ' characters around the executable and arguments are
>not part of the command.
> 
>Client connected.
>Receiving data ...
>Sending acknowledgement to player to start sending test data ...
> 
>RoyaleUnit test testGetDynamicFields in suite 
> flexUnitTests.reflection.ReflectionTesterTestDynamic failed.
> 
>Stopping server ...
>End of test data reached, sending acknowledgement to player ...
>Analyzing reports ...
> 
>Suite: flexUnitTests.reflection.ReflectionTesterTest
>Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.738 sec
>Suite: flexUnitTests.reflection.ReflectionTesterNativeTypes
>Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.476 sec
>Suite: flexUnitTests.reflection.ReflectionTesterTestEdgeCases
>Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.615 sec
>Suite: flexUnitTests.reflection.ReflectionTesterTestUseCache
>Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.123 sec
>Suite: flexUnitTests.reflection.ReflectionTesterTestDynamic
>Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.369 sec
>Suite: flexUnitTests.reflection.ReflectionTesterTestAlias
>Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.123 sec
> 
>Results :
> 
>Tests run: 28, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.444 sec
> 
>JS-RELEASE TESTS FAILED
>Running backup tests in js-debug build, because release build tests failed
>OS: [Mac]
>Local path to SWF was given and SWF property will be used.
>Validating task attributes ...
>Generating default values ...
>Using the following settings for the test run:
>   ROYALE_HOME: [/Apache/approve_ant/apache-royale-0.9.7-src/royale-asjs]
>   haltonfailure: [false]
>   headless: [false]
>   display: [99]
>   localTrusted: [true]
>   player: [html]
>   command: [/Applications/Google Chrome.app/Contents/MacOS/Google Chrome]
>   port: [1024]
>   swf: 
> [/Apache/approve_ant/apache-royale-0.9.7-src/royale-asjs/frameworks/js/projects/ReflectionJS/src/test/royale/target/bin/js-debug/index.html]
>   timeout: [9ms]
>   toDir: 
> [/Apache/approve_ant/apache-royale-0.9.7-src/royale-asjs/frameworks/js/projects/ReflectionJS/src/test/royale/out]
>Setting up server process ...
>Entry 
> [/Apache/approve_ant/apache-royale-0.9.7-src/royale-asjs/frameworks/js/projects/ReflectionJS/src/test/royale/target/bin/js-debug]
>  already available in local trust file at 
> [/Users/harbs/Library/Preferences/Macromedia/Flash 
> Player/#Security/FlashPlayerTrust/royaleUnit.cfg].
>Executing '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome' 
> with arguments:
>
> '/Apache/approve_ant/apache-royale-0.9.7-src/royale-asjs/frameworks/js/projects/ReflectionJS/src/test/royale/target/bin/js-debug/index.html'
> 
>The ' characters around the executable and arguments are
>not part of the command.
> 
>Starting server ...
>Waiting for client connection ...
>Client connected.
>Receiving data ...
>Sending acknowledgement to player to start sending test data ...
> 
> 
>Stopping server ...
>End of test data reached, sending acknowledgement to player ...
>Analyzing reports ...
> 
>Suite: flexUnitTests.reflection.ReflectionTesterTest
>Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.738 sec
>Suite: flexUnitTests.reflection.ReflectionTesterNativeTypes
>Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.476 sec
>Suite: flexUnitTests.reflection.ReflectionTesterTestEdgeCases
>Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.615 sec
>Suite: flexUnitTests.reflection.ReflectionTesterTestUseCache
>Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.123 sec
>Suite: flexUnitTests.reflection.ReflectionTesterTestDynamic
>Tests run: 3, Failures: 0,

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-12 Thread Alex Harui

Yes, that's the "ant all" build.  I'm a bit puzzled because if you were running 
into issues building maven yesterday, you would have gotten past this point.  
The maven build comes after "ant all" and using ant to build examples.  Are you 
starting over so that there aren't any pre-existing compile outputs?

I don't know RoyaleUnit that well, but I assume there are test results stored 
in a file to review.
I have some in frameworks/projects/Reflection/src/test/royale/out

HTH,
-Alex

On 5/12/20, 8:50 AM, "Harbs"  wrote:

I think ant. Here’s more output:

Executing '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome' 
with arguments:

'/Apache/approve_ant/apache-royale-0.9.7-src/royale-asjs/frameworks/js/projects/ReflectionJS/src/test/royale/target/bin/js-release/index.html'

The ' characters around the executable and arguments are
not part of the command.

Client connected.
Receiving data ...
Sending acknowledgement to player to start sending test data ...

RoyaleUnit test testGetDynamicFields in suite 
flexUnitTests.reflection.ReflectionTesterTestDynamic failed.

Stopping server ...
End of test data reached, sending acknowledgement to player ...
Analyzing reports ...

Suite: flexUnitTests.reflection.ReflectionTesterTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.738 sec
Suite: flexUnitTests.reflection.ReflectionTesterNativeTypes
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.476 sec
Suite: flexUnitTests.reflection.ReflectionTesterTestEdgeCases
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.615 sec
Suite: flexUnitTests.reflection.ReflectionTesterTestUseCache
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.123 sec
Suite: flexUnitTests.reflection.ReflectionTesterTestDynamic
Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.369 sec
Suite: flexUnitTests.reflection.ReflectionTesterTestAlias
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.123 sec

Results :

Tests run: 28, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.444 sec

JS-RELEASE TESTS FAILED
Running backup tests in js-debug build, because release build tests failed
OS: [Mac]
Local path to SWF was given and SWF property will be used.
Validating task attributes ...
Generating default values ...
Using the following settings for the test run:
ROYALE_HOME: [/Apache/approve_ant/apache-royale-0.9.7-src/royale-asjs]
haltonfailure: [false]
headless: [false]
display: [99]
localTrusted: [true]
player: [html]
command: [/Applications/Google Chrome.app/Contents/MacOS/Google Chrome]
port: [1024]
swf: 
[/Apache/approve_ant/apache-royale-0.9.7-src/royale-asjs/frameworks/js/projects/ReflectionJS/src/test/royale/target/bin/js-debug/index.html]
timeout: [9ms]
toDir: 
[/Apache/approve_ant/apache-royale-0.9.7-src/royale-asjs/frameworks/js/projects/ReflectionJS/src/test/royale/out]
Setting up server process ...
Entry 
[/Apache/approve_ant/apache-royale-0.9.7-src/royale-asjs/frameworks/js/projects/ReflectionJS/src/test/royale/target/bin/js-debug]
 already available in local trust file at 
[/Users/harbs/Library/Preferences/Macromedia/Flash 
Player/#Security/FlashPlayerTrust/royaleUnit.cfg].
Executing '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome' 
with arguments:

'/Apache/approve_ant/apache-royale-0.9.7-src/royale-asjs/frameworks/js/projects/ReflectionJS/src/test/royale/target/bin/js-debug/index.html'

The ' characters around the executable and arguments are
not part of the command.

Starting server ...
Waiting for client connection ...
Client connected.
Receiving data ...
Sending acknowledgement to player to start sending test data ...


Stopping server ...
End of test data reached, sending acknowledgement to player ...
Analyzing reports ...

Suite: flexUnitTests.reflection.ReflectionTesterTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.738 sec
Suite: flexUnitTests.reflection.ReflectionTesterNativeTypes
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.476 sec
Suite: flexUnitTests.reflection.ReflectionTesterTestEdgeCases
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.615 sec
Suite: flexUnitTests.reflection.ReflectionTesterTestUseCache
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.123 sec
Suite: flexUnitTests.reflection.ReflectionTesterTestDynamic
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.369 sec
Suite: flexUnitTests.reflection.ReflectionTesterTestAlias
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.123 sec

Results :

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-12 Thread Harbs

I think ant. Here’s more output:

Executing '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome' with 
arguments:
'/Apache/approve_ant/apache-royale-0.9.7-src/royale-asjs/frameworks/js/projects/ReflectionJS/src/test/royale/target/bin/js-release/index.html'

The ' characters around the executable and arguments are
not part of the command.

Client connected.
Receiving data ...
Sending acknowledgement to player to start sending test data ...

RoyaleUnit test testGetDynamicFields in suite 
flexUnitTests.reflection.ReflectionTesterTestDynamic failed.

Stopping server ...
End of test data reached, sending acknowledgement to player ...
Analyzing reports ...

Suite: flexUnitTests.reflection.ReflectionTesterTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.738 sec
Suite: flexUnitTests.reflection.ReflectionTesterNativeTypes
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.476 sec
Suite: flexUnitTests.reflection.ReflectionTesterTestEdgeCases
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.615 sec
Suite: flexUnitTests.reflection.ReflectionTesterTestUseCache
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.123 sec
Suite: flexUnitTests.reflection.ReflectionTesterTestDynamic
Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.369 sec
Suite: flexUnitTests.reflection.ReflectionTesterTestAlias
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.123 sec

Results :

Tests run: 28, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.444 sec

JS-RELEASE TESTS FAILED
Running backup tests in js-debug build, because release build tests failed
OS: [Mac]
Local path to SWF was given and SWF property will be used.
Validating task attributes ...
Generating default values ...
Using the following settings for the test run:
ROYALE_HOME: [/Apache/approve_ant/apache-royale-0.9.7-src/royale-asjs]
haltonfailure: [false]
headless: [false]
display: [99]
localTrusted: [true]
player: [html]
command: [/Applications/Google Chrome.app/Contents/MacOS/Google Chrome]
port: [1024]
swf: 
[/Apache/approve_ant/apache-royale-0.9.7-src/royale-asjs/frameworks/js/projects/ReflectionJS/src/test/royale/target/bin/js-debug/index.html]
timeout: [9ms]
toDir: 
[/Apache/approve_ant/apache-royale-0.9.7-src/royale-asjs/frameworks/js/projects/ReflectionJS/src/test/royale/out]
Setting up server process ...
Entry 
[/Apache/approve_ant/apache-royale-0.9.7-src/royale-asjs/frameworks/js/projects/ReflectionJS/src/test/royale/target/bin/js-debug]
 already available in local trust file at 
[/Users/harbs/Library/Preferences/Macromedia/Flash 
Player/#Security/FlashPlayerTrust/royaleUnit.cfg].
Executing '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome' with 
arguments:
'/Apache/approve_ant/apache-royale-0.9.7-src/royale-asjs/frameworks/js/projects/ReflectionJS/src/test/royale/target/bin/js-debug/index.html'

The ' characters around the executable and arguments are
not part of the command.

Starting server ...
Waiting for client connection ...
Client connected.
Receiving data ...
Sending acknowledgement to player to start sending test data ...


Stopping server ...
End of test data reached, sending acknowledgement to player ...
Analyzing reports ...

Suite: flexUnitTests.reflection.ReflectionTesterTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.738 sec
Suite: flexUnitTests.reflection.ReflectionTesterNativeTypes
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.476 sec
Suite: flexUnitTests.reflection.ReflectionTesterTestEdgeCases
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.615 sec
Suite: flexUnitTests.reflection.ReflectionTesterTestUseCache
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.123 sec
Suite: flexUnitTests.reflection.ReflectionTesterTestDynamic
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.369 sec
Suite: flexUnitTests.reflection.ReflectionTesterTestAlias
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.123 sec

Results :

Tests run: 28, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.444 sec

Processing 
/Apache/approve_ant/apache-royale-0.9.7-src/royale-asjs/frameworks/js/projects/ReflectionJS/src/test/royale/out/TESTS-TestSuites.xml
 to /var/folders/k8/f8qyn4px641_zm313rvprfhwgn/T/null1887208993
Loading stylesheet 
jar:file:/usr/local/Cellar/ant/1.10.7/libexec/lib/ant-junit.jar!/org/apache/tools/ant/taskdefs/optional/junit/xsl/junit-frames.xsl
Transform time: 68ms
Deleting: /var/folders/k8/f8qyn4px641_zm313rvprfhwgn/T/null1887208993

BUILD FAILED
/Apache/approve_ant/ApproveRoyale.xml:780: The following error occurred while 
executing this line:
/Apache/approve_ant/apache-royale-0.9.7-src/royale-asjs/build.xml:667: The 
following error occurred while executing this line:

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-12 Thread Alex Harui

Is that from the Maven or Ant build?

On 5/12/20, 8:04 AM, "Harbs"  wrote:

I’m now getting:
ReflectionJS.test RoyaleUnit Release build tests: FAILED
ReflectionJS.test RoyaleUnit Debug build tests: PASSED

Any ideas?

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-12 Thread Harbs

I’m now getting:
ReflectionJS.test RoyaleUnit Release build tests: FAILED
ReflectionJS.test RoyaleUnit Debug build tests: PASSED

Any ideas?

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-12 Thread Christofer Dutz

And after hearing Piotr managing to build the maven distribution ... I 
re-unpacked the source bundle and the distribution directory wasn't empty 
anymore.
I tried reproducing what I did last time ... I thought perhaps the ant clean 
scripts accidentally deleted something ... but no ... so I can't really explain 
why it was empty in my case. So please ignore the findings related to 
distribution being empty.

Chris



Am 12.05.20, 10:28 schrieb "Christofer Dutz" :

Hi all,

well yes the check is new, the playerversion was 20 for the past 4-5 years 
... it's the version of the playerglobal the mavenizer downloads and uses 
throughout the build.

Technically the player being used to run the application should be at least 
the version of the playerglobal. In the prerequisiteCheck I added checks for 
all sorts of hard to diagnose things that could go wrong with the build before 
the build actually starts. 

So perhaps set the version used in the pom "flash.version" to the version 
used in the Ant build. So then the prerequisiteCheck would pick that up and 
also allow older versions. I do think checking the compatibility of the used 
player is quite important.

Chris



Am 12.05.20, 06:11 schrieb "Alex Harui" :

I think that's a new check.  You can get old FP versions from here: 
https://helpx.adobe.com/flash-player/kb/archived-flash-player-versions.html

-Alex

On 5/11/20, 3:57 PM, "Harbs"  wrote:

Why is the minimum Flash version for Maven 20.0? I’ve been using 
11.4 for years without issues.

The build just failed for me…
Detecting FlashPlayer Debugger:  11.4.402.265  FAILED (required 
20.0)

….


[ERROR] Failed to execute goal 
org.codehaus.gmaven:groovy-maven-plugin:2.1.1:execute (prerequisite-check) on 
project royale-compiler-parent: Execution prerequisite-check of goal 
org.codehaus.gmaven:groovy-maven-plugin:2.1.1:execute failed: Not all 
conditions met, see log for details. -> [Help 1]

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-12 Thread Christofer Dutz

Hi all,

well yes the check is new, the playerversion was 20 for the past 4-5 years ... 
it's the version of the playerglobal the mavenizer downloads and uses 
throughout the build.

Technically the player being used to run the application should be at least the 
version of the playerglobal. In the prerequisiteCheck I added checks for all 
sorts of hard to diagnose things that could go wrong with the build before the 
build actually starts. 

So perhaps set the version used in the pom "flash.version" to the version used 
in the Ant build. So then the prerequisiteCheck would pick that up and also 
allow older versions. I do think checking the compatibility of the used player 
is quite important.

Chris



Am 12.05.20, 06:11 schrieb "Alex Harui" :

I think that's a new check.  You can get old FP versions from here: 
https://helpx.adobe.com/flash-player/kb/archived-flash-player-versions.html

-Alex

On 5/11/20, 3:57 PM, "Harbs"  wrote:

Why is the minimum Flash version for Maven 20.0? I’ve been using 11.4 
for years without issues.

The build just failed for me…
Detecting FlashPlayer Debugger:  11.4.402.265  FAILED (required 20.0)

….


[ERROR] Failed to execute goal 
org.codehaus.gmaven:groovy-maven-plugin:2.1.1:execute (prerequisite-check) on 
project royale-compiler-parent: Execution prerequisite-check of goal 
org.codehaus.gmaven:groovy-maven-plugin:2.1.1:execute failed: Not all 
conditions met, see log for details. -> [Help 1]

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-11 Thread Alex Harui

I think that's a new check.  You can get old FP versions from here: 
https://helpx.adobe.com/flash-player/kb/archived-flash-player-versions.html

-Alex

On 5/11/20, 3:57 PM, "Harbs"  wrote:

Why is the minimum Flash version for Maven 20.0? I’ve been using 11.4 for 
years without issues.

The build just failed for me…
Detecting FlashPlayer Debugger:  11.4.402.265  FAILED (required 20.0)

….


[ERROR] Failed to execute goal 
org.codehaus.gmaven:groovy-maven-plugin:2.1.1:execute (prerequisite-check) on 
project royale-compiler-parent: Execution prerequisite-check of goal 
org.codehaus.gmaven:groovy-maven-plugin:2.1.1:execute failed: Not all 
conditions met, see log for details. -> [Help 1]

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-11 Thread Harbs

Why is the minimum Flash version for Maven 20.0? I’ve been using 11.4 for years 
without issues.

The build just failed for me…
Detecting FlashPlayer Debugger:  11.4.402.265  FAILED (required 20.0)

….


[ERROR] Failed to execute goal 
org.codehaus.gmaven:groovy-maven-plugin:2.1.1:execute (prerequisite-check) on 
project royale-compiler-parent: Execution prerequisite-check of goal 
org.codehaus.gmaven:groovy-maven-plugin:2.1.1:execute failed: Not all 
conditions met, see log for details. -> [Help 1]

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-11 Thread Harbs

It was noticed and not ignored by me.

I appreciate Chris taking the time to work through the release and point out 
the issues he saw.

I’m in the process of working through the release. I will evaluate the issues 
he raised as I do that.

Thanks,
Harbs

> On May 12, 2020, at 12:52 AM, Carlos Rovira  wrote:
> 
> since I was seeing the issues raised by Chris mostly unnoticed or ignored,

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-11 Thread Carlos Rovira

Hi Yishay,

since I was seeing the issues raised by Chris mostly unnoticed or ignored,
I was saying that if nobody thinks the issues are important I'll by
changing my vote. So, I'm not saying we need to cover now, we can let for
the next one, just ask for people noticing that is important.

Hope that's more clear now

Thanks



El lun., 11 may. 2020 a las 20:37, Yishay Weiss ()
escribió:

> Hi Carlos,
>
> Responding here to your comment on VOTE. I think it goes without saying
> that we should address the issues uncovered during the release vote. The
> question is whether it should be done before or after this release. Let’s
> wait for the remaining reviews and decide.
>
> Thanks,
> Yishay
>
> From: Carlos Rovira<mailto:carlosrov...@apache.org>
> Sent: Monday, May 11, 2020 4:33 PM
> To: Apache Royale Development<mailto:dev@royale.apache.org>
> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7
>
> Hi Harbs,
>
> I use as well homebrew and installed ANT with it. I have this in my
> .bas_profile:
>
> export ANT_HOME=/usr/local/Cellar/ant/1.10.7/libexec
>
>
> and I'm using it without any problem
>
>
> HTH
>
>
> Carlos
>
>
>
> El dom., 10 may. 2020 a las 17:53, Harbs ()
> escribió:
>
> > I’m having trouble with the approval script.
> >
> > I have ant installed with Homebrew and I don’t have a ANT_HOME var. I’m
> > not sure why it’s necessary, but I can’t figure out what to use.
> >
> > Homebrew puts ant in the following location: /usr/local/Cellar/ant/1.10.7
> > If I set ANT_HOME to that, ant becomes non-functional and I get Error:
> > Could not find or load main class org.apache.tools.ant.launch.Launcher.
> >
> > Suggestions?
> > Harbs
> >
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

-- 
Carlos Rovira
http://about.me/carlosrovira

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-11 Thread Alex Harui

Binding votes matter.  Non-binding votes are advisory only.

I see a distribution folder with stuff in it the source package.  It built for 
me.
Crux is associated with Swiz in the LICENSE.  We just didn’t mention some of 
the folders
The TTF file is mentioned in the LICENSE.

I am not planning to change my vote.  Could we be more accurate and clear in 
the README/RELEASE_NOTES/LICENSE/NOTICE?  Sure.  But AFAICT, everyone who 
should have been attributed was and the source files we’ve reviewed are present.

Thanks,
-Alex

From: Yishay Weiss 
Reply-To: "dev@royale.apache.org" 
Date: Monday, May 11, 2020 at 7:59 AM
To: "dev@royale.apache.org" 
Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

I think 72 hours have passed. So far I see four +1 and one -1. It looks like 
Harbs and Piotr are still working on it, so I’ll wait for their votes before we 
proceed.


From: Carlos Rovira 
Sent: Monday, May 11, 2020 4:32:54 PM
To: Apache Royale Development 
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Hi Harbs,

I use as well homebrew and installed ANT with it. I have this in my
.bas_profile:

export ANT_HOME=/usr/local/Cellar/ant/1.10.7/libexec


and I'm using it without any problem


HTH


Carlos



El dom., 10 may. 2020 a las 17:53, Harbs () escribió:

> I’m having trouble with the approval script.
>
> I have ant installed with Homebrew and I don’t have a ANT_HOME var. I’m
> not sure why it’s necessary, but I can’t figure out what to use.
>
> Homebrew puts ant in the following location: /usr/local/Cellar/ant/1.10.7
> If I set ANT_HOME to that, ant becomes non-functional and I get Error:
> Could not find or load main class org.apache.tools.ant.launch.Launcher.
>
> Suggestions?
> Harbs
>
>
>

--
Carlos Rovira
http://about.me/carlosrovira<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira=02%7C01%7Caharui%40adobe.com%7C224983395bfa4d35ef4e08d7f5bbd982%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248059508304446=L33ufhZ%2FN1KVVwYwWISyEaARxkAY7UwvUrJpRwb0UIQ%3D=0>
From: Carlos Rovira<mailto:carlosrov...@apache.org>
Sent: Monday, May 11, 2020 4:33 PM
To: Apache Royale Development<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Hi Harbs,

I use as well homebrew and installed ANT with it. I have this in my
.bas_profile:

export ANT_HOME=/usr/local/Cellar/ant/1.10.7/libexec


and I'm using it without any problem


HTH


Carlos



El dom., 10 may. 2020 a las 17:53, Harbs () escribió:

> I’m having trouble with the approval script.
>
> I have ant installed with Homebrew and I don’t have a ANT_HOME var. I’m
> not sure why it’s necessary, but I can’t figure out what to use.
>
> Homebrew puts ant in the following location: /usr/local/Cellar/ant/1.10.7
> If I set ANT_HOME to that, ant becomes non-functional and I get Error:
> Could not find or load main class org.apache.tools.ant.launch.Launcher.
>
> Suggestions?
> Harbs
>
>
>

--
Carlos Rovira
http://about.me/carlosrovira<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira=02%7C01%7Caharui%40adobe.com%7C224983395bfa4d35ef4e08d7f5bbd982%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637248059508304446=L33ufhZ%2FN1KVVwYwWISyEaARxkAY7UwvUrJpRwb0UIQ%3D=0>

RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-11 Thread Yishay Weiss

Hi Carlos,

Responding here to your comment on VOTE. I think it goes without saying that we 
should address the issues uncovered during the release vote. The question is 
whether it should be done before or after this release. Let’s wait for the 
remaining reviews and decide.

Thanks,
Yishay

From: Carlos Rovira<mailto:carlosrov...@apache.org>
Sent: Monday, May 11, 2020 4:33 PM
To: Apache Royale Development<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Hi Harbs,

I use as well homebrew and installed ANT with it. I have this in my
.bas_profile:

export ANT_HOME=/usr/local/Cellar/ant/1.10.7/libexec


and I'm using it without any problem


HTH


Carlos



El dom., 10 may. 2020 a las 17:53, Harbs () escribió:

> I’m having trouble with the approval script.
>
> I have ant installed with Homebrew and I don’t have a ANT_HOME var. I’m
> not sure why it’s necessary, but I can’t figure out what to use.
>
> Homebrew puts ant in the following location: /usr/local/Cellar/ant/1.10.7
> If I set ANT_HOME to that, ant becomes non-functional and I get Error:
> Could not find or load main class org.apache.tools.ant.launch.Launcher.
>
> Suggestions?
> Harbs
>
>
>

--
Carlos Rovira
http://about.me/carlosrovira

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-11 Thread Alex Harui

 > > >>
> > > > >>
> > > >
> > >
> >
> 
-load-config+=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/src/main/config/compile-app-config.xml
> > > > >>
> > > > >> +playerglobal.version=11.1
> > > > >>
> > > > >>
> > >  +env.PLAYERGLOBAL_HOME=/Users/carlosrovira/Dev/Flash/Player
> > > > >>
> > > > >> -compiler.debug=true
> > > > >>
> > > > >>
> > > > >>
> > > >
> > >
> >
> 
+royalelib=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/
> > > > >>
> > > > >>
> > > > >>
> > > >
> > >
> >
> 
-closure-lib=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js/lib/google/closure-library
> > > > >>
> > > > >> +configname=royale
> > > > >>
> > > > >> -swf-version
> > > > >>
> > > > >> 14
> > > > >>
> > >     >     >>
    > > > > >>
> > > >
> > >
> >
> 
-output=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/bin-debug/Ace.swf
> > > > >>
> > > > >> --
> > > > >>
> > > > >>
> > > > >>
> > > >
> > >
> >
> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/src/main/royale/Ace.mxml
> > > > >>
> > > > >> 0.655243136 seconds
> > > > >>
> > > > >>
> > > > >>
> > > >
> > >
> >
> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml(74):
> > > > >> col: 0 Error: unable to open
> > > > >>
> > > > >>
> > > >
> > >
> >
> 
'/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/libs/player/11.1/playerglobal.swc'.
> > > > >>
> > > > >>
> > > > >>
> > > >
> > >
> >
> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml
> > > > >> (line: 74)
> > > > >>
> > > > >>
> > > > >>   
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >> BUILD FAILED
> > > > >>
> > > > >>
> > > >
> > /Users/carlosrovira/Downloads/royale097rc5/ApproveRoyale.xml:781:
> > > The
> > > > >> following error occurred while executing this
> > line:
> > > > >>
> > > > >>
> > > > >>
> > > >
> > >
> >
> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/bu

RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-11 Thread Yishay Weiss

I think 72 hours have passed. So far I see four +1 and one -1. It looks like 
Harbs and Piotr are still working on it, so I’ll wait for their votes before we 
proceed.


From: Carlos Rovira 
Sent: Monday, May 11, 2020 4:32:54 PM
To: Apache Royale Development 
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Hi Harbs,

I use as well homebrew and installed ANT with it. I have this in my
.bas_profile:

export ANT_HOME=/usr/local/Cellar/ant/1.10.7/libexec


and I'm using it without any problem


HTH


Carlos



El dom., 10 may. 2020 a las 17:53, Harbs () escribió:

> I’m having trouble with the approval script.
>
> I have ant installed with Homebrew and I don’t have a ANT_HOME var. I’m
> not sure why it’s necessary, but I can’t figure out what to use.
>
> Homebrew puts ant in the following location: /usr/local/Cellar/ant/1.10.7
> If I set ANT_HOME to that, ant becomes non-functional and I get Error:
> Could not find or load main class org.apache.tools.ant.launch.Launcher.
>
> Suggestions?
> Harbs
>
>
>

--
Carlos Rovira
http://about.me/carlosrovira
From: Carlos Rovira<mailto:carlosrov...@apache.org>
Sent: Monday, May 11, 2020 4:33 PM
To: Apache Royale Development<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Hi Harbs,

I use as well homebrew and installed ANT with it. I have this in my
.bas_profile:

export ANT_HOME=/usr/local/Cellar/ant/1.10.7/libexec


and I'm using it without any problem


HTH


Carlos



El dom., 10 may. 2020 a las 17:53, Harbs () escribió:

> I’m having trouble with the approval script.
>
> I have ant installed with Homebrew and I don’t have a ANT_HOME var. I’m
> not sure why it’s necessary, but I can’t figure out what to use.
>
> Homebrew puts ant in the following location: /usr/local/Cellar/ant/1.10.7
> If I set ANT_HOME to that, ant becomes non-functional and I get Error:
> Could not find or load main class org.apache.tools.ant.launch.Launcher.
>
> Suggestions?
> Harbs
>
>
>

--
Carlos Rovira
http://about.me/carlosrovira

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-11 Thread Carlos Rovira

Hi Harbs,

I use as well homebrew and installed ANT with it. I have this in my
.bas_profile:

export ANT_HOME=/usr/local/Cellar/ant/1.10.7/libexec


and I'm using it without any problem


HTH


Carlos



El dom., 10 may. 2020 a las 17:53, Harbs () escribió:

> I’m having trouble with the approval script.
>
> I have ant installed with Homebrew and I don’t have a ANT_HOME var. I’m
> not sure why it’s necessary, but I can’t figure out what to use.
>
> Homebrew puts ant in the following location: /usr/local/Cellar/ant/1.10.7
> If I set ANT_HOME to that, ant becomes non-functional and I get Error:
> Could not find or load main class org.apache.tools.ant.launch.Launcher.
>
> Suggestions?
> Harbs
>
>
>

-- 
Carlos Rovira
http://about.me/carlosrovira

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-11 Thread Piotr Zarzycki

> Greg
> > > > >
> > > > > On Sat, May 9, 2020 at 6:31 AM Alex Harui
> > > > 
> > > > > wrote:
> > > > >
> > > > >> Carlos,
> > > > >>
> > > > >> What scenario are you testing?  If you are using "
> > > > -Duse-flash=true" then
> > > > >> is PLAYERGLOBAL_HOME and other environment
> variable
> > set up
> > > > properly?
> > > > >>
> > > > >> -Alex
> > > > >>
> > > > >> On 5/8/20, 10:21 AM, "Carlos Rovira" <
> > > carlosrov...@apache.org>
> > > > wrote:
> > > > >>
> > > > >> Hi,
> > > > >>
> > > > >> I had a similar experience with approve xml,
> so
> > I'll
> > > check
> > > > as I have
> > > > >> more
> > > > >> time during weekend in other way:
> > > > >>
> > > > >> build_example.compile:
> > > > >>
> > > > >> Compiling Ace.swf
> > > > >>
> > > > >> ROYALE_HOME:
> > > > >>
> > > > >>
> > > >
> > >
> >
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs
> > > > >>
> > > > >> ROYALE_COMPILER_HOME:
> > > > >>
> > > > >>
> > > >
> > >
> >
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js
> > > > >>
> > > > >> GOOG_HOME:
> > > > >>
> > > > >>
> > > >
> > >
> >
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js/lib/google/closure-library
> > > > >>
> > > > >> MXMLJSC
> > > > >>
> > > > >>
> > > > >>
> > > >
> > >
> >
> -load-config+=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/src/main/config/compile-app-config.xml
> > > > >>
> > > > >> +playerglobal.version=11.1
> > > > >>
> > > > >>
> > >  +env.PLAYERGLOBAL_HOME=/Users/carlosrovira/Dev/Flash/Player
> > > > >>
> > > > >> -compiler.debug=true
> > > > >>
> > > > >>
> > > > >>
> > > >
> > >
> >
> +royalelib=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/
> > > > >>
> > > > >>
> > > > >>
> > > >
> > >
> >
> -closure-lib=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js/lib/google/closure-library
> >     > > >>
> > > > >> +configname=royale
> > > > >>
> > > > >> -swf-version
> > > > >>
> > > > >> 14
> > > > >>
> > > > >>
> > > > >>
> > > >
> > >
> >
> -output=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/bin-debug/Ace.swf
> > > > >>
> > > > >> --
> > > > >>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-10 Thread Greg Dove

t;> ROYALE_COMPILER_HOME:
> > > >>
> > > >>
> > >
> >
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js
> > > >>
> > > >> GOOG_HOME:
> > > >>
> > > >>
> > >
> >
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js/lib/google/closure-library
> > > >>
> > > >> MXMLJSC
> > > >>
> > > >>
> > > >>
> > >
> >
> -load-config+=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/src/main/config/compile-app-config.xml
> > > >>
> > > >> +playerglobal.version=11.1
> > > >>
> > > >>
> >  +env.PLAYERGLOBAL_HOME=/Users/carlosrovira/Dev/Flash/Player
> > > >>
> > > >> -compiler.debug=true
> > > >>
> > > >>
> > > >>
> > >
> >
> +royalelib=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/
> > > >>
> > > >>
> > > >>
> > >
> >
> -closure-lib=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js/lib/google/closure-library
> > > >>
> > > >> +configname=royale
> > > >>
> > > >> -swf-version
> > > >>
> > > >> 14
> > > >>
> > > >>
> > > >>
> > >
> >
> -output=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/bin-debug/Ace.swf
> > > >>
> > > >> --
> > > >>
> > > >>
> > > >>
> > >
> >
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/src/main/royale/Ace.mxml
>     > >     >>
> > > >> 0.655243136 seconds
> > > >>
> > > >>
> > > >>
> > >
> >
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml(74):
> > > >> col: 0 Error: unable to open
> > > >>
> > > >>
> > >
> >
> '/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/libs/player/11.1/playerglobal.swc'.
> > > >>
> > > >>
> > > >>
> > >
> >
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml
> > > >> (line: 74)
> > > >>
> > > >>
> > > >>   
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> BUILD FAILED
> > > >>
> > > >>
> > >
> /Users/carlosrovira/Downloads/royale097rc5/ApproveRoyale.xml:781:
> > The
> > > >> following error occurred while executing this
> line:
> > > >>
> > > >>
> > > >>
> > >
> >
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/build.xml:659:
> > > >> The following error occurred while executing
> this
> > line:
> > > >>
> > > >>
> > >

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-10 Thread Christofer Dutz

Hi all,

forget that ... I just re-checked the vote email and you simply only have it in 
the dist and not in the rc staging area ...

Chris



Am 10.05.20, 20:25 schrieb "Christofer Dutz" :

Just a small question  

where's the KEYS file located? I can't find it in the default location:
https://dist.apache.org/repos/dist/dev/royale/KEYS

Chris


Am 10.05.20, 19:44 schrieb "Alex Harui" :

Maybe edit the README to specify that ANT_HOME should have a bin and 
lib folder?

On 5/10/20, 10:41 AM, "Harbs"  wrote:

Thanks that helped.

FTR, it looks like Homebrew puts it in a libexec folder, so it 
needs to be:

export ANT_HOME=/usr/local/Cellar/ant/1.10.7/libexec

> On May 10, 2020, at 7:00 PM, Alex Harui 
 wrote:
> 
> ANT_HOME is for the compiler so it doesn't have to learn how to 
search for Ant on your computer when building our Ant tasks.
> 
> What is in the /usr/local/Cellar/ant/1.10.7 folder?
> 
> In my ANT_HOME folder I have:
> INSTALL   NOTICE  bin get-m2.xml
> KEYS  README  etc lib
> LICENSE   WHATSNEWfetch.xml   manual
> 
> -Alex
> 
> On 5/10/20, 8:53 AM, "Harbs"  wrote:
> 
>I’m having trouble with the approval script.
> 
>I have ant installed with Homebrew and I don’t have a ANT_HOME 
var. I’m not sure why it’s necessary, but I can’t figure out what to use.
> 
>Homebrew puts ant in the following location: 
/usr/local/Cellar/ant/1.10.7 If I set ANT_HOME to that, ant becomes 
non-functional and I get Error: Could not find or load main class 
org.apache.tools.ant.launch.Launcher.
> 
>Suggestions?
>Harbs
> 
> 
> 
>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-10 Thread Christofer Dutz

Just a small question  

where's the KEYS file located? I can't find it in the default location:
https://dist.apache.org/repos/dist/dev/royale/KEYS

Chris


Am 10.05.20, 19:44 schrieb "Alex Harui" :

Maybe edit the README to specify that ANT_HOME should have a bin and lib 
folder?

On 5/10/20, 10:41 AM, "Harbs"  wrote:

Thanks that helped.

FTR, it looks like Homebrew puts it in a libexec folder, so it needs to 
be:

export ANT_HOME=/usr/local/Cellar/ant/1.10.7/libexec

> On May 10, 2020, at 7:00 PM, Alex Harui  
wrote:
> 
> ANT_HOME is for the compiler so it doesn't have to learn how to 
search for Ant on your computer when building our Ant tasks.
> 
> What is in the /usr/local/Cellar/ant/1.10.7 folder?
> 
> In my ANT_HOME folder I have:
> INSTALL   NOTICE  bin get-m2.xml
> KEYS  README  etc lib
> LICENSE   WHATSNEWfetch.xml   manual
> 
> -Alex
> 
> On 5/10/20, 8:53 AM, "Harbs"  wrote:
> 
>I’m having trouble with the approval script.
> 
>I have ant installed with Homebrew and I don’t have a ANT_HOME 
var. I’m not sure why it’s necessary, but I can’t figure out what to use.
> 
>Homebrew puts ant in the following location: 
/usr/local/Cellar/ant/1.10.7 If I set ANT_HOME to that, ant becomes 
non-functional and I get Error: Could not find or load main class 
org.apache.tools.ant.launch.Launcher.
> 
>Suggestions?
>Harbs
> 
> 
> 
>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-10 Thread Alex Harui

Maybe edit the README to specify that ANT_HOME should have a bin and lib folder?

On 5/10/20, 10:41 AM, "Harbs"  wrote:

Thanks that helped.

FTR, it looks like Homebrew puts it in a libexec folder, so it needs to be:

export ANT_HOME=/usr/local/Cellar/ant/1.10.7/libexec

> On May 10, 2020, at 7:00 PM, Alex Harui  wrote:
> 
> ANT_HOME is for the compiler so it doesn't have to learn how to search 
for Ant on your computer when building our Ant tasks.
> 
> What is in the /usr/local/Cellar/ant/1.10.7 folder?
> 
> In my ANT_HOME folder I have:
> INSTALL   NOTICE  bin get-m2.xml
> KEYS  README  etc lib
> LICENSE   WHATSNEWfetch.xml   manual
> 
> -Alex
> 
> On 5/10/20, 8:53 AM, "Harbs"  wrote:
> 
>I’m having trouble with the approval script.
> 
>I have ant installed with Homebrew and I don’t have a ANT_HOME var. 
I’m not sure why it’s necessary, but I can’t figure out what to use.
> 
>Homebrew puts ant in the following location: 
/usr/local/Cellar/ant/1.10.7 If I set ANT_HOME to that, ant becomes 
non-functional and I get Error: Could not find or load main class 
org.apache.tools.ant.launch.Launcher.
> 
>Suggestions?
>Harbs
> 
> 
> 
>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-10 Thread Harbs

Thanks that helped.

FTR, it looks like Homebrew puts it in a libexec folder, so it needs to be:

export ANT_HOME=/usr/local/Cellar/ant/1.10.7/libexec

> On May 10, 2020, at 7:00 PM, Alex Harui  wrote:
> 
> ANT_HOME is for the compiler so it doesn't have to learn how to search for 
> Ant on your computer when building our Ant tasks.
> 
> What is in the /usr/local/Cellar/ant/1.10.7 folder?
> 
> In my ANT_HOME folder I have:
> INSTALL   NOTICE  bin get-m2.xml
> KEYS  README  etc lib
> LICENSE   WHATSNEWfetch.xml   manual
> 
> -Alex
> 
> On 5/10/20, 8:53 AM, "Harbs"  wrote:
> 
>I’m having trouble with the approval script.
> 
>I have ant installed with Homebrew and I don’t have a ANT_HOME var. I’m 
> not sure why it’s necessary, but I can’t figure out what to use.
> 
>Homebrew puts ant in the following location: /usr/local/Cellar/ant/1.10.7 
> If I set ANT_HOME to that, ant becomes non-functional and I get Error: Could 
> not find or load main class org.apache.tools.ant.launch.Launcher.
> 
>Suggestions?
>Harbs
> 
> 
> 
>

RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-10 Thread Yishay Weiss

I think you need to have all keys in KEYS [1] file imported to check the 
signature. If I recall correctly Carlos had a similar issue when he was 
checking build tools. Search DISCUSS for release of 1.2.0.

[1] https://dist.apache.org/repos/dist/release/royale/KEYS


From: Piotr Zarzycki 
Sent: Sunday, May 10, 2020 7:43:20 PM
To: Apache Royale Development 
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Hi Guys,

When I was trying to use Approval script I'm getting this kind of error:

check-sigs:

gpg_check:
gpg: Signature made 05/08/20 09:24:15 Central European Daylight Time
gpg:using RSA key
gpg: Can't check signature: No public key

Is this my fault ?

Thanks,
Piotr

niedz., 10 maj 2020 o 18:01 Alex Harui 
napisał(a):

> ANT_HOME is for the compiler so it doesn't have to learn how to search for
> Ant on your computer when building our Ant tasks.
>
> What is in the /usr/local/Cellar/ant/1.10.7 folder?
>
> In my ANT_HOME folder I have:
> INSTALL NOTICE  bin get-m2.xml
> KEYSREADME  etc lib
> LICENSE WHATSNEWfetch.xml   manual
>
> -Alex
>
> On 5/10/20, 8:53 AM, "Harbs"  wrote:
>
> I’m having trouble with the approval script.
>
> I have ant installed with Homebrew and I don’t have a ANT_HOME var.
> I’m not sure why it’s necessary, but I can’t figure out what to use.
>
> Homebrew puts ant in the following location:
> /usr/local/Cellar/ant/1.10.7 If I set ANT_HOME to that, ant becomes
> non-functional and I get Error: Could not find or load main class
> org.apache.tools.ant.launch.Launcher.
>
> Suggestions?
> Harbs
>
>
>
>
>

--

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
From: Piotr Zarzycki<mailto:piotrzarzyck...@gmail.com>
Sent: Sunday, May 10, 2020 7:43 PM
To: Apache Royale Development<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Hi Guys,

When I was trying to use Approval script I'm getting this kind of error:

check-sigs:

gpg_check:
gpg: Signature made 05/08/20 09:24:15 Central European Daylight Time
gpg:using RSA key
gpg: Can't check signature: No public key

Is this my fault ?

Thanks,
Piotr

niedz., 10 maj 2020 o 18:01 Alex Harui 
napisał(a):

> ANT_HOME is for the compiler so it doesn't have to learn how to search for
> Ant on your computer when building our Ant tasks.
>
> What is in the /usr/local/Cellar/ant/1.10.7 folder?
>
> In my ANT_HOME folder I have:
> INSTALL NOTICE  bin get-m2.xml
> KEYSREADME  etc lib
> LICENSE WHATSNEWfetch.xml   manual
>
> -Alex
>
> On 5/10/20, 8:53 AM, "Harbs"  wrote:
>
> I’m having trouble with the approval script.
>
> I have ant installed with Homebrew and I don’t have a ANT_HOME var.
> I’m not sure why it’s necessary, but I can’t figure out what to use.
>
> Homebrew puts ant in the following location:
> /usr/local/Cellar/ant/1.10.7 If I set ANT_HOME to that, ant becomes
> non-functional and I get Error: Could not find or load main class
> org.apache.tools.ant.launch.Launcher.
>
> Suggestions?
> Harbs
>
>
>
>
>

--

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-10 Thread Piotr Zarzycki

Hi Guys,

When I was trying to use Approval script I'm getting this kind of error:

check-sigs:

gpg_check:
gpg: Signature made 05/08/20 09:24:15 Central European Daylight Time
gpg:using RSA key
gpg: Can't check signature: No public key

Is this my fault ?

Thanks,
Piotr

niedz., 10 maj 2020 o 18:01 Alex Harui 
napisał(a):

> ANT_HOME is for the compiler so it doesn't have to learn how to search for
> Ant on your computer when building our Ant tasks.
>
> What is in the /usr/local/Cellar/ant/1.10.7 folder?
>
> In my ANT_HOME folder I have:
> INSTALL NOTICE  bin get-m2.xml
> KEYSREADME  etc lib
> LICENSE WHATSNEWfetch.xml   manual
>
> -Alex
>
> On 5/10/20, 8:53 AM, "Harbs"  wrote:
>
> I’m having trouble with the approval script.
>
> I have ant installed with Homebrew and I don’t have a ANT_HOME var.
> I’m not sure why it’s necessary, but I can’t figure out what to use.
>
> Homebrew puts ant in the following location:
> /usr/local/Cellar/ant/1.10.7 If I set ANT_HOME to that, ant becomes
> non-functional and I get Error: Could not find or load main class
> org.apache.tools.ant.launch.Launcher.
>
> Suggestions?
> Harbs
>
>
>
>
>

-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-10 Thread Alex Harui

ANT_HOME is for the compiler so it doesn't have to learn how to search for Ant 
on your computer when building our Ant tasks.

What is in the /usr/local/Cellar/ant/1.10.7 folder?

In my ANT_HOME folder I have:
INSTALL NOTICE  bin get-m2.xml
KEYSREADME  etc lib
LICENSE WHATSNEWfetch.xml   manual

-Alex

On 5/10/20, 8:53 AM, "Harbs"  wrote:

I’m having trouble with the approval script.

I have ant installed with Homebrew and I don’t have a ANT_HOME var. I’m not 
sure why it’s necessary, but I can’t figure out what to use.

Homebrew puts ant in the following location: /usr/local/Cellar/ant/1.10.7 
If I set ANT_HOME to that, ant becomes non-functional and I get Error: Could 
not find or load main class org.apache.tools.ant.launch.Launcher.

Suggestions?
Harbs

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-10 Thread Harbs

I’m having trouble with the approval script.

I have ant installed with Homebrew and I don’t have a ANT_HOME var. I’m not 
sure why it’s necessary, but I can’t figure out what to use.

Homebrew puts ant in the following location: /usr/local/Cellar/ant/1.10.7 If I 
set ANT_HOME to that, ant becomes non-functional and I get Error: Could not 
find or load main class org.apache.tools.ant.launch.Launcher.

Suggestions?
Harbs

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-10 Thread Alex Harui

   > >
> >
> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/src/main/royale/Ace.mxml
> > > >>
> > > >> 0.655243136 seconds
> > > >>
> > > >>
> > > >>
> > >
> >
> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml(74):
> > > >> col: 0 Error: unable to open
> > > >>
> > > >>
> > >
> >
> 
'/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/libs/player/11.1/playerglobal.swc'.
> > > >>
> > > >>
> > > >>
> > >
> >
> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml
> > > >> (line: 74)
> > > >>
> > > >>
> > > >>   
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> BUILD FAILED
> > > >>
> > > >>
> > >
> /Users/carlosrovira/Downloads/royale097rc5/ApproveRoyale.xml:781:
> > The
> > > >> following error occurred while executing this
> line:
> > > >>
> > > >>
> > > >>
> > >
> >
> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/build.xml:659:
> > > >> The following error occurred while executing
> this
> > line:
> > > >>
> > > >>
> > > >>
> > >
> >
> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/build.xml:77:
> > > >> The following error occurred while executing
> this
> > line:
> > > >>
> > > >>
> > > >>
> > >
> >
> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/build_example.xml:157:
> > > >> mxmlc task failed.
> > > >>
> > > >>
> > > >> Total time: 6 minutes 44 seconds
> > > >>
> > > >> El vie., 8 may. 2020 a las 13:44, Yishay Weiss
> (<
> > > >> yishayj...@hotmail.com>)
> > > >> escribió:
> > > >>
> > > >> > Rc4 had an xml bug, rc3 couldn’t build maven
> from
> > > distribution
> > > >> sources. I
> > > >> > tested ApproveRoyale.xml and it worked for me
> for
> > this
> > > release.
> > > >> >
> > > >> > From: Piotr Zarzycki > piotrzarzyck...@gmail.com>
> > > >> > Sent: Friday, May 8, 2020 2:40 PM
> > > >> > To: Apache Royale Development > > dev@royale.apache.org>
> > > >> > Subject: Re: [DISCUSS] Discuss Release Apache
> > Royale 0.9.7
> > > >> >
> > > >> > What are the changes in comparison to the
> previous
> > RC? I'm
> > > >> interested
> > > >> > whether I can use  ApproveRoyale.xml
> > > >> > <
> > > >>
> > >
> >
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.7%2Frc5%2FApproveRoyale.xmldata=02%7C01%7Caharui%40adobe.com%7Cf8284f586e1246a31bf008d7f4b01a96%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637246909522588042sdata=OMQtz0oBTVDGpbnFFjGZBAzG%2FXHNhkG%2FwSBasUAjJ54%3Dreserved=0
> > > >> > >
> > > >> > script
> > > >> > ?
> > > >> >
> > > >> > pt., 8 maj 2020 o 13:29 <
> apacheroyal...@gmail.com>
> > > napisał(a):
> > > >> >
> > > >> > > This is the discussion thread.
> > > >> > >
> > > >> > > Thanks,
> > > >> > > Yishay Weiss
> > > >> >
> > > >> >
> > > >> >
> > > >> > --
> > > >> >
> > > >> > Piotr Zarzycki
> > > >> >
> > > >> > Patreon: *
> > > >>
> > >
> >
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Cf8284f586e1246a31bf008d7f4b01a96%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637246909522588042sdata=YdWgA8sSmSuhMcKoARfbTCOm6rDt8XcZgllz%2B8izpxk%3Dreserved=0
> > > >> > <
> > > >>
> > >
> >
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Cf8284f586e1246a31bf008d7f4b01a96%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637246909522588042sdata=YdWgA8sSmSuhMcKoARfbTCOm6rDt8XcZgllz%2B8izpxk%3Dreserved=0
> > > >> >*
> > > >> >
> > > >> >
> > > >>
> > > >> --
> > > >> Carlos Rovira
> > > >>
> > > >>
> > >
> >
> 
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7Cf8284f586e1246a31bf008d7f4b01a96%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637246909522588042sdata=HyHxXk5Y60v2oLfpGU7KXpkWL7lNSYwxIXgJ%2FubU42w%3Dreserved=0
> > > >>
> > > >>
> > > >>
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
>
>
>

-- 
Carlos Rovira

https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7Cf8284f586e1246a31bf008d7f4b01a96%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637246909522598031sdata=ofE%2F1K2zAJZVkPFEBDF7UA7HaRGCfP8FTp1jw473db8%3Dreserved=0

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-10 Thread Carlos Rovira

> > > >>
> > > >> Compiling Ace.swf
> > > >>
> > > >> ROYALE_HOME:
> > > >>
> > > >>
> > >
> >
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs
> > > >>
> > > >> ROYALE_COMPILER_HOME:
> > > >>
> > > >>
> > >
> >
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js
> > > >>
> > > >> GOOG_HOME:
> > > >>
> > > >>
> > >
> >
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js/lib/google/closure-library
> > > >>
> > > >> MXMLJSC
> > > >>
> > > >>
> > > >>
> > >
> >
> -load-config+=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/src/main/config/compile-app-config.xml
> > > >>
> > > >> +playerglobal.version=11.1
> > > >>
> > > >>
> >  +env.PLAYERGLOBAL_HOME=/Users/carlosrovira/Dev/Flash/Player
> > > >>
> > > >> -compiler.debug=true
> > > >>
> > > >>
> > > >>
> > >
> >
> +royalelib=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/
> > > >>
> > > >>
> > > >>
> > >
> >
> -closure-lib=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js/lib/google/closure-library
> > > >>
> > > >> +configname=royale
> > > >>
> > > >> -swf-version
> > > >>
> > > >> 14
> > > >>
> > > >>
> > > >>
> > >
> >
> -output=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/bin-debug/Ace.swf
> > > >>
> > > >> --
> > > >>
> > > >>
> > > >>
> > >
> >
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/src/main/royale/Ace.mxml
>     > >     >>
> > > >> 0.655243136 seconds
> > > >>
> > > >>
> > > >>
> > >
> >
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml(74):
> > > >> col: 0 Error: unable to open
> > > >>
> > > >>
> > >
> >
> '/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/libs/player/11.1/playerglobal.swc'.
> > > >>
> > > >>
> > > >>
> > >
> >
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml
> > > >> (line: 74)
> > > >>
> > > >>
> > > >>   
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> BUILD FAILED
> > > >>
> > > >>
> > >
> /Users/carlosrovira/Downloads/royale097rc5/ApproveRoyale.xml:781:
> > The
> > > >> following error occurred while executing this
> line:
> > > >>
>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-09 Thread Alex Harui

-src/royale-asjs/js/lib/google/closure-library
> > >>
> > >> +configname=royale
> > >>
> > >> -swf-version
> > >>
> > >> 14
> > >>
> > >>
> > >>
> >
> 
-output=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/bin-debug/Ace.swf
> > >>
> > >> --
> > >>
> > >>
> > >>
> >
> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/src/main/royale/Ace.mxml
> > >>
> > >> 0.655243136 seconds
> > >>
> > >>
> > >>
> >
> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml(74):
> > >> col: 0 Error: unable to open
> > >>
> > >>
> >
> 
'/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/libs/player/11.1/playerglobal.swc'.
> > >>
> > >>
> > >>
> >
> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml
> > >>     (line: 74)
    >     >     >>
    > > >>
> > >>   
> > >>
> > >>
> > >>
> > >>
> > >> BUILD FAILED
> > >>
> > >>
> >  /Users/carlosrovira/Downloads/royale097rc5/ApproveRoyale.xml:781:
> The
> > >> following error occurred while executing this line:
> > >>
> > >>
> > >>
> >
> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/build.xml:659:
> > >> The following error occurred while executing this
> line:
> > >>
> > >>
> > >>
> >
> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/build.xml:77:
> > >> The following error occurred while executing this
> line:
> > >>
> > >>
> > >>
> >
> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/build_example.xml:157:
> > >> mxmlc task failed.
> > >>
> > >>
> > >> Total time: 6 minutes 44 seconds
> > >>
> > >> El vie., 8 may. 2020 a las 13:44, Yishay Weiss (<
> > >> yishayj...@hotmail.com>)
> > >> escribió:
> > >>
> > >> > Rc4 had an xml bug, rc3 couldn’t build maven from
> > distribution
> > >> sources. I
> > >> > tested ApproveRoyale.xml and it worked for me for
> this
> > release.
> > >> >
> > >> > From: Piotr Zarzycki piotrzarzyck...@gmail.com>
> > >> > Sent: Friday, May 8, 2020 2:40 PM
> > >> > To: Apache Royale Development > dev@royale.apache.org>
> > >> > Subject: Re: [DISCUSS] Discuss Release Apache
> Royale 0.9.7
> > >> >
> > >> > What are the changes in comparison to the previous
> RC? I'm
> > >> interested
> > >> > whether I can use  ApproveRoyale.xml
> > >> > <
> > >>
> >
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.7%2Frc5%2FApproveRoyale.xmldata=02%7C01%7Caharui%40adobe.com%7C8f0434df56b24274577a08d7f46b4b87%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637246613980395149sdata=BsdRIUFMatRAO7C5QtFmoQK0ML64jhrLHs9KJ0wrd4I%3Dreserved=0
> > >> > >
> > >> > script
> > >> > ?
> > >> >
> > >> > pt., 8 maj 2020 o 13:29 
> > napisał(a):
> > >> >
> > >> > > This is the discussion thread.
> > >> > >
> > >> > > Thanks,
> > >> > > Yishay Weiss
> > >> >
> > >> >
> > >> >
> > >> > --
> > >> >
> > >> > Piotr Zarzycki
> > >> >
> > >> > Patreon: *
> > >>
> >
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7C8f0434df56b24274577a08d7f46b4b87%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637246613980405146sdata=x2EZ8TqMkdbu3CVVO1zAMqkT5L6Ezpy2cX5s8UBDaUA%3Dreserved=0
> > >> > <
> > >>
> >
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7C8f0434df56b24274577a08d7f46b4b87%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637246613980405146sdata=x2EZ8TqMkdbu3CVVO1zAMqkT5L6Ezpy2cX5s8UBDaUA%3Dreserved=0
> > >> >*
> > >> >
> > >> >
> > >>
> > >> --
> > >> Carlos Rovira
> > >>
> > >>
> >
> 
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C8f0434df56b24274577a08d7f46b4b87%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637246613980405146sdata=Q2bFpaJhnU7mIQESmYabmTiNuuExQdnvwxuAyWLnsxk%3Dreserved=0
> > >>
> > >>
> > >>
> >
> >
> >
> >
> >
>
>
>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-09 Thread Carlos Rovira

> >
> -closure-lib=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js/lib/google/closure-library
> > > >>
> > > >> +configname=royale
> > > >>
> > > >> -swf-version
> > > >>
> > > >> 14
> > > >>
> > > >>
> > > >>
> > >
> >
> -output=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/bin-debug/Ace.swf
> > > >>
> > > >> --
> > > >>
> > > >>
> > >     >>
> > >
> >
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/src/main/royale/Ace.mxml
> > > >>
> > > >> 0.655243136 seconds
> > > >>
> > > >>
> > > >>
> > >
> >
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml(74):
> > > >> col: 0 Error: unable to open
> > > >>
> > > >>
> > >
> >
> '/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/libs/player/11.1/playerglobal.swc'.
> > > >>
> > > >>
> > > >>
> > >
> >
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml
> > > >> (line: 74)
> > > >>
> > > >>
> > > >>   
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> BUILD FAILED
> > > >>
> > > >>
> > >  /Users/carlosrovira/Downloads/royale097rc5/ApproveRoyale.xml:781:
> > The
> > > >> following error occurred while executing this line:
> > > >>
> > > >>
> > > >>
> > >
> >
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/build.xml:659:
> > > >> The following error occurred while executing this
> > line:
> > > >>
> > > >>
> > > >>
> > >
> >
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/build.xml:77:
> > > >> The following error occurred while executing this
> > line:
> > > >>
> > > >>
> > > >>
> > >
> >
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/build_example.xml:157:
> > > >> mxmlc task failed.
> > > >>
> > > >>
> > > >> Total time: 6 minutes 44 seconds
> > > >>
> > > >> El vie., 8 may. 2020 a las 13:44, Yishay Weiss (<
> > > >> yishayj...@hotmail.com>)
> > > >> escribió:
> > > >>
> > > >> > Rc4 had an xml bug, rc3 couldn’t build maven from
> > > distribution
> > > >> sources. I
> > > >> > tested ApproveRoyale.xml and it worked for me for
> > this
> > > release.
> > > >> >
> > > >> > From: Piotr Zarzycki > piotrzarzyck...@gmail.com>
> > > >> > Sent: Friday, May 8, 2020 2:40 PM
> > > >> > To: Apache Royale Development > > dev@royale.apache.org>
> > > >> > Subject: Re: [DISCUSS] Discuss Release Apache
> > Royale 0.9.7
> > > >> >
> > > >> > What are the changes in comparison to the previous
> > RC? I'm
> > > >> interested
> > > >> > whether I can use  ApproveRoyale.xml
> > > >> > <
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.7%2Frc5%2FApproveRoyale.xmldata=02%7C01%7Caharui%40adobe.com%7Ce15ad53d26b040bb2f8308d7f4530937%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637246509831176293sdata=wATKdT98KCcivV0e7oq800m5co6wqANCGhOmUgnPAV8%3Dreserved=0
> > > >> > >
> > > >> > script
> > > >> > ?
> > > >> >
> > > >> > pt., 8 maj 2020 o 13:29  >
> > > napisał(a):
> > > >> >
> > > >> > > This is the discussion thread.
> > > >> > >
> > > >> > > Thanks,
> > > >> > > Yishay Weiss
> > > >> >
> > > >> >
> > > >> >
> > > >> > --
> > > >> >
> > > >> > Piotr Zarzycki
> > > >> >
> > > >> > Patreon: *
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Ce15ad53d26b040bb2f8308d7f4530937%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637246509831176293sdata=mMyxAKT6nQUOuKcpMxxtEVn4G%2FEFwQo9YivEsGaI6gQ%3Dreserved=0
> > > >> > <
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Ce15ad53d26b040bb2f8308d7f4530937%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637246509831176293sdata=mMyxAKT6nQUOuKcpMxxtEVn4G%2FEFwQo9YivEsGaI6gQ%3Dreserved=0
> > > >> >*
> > > >> >
> > > >> >
> > > >>
> > > >> --
> > > >> Carlos Rovira
> > > >>
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7Ce15ad53d26b040bb2f8308d7f4530937%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637246509831176293sdata=Mdpl6um0z1CoVXEZYAuoLe6AamPwgLcqzSOCJD7JGCo%3Dreserved=0
> > > >>
> > > >>
> > > >>
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
>


-- 
Carlos Rovira
http://about.me/carlosrovira

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-09 Thread Greg Dove

   > Does anyone have any clues?
> > > Thanks,
> > > Greg
> > >
> > > On Sat, May 9, 2020 at 6:31 AM Alex Harui
> > 
> > > wrote:
> > >
> > >> Carlos,
> > >>
> > >> What scenario are you testing?  If you are using "
> > -Duse-flash=true" then
> > >> is PLAYERGLOBAL_HOME and other environment variable set up
> > properly?
> > >>
> > >> -Alex
> > >>
> > >> On 5/8/20, 10:21 AM, "Carlos Rovira" <
> carlosrov...@apache.org>
> > wrote:
> > >>
> > >> Hi,
> > >>
> > >> I had a similar experience with approve xml, so I'll
> check
> > as I have
> > >> more
> > >> time during weekend in other way:
> > >>
> > >> build_example.compile:
> > >>
> > >> Compiling Ace.swf
> > >>
> > >> ROYALE_HOME:
> > >>
> > >>
> >
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs
> > >>
> > >> ROYALE_COMPILER_HOME:
> > >>
> > >>
> >
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js
> > >>
> > >> GOOG_HOME:
> > >>
> > >>
> >
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js/lib/google/closure-library
> > >>
> > >> MXMLJSC
> > >>
> > >>
> > >>
> >
> -load-config+=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/src/main/config/compile-app-config.xml
> > >>
> > >> +playerglobal.version=11.1
> > >>
> > >>
>  +env.PLAYERGLOBAL_HOME=/Users/carlosrovira/Dev/Flash/Player
> > >>
> > >> -compiler.debug=true
> > >>
> > >>
> > >>
> >
> +royalelib=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/
> > >>
> > >>
> > >>
> >
> -closure-lib=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js/lib/google/closure-library
> > >>
> > >> +configname=royale
> > >>
> > >> -swf-version
> > >>
> > >> 14
> > >>
> > >>
> > >>
> >
> -output=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/bin-debug/Ace.swf
> > >>
> > >> --
> > >>
> > >>
> > >>
> >
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/src/main/royale/Ace.mxml
> > >>
> > >> 0.655243136 seconds
> > >>
> > >>
> > >>
> >
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml(74):
> > >> col: 0 Error: unable to open
> > >>
> > >>
> >
> '/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/libs/player/11.1/playerglobal.swc'.
> > >>
> >         >>
>     >     >>
> >
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml
> > >> (line: 74)
> > >>
> > >>
> > >>   
> > >>
> > >>
> > >>
> >

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-09 Thread Alex Harui

h/Player
> >>
> >> -compiler.debug=true
> >>
> >>
> >>
> 
+royalelib=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/
> >>
> >>
> >>
> 
-closure-lib=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js/lib/google/closure-library
> >>
> >> +configname=royale
> >>
> >> -swf-version
> >>
> >> 14
> >>
> >>
> >>
> 
-output=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/bin-debug/Ace.swf
> >>
> >> --
> >>
> >>
> >>
> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/src/main/royale/Ace.mxml
> >>
> >> 0.655243136 seconds
> >>
> >>
> >>
> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml(74):
> >> col: 0 Error: unable to open
> >>
> >>
> 
'/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/libs/player/11.1/playerglobal.swc'.
> >>
> >>
> >>
> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml
> >> (line: 74)
> >>
> >>
> >>   
> >>
> >>
> >>
> >>
> >> BUILD FAILED
> >>
> >>
>  /Users/carlosrovira/Downloads/royale097rc5/ApproveRoyale.xml:781: The
> >> following error occurred while executing this line:
> >>
> >>
> >>
> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/build.xml:659:
> >> The following error occurred while executing this line:
> >>
> >>
> >>
> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/build.xml:77:
> >> The following error occurred while executing this line:
> >>
> >>
> >>
> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/build_example.xml:157:
> >> mxmlc task failed.
> >>
> >>
> >> Total time: 6 minutes 44 seconds
> >>
> >> El vie., 8 may. 2020 a las 13:44, Yishay Weiss (<
> >> yishayj...@hotmail.com>)
> >> escribió:
> >>
> >> > Rc4 had an xml bug, rc3 couldn’t build maven from
> distribution
> >> sources. I
> >> > tested ApproveRoyale.xml and it worked for me for this
> release.
> >> >
> >> > From: Piotr Zarzycki<mailto:piotrzarzyck...@gmail.com>
> >> > Sent: Friday, May 8, 2020 2:40 PM
> >> > To: Apache Royale Development dev@royale.apache.org>
> >> > Subject: Re: [DISCUSS] Discuss Release Apache Royale 
0.9.7
> >> >
> >> > What are the changes in comparison to the previous RC? 
I'm
> >> interested
> >> > whether I can use  ApproveRoyale.xml
> >> > <
> >>
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.7%2Frc5%2FApproveRoyale.xmldata=02%7C01%7Caharui%40adobe.com%7Ce15ad53d26b040bb2f8308d7f4530937%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637246509831176293sdata=wATKdT98KCcivV0e7oq800m5co6wqANCGhOmUgnPAV8%3Dreserved=0
> >> > >
> >> > script
> >> > ?
> >> >
> >> > pt., 8 maj 2020 o 13:29 
> napisał(a):
> >> >
> >> > > This is the discussion thread.
> >> > >
> >> > > Thanks,
> >> > > Yishay Weiss
> >> >
> >> >
> >> >
> >> > --
> >> >
> >> > Piotr Zarzycki
> >> >
> >> > Patreon: *
> >>
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Ce15ad53d26b040bb2f8308d7f4530937%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637246509831176293sdata=mMyxAKT6nQUOuKcpMxxtEVn4G%2FEFwQo9YivEsGaI6gQ%3Dreserved=0
> >> > <
> >>
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Ce15ad53d26b040bb2f8308d7f4530937%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637246509831176293sdata=mMyxAKT6nQUOuKcpMxxtEVn4G%2FEFwQo9YivEsGaI6gQ%3Dreserved=0
> >> >*
> >> >
> >> >
> >>
> >> --
> >> Carlos Rovira
> >>
> >>
> 
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7Ce15ad53d26b040bb2f8308d7f4530937%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637246509831176293sdata=Mdpl6um0z1CoVXEZYAuoLe6AamPwgLcqzSOCJD7JGCo%3Dreserved=0
> >>
> >>
> >>
>
>
>
>
>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-09 Thread Greg Dove

playerglobal.swc'.
> >>
> >>
> >>
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml
> >> (line: 74)
> >>
> >>
> >>   
> >>
> >>
> >>
> >>
> >> BUILD FAILED
> >>
> >>
>  /Users/carlosrovira/Downloads/royale097rc5/ApproveRoyale.xml:781: The
> >> following error occurred while executing this line:
>     >>
> >>
> >>
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/build.xml:659:
> >> The following error occurred while executing this line:
> >>
> >>
> >>
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/build.xml:77:
> >> The following error occurred while executing this line:
> >>
> >>
> >>
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/build_example.xml:157:
> >> mxmlc task failed.
> >>
> >>
> >> Total time: 6 minutes 44 seconds
> >>
> >> El vie., 8 may. 2020 a las 13:44, Yishay Weiss (<
> >> yishayj...@hotmail.com>)
> >> escribió:
> >>
> >> > Rc4 had an xml bug, rc3 couldn’t build maven from
> distribution
> >> sources. I
> >> > tested ApproveRoyale.xml and it worked for me for this
> release.
> >> >
> >> > From: Piotr Zarzycki<mailto:piotrzarzyck...@gmail.com>
> >> > Sent: Friday, May 8, 2020 2:40 PM
> >> > To: Apache Royale Development dev@royale.apache.org>
> >> > Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7
> >> >
> >> > What are the changes in comparison to the previous RC? I'm
> >> interested
> >> > whether I can use  ApproveRoyale.xml
> >> > <
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.7%2Frc5%2FApproveRoyale.xmldata=02%7C01%7Caharui%40adobe.com%7C5673a89559ab4f9192c608d7f3dcac51%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637246001469309474sdata=fb7TPt8w99nBA6XainkulIxnS6yE7DZzpxB88B3fQRU%3Dreserved=0
> >> > >
> >> > script
> >> > ?
> >> >
> >> > pt., 8 maj 2020 o 13:29 
> napisał(a):
> >> >
> >> > > This is the discussion thread.
> >> > >
> >> > > Thanks,
> >> > > Yishay Weiss
> >> >
> >> >
> >> >
> >> > --
> >> >
> >> > Piotr Zarzycki
> >> >
> >> > Patreon: *
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7C5673a89559ab4f9192c608d7f3dcac51%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637246001469309474sdata=tCYsNkFH0Aq%2FPUSHDix97dBf8%2FVd5pMT6BHPdvsQjLQ%3Dreserved=0
> >> > <
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7C5673a89559ab4f9192c608d7f3dcac51%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637246001469309474sdata=tCYsNkFH0Aq%2FPUSHDix97dBf8%2FVd5pMT6BHPdvsQjLQ%3Dreserved=0
> >> >*
> >> >
> >> >
> >>
> >> --
> >> Carlos Rovira
> >>
> >>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C5673a89559ab4f9192c608d7f3dcac51%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637246001469309474sdata=HanXAncqzaXgAem0stZeHaggXUrnlVQAs8j2uwjO1ro%3Dreserved=0
> >>
> >>
> >>
>
>
>
>
>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-09 Thread Carlos Rovira

t;>>
>>>>> -Alex
>>>>>
>>>>> On 5/8/20, 10:21 AM, "Carlos Rovira"  wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> I had a similar experience with approve xml, so I'll check as I
>>>>> have more
>>>>> time during weekend in other way:
>>>>>
>>>>> build_example.compile:
>>>>>
>>>>> Compiling Ace.swf
>>>>>
>>>>> ROYALE_HOME:
>>>>>
>>>>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs
>>>>>
>>>>> ROYALE_COMPILER_HOME:
>>>>>
>>>>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js
>>>>>
>>>>> GOOG_HOME:
>>>>>
>>>>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js/lib/google/closure-library
>>>>>
>>>>> MXMLJSC
>>>>>
>>>>>
>>>>> -load-config+=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/src/main/config/compile-app-config.xml
>>>>>
>>>>> +playerglobal.version=11.1
>>>>>
>>>>> +env.PLAYERGLOBAL_HOME=/Users/carlosrovira/Dev/Flash/Player
>>>>>
>>>>> -compiler.debug=true
>>>>>
>>>>>
>>>>> +royalelib=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/
>>>>>
>>>>>
>>>>> -closure-lib=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js/lib/google/closure-library
>>>>>
>>>>> +configname=royale
>>>>>
>>>>> -swf-version
>>>>>
>>>>> 14
>>>>>
>>>>>
>>>>> -output=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/bin-debug/Ace.swf
>>>>>
>>>>> --
>>>>>
>>>>>
>>>>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/src/main/royale/Ace.mxml
>>>>>
>>>>> 0.655243136 seconds
>>>>>
>>>>>
>>>>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml(74):
>>>>> col: 0 Error: unable to open
>>>>>
>>>>> '/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/libs/player/11.1/playerglobal.swc'.
>>>>>
>>>>>
>>>>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml
>>>>> (line: 74)
>>>>>
>>>>>
>>>>>   
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> BUILD FAILED
>>>>>
>>>>> /Users/carlosrovira/Downloads/royale097rc5/ApproveRoyale.xml:781:
>>>>> The
>>>>> following error occurred while executing this line:
>>>>>
>>>>>
>>>>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/build.xml:659:
>>>>> The following error occurred while executing this line:
>>>>>
>>>>>
>>>>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/build.xml:77:
>>>>> The following error occurred while executing this line:
>>>>>
>>>>>
>>>>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/build_example.xml:157:
>>>>> mxmlc task failed.
>>>>>
>>>>>
>>>>> Total time: 6 minutes 44 seconds
>>>>>
>>>>> El vie., 8 may. 2020 a las 13:44, Yishay Weiss (<
>>>>> yishayj...@hotmail.com>)
>>>>> escribió:
>>>>>
>>>>> > Rc4 had an xml bug, rc3 couldn’t build maven from distribution
>>>>> sources. I
>>>>> > tested ApproveRoyale.xml and it worked for me for this release.
>>>>> >
>>>>> > From: Piotr Zarzycki<mailto:piotrzarzyck...@gmail.com>
>>>>> > Sent: Friday, May 8, 2020 2:40 PM
>>>>> > To: Apache Royale Development<mailto:dev@royale.apache.org>
>>>>> > Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7
>>>>> >
>>>>> > What are the changes in comparison to the previous RC? I'm
>>>>> interested
>>>>> > whether I can use  ApproveRoyale.xml
>>>>> > <
>>>>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.7%2Frc5%2FApproveRoyale.xmldata=02%7C01%7Caharui%40adobe.com%7C78411875091249af8a8308d7f3744b71%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637245553115240738sdata=aI3XkJzWy60XnLerQ2F1idJsY2Sr%2BX78wDezgsoosdM%3Dreserved=0
>>>>> > >
>>>>> > script
>>>>> > ?
>>>>> >
>>>>> > pt., 8 maj 2020 o 13:29  napisał(a):
>>>>> >
>>>>> > > This is the discussion thread.
>>>>> > >
>>>>> > > Thanks,
>>>>> > > Yishay Weiss
>>>>> >
>>>>> >
>>>>> >
>>>>> > --
>>>>> >
>>>>> > Piotr Zarzycki
>>>>> >
>>>>> > Patreon: *
>>>>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7C78411875091249af8a8308d7f3744b71%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637245553115240738sdata=%2B%2BcrUnwxDk2PJ1DMDKKOfaAOendlSFsHuykEv3MqKpY%3Dreserved=0
>>>>> > <
>>>>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7C78411875091249af8a8308d7f3744b71%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637245553115240738sdata=%2B%2BcrUnwxDk2PJ1DMDKKOfaAOendlSFsHuykEv3MqKpY%3Dreserved=0
>>>>> >*
>>>>> >
>>>>> >
>>>>>
>>>>> --
>>>>> Carlos Rovira
>>>>>
>>>>> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C78411875091249af8a8308d7f3744b71%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637245553115240738sdata=8qT4GaOC3WSS%2FPihAkExVC83BvkpgSE%2BirVYGRmx4nE%3Dreserved=0
>>>>>
>>>>>
>>>>>
>>>>
>>>> --
>>>> Carlos Rovira
>>>> http://about.me/carlosrovira
>>>>
>>>>
>>>
>>> --
>>> Carlos Rovira
>>> http://about.me/carlosrovira
>>>
>>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

-- 
Carlos Rovira
http://about.me/carlosrovira

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-09 Thread Carlos Rovira

enario are you testing?  If you are using " -Duse-flash=true"
>>>> then is PLAYERGLOBAL_HOME and other environment variable set up properly?
>>>>
>>>> -Alex
>>>>
>>>> On 5/8/20, 10:21 AM, "Carlos Rovira"  wrote:
>>>>
>>>> Hi,
>>>>
>>>> I had a similar experience with approve xml, so I'll check as I
>>>> have more
>>>> time during weekend in other way:
>>>>
>>>> build_example.compile:
>>>>
>>>> Compiling Ace.swf
>>>>
>>>> ROYALE_HOME:
>>>>
>>>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs
>>>>
>>>> ROYALE_COMPILER_HOME:
>>>>
>>>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js
>>>>
>>>> GOOG_HOME:
>>>>
>>>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js/lib/google/closure-library
>>>>
>>>> MXMLJSC
>>>>
>>>>
>>>> -load-config+=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/src/main/config/compile-app-config.xml
>>>>
>>>> +playerglobal.version=11.1
>>>>
>>>> +env.PLAYERGLOBAL_HOME=/Users/carlosrovira/Dev/Flash/Player
>>>>
>>>> -compiler.debug=true
>>>>
>>>>
>>>> +royalelib=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/
>>>>
>>>>
>>>> -closure-lib=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js/lib/google/closure-library
>>>>
>>>> +configname=royale
>>>>
>>>> -swf-version
>>>>
>>>> 14
>>>>
>>>>
>>>> -output=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/bin-debug/Ace.swf
>>>>
>>>> --
>>>>
>>>>
>>>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/src/main/royale/Ace.mxml
>>>>
>>>> 0.655243136 seconds
>>>>
>>>>
>>>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml(74):
>>>> col: 0 Error: unable to open
>>>>
>>>> '/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/libs/player/11.1/playerglobal.swc'.
>>>>
>>>>
>>>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml
>>>> (line: 74)
>>>>
>>>>
>>>>   
>>>>
>>>>
>>>>
>>>>
>>>> BUILD FAILED
>>>>
>>>> /Users/carlosrovira/Downloads/royale097rc5/ApproveRoyale.xml:781:
>>>> The
>>>> following error occurred while executing this line:
>>>>
>>>>
>>>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/build.xml:659:
>>>> The following error occurred while executing this line:
>>>>
>>>>
>>>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/build.xml:77:
>>>> The following error occurred while executing this line:
>>>>
>>>>
>>>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/build_example.xml:157:
>>>> mxmlc task failed.
>>>>
>>>>
>>>> Total time: 6 minutes 44 seconds
>>>>
>>>> El vie., 8 may. 2020 a las 13:44, Yishay Weiss (<
>>>> yishayj...@hotmail.com>)
>>>> escribió:
>>>>
>>>> > Rc4 had an xml bug, rc3 couldn’t build maven from distribution
>>>> sources. I
>>>> > tested ApproveRoyale.xml and it worked for me for this release.
>>>> >
>>>> > From: Piotr Zarzycki<mailto:piotrzarzyck...@gmail.com>
>>>> > Sent: Friday, May 8, 2020 2:40 PM
>>>> > To: Apache Royale Development<mailto:dev@royale.apache.org>
>>>> > Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7
>>>>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-09 Thread Carlos Rovira

for now I need to enable my AIR_HOME var in ,bash_profile.
Maybe that need could be removed in ANT, in MAVEN is not needed anymore
although we add flash to the build

El sáb., 9 may. 2020 a las 10:16, Carlos Rovira ()
escribió:

> forgot to say that I used:
>
> ant -e -f ApproveRoyale.xml -Drelease.version=0.9.7 -Drc=5
>
> so no flash tested, going to try with flash enabled now
>
>
>
> El sáb., 9 may. 2020 a las 10:12, Carlos Rovira ()
> escribió:
>
>> Hi Alex,
>>
>> I post the sensible part of my .bash_profile:
>>
>> export JAVA_HOME=$(/usr/libexec/java_home -v 1.8)
>>
>> export ANT_HOME=/usr/local/Cellar/ant/1.10.7/libexec
>>
>> export MAVEN_OPTS="-Xms256m -Xmx1820m"
>>
>> export PLAYERGLOBAL_HOME=~/Dev/Flash/Player
>>
>> export PLAYERGLOBAL_VERSION=30.0
>>
>> export FLASHPLAYER_DEBUGGER=/Applications/Flash\
>> Player.app/Contents/MacOS/Flash\ Player\$
>>
>> export ROYALE_HOME=~/Dev/Royale/Sdks/apache-royale-maven
>>
>> export ROYALE_ASJS_HOME=~/Dev/Royale/Source/royale-asjs
>>
>> export ROYALE_COMPILER_HOME=~/Dev/Royale/Source/royale-compiler
>>
>> export ROYALE_TYPEDEFS_HOME=~/Dev/Royale/Source/royale-typedefs
>>
>> export TLF_HOME=~/Dev/Flex/Source/flex-tlf
>>
>> export FLEXUNIT_HOME=~/Dev/Flex/Source/flex-flexunit
>>
>>
>> I think I have all needed
>>
>> Thanks
>>
>> Carlos
>>
>>
>> El vie., 8 may. 2020 a las 20:31, Alex Harui ()
>> escribió:
>>
>>> Carlos,
>>>
>>> What scenario are you testing?  If you are using " -Duse-flash=true"
>>> then is PLAYERGLOBAL_HOME and other environment variable set up properly?
>>>
>>> -Alex
>>>
>>> On 5/8/20, 10:21 AM, "Carlos Rovira"  wrote:
>>>
>>> Hi,
>>>
>>> I had a similar experience with approve xml, so I'll check as I have
>>> more
>>> time during weekend in other way:
>>>
>>> build_example.compile:
>>>
>>> Compiling Ace.swf
>>>
>>> ROYALE_HOME:
>>>
>>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs
>>>
>>> ROYALE_COMPILER_HOME:
>>>
>>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js
>>>
>>> GOOG_HOME:
>>>
>>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js/lib/google/closure-library
>>>
>>> MXMLJSC
>>>
>>>
>>> -load-config+=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/src/main/config/compile-app-config.xml
>>>
>>> +playerglobal.version=11.1
>>>
>>> +env.PLAYERGLOBAL_HOME=/Users/carlosrovira/Dev/Flash/Player
>>>
>>> -compiler.debug=true
>>>
>>>
>>> +royalelib=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/
>>>
>>>
>>> -closure-lib=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js/lib/google/closure-library
>>>
>>> +configname=royale
>>>
>>> -swf-version
>>>
>>> 14
>>>
>>>
>>> -output=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/bin-debug/Ace.swf
>>>
>>> --
>>>
>>>
>>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/src/main/royale/Ace.mxml
>>>
>>> 0.655243136 seconds
>>>
>>>
>>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml(74):
>>> col: 0 Error: unable to open
>>>
>>> '/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/libs/player/11.1/playerglobal.swc'.
>>>
>>>
>>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml
>>> (line: 74)
>>>
>>>
>>>   
>>>
>>>
>>>
>>>
>>> BUILD FAILED
>>>
>>> /Users/carlosrovira/Downloads/royale097rc5/ApproveRoyale.xml:781: The
>>> following error occurred while executing this line:
>>>
>>>
>>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/build.xml:659:
&

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-09 Thread Carlos Rovira

forgot to say that I used:

ant -e -f ApproveRoyale.xml -Drelease.version=0.9.7 -Drc=5

so no flash tested, going to try with flash enabled now



El sáb., 9 may. 2020 a las 10:12, Carlos Rovira ()
escribió:

> Hi Alex,
>
> I post the sensible part of my .bash_profile:
>
> export JAVA_HOME=$(/usr/libexec/java_home -v 1.8)
>
> export ANT_HOME=/usr/local/Cellar/ant/1.10.7/libexec
>
> export MAVEN_OPTS="-Xms256m -Xmx1820m"
>
> export PLAYERGLOBAL_HOME=~/Dev/Flash/Player
>
> export PLAYERGLOBAL_VERSION=30.0
>
> export FLASHPLAYER_DEBUGGER=/Applications/Flash\
> Player.app/Contents/MacOS/Flash\ Player\$
>
> export ROYALE_HOME=~/Dev/Royale/Sdks/apache-royale-maven
>
> export ROYALE_ASJS_HOME=~/Dev/Royale/Source/royale-asjs
>
> export ROYALE_COMPILER_HOME=~/Dev/Royale/Source/royale-compiler
>
> export ROYALE_TYPEDEFS_HOME=~/Dev/Royale/Source/royale-typedefs
>
> export TLF_HOME=~/Dev/Flex/Source/flex-tlf
>
> export FLEXUNIT_HOME=~/Dev/Flex/Source/flex-flexunit
>
>
> I think I have all needed
>
> Thanks
>
> Carlos
>
>
> El vie., 8 may. 2020 a las 20:31, Alex Harui ()
> escribió:
>
>> Carlos,
>>
>> What scenario are you testing?  If you are using " -Duse-flash=true" then
>> is PLAYERGLOBAL_HOME and other environment variable set up properly?
>>
>> -Alex
>>
>> On 5/8/20, 10:21 AM, "Carlos Rovira"  wrote:
>>
>> Hi,
>>
>> I had a similar experience with approve xml, so I'll check as I have
>> more
>> time during weekend in other way:
>>
>> build_example.compile:
>>
>> Compiling Ace.swf
>>
>> ROYALE_HOME:
>>
>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs
>>
>> ROYALE_COMPILER_HOME:
>>
>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js
>>
>> GOOG_HOME:
>>
>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js/lib/google/closure-library
>>
>> MXMLJSC
>>
>>
>> -load-config+=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/src/main/config/compile-app-config.xml
>>
>> +playerglobal.version=11.1
>>
>> +env.PLAYERGLOBAL_HOME=/Users/carlosrovira/Dev/Flash/Player
>>
>> -compiler.debug=true
>>
>>
>> +royalelib=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/
>>
>>
>> -closure-lib=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js/lib/google/closure-library
>>
>> +configname=royale
>>
>> -swf-version
>>
>> 14
>>
>>
>> -output=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/bin-debug/Ace.swf
>>
>> --
>>
>>
>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/src/main/royale/Ace.mxml
>>
>> 0.655243136 seconds
>>
>>
>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml(74):
>> col: 0 Error: unable to open
>>
>> '/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/libs/player/11.1/playerglobal.swc'.
>>
>>
>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml
>> (line: 74)
>>
>>
>>   
>>
>>
>>
>>
>> BUILD FAILED
>>
>> /Users/carlosrovira/Downloads/royale097rc5/ApproveRoyale.xml:781: The
>> following error occurred while executing this line:
>>
>>
>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/build.xml:659:
>> The following error occurred while executing this line:
>>
>>
>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/build.xml:77:
>> The following error occurred while executing this line:
>>
>>
>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/build_example.xml:157:
>> mxmlc task failed.
>>
>>
>> Total time: 6 minutes 44 seconds
>>
>> El vie., 8 may. 2020 a las 13:44, Yishay Weiss (<
>> yishayj...@hotmail.com>)
>> escribió:
>>
>> > Rc4 had an xml bug, rc3 couldn’t build maven from distribution
>> sources. I
>> > teste

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-09 Thread Carlos Rovira

Hi Alex,

I post the sensible part of my .bash_profile:

export JAVA_HOME=$(/usr/libexec/java_home -v 1.8)

export ANT_HOME=/usr/local/Cellar/ant/1.10.7/libexec

export MAVEN_OPTS="-Xms256m -Xmx1820m"

export PLAYERGLOBAL_HOME=~/Dev/Flash/Player

export PLAYERGLOBAL_VERSION=30.0

export FLASHPLAYER_DEBUGGER=/Applications/Flash\
Player.app/Contents/MacOS/Flash\ Player\$

export ROYALE_HOME=~/Dev/Royale/Sdks/apache-royale-maven

export ROYALE_ASJS_HOME=~/Dev/Royale/Source/royale-asjs

export ROYALE_COMPILER_HOME=~/Dev/Royale/Source/royale-compiler

export ROYALE_TYPEDEFS_HOME=~/Dev/Royale/Source/royale-typedefs

export TLF_HOME=~/Dev/Flex/Source/flex-tlf

export FLEXUNIT_HOME=~/Dev/Flex/Source/flex-flexunit


I think I have all needed

Thanks

Carlos


El vie., 8 may. 2020 a las 20:31, Alex Harui ()
escribió:

> Carlos,
>
> What scenario are you testing?  If you are using " -Duse-flash=true" then
> is PLAYERGLOBAL_HOME and other environment variable set up properly?
>
> -Alex
>
> On 5/8/20, 10:21 AM, "Carlos Rovira"  wrote:
>
> Hi,
>
> I had a similar experience with approve xml, so I'll check as I have
> more
> time during weekend in other way:
>
> build_example.compile:
>
> Compiling Ace.swf
>
> ROYALE_HOME:
>
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs
>
> ROYALE_COMPILER_HOME:
>
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js
>
> GOOG_HOME:
>
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js/lib/google/closure-library
>
> MXMLJSC
>
>
> -load-config+=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/src/main/config/compile-app-config.xml
>
> +playerglobal.version=11.1
>
> +env.PLAYERGLOBAL_HOME=/Users/carlosrovira/Dev/Flash/Player
>
> -compiler.debug=true
>
>
> +royalelib=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/
>
>
> -closure-lib=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js/lib/google/closure-library
>
> +configname=royale
>
> -swf-version
>
> 14
>
>
> -output=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/bin-debug/Ace.swf
>
> --
>
>
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/src/main/royale/Ace.mxml
>
> 0.655243136 seconds
>
>
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml(74):
> col: 0 Error: unable to open
>
> '/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/libs/player/11.1/playerglobal.swc'.
>
>
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml
> (line: 74)
>
>
>   
>
>
>
>
> BUILD FAILED
>
> /Users/carlosrovira/Downloads/royale097rc5/ApproveRoyale.xml:781: The
> following error occurred while executing this line:
>
>
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/build.xml:659:
> The following error occurred while executing this line:
>
>
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/build.xml:77:
> The following error occurred while executing this line:
>
>
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/build_example.xml:157:
> mxmlc task failed.
>
>
> Total time: 6 minutes 44 seconds
>
> El vie., 8 may. 2020 a las 13:44, Yishay Weiss (<
> yishayj...@hotmail.com>)
> escribió:
>
>     > Rc4 had an xml bug, rc3 couldn’t build maven from distribution
> sources. I
> > tested ApproveRoyale.xml and it worked for me for this release.
> >
> > From: Piotr Zarzycki<mailto:piotrzarzyck...@gmail.com>
> > Sent: Friday, May 8, 2020 2:40 PM
> > To: Apache Royale Development<mailto:dev@royale.apache.org>
> > Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7
> >
> > What are the changes in comparison to the previous RC? I'm interested
> > whether I can use  ApproveRoyale.xml
> > <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.7%2Frc5%2FApproveRoyale.xmldata=02%7C01%7Caharui%40adobe.com%7C78411875091249af8a8308d7f3744b71%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637245553115240738sdata=aI3XkJzWy60XnLerQ2F1idJsY

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-09 Thread Alex Harui

>
> Does anyone have any clues?
> Thanks,
> Greg
>
> On Sat, May 9, 2020 at 6:31 AM Alex Harui 
> wrote:
>
>> Carlos,
>>
>> What scenario are you testing?  If you are using " -Duse-flash=true" 
then
>> is PLAYERGLOBAL_HOME and other environment variable set up properly?
>>
>> -Alex
>>
>> On 5/8/20, 10:21 AM, "Carlos Rovira"  wrote:
>>
>> Hi,
>>
>> I had a similar experience with approve xml, so I'll check as I 
have
>> more
>> time during weekend in other way:
>>
>> build_example.compile:
>>
>> Compiling Ace.swf
>>
>> ROYALE_HOME:
>>
>> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs
>>
>> ROYALE_COMPILER_HOME:
>>
>> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js
>>
>> GOOG_HOME:
>>
>> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js/lib/google/closure-library
>>
>> MXMLJSC
>>
>>
>> 
-load-config+=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/src/main/config/compile-app-config.xml
>>
>> +playerglobal.version=11.1
>>
>> +env.PLAYERGLOBAL_HOME=/Users/carlosrovira/Dev/Flash/Player
>>
>> -compiler.debug=true
>>
>>
>> 
+royalelib=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/
>>
>>
>> 
-closure-lib=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js/lib/google/closure-library
>>
>> +configname=royale
>>
>> -swf-version
>>
>> 14
>>
>>
>> 
-output=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/bin-debug/Ace.swf
>>
>> --
>>
>>
>> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/src/main/royale/Ace.mxml
>>
>> 0.655243136 seconds
>>
>>
>> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml(74):
>> col: 0 Error: unable to open
>>
>> 
'/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/libs/player/11.1/playerglobal.swc'.
>>
>>
>> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml
>> (line: 74)
>>
>>
>>   
>>
>>
>>
>>
>> BUILD FAILED
>>
>> 
/Users/carlosrovira/Downloads/royale097rc5/ApproveRoyale.xml:781: The
>> following error occurred while executing this line:
>>
>>
>> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/build.xml:659:
>> The following error occurred while executing this line:
>>
>>
>> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/build.xml:77:
>> The following error occurred while executing this line:
>>
>>
>> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/build_example.xml:157:
>> mxmlc task failed.
>>
>>
>> Total time: 6 minutes 44 seconds
>>
>> El vie., 8 may. 2020 a las 13:44, Yishay Weiss (<
>> yishayj...@hotmail.com>)
>> escribió:
>>
>> > Rc4 had an xml bug, rc3 couldn’t build maven from distribution
>> sources. I
>> > tested ApproveRoyale.xml and it worked for me for this release.
>> >
>> > From: Piotr Zarzycki<mailto:piotrzarzyck...@gmail.com>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-08 Thread Alex Harui

>
>> -Alex
>>
>> On 5/8/20, 10:21 AM, "Carlos Rovira"  wrote:
>>
>> Hi,
>>
>> I had a similar experience with approve xml, so I'll check as I have
>> more
>> time during weekend in other way:
>>
>> build_example.compile:
>>
>> Compiling Ace.swf
>>
>> ROYALE_HOME:
>>
>> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs
>>
>> ROYALE_COMPILER_HOME:
>>
>> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js
>>
>> GOOG_HOME:
>>
>> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js/lib/google/closure-library
>>
>> MXMLJSC
>>
>>
>> 
-load-config+=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/src/main/config/compile-app-config.xml
>>
>> +playerglobal.version=11.1
>>
>> +env.PLAYERGLOBAL_HOME=/Users/carlosrovira/Dev/Flash/Player
>>
>> -compiler.debug=true
>>
>>
>> 
+royalelib=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/
>>
>>
>> 
-closure-lib=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js/lib/google/closure-library
>>
>> +configname=royale
>>
>> -swf-version
>>
>> 14
>>
>>
>> 
-output=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/bin-debug/Ace.swf
>>
>> --
>>
>>
>> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/src/main/royale/Ace.mxml
>>
>> 0.655243136 seconds
>>
>>
>> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml(74):
>> col: 0 Error: unable to open
>>
>> 
'/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/libs/player/11.1/playerglobal.swc'.
>>
>>
>> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml
>> (line: 74)
>>
>>
>>   
>>
>>
>>
>>
>> BUILD FAILED
>>
>> /Users/carlosrovira/Downloads/royale097rc5/ApproveRoyale.xml:781: The
>> following error occurred while executing this line:
>>
>>
>> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/build.xml:659:
>> The following error occurred while executing this line:
>>
>>
>> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/build.xml:77:
>> The following error occurred while executing this line:
>>
    >>
    >> 
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/build_example.xml:157:
>> mxmlc task failed.
>>
>>
>> Total time: 6 minutes 44 seconds
>>
>> El vie., 8 may. 2020 a las 13:44, Yishay Weiss (<
>> yishayj...@hotmail.com>)
>> escribió:
>>
>> > Rc4 had an xml bug, rc3 couldn’t build maven from distribution
>> sources. I
>> > tested ApproveRoyale.xml and it worked for me for this release.
>> >
>> > From: Piotr Zarzycki<mailto:piotrzarzyck...@gmail.com>
>> > Sent: Friday, May 8, 2020 2:40 PM
>> > To: Apache Royale Development<mailto:dev@royale.apache.org>
>> > Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7
>> >
>> > What are the changes in comparison to the previous RC? I'm
>> interested
>> > whether I can use  ApproveRoyale.xml
>> > <
>> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.7%2Frc5%2FApproveRoyale.xmldata=02%7C01%7Caharui%40adobe.com%7C73949aa768c043b280b408d7f3d6098c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637245972940550782sdata=eAfkwFy2Z9EMedVQcfIXKGYKe5UplT13QnXkcfr5rhQ%3Dreserved=0
>> > >
>> &g

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-08 Thread Greg Dove

/src/main/royale/Ace.mxml
>>
>> 0.655243136 seconds
>>
>>
>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml(74):
>> col: 0 Error: unable to open
>>
>> '/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/libs/player/11.1/playerglobal.swc'.
>>
>>
>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml
>> (line: 74)
>>
>>
>>   
>>
>>
>>
>>
>> BUILD FAILED
>>
>> /Users/carlosrovira/Downloads/royale097rc5/ApproveRoyale.xml:781: The
>> following error occurred while executing this line:
>>
>>
>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/build.xml:659:
>> The following error occurred while executing this line:
>>
>>
>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/build.xml:77:
>> The following error occurred while executing this line:
>>
>>
>> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/build_example.xml:157:
>> mxmlc task failed.
>>
>>
>> Total time: 6 minutes 44 seconds
>>
>> El vie., 8 may. 2020 a las 13:44, Yishay Weiss (<
>> yishayj...@hotmail.com>)
>> escribió:
>>
>> > Rc4 had an xml bug, rc3 couldn’t build maven from distribution
>> sources. I
>> > tested ApproveRoyale.xml and it worked for me for this release.
>> >
>> > From: Piotr Zarzycki<mailto:piotrzarzyck...@gmail.com>
>> > Sent: Friday, May 8, 2020 2:40 PM
>> > To: Apache Royale Development<mailto:dev@royale.apache.org>
>> > Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7
>> >
>> > What are the changes in comparison to the previous RC? I'm
>> interested
>> > whether I can use  ApproveRoyale.xml
>> > <
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.7%2Frc5%2FApproveRoyale.xmldata=02%7C01%7Caharui%40adobe.com%7C78411875091249af8a8308d7f3744b71%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637245553115240738sdata=aI3XkJzWy60XnLerQ2F1idJsY2Sr%2BX78wDezgsoosdM%3Dreserved=0
>> > >
>> > script
>> > ?
>> >
>> > pt., 8 maj 2020 o 13:29  napisał(a):
>> >
>> > > This is the discussion thread.
>> > >
>> > > Thanks,
>> > > Yishay Weiss
>> >
>> >
>> >
>> > --
>> >
>> > Piotr Zarzycki
>> >
>> > Patreon: *
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7C78411875091249af8a8308d7f3744b71%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637245553115240738sdata=%2B%2BcrUnwxDk2PJ1DMDKKOfaAOendlSFsHuykEv3MqKpY%3Dreserved=0
>> > <
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7C78411875091249af8a8308d7f3744b71%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637245553115240738sdata=%2B%2BcrUnwxDk2PJ1DMDKKOfaAOendlSFsHuykEv3MqKpY%3Dreserved=0
>> >*
>> >
>> >
>>
>> --
>> Carlos Rovira
>>
>> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C78411875091249af8a8308d7f3744b71%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637245553115240738sdata=8qT4GaOC3WSS%2FPihAkExVC83BvkpgSE%2BirVYGRmx4nE%3Dreserved=0
>>
>>
>>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-08 Thread Greg Dove

rs/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/build.xml:77:
> The following error occurred while executing this line:
>
>
> /Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/build_example.xml:157:
> mxmlc task failed.
>
>
> Total time: 6 minutes 44 seconds
>
> El vie., 8 may. 2020 a las 13:44, Yishay Weiss (<
> yishayj...@hotmail.com>)
> escribió:
>
> > Rc4 had an xml bug, rc3 couldn’t build maven from distribution
> sources. I
> > tested ApproveRoyale.xml and it worked for me for this release.
> >
> > From: Piotr Zarzycki<mailto:piotrzarzyck...@gmail.com>
> > Sent: Friday, May 8, 2020 2:40 PM
> > To: Apache Royale Development<mailto:dev@royale.apache.org>
> > Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7
> >
> > What are the changes in comparison to the previous RC? I'm interested
> > whether I can use  ApproveRoyale.xml
> > <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.7%2Frc5%2FApproveRoyale.xmldata=02%7C01%7Caharui%40adobe.com%7C78411875091249af8a8308d7f3744b71%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637245553115240738sdata=aI3XkJzWy60XnLerQ2F1idJsY2Sr%2BX78wDezgsoosdM%3Dreserved=0
> > >
> > script
> > ?
> >
> > pt., 8 maj 2020 o 13:29  napisał(a):
> >
> > > This is the discussion thread.
> > >
> > > Thanks,
> > > Yishay Weiss
> >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7C78411875091249af8a8308d7f3744b71%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637245553115240738sdata=%2B%2BcrUnwxDk2PJ1DMDKKOfaAOendlSFsHuykEv3MqKpY%3Dreserved=0
> > <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7C78411875091249af8a8308d7f3744b71%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637245553115240738sdata=%2B%2BcrUnwxDk2PJ1DMDKKOfaAOendlSFsHuykEv3MqKpY%3Dreserved=0
> >*
> >
> >
>
> --
> Carlos Rovira
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C78411875091249af8a8308d7f3744b71%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637245553115240738sdata=8qT4GaOC3WSS%2FPihAkExVC83BvkpgSE%2BirVYGRmx4nE%3Dreserved=0
>
>
>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-08 Thread Alex Harui

Carlos,

What scenario are you testing?  If you are using " -Duse-flash=true" then is 
PLAYERGLOBAL_HOME and other environment variable set up properly?

-Alex

On 5/8/20, 10:21 AM, "Carlos Rovira"  wrote:

Hi,

I had a similar experience with approve xml, so I'll check as I have more
time during weekend in other way:

build_example.compile:

Compiling Ace.swf

ROYALE_HOME:

/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs

ROYALE_COMPILER_HOME:

/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js

GOOG_HOME:

/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js/lib/google/closure-library

MXMLJSC


-load-config+=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/src/main/config/compile-app-config.xml

+playerglobal.version=11.1

+env.PLAYERGLOBAL_HOME=/Users/carlosrovira/Dev/Flash/Player

-compiler.debug=true


+royalelib=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/


-closure-lib=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js/lib/google/closure-library

+configname=royale

-swf-version

14


-output=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/bin-debug/Ace.swf

--


/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/src/main/royale/Ace.mxml

0.655243136 seconds


/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml(74):
col: 0 Error: unable to open

'/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/libs/player/11.1/playerglobal.swc'.


/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml
(line: 74)


  




BUILD FAILED

/Users/carlosrovira/Downloads/royale097rc5/ApproveRoyale.xml:781: The
following error occurred while executing this line:


/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/build.xml:659:
The following error occurred while executing this line:


/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/build.xml:77:
The following error occurred while executing this line:


/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/build_example.xml:157:
mxmlc task failed.


Total time: 6 minutes 44 seconds

El vie., 8 may. 2020 a las 13:44, Yishay Weiss ()
escribió:

> Rc4 had an xml bug, rc3 couldn’t build maven from distribution sources. I
> tested ApproveRoyale.xml and it worked for me for this release.
>
> From: Piotr Zarzycki<mailto:piotrzarzyck...@gmail.com>
> Sent: Friday, May 8, 2020 2:40 PM
> To: Apache Royale Development<mailto:dev@royale.apache.org>
    > Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7
>
> What are the changes in comparison to the previous RC? I'm interested
> whether I can use  ApproveRoyale.xml
> 
<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.7%2Frc5%2FApproveRoyale.xmldata=02%7C01%7Caharui%40adobe.com%7C78411875091249af8a8308d7f3744b71%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637245553115240738sdata=aI3XkJzWy60XnLerQ2F1idJsY2Sr%2BX78wDezgsoosdM%3Dreserved=0
> >
> script
> ?
>
> pt., 8 maj 2020 o 13:29  napisał(a):
>
> > This is the discussion thread.
> >
> > Thanks,
> > Yishay Weiss
>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: 
*https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7C78411875091249af8a8308d7f3744b71%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637245553115240738sdata=%2B%2BcrUnwxDk2PJ1DMDKKOfaAOendlSFsHuykEv3MqKpY%3Dreserved=0
> 
<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7C78411875091249af8a8308d7f3744b71%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637245553115240738sdata=%2B%2BcrUnwxDk2PJ1DMDKKOfaAOendlSFsHuykEv3MqKpY%3Dreserved=0>*
>
>

-- 
Carlos Rovira

https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C78411875091249af8a8308d7f3744b71%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637245553115240738sdata=8qT4GaOC3WSS%2FPihAkExVC83BvkpgSE%2BirVYGRmx4nE%3Dreserved=0

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-08 Thread Carlos Rovira

Hi,

I had a similar experience with approve xml, so I'll check as I have more
time during weekend in other way:

build_example.compile:

Compiling Ace.swf

ROYALE_HOME:
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs

ROYALE_COMPILER_HOME:
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js

GOOG_HOME:
/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js/lib/google/closure-library

MXMLJSC

-load-config+=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/src/main/config/compile-app-config.xml

+playerglobal.version=11.1

+env.PLAYERGLOBAL_HOME=/Users/carlosrovira/Dev/Flash/Player

-compiler.debug=true

+royalelib=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/

-closure-lib=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/js/lib/google/closure-library

+configname=royale

-swf-version

14

-output=/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/bin-debug/Ace.swf

--

/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/src/main/royale/Ace.mxml

0.655243136 seconds

/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml(74):
col: 0 Error: unable to open
'/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/libs/player/11.1/playerglobal.swc'.

/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml
(line: 74)


  




BUILD FAILED

/Users/carlosrovira/Downloads/royale097rc5/ApproveRoyale.xml:781: The
following error occurred while executing this line:

/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/build.xml:659:
The following error occurred while executing this line:

/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/build.xml:77:
The following error occurred while executing this line:

/Users/carlosrovira/Downloads/royale097rc5/apache-royale-0.9.7-src/royale-asjs/examples/build_example.xml:157:
mxmlc task failed.


Total time: 6 minutes 44 seconds

El vie., 8 may. 2020 a las 13:44, Yishay Weiss ()
escribió:

> Rc4 had an xml bug, rc3 couldn’t build maven from distribution sources. I
> tested ApproveRoyale.xml and it worked for me for this release.
>
> From: Piotr Zarzycki<mailto:piotrzarzyck...@gmail.com>
> Sent: Friday, May 8, 2020 2:40 PM
> To: Apache Royale Development<mailto:dev@royale.apache.org>
> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7
>
> What are the changes in comparison to the previous RC? I'm interested
> whether I can use  ApproveRoyale.xml
> <https://dist.apache.org/repos/dist/dev/royale/0.9.7/rc5/ApproveRoyale.xml
> >
> script
> ?
>
> pt., 8 maj 2020 o 13:29  napisał(a):
>
> > This is the discussion thread.
> >
> > Thanks,
> > Yishay Weiss
>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>
>

-- 
Carlos Rovira
http://about.me/carlosrovira

RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-08 Thread Yishay Weiss

Rc4 had an xml bug, rc3 couldn’t build maven from distribution sources. I 
tested ApproveRoyale.xml and it worked for me for this release.

From: Piotr Zarzycki<mailto:piotrzarzyck...@gmail.com>
Sent: Friday, May 8, 2020 2:40 PM
To: Apache Royale Development<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

What are the changes in comparison to the previous RC? I'm interested
whether I can use  ApproveRoyale.xml
<https://dist.apache.org/repos/dist/dev/royale/0.9.7/rc5/ApproveRoyale.xml>
script
?

pt., 8 maj 2020 o 13:29  napisał(a):

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

--

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-08 Thread Piotr Zarzycki

What are the changes in comparison to the previous RC? I'm interested
whether I can use  ApproveRoyale.xml

script
?

pt., 8 maj 2020 o 13:29  napisał(a):

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



-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*

RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-07 Thread Yishay Weiss

I don’t have time to look at it now, but as a wild guess it could be a network 
problem. GitBox has been really slow and timing out.

From: Carlos Rovira<mailto:carlosrov...@apache.org>
Sent: Thursday, May 7, 2020 11:14 AM
To: Apache Royale Development<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Hi,

just was trying the RC4 when saw that Yishay cancelled. I left the process
go and I get this fail:

check-compile-env:

OS: Mac OS X / 10.15.4 / x86_64

VM: Java HotSpot(TM) 64-Bit Server VM / 25.181-b13

Java: 1.8.0_181

Ant: Apache Ant(TM) version 1.10.7 compiled on September 1 2019 Ant Java
Version: 1.8


clean:


...


build_example.compile:

Compiling Ace.swf

ROYALE_HOME:
/Users/carlosrovira/Downloads/royale097/apache-royale-0.9.7-src/royale-asjs

ROYALE_COMPILER_HOME:
/Users/carlosrovira/Downloads/royale097/apache-royale-0.9.7-src/royale-asjs/js

GOOG_HOME:
/Users/carlosrovira/Downloads/royale097/apache-royale-0.9.7-src/royale-asjs/js/lib/google/closure-library

MXMLJSC

-load-config+=/Users/carlosrovira/Downloads/royale097/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/src/main/config/compile-app-config.xml

+playerglobal.version=11.1

+env.PLAYERGLOBAL_HOME=/Users/carlosrovira/Dev/Flash/Player

-compiler.debug=true

+royalelib=/Users/carlosrovira/Downloads/royale097/apache-royale-0.9.7-src/royale-asjs/frameworks/

-closure-lib=/Users/carlosrovira/Downloads/royale097/apache-royale-0.9.7-src/royale-asjs/js/lib/google/closure-library

+configname=royale

-swf-version

14

-output=/Users/carlosrovira/Downloads/royale097/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/bin-debug/Ace.swf

--

/Users/carlosrovira/Downloads/royale097/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/src/main/royale/Ace.mxml

0.647931553 seconds

/Users/carlosrovira/Downloads/royale097/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml(74):
col: 0 Error: unable to open
'/Users/carlosrovira/Downloads/royale097/apache-royale-0.9.7-src/royale-asjs/frameworks/libs/player/11.1/playerglobal.swc'.

/Users/carlosrovira/Downloads/royale097/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml
(line: 74)


  




BUILD FAILED

/Users/carlosrovira/Downloads/royale097/ApproveRoyale.xml:781: The
following error occurred while executing this line:

/Users/carlosrovira/Downloads/royale097/apache-royale-0.9.7-src/royale-asjs/build.xml:659:
The following error occurred while executing this line:

/Users/carlosrovira/Downloads/royale097/apache-royale-0.9.7-src/royale-asjs/examples/build.xml:77:
The following error occurred while executing this line:

/Users/carlosrovira/Downloads/royale097/apache-royale-0.9.7-src/royale-asjs/examples/build_example.xml:157:
mxmlc task failed.


Total time: 12 minutes 2 seconds



(just copy the last part)



El mié., 6 may. 2020 a las 14:54,  escribió:

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



--
Carlos Rovira
http://about.me/carlosrovira

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-07 Thread Carlos Rovira

Hi,

just was trying the RC4 when saw that Yishay cancelled. I left the process
go and I get this fail:

check-compile-env:

OS: Mac OS X / 10.15.4 / x86_64

VM: Java HotSpot(TM) 64-Bit Server VM / 25.181-b13

Java: 1.8.0_181

Ant: Apache Ant(TM) version 1.10.7 compiled on September 1 2019 Ant Java
Version: 1.8


clean:


...


build_example.compile:

Compiling Ace.swf

ROYALE_HOME:
/Users/carlosrovira/Downloads/royale097/apache-royale-0.9.7-src/royale-asjs

ROYALE_COMPILER_HOME:
/Users/carlosrovira/Downloads/royale097/apache-royale-0.9.7-src/royale-asjs/js

GOOG_HOME:
/Users/carlosrovira/Downloads/royale097/apache-royale-0.9.7-src/royale-asjs/js/lib/google/closure-library

MXMLJSC

-load-config+=/Users/carlosrovira/Downloads/royale097/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/src/main/config/compile-app-config.xml

+playerglobal.version=11.1

+env.PLAYERGLOBAL_HOME=/Users/carlosrovira/Dev/Flash/Player

-compiler.debug=true

+royalelib=/Users/carlosrovira/Downloads/royale097/apache-royale-0.9.7-src/royale-asjs/frameworks/

-closure-lib=/Users/carlosrovira/Downloads/royale097/apache-royale-0.9.7-src/royale-asjs/js/lib/google/closure-library

+configname=royale

-swf-version

14

-output=/Users/carlosrovira/Downloads/royale097/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/bin-debug/Ace.swf

--

/Users/carlosrovira/Downloads/royale097/apache-royale-0.9.7-src/royale-asjs/examples/royale/Ace/src/main/royale/Ace.mxml

0.647931553 seconds

/Users/carlosrovira/Downloads/royale097/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml(74):
col: 0 Error: unable to open
'/Users/carlosrovira/Downloads/royale097/apache-royale-0.9.7-src/royale-asjs/frameworks/libs/player/11.1/playerglobal.swc'.

/Users/carlosrovira/Downloads/royale097/apache-royale-0.9.7-src/royale-asjs/frameworks/royale-config.xml
(line: 74)


  




BUILD FAILED

/Users/carlosrovira/Downloads/royale097/ApproveRoyale.xml:781: The
following error occurred while executing this line:

/Users/carlosrovira/Downloads/royale097/apache-royale-0.9.7-src/royale-asjs/build.xml:659:
The following error occurred while executing this line:

/Users/carlosrovira/Downloads/royale097/apache-royale-0.9.7-src/royale-asjs/examples/build.xml:77:
The following error occurred while executing this line:

/Users/carlosrovira/Downloads/royale097/apache-royale-0.9.7-src/royale-asjs/examples/build_example.xml:157:
mxmlc task failed.


Total time: 12 minutes 2 seconds



(just copy the last part)



El mié., 6 may. 2020 a las 14:54,  escribió:

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



-- 
Carlos Rovira
http://about.me/carlosrovira

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-05 Thread Carlos Rovira

Hi Ysihay,

to be as short as possible, for me is like if we are making build systems
suffer due to release needs (that I at least do not see as a real need), or
at least is what I understand. I think build is over release. At the end
release is a need to put some concrete bytes for public consume, but
building from source is daily work tool.

HTH

Carlos

El mar., 5 may. 2020 a las 16:47, Yishay Weiss ()
escribió:

>
> >And Alex, considering the intensity of you insisting everything to be
> reproducible on Ant and Maven and all sorts of >additional hoops Apache is
> not even asking for, it puzzles me how you could even consider releasing
> something >that doesn't build with one of the two equally supported
> build-systems.
>
> Hi Chris,
> For what it’s worth, I’m the RM for this release and it is my decision
> whether or not to start an new RC (which I am). Alex has one vote, just
> like everyone else. I appreciate your technical input, but I don’t think
> it’s helpful to drag this thread into past arguments. To me, that creates
> an atmosphere where people think too much about whether or not they will
> want to express their opinions, and that’s not helpful.
> Thanks,
> Yishay
>
>
>
> Am 05.05.20, 07:48 schrieb "Yishay Weiss" :
>
> Hi All,
>
> It’s starting to look like the cleanest solution is to start an RC4. I
> intend to start working on that in 10 hours or so. In the meantime, I’d
> appreciate it if people took time to look at RC3, so we don’t end up with
> an RC5.
>
> Thanks,
> Yishay
>
> From: Alex Harui<mailto:aha...@adobe.com.INVALID>
> Sent: Tuesday, May 5, 2020 12:22 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7
>
> The Ant packages only contain things we know we want to release.
> Top-level folders are not whitelisted in because you never know what might
> be in them.  We've never released the manualtests folder for example, so we
> don't have to spend time certifying it for code quality and build-ability,
> license, etc.  We've never shipped the top-level src folder because it used
> to only contain a site folder that wasn't going to be of use to our users.
> So when the groovy scripts were added to the src folder, they were not
> included in the Ant packaging.
>
> We also have never voted on and released the 3 top-level Maven source
> packages, mainly to reduce the amount of work the voters need to do.  The
> Maven source packages are "tested" by the Maven release plugin, and the 3
> packages are unpacked and repacked into the Ant package.  So far, we've
> found that two new files were missed.
>
> How many of our users build the source package is one factor and I
> think the answer for Royale is that few people do it.  Apache release are
> supposed to "build" and the Ant source package will build with Ant.
>
> IMO, the best next thing for PMC members to do is to download the RC
> and try it with Ant, and/or use Maven to point to the staging repos and
> test the artifacts that have been staged up there and see if we see any
> other big issues.  Maybe we'll find something else and make RC4 an obvious
> choice.
>
> Other choices are:
> A) Release RC3 with documenting all of the problems in the online
> release notes
> B) Also certifying and voting on the 3 Maven source packages.
>
> IMO, what we don't want to see happen is for folks to not test RC3 and
> find out some big issue later.
>
> My 2 cents,
> -Alex
>
> On 5/4/20, 12:24 PM, "Christofer Dutz" 
> wrote:
>
> The more I think about it  it's actually not good that the
> groovy script isn't in there as this way you will not be able to download,
> unpack and build anything with maven.
> As maven calls this script as the first thing in every maven build
> to ensure everything is setup.
>
> Without this, you will never get past the Maven validate phase ...
> so if I had a vote, I would probably vote -1 on that.
>
> When ere these files getting lost? In the initial source bundles
> built by maven they should be in there ... so probably you only have to
> re-do some of the last steps.
>
> Chris
>
>
>
> Am 04.05.20, 20:13 schrieb "Yishay Weiss"  >:
>
> Ok, I just verified that copying the script to the right
> location makes the groovy plugin happy, so it doesn’t seem to be a windows
> or backslash issue after all.
>
>     I need an explanation on when Maven will be used to build the
> Ant sources to decide if it’s worth an RC4.
>
> From: A

RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-05 Thread Yishay Weiss

>And Alex, considering the intensity of you insisting everything to be 
>reproducible on Ant and Maven and all sorts of >additional hoops Apache is not 
>even asking for, it puzzles me how you could even consider releasing something 
>>that doesn't build with one of the two equally supported build-systems.

Hi Chris,
For what it’s worth, I’m the RM for this release and it is my decision whether 
or not to start an new RC (which I am). Alex has one vote, just like everyone 
else. I appreciate your technical input, but I don’t think it’s helpful to drag 
this thread into past arguments. To me, that creates an atmosphere where people 
think too much about whether or not they will want to express their opinions, 
and that’s not helpful.
Thanks,
Yishay

Am 05.05.20, 07:48 schrieb "Yishay Weiss" :

Hi All,

It’s starting to look like the cleanest solution is to start an RC4. I 
intend to start working on that in 10 hours or so. In the meantime, I’d 
appreciate it if people took time to look at RC3, so we don’t end up with an 
RC5.

Thanks,
Yishay

From: Alex Harui<mailto:aha...@adobe.com.INVALID>
Sent: Tuesday, May 5, 2020 12:22 AM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
    Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

The Ant packages only contain things we know we want to release.  Top-level 
folders are not whitelisted in because you never know what might be in them.  
We've never released the manualtests folder for example, so we don't have to 
spend time certifying it for code quality and build-ability, license, etc.  
We've never shipped the top-level src folder because it used to only contain a 
site folder that wasn't going to be of use to our users.  So when the groovy 
scripts were added to the src folder, they were not included in the Ant 
packaging.

We also have never voted on and released the 3 top-level Maven source 
packages, mainly to reduce the amount of work the voters need to do.  The Maven 
source packages are "tested" by the Maven release plugin, and the 3 packages 
are unpacked and repacked into the Ant package.  So far, we've found that two 
new files were missed.

How many of our users build the source package is one factor and I think 
the answer for Royale is that few people do it.  Apache release are supposed to 
"build" and the Ant source package will build with Ant.

IMO, the best next thing for PMC members to do is to download the RC and 
try it with Ant, and/or use Maven to point to the staging repos and test the 
artifacts that have been staged up there and see if we see any other big 
issues.  Maybe we'll find something else and make RC4 an obvious choice.

Other choices are:
A) Release RC3 with documenting all of the problems in the online release 
notes
B) Also certifying and voting on the 3 Maven source packages.

IMO, what we don't want to see happen is for folks to not test RC3 and find 
out some big issue later.

My 2 cents,
-Alex

On 5/4/20, 12:24 PM, "Christofer Dutz"  wrote:

The more I think about it  it's actually not good that the groovy 
script isn't in there as this way you will not be able to download, unpack and 
build anything with maven.
As maven calls this script as the first thing in every maven build to 
ensure everything is setup.

Without this, you will never get past the Maven validate phase ... so 
if I had a vote, I would probably vote -1 on that.

When ere these files getting lost? In the initial source bundles built 
by maven they should be in there ... so probably you only have to re-do some of 
the last steps.

Chris

Am 04.05.20, 20:13 schrieb "Yishay Weiss" :

Ok, I just verified that copying the script to the right location 
makes the groovy plugin happy, so it doesn’t seem to be a windows or backslash 
issue after all.

I need an explanation on when Maven will be used to build the Ant 
sources to decide if it’s worth an RC4.

From: Alex Harui<mailto:aha...@adobe.com.INVALID>
Sent: Monday, May 4, 2020 7:14 PM
        To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

The groovy script is not in the ant packages on dist.  My earlier 
email tried to explain that.   Not every file in the repo ends up in the ant 
packages on purpose.   If we do an RC4, hopefully the changes I made will pick 
those two files.

-Alex

On 5/4/20, 8:54 AM, "Yishay Weiss"  wrote:

.mvn folder exists in GitHub but not in SVN. Could that be 
related?

From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Monday, May 4, 2020 6:40 PM
        To: dev@royale.apache.org<mailto:dev@royale.ap

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-05 Thread Alex Harui

The CI Jobs indicate that my changes worked and the groovy files will be in the 
unified source package.  I also reverted the pom changes made by the 
release-plugin so the branches should be ready to go.  That said, you might 
want to wait until other PMC members have reviewed RC3.

HTH,
-Alex

On 5/4/20, 11:24 PM, "Alex Harui"  wrote:

Thanks Yishay.

I am putting together CI jobs to verify that my changes will pick up the 
groovy files.  The files that changed are part of the source package and were 
tagged as RC3 and one of them is in royale-compiler which is why we must start 
essentially from the beginning.  You can skip the CI steps that create the 
release branches and set version numbers, but we have to run pretty much all of 
the steps you ran last time (2, 3, 6, 7,  10, 11, 13).  If I have time I will 
revert the pom changes the release-plugin makes to the release branch.

-Alex

On 5/4/20, 10:48 PM, "Yishay Weiss"  wrote:

Hi All,

It’s starting to look like the cleanest solution is to start an RC4. I 
intend to start working on that in 10 hours or so. In the meantime, I’d 
appreciate it if people took time to look at RC3, so we don’t end up with an 
RC5.

Thanks,
Yishay

From: Alex Harui<mailto:aha...@adobe.com.INVALID>
Sent: Tuesday, May 5, 2020 12:22 AM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
    Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

The Ant packages only contain things we know we want to release.  
Top-level folders are not whitelisted in because you never know what might be 
in them.  We've never released the manualtests folder for example, so we don't 
have to spend time certifying it for code quality and build-ability, license, 
etc.  We've never shipped the top-level src folder because it used to only 
contain a site folder that wasn't going to be of use to our users.  So when the 
groovy scripts were added to the src folder, they were not included in the Ant 
packaging.

We also have never voted on and released the 3 top-level Maven source 
packages, mainly to reduce the amount of work the voters need to do.  The Maven 
source packages are "tested" by the Maven release plugin, and the 3 packages 
are unpacked and repacked into the Ant package.  So far, we've found that two 
new files were missed.

How many of our users build the source package is one factor and I 
think the answer for Royale is that few people do it.  Apache release are 
supposed to "build" and the Ant source package will build with Ant.

IMO, the best next thing for PMC members to do is to download the RC 
and try it with Ant, and/or use Maven to point to the staging repos and test 
the artifacts that have been staged up there and see if we see any other big 
issues.  Maybe we'll find something else and make RC4 an obvious choice.

Other choices are:
A) Release RC3 with documenting all of the problems in the online 
release notes
B) Also certifying and voting on the 3 Maven source packages.

IMO, what we don't want to see happen is for folks to not test RC3 and 
find out some big issue later.

My 2 cents,
-Alex

On 5/4/20, 12:24 PM, "Christofer Dutz"  
wrote:

The more I think about it  it's actually not good that the 
groovy script isn't in there as this way you will not be able to download, 
unpack and build anything with maven.
As maven calls this script as the first thing in every maven build 
to ensure everything is setup.

Without this, you will never get past the Maven validate phase ... 
so if I had a vote, I would probably vote -1 on that.

When ere these files getting lost? In the initial source bundles 
built by maven they should be in there ... so probably you only have to re-do 
some of the last steps.

Chris



Am 04.05.20, 20:13 schrieb "Yishay Weiss" :

Ok, I just verified that copying the script to the right 
location makes the groovy plugin happy, so it doesn’t seem to be a windows or 
backslash issue after all.

I need an explanation on when Maven will be used to build the 
Ant sources to decide if it’s worth an RC4.

From: Alex Harui<mailto:aha...@adobe.com.INVALID>
Sent: Monday, May 4, 2020 7:14 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

The groovy script is not in the ant packages on dist.  My 
earlier email tried to explain that.   Not every file in the repo ends

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-05 Thread Alex Harui

I removed TDF and ASDoc from running after asjs.  That should reduce the 
changes you get blocked by something that takes a long time.  We can put it 
back later.

-Alex

On 5/4/20, 11:29 PM, "Yishay Weiss"  wrote:

Great. Thanks to Alex and Chris for reviewing this. Om, is there any chance 
you can look at the CI configuration and see if the jobs are still distributed 
between the 2 agents? Last time I looked it looked like they were all 
configured to work with agent1, which would mean TDF slowing down the build 
again. I may have missed something.

From: Alex Harui<mailto:aha...@adobe.com.INVALID>
Sent: Tuesday, May 5, 2020 9:24 AM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
    Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Thanks Yishay.

I am putting together CI jobs to verify that my changes will pick up the 
groovy files.  The files that changed are part of the source package and were 
tagged as RC3 and one of them is in royale-compiler which is why we must start 
essentially from the beginning.  You can skip the CI steps that create the 
release branches and set version numbers, but we have to run pretty much all of 
the steps you ran last time (2, 3, 6, 7,  10, 11, 13).  If I have time I will 
revert the pom changes the release-plugin makes to the release branch.

-Alex

On 5/4/20, 10:48 PM, "Yishay Weiss"  wrote:

Hi All,

It’s starting to look like the cleanest solution is to start an RC4. I 
intend to start working on that in 10 hours or so. In the meantime, I’d 
appreciate it if people took time to look at RC3, so we don’t end up with an 
RC5.

Thanks,
Yishay

From: Alex Harui<mailto:aha...@adobe.com.INVALID>
Sent: Tuesday, May 5, 2020 12:22 AM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
    Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

The Ant packages only contain things we know we want to release.  
Top-level folders are not whitelisted in because you never know what might be 
in them.  We've never released the manualtests folder for example, so we don't 
have to spend time certifying it for code quality and build-ability, license, 
etc.  We've never shipped the top-level src folder because it used to only 
contain a site folder that wasn't going to be of use to our users.  So when the 
groovy scripts were added to the src folder, they were not included in the Ant 
packaging.

We also have never voted on and released the 3 top-level Maven source 
packages, mainly to reduce the amount of work the voters need to do.  The Maven 
source packages are "tested" by the Maven release plugin, and the 3 packages 
are unpacked and repacked into the Ant package.  So far, we've found that two 
new files were missed.

How many of our users build the source package is one factor and I 
think the answer for Royale is that few people do it.  Apache release are 
supposed to "build" and the Ant source package will build with Ant.

IMO, the best next thing for PMC members to do is to download the RC 
and try it with Ant, and/or use Maven to point to the staging repos and test 
the artifacts that have been staged up there and see if we see any other big 
issues.  Maybe we'll find something else and make RC4 an obvious choice.

Other choices are:
A) Release RC3 with documenting all of the problems in the online 
release notes
B) Also certifying and voting on the 3 Maven source packages.

IMO, what we don't want to see happen is for folks to not test RC3 and 
find out some big issue later.

My 2 cents,
-Alex

On 5/4/20, 12:24 PM, "Christofer Dutz"  
wrote:

The more I think about it  it's actually not good that the 
groovy script isn't in there as this way you will not be able to download, 
unpack and build anything with maven.
As maven calls this script as the first thing in every maven build 
to ensure everything is setup.

Without this, you will never get past the Maven validate phase ... 
so if I had a vote, I would probably vote -1 on that.

When ere these files getting lost? In the initial source bundles 
built by maven they should be in there ... so probably you only have to re-do 
some of the last steps.

Chris



Am 04.05.20, 20:13 schrieb "Yishay Weiss" :

Ok, I just verified that copying the script to the right 
location makes the groovy plugin happy, so it doesn’t seem to be a windows or 
backslash issue after all.

I need an explanation on when Maven will be used to build the 
Ant sources to decide if it’s worth an RC4.

From: Alex Harui<mailto:aha...@adobe

RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-05 Thread Yishay Weiss

Great. Thanks to Alex and Chris for reviewing this. Om, is there any chance you 
can look at the CI configuration and see if the jobs are still distributed 
between the 2 agents? Last time I looked it looked like they were all 
configured to work with agent1, which would mean TDF slowing down the build 
again. I may have missed something.

From: Alex Harui<mailto:aha...@adobe.com.INVALID>
Sent: Tuesday, May 5, 2020 9:24 AM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Thanks Yishay.

I am putting together CI jobs to verify that my changes will pick up the groovy 
files.  The files that changed are part of the source package and were tagged 
as RC3 and one of them is in royale-compiler which is why we must start 
essentially from the beginning.  You can skip the CI steps that create the 
release branches and set version numbers, but we have to run pretty much all of 
the steps you ran last time (2, 3, 6, 7,  10, 11, 13).  If I have time I will 
revert the pom changes the release-plugin makes to the release branch.

-Alex

On 5/4/20, 10:48 PM, "Yishay Weiss"  wrote:

Hi All,

It’s starting to look like the cleanest solution is to start an RC4. I 
intend to start working on that in 10 hours or so. In the meantime, I’d 
appreciate it if people took time to look at RC3, so we don’t end up with an 
RC5.

Thanks,
Yishay

From: Alex Harui<mailto:aha...@adobe.com.INVALID>
Sent: Tuesday, May 5, 2020 12:22 AM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
    Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

The Ant packages only contain things we know we want to release.  Top-level 
folders are not whitelisted in because you never know what might be in them.  
We've never released the manualtests folder for example, so we don't have to 
spend time certifying it for code quality and build-ability, license, etc.  
We've never shipped the top-level src folder because it used to only contain a 
site folder that wasn't going to be of use to our users.  So when the groovy 
scripts were added to the src folder, they were not included in the Ant 
packaging.

We also have never voted on and released the 3 top-level Maven source 
packages, mainly to reduce the amount of work the voters need to do.  The Maven 
source packages are "tested" by the Maven release plugin, and the 3 packages 
are unpacked and repacked into the Ant package.  So far, we've found that two 
new files were missed.

How many of our users build the source package is one factor and I think 
the answer for Royale is that few people do it.  Apache release are supposed to 
"build" and the Ant source package will build with Ant.

IMO, the best next thing for PMC members to do is to download the RC and 
try it with Ant, and/or use Maven to point to the staging repos and test the 
artifacts that have been staged up there and see if we see any other big 
issues.  Maybe we'll find something else and make RC4 an obvious choice.

Other choices are:
A) Release RC3 with documenting all of the problems in the online release 
notes
B) Also certifying and voting on the 3 Maven source packages.

IMO, what we don't want to see happen is for folks to not test RC3 and find 
out some big issue later.

My 2 cents,
-Alex

On 5/4/20, 12:24 PM, "Christofer Dutz"  wrote:

The more I think about it  it's actually not good that the groovy 
script isn't in there as this way you will not be able to download, unpack and 
build anything with maven.
As maven calls this script as the first thing in every maven build to 
ensure everything is setup.

Without this, you will never get past the Maven validate phase ... so 
if I had a vote, I would probably vote -1 on that.

When ere these files getting lost? In the initial source bundles built 
by maven they should be in there ... so probably you only have to re-do some of 
the last steps.

Chris

Am 04.05.20, 20:13 schrieb "Yishay Weiss" :

Ok, I just verified that copying the script to the right location 
makes the groovy plugin happy, so it doesn’t seem to be a windows or backslash 
issue after all.

I need an explanation on when Maven will be used to build the Ant 
sources to decide if it’s worth an RC4.

From: Alex Harui<mailto:aha...@adobe.com.INVALID>
Sent: Monday, May 4, 2020 7:14 PM
    To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

The groovy script is not in the ant packages on dist.  My earlier 
email tried to explain that.   Not every file in the repo ends up in the ant 
packages on purpose.   If we do an RC4, hopefully the changes I made will pick 
those two files.

-Ale

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-05 Thread Alex Harui

Thanks Yishay.

I am putting together CI jobs to verify that my changes will pick up the groovy 
files.  The files that changed are part of the source package and were tagged 
as RC3 and one of them is in royale-compiler which is why we must start 
essentially from the beginning.  You can skip the CI steps that create the 
release branches and set version numbers, but we have to run pretty much all of 
the steps you ran last time (2, 3, 6, 7,  10, 11, 13).  If I have time I will 
revert the pom changes the release-plugin makes to the release branch.

-Alex

On 5/4/20, 10:48 PM, "Yishay Weiss"  wrote:

Hi All,

It’s starting to look like the cleanest solution is to start an RC4. I 
intend to start working on that in 10 hours or so. In the meantime, I’d 
appreciate it if people took time to look at RC3, so we don’t end up with an 
RC5.

Thanks,
Yishay

From: Alex Harui<mailto:aha...@adobe.com.INVALID>
Sent: Tuesday, May 5, 2020 12:22 AM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
    Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

The Ant packages only contain things we know we want to release.  Top-level 
folders are not whitelisted in because you never know what might be in them.  
We've never released the manualtests folder for example, so we don't have to 
spend time certifying it for code quality and build-ability, license, etc.  
We've never shipped the top-level src folder because it used to only contain a 
site folder that wasn't going to be of use to our users.  So when the groovy 
scripts were added to the src folder, they were not included in the Ant 
packaging.

We also have never voted on and released the 3 top-level Maven source 
packages, mainly to reduce the amount of work the voters need to do.  The Maven 
source packages are "tested" by the Maven release plugin, and the 3 packages 
are unpacked and repacked into the Ant package.  So far, we've found that two 
new files were missed.

How many of our users build the source package is one factor and I think 
the answer for Royale is that few people do it.  Apache release are supposed to 
"build" and the Ant source package will build with Ant.

IMO, the best next thing for PMC members to do is to download the RC and 
try it with Ant, and/or use Maven to point to the staging repos and test the 
artifacts that have been staged up there and see if we see any other big 
issues.  Maybe we'll find something else and make RC4 an obvious choice.

Other choices are:
A) Release RC3 with documenting all of the problems in the online release 
notes
B) Also certifying and voting on the 3 Maven source packages.

IMO, what we don't want to see happen is for folks to not test RC3 and find 
out some big issue later.

My 2 cents,
-Alex

On 5/4/20, 12:24 PM, "Christofer Dutz"  wrote:

The more I think about it  it's actually not good that the groovy 
script isn't in there as this way you will not be able to download, unpack and 
build anything with maven.
As maven calls this script as the first thing in every maven build to 
ensure everything is setup.

Without this, you will never get past the Maven validate phase ... so 
if I had a vote, I would probably vote -1 on that.

When ere these files getting lost? In the initial source bundles built 
by maven they should be in there ... so probably you only have to re-do some of 
the last steps.

Chris



Am 04.05.20, 20:13 schrieb "Yishay Weiss" :

Ok, I just verified that copying the script to the right location 
makes the groovy plugin happy, so it doesn’t seem to be a windows or backslash 
issue after all.

I need an explanation on when Maven will be used to build the Ant 
sources to decide if it’s worth an RC4.

From: Alex Harui<mailto:aha...@adobe.com.INVALID>
Sent: Monday, May 4, 2020 7:14 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

The groovy script is not in the ant packages on dist.  My earlier 
email tried to explain that.   Not every file in the repo ends up in the ant 
packages on purpose.   If we do an RC4, hopefully the changes I made will pick 
those two files.

-Alex

On 5/4/20, 8:54 AM, "Yishay Weiss"  wrote:

.mvn folder exists in GitHub but not in SVN. Could that be 
related?

From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Monday, May 4, 2020 6:40 PM
        To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

Look

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-05 Thread Christofer Dutz

Hi Yishay,

Thank you very much for that. I was starting to get worried after seeing Alex' 
response.

And replying to that (Alex' email):
- Apache releases sources, not binaries (The binaries are convenience). So 
releasing something that doesn't build is topmost-validity reason for a -1 vote.
- As it's difficult to keep track of what's needed in a source bundle and 
what's not Maven has the simple convention of:
- Everything in the target directory is excluded, the rest is included 
per default
- You can add exclusions to the inclusions (usually it's best practice 
to automatically exclude everything in the gitignore
- Regarding the amount of additional work: 
- It's 2 groovy files ... 
- You could simply remove the src/site directories in the future ... I 
set them up years ago as a proposal for an alternate way to build the FlexJS 
website

And Alex, considering the intensity of you insisting everything to be 
reproducible on Ant and Maven and all sorts of additional hoops Apache is not 
even asking for, it puzzles me how you could even consider releasing something 
that doesn't build with one of the two equally supported build-systems.

So I'll put all my non-binding vote-weight on -1 for releasing RC3 and +1 for 
creating a RC4.

However I'm not sure however if this is even needed and perhaps you only need 
to do the steps for creating the big source-archive again. As Alex mentioned, 
it seems to copy the content of the maven source assemblies ... these do 
contain the groovy files. So I would guess you only need to continue from the 
last step involving maven. But I could be wrong as what actually happens in the 
Ant build isn't really documented anywhere I could find it.

Chris


Am 05.05.20, 07:48 schrieb "Yishay Weiss" :

Hi All,

It’s starting to look like the cleanest solution is to start an RC4. I 
intend to start working on that in 10 hours or so. In the meantime, I’d 
appreciate it if people took time to look at RC3, so we don’t end up with an 
RC5.

Thanks,
Yishay

From: Alex Harui<mailto:aha...@adobe.com.INVALID>
Sent: Tuesday, May 5, 2020 12:22 AM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
    Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

The Ant packages only contain things we know we want to release.  Top-level 
folders are not whitelisted in because you never know what might be in them.  
We've never released the manualtests folder for example, so we don't have to 
spend time certifying it for code quality and build-ability, license, etc.  
We've never shipped the top-level src folder because it used to only contain a 
site folder that wasn't going to be of use to our users.  So when the groovy 
scripts were added to the src folder, they were not included in the Ant 
packaging.

We also have never voted on and released the 3 top-level Maven source 
packages, mainly to reduce the amount of work the voters need to do.  The Maven 
source packages are "tested" by the Maven release plugin, and the 3 packages 
are unpacked and repacked into the Ant package.  So far, we've found that two 
new files were missed.

How many of our users build the source package is one factor and I think 
the answer for Royale is that few people do it.  Apache release are supposed to 
"build" and the Ant source package will build with Ant.

IMO, the best next thing for PMC members to do is to download the RC and 
try it with Ant, and/or use Maven to point to the staging repos and test the 
artifacts that have been staged up there and see if we see any other big 
issues.  Maybe we'll find something else and make RC4 an obvious choice.

Other choices are:
A) Release RC3 with documenting all of the problems in the online release 
notes
B) Also certifying and voting on the 3 Maven source packages.

IMO, what we don't want to see happen is for folks to not test RC3 and find 
out some big issue later.

My 2 cents,
-Alex

On 5/4/20, 12:24 PM, "Christofer Dutz"  wrote:

The more I think about it  it's actually not good that the groovy 
script isn't in there as this way you will not be able to download, unpack and 
build anything with maven.
As maven calls this script as the first thing in every maven build to 
ensure everything is setup.

Without this, you will never get past the Maven validate phase ... so 
if I had a vote, I would probably vote -1 on that.

When ere these files getting lost? In the initial source bundles built 
by maven they should be in there ... so probably you only have to re-do some of 
the last steps.

Chris



Am 04.05.20, 20:13 schrieb "Yishay Weiss" :

Ok, I just verified that copying the script to the right location 
makes the groovy plugin happy, so it doesn’t seem to be a windows or backslash 
issue after all.

I need an ex

RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-04 Thread Yishay Weiss

Hi All,

It’s starting to look like the cleanest solution is to start an RC4. I intend 
to start working on that in 10 hours or so. In the meantime, I’d appreciate it 
if people took time to look at RC3, so we don’t end up with an RC5.

Thanks,
Yishay

From: Alex Harui<mailto:aha...@adobe.com.INVALID>
Sent: Tuesday, May 5, 2020 12:22 AM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

The Ant packages only contain things we know we want to release.  Top-level 
folders are not whitelisted in because you never know what might be in them.  
We've never released the manualtests folder for example, so we don't have to 
spend time certifying it for code quality and build-ability, license, etc.  
We've never shipped the top-level src folder because it used to only contain a 
site folder that wasn't going to be of use to our users.  So when the groovy 
scripts were added to the src folder, they were not included in the Ant 
packaging.

We also have never voted on and released the 3 top-level Maven source packages, 
mainly to reduce the amount of work the voters need to do.  The Maven source 
packages are "tested" by the Maven release plugin, and the 3 packages are 
unpacked and repacked into the Ant package.  So far, we've found that two new 
files were missed.

How many of our users build the source package is one factor and I think the 
answer for Royale is that few people do it.  Apache release are supposed to 
"build" and the Ant source package will build with Ant.

IMO, the best next thing for PMC members to do is to download the RC and try it 
with Ant, and/or use Maven to point to the staging repos and test the artifacts 
that have been staged up there and see if we see any other big issues.  Maybe 
we'll find something else and make RC4 an obvious choice.

Other choices are:
A) Release RC3 with documenting all of the problems in the online release notes
B) Also certifying and voting on the 3 Maven source packages.

IMO, what we don't want to see happen is for folks to not test RC3 and find out 
some big issue later.

My 2 cents,
-Alex

On 5/4/20, 12:24 PM, "Christofer Dutz"  wrote:

The more I think about it  it's actually not good that the groovy 
script isn't in there as this way you will not be able to download, unpack and 
build anything with maven.
As maven calls this script as the first thing in every maven build to 
ensure everything is setup.

Without this, you will never get past the Maven validate phase ... so if I 
had a vote, I would probably vote -1 on that.

When ere these files getting lost? In the initial source bundles built by 
maven they should be in there ... so probably you only have to re-do some of 
the last steps.

Chris

Am 04.05.20, 20:13 schrieb "Yishay Weiss" :

Ok, I just verified that copying the script to the right location makes 
the groovy plugin happy, so it doesn’t seem to be a windows or backslash issue 
after all.

I need an explanation on when Maven will be used to build the Ant 
sources to decide if it’s worth an RC4.

From: Alex Harui<mailto:aha...@adobe.com.INVALID>
Sent: Monday, May 4, 2020 7:14 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
    Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

The groovy script is not in the ant packages on dist.  My earlier email 
tried to explain that.   Not every file in the repo ends up in the ant packages 
on purpose.   If we do an RC4, hopefully the changes I made will pick those two 
files.

-Alex

On 5/4/20, 8:54 AM, "Yishay Weiss"  wrote:

.mvn folder exists in GitHub but not in SVN. Could that be related?

From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Monday, May 4, 2020 6:40 PM
    To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

Look down-thread:

> >  [exec] [ERROR] Failed to execute goal
> > org.codehaus.gmaven:groovy-maven-plugin:2.1.1:execute
> (prerequisite-check)
> > on project royale-compiler-parent: Executi
> > on prerequisite-check of goal
> > org.codehaus.gmaven:groovy-maven-plugin:2.1.1:execute 
failed: startup
> > failed:
> >  [exec] [ERROR] script1.groovy: 1: 
unexpected
> char:
> > '\' @ line 1, column 3.
> >  [exec] [ERROR]
> >
> 
C:\dev\dist\dist\dev\royale\0.9.7\rc3\apache-royale-0.9.7-maven-src\royale-compiler/src/main/script/prerequisiteCheck.groovy

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-04 Thread Alex Harui

The Ant packages only contain things we know we want to release.  Top-level 
folders are not whitelisted in because you never know what might be in them.  
We've never released the manualtests folder for example, so we don't have to 
spend time certifying it for code quality and build-ability, license, etc.  
We've never shipped the top-level src folder because it used to only contain a 
site folder that wasn't going to be of use to our users.  So when the groovy 
scripts were added to the src folder, they were not included in the Ant 
packaging.

We also have never voted on and released the 3 top-level Maven source packages, 
mainly to reduce the amount of work the voters need to do.  The Maven source 
packages are "tested" by the Maven release plugin, and the 3 packages are 
unpacked and repacked into the Ant package.  So far, we've found that two new 
files were missed.

How many of our users build the source package is one factor and I think the 
answer for Royale is that few people do it.  Apache release are supposed to 
"build" and the Ant source package will build with Ant.

IMO, the best next thing for PMC members to do is to download the RC and try it 
with Ant, and/or use Maven to point to the staging repos and test the artifacts 
that have been staged up there and see if we see any other big issues.  Maybe 
we'll find something else and make RC4 an obvious choice.

Other choices are:
A) Release RC3 with documenting all of the problems in the online release notes
B) Also certifying and voting on the 3 Maven source packages.

IMO, what we don't want to see happen is for folks to not test RC3 and find out 
some big issue later.

My 2 cents,
-Alex

On 5/4/20, 12:24 PM, "Christofer Dutz"  wrote:

The more I think about it  it's actually not good that the groovy 
script isn't in there as this way you will not be able to download, unpack and 
build anything with maven.
As maven calls this script as the first thing in every maven build to 
ensure everything is setup.

Without this, you will never get past the Maven validate phase ... so if I 
had a vote, I would probably vote -1 on that.

When ere these files getting lost? In the initial source bundles built by 
maven they should be in there ... so probably you only have to re-do some of 
the last steps.

Chris

Am 04.05.20, 20:13 schrieb "Yishay Weiss" :

Ok, I just verified that copying the script to the right location makes 
the groovy plugin happy, so it doesn’t seem to be a windows or backslash issue 
after all.

I need an explanation on when Maven will be used to build the Ant 
sources to decide if it’s worth an RC4.

From: Alex Harui<mailto:aha...@adobe.com.INVALID>
Sent: Monday, May 4, 2020 7:14 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
    Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

The groovy script is not in the ant packages on dist.  My earlier email 
tried to explain that.   Not every file in the repo ends up in the ant packages 
on purpose.   If we do an RC4, hopefully the changes I made will pick those two 
files.

-Alex

On 5/4/20, 8:54 AM, "Yishay Weiss"  wrote:

.mvn folder exists in GitHub but not in SVN. Could that be related?

From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Monday, May 4, 2020 6:40 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

Look down-thread:

> >  [exec] [ERROR] Failed to execute goal
> > org.codehaus.gmaven:groovy-maven-plugin:2.1.1:execute
> (prerequisite-check)
> > on project royale-compiler-parent: Executi
> > on prerequisite-check of goal
> > org.codehaus.gmaven:groovy-maven-plugin:2.1.1:execute 
failed: startup
> > failed:
> >  [exec] [ERROR] script1.groovy: 1: 
unexpected
> char:
> > '\' @ line 1, column 3.
> >  [exec] [ERROR]
> >
> 
C:\dev\dist\dist\dev\royale\0.9.7\rc3\apache-royale-0.9.7-maven-src\royale-compiler/src/main/script/prerequisiteCheck.groovy
I verified that the groovy plugin was being called in both case and 
was being fed backslashes as well as forward slashes in both cases. Also, both 
have the same version: 2.1.1

        From: Piotr Zarzycki 
    Sent: Monday, May 4, 2020 6:35:22 PM
To: Apache Royale Development 
Subject: Re: [DISCUSS] Discuss Release Apache

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-04 Thread Christofer Dutz

The more I think about it  it's actually not good that the groovy script 
isn't in there as this way you will not be able to download, unpack and build 
anything with maven.
As maven calls this script as the first thing in every maven build to ensure 
everything is setup.

Without this, you will never get past the Maven validate phase ... so if I had 
a vote, I would probably vote -1 on that.

When ere these files getting lost? In the initial source bundles built by maven 
they should be in there ... so probably you only have to re-do some of the last 
steps.

Chris

Am 04.05.20, 20:13 schrieb "Yishay Weiss" :

Ok, I just verified that copying the script to the right location makes the 
groovy plugin happy, so it doesn’t seem to be a windows or backslash issue 
after all.

I need an explanation on when Maven will be used to build the Ant sources 
to decide if it’s worth an RC4.

From: Alex Harui<mailto:aha...@adobe.com.INVALID>
Sent: Monday, May 4, 2020 7:14 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
    Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

The groovy script is not in the ant packages on dist.  My earlier email 
tried to explain that.   Not every file in the repo ends up in the ant packages 
on purpose.   If we do an RC4, hopefully the changes I made will pick those two 
files.

-Alex

On 5/4/20, 8:54 AM, "Yishay Weiss"  wrote:

.mvn folder exists in GitHub but not in SVN. Could that be related?

From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Monday, May 4, 2020 6:40 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
    Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

Look down-thread:

> >  [exec] [ERROR] Failed to execute goal
> > org.codehaus.gmaven:groovy-maven-plugin:2.1.1:execute
> (prerequisite-check)
> > on project royale-compiler-parent: Executi
> > on prerequisite-check of goal
> > org.codehaus.gmaven:groovy-maven-plugin:2.1.1:execute failed: 
startup
> > failed:
> >  [exec] [ERROR] script1.groovy: 1: 
unexpected
> char:
> > '\' @ line 1, column 3.
> >  [exec] [ERROR]
> >
> 
C:\dev\dist\dist\dev\royale\0.9.7\rc3\apache-royale-0.9.7-maven-src\royale-compiler/src/main/script/prerequisiteCheck.groovy
I verified that the groovy plugin was being called in both case and was 
being fed backslashes as well as forward slashes in both cases. Also, both have 
the same version: 2.1.1

From: Piotr Zarzycki 
    Sent: Monday, May 4, 2020 6:35:22 PM
To: Apache Royale Development 
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Something cut the message. Could you paste here  
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fdata=02%7C01%7Caharui%40adobe.com%7C02b497be17d44111d58908d7f043741c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637242044828340223sdata=jH6wNlW8ieReWyB%2FcYcDIPqSabr9sDizEhsYz62k90A%3Dreserved=0

pon., 4 maj 2020 o 17:32 Yishay Weiss  
napisał(a):

> This means though, that it’s still failing on Windows after Alex’s
> changes, as I’ve verified. I’m getting a bit lost trying to debug 
this.
>
> Running from the SVN dist repo
>
> 
C:\dev\dist\dist\dev\royale\0.9.7\rc3\apache-royale-0.9.7-maven-src\royale-compiler>
> mvn clean install
>
> Fails with the below message,
>
> But running the same command from the git repo
>
> C:\dev\flexjs\royale-compiler [release/0.9.7 =]> mvn clean install
>
> Does not fail.
>
> Any ideas?
>
>
>
>
    > From: Yishay Weiss<mailto:yishayj...@hotmail.com>
> Sent: Monday, May 4, 2020 3:04 PM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.7
>
> Good catch Chris. I was focusing on the wrong message.
    >
    > From: Christofer Dutz<mailto:christofer.d...@c-ware.de>
> Sent: Monday, May 4, 2020 2:09 PM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7
>
> Just some input from the sidelines:
> - It shouldn't have any impact on the build if you enable/disable 
profiles
> that don't exist. All you get is a warning that tells you the profiles
&

RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-04 Thread Yishay Weiss

Ok, I just verified that copying the script to the right location makes the 
groovy plugin happy, so it doesn’t seem to be a windows or backslash issue 
after all.

I need an explanation on when Maven will be used to build the Ant sources to 
decide if it’s worth an RC4.

From: Alex Harui<mailto:aha...@adobe.com.INVALID>
Sent: Monday, May 4, 2020 7:14 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

The groovy script is not in the ant packages on dist.  My earlier email tried 
to explain that.   Not every file in the repo ends up in the ant packages on 
purpose.   If we do an RC4, hopefully the changes I made will pick those two 
files.

-Alex

On 5/4/20, 8:54 AM, "Yishay Weiss"  wrote:

.mvn folder exists in GitHub but not in SVN. Could that be related?

From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Monday, May 4, 2020 6:40 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
    Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

Look down-thread:

> >  [exec] [ERROR] Failed to execute goal
> > org.codehaus.gmaven:groovy-maven-plugin:2.1.1:execute
> (prerequisite-check)
> > on project royale-compiler-parent: Executi
> > on prerequisite-check of goal
> > org.codehaus.gmaven:groovy-maven-plugin:2.1.1:execute failed: 
startup
> > failed:
> >  [exec] [ERROR] script1.groovy: 1: unexpected
> char:
> > '\' @ line 1, column 3.
> >  [exec] [ERROR]
> >
> 
C:\dev\dist\dist\dev\royale\0.9.7\rc3\apache-royale-0.9.7-maven-src\royale-compiler/src/main/script/prerequisiteCheck.groovy
I verified that the groovy plugin was being called in both case and was 
being fed backslashes as well as forward slashes in both cases. Also, both have 
the same version: 2.1.1




From: Piotr Zarzycki 
Sent: Monday, May 4, 2020 6:35:22 PM
To: Apache Royale Development 
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Something cut the message. Could you paste here  
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fdata=02%7C01%7Caharui%40adobe.com%7C02b497be17d44111d58908d7f043741c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637242044828340223sdata=jH6wNlW8ieReWyB%2FcYcDIPqSabr9sDizEhsYz62k90A%3Dreserved=0

pon., 4 maj 2020 o 17:32 Yishay Weiss  napisał(a):

> This means though, that it’s still failing on Windows after Alex’s
> changes, as I’ve verified. I’m getting a bit lost trying to debug this.
>
> Running from the SVN dist repo
>
> 
C:\dev\dist\dist\dev\royale\0.9.7\rc3\apache-royale-0.9.7-maven-src\royale-compiler>
> mvn clean install
>
> Fails with the below message,
>
> But running the same command from the git repo
>
> C:\dev\flexjs\royale-compiler [release/0.9.7 =]> mvn clean install
>
> Does not fail.
>
> Any ideas?
>
>
>
>
    > From: Yishay Weiss<mailto:yishayj...@hotmail.com>
> Sent: Monday, May 4, 2020 3:04 PM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.7
>
> Good catch Chris. I was focusing on the wrong message.
>
    > From: Christofer Dutz<mailto:christofer.d...@c-ware.de>
> Sent: Monday, May 4, 2020 2:09 PM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7
>
> Just some input from the sidelines:
> - It shouldn't have any impact on the build if you enable/disable profiles
> that don't exist. All you get is a warning that tells you the profiles
> don't exist.
>
> - The actual failure is because the the path to the prerequisiteCheck
> script is windows-encoded (Backslashs) ... strange thing is that this
> didn't fail for normal Windows executions both for Royale same as in PLC4X
> ... we've got the identical setup for 2-3 years now and haven't heard of
> any issues with it. I would guess the build is started somewhat 
differently
> than others ... perhaps it could be fixed by removing the
> "${project.basedir}/" prefix and using relative paths instead.
>
> And just a little explanation what this script does:
> It's a goovy script that is executed and checks if all required tools are
> available in the right versions and if all required environment-variables
> are set and are set to valid values. As soon as you run a Maven build it
>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-04 Thread Alex Harui

The groovy script is not in the ant packages on dist.  My earlier email tried 
to explain that.   Not every file in the repo ends up in the ant packages on 
purpose.   If we do an RC4, hopefully the changes I made will pick those two 
files.

-Alex

On 5/4/20, 8:54 AM, "Yishay Weiss"  wrote:

.mvn folder exists in GitHub but not in SVN. Could that be related?

From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Monday, May 4, 2020 6:40 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
    Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

Look down-thread:

> >  [exec] [ERROR] Failed to execute goal
> > org.codehaus.gmaven:groovy-maven-plugin:2.1.1:execute
> (prerequisite-check)
> > on project royale-compiler-parent: Executi
> > on prerequisite-check of goal
> > org.codehaus.gmaven:groovy-maven-plugin:2.1.1:execute failed: 
startup
> > failed:
> >  [exec] [ERROR] script1.groovy: 1: unexpected
> char:
> > '\' @ line 1, column 3.
> >  [exec] [ERROR]
> >
> 
C:\dev\dist\dist\dev\royale\0.9.7\rc3\apache-royale-0.9.7-maven-src\royale-compiler/src/main/script/prerequisiteCheck.groovy
I verified that the groovy plugin was being called in both case and was 
being fed backslashes as well as forward slashes in both cases. Also, both have 
the same version: 2.1.1




From: Piotr Zarzycki 
    Sent: Monday, May 4, 2020 6:35:22 PM
    To: Apache Royale Development 
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Something cut the message. Could you paste here  
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fdata=02%7C01%7Caharui%40adobe.com%7C02b497be17d44111d58908d7f043741c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637242044828340223sdata=jH6wNlW8ieReWyB%2FcYcDIPqSabr9sDizEhsYz62k90A%3Dreserved=0

pon., 4 maj 2020 o 17:32 Yishay Weiss  napisał(a):

> This means though, that it’s still failing on Windows after Alex’s
> changes, as I’ve verified. I’m getting a bit lost trying to debug this.
>
> Running from the SVN dist repo
>
> 
C:\dev\dist\dist\dev\royale\0.9.7\rc3\apache-royale-0.9.7-maven-src\royale-compiler>
> mvn clean install
>
> Fails with the below message,
>
> But running the same command from the git repo
>
> C:\dev\flexjs\royale-compiler [release/0.9.7 =]> mvn clean install
>
> Does not fail.
>
> Any ideas?
>
>
>
>
> From: Yishay Weiss<mailto:yishayj...@hotmail.com>
> Sent: Monday, May 4, 2020 3:04 PM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.7
>
> Good catch Chris. I was focusing on the wrong message.
>
> From: Christofer Dutz<mailto:christofer.d...@c-ware.de>
> Sent: Monday, May 4, 2020 2:09 PM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7
>
> Just some input from the sidelines:
> - It shouldn't have any impact on the build if you enable/disable profiles
> that don't exist. All you get is a warning that tells you the profiles
> don't exist.
>
> - The actual failure is because the the path to the prerequisiteCheck
> script is windows-encoded (Backslashs) ... strange thing is that this
> didn't fail for normal Windows executions both for Royale same as in PLC4X
> ... we've got the identical setup for 2-3 years now and haven't heard of
> any issues with it. I would guess the build is started somewhat 
differently
> than others ... perhaps it could be fixed by removing the
> "${project.basedir}/" prefix and using relative paths instead.
>
> And just a little explanation what this script does:
> It's a goovy script that is executed and checks if all required tools are
> available in the right versions and if all required environment-variables
> are set and are set to valid values. As soon as you run a Maven build it
> outputs a list of thigs it checked and if checks fail, it quickly fails 
the
> build with a list of findings the user has to address first.
>
> Hope that helps.
>
> Chris
>
>
>
> Am 04.05.20, 11:45 schrieb "Carlos Rovira" :
>
> Hi Alex and Yishay,
>
> first, congrats for the hard work to reach to this point. I think many
> issues ha

RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-04 Thread Yishay Weiss

.mvn folder exists in GitHub but not in SVN. Could that be related?

From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Monday, May 4, 2020 6:40 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

Look down-thread:

> >  [exec] [ERROR] Failed to execute goal
> > org.codehaus.gmaven:groovy-maven-plugin:2.1.1:execute
> (prerequisite-check)
> > on project royale-compiler-parent: Executi
> > on prerequisite-check of goal
> > org.codehaus.gmaven:groovy-maven-plugin:2.1.1:execute failed: startup
> > failed:
> >  [exec] [ERROR] script1.groovy: 1: unexpected
> char:
> > '\' @ line 1, column 3.
> >  [exec] [ERROR]
> >
> C:\dev\dist\dist\dev\royale\0.9.7\rc3\apache-royale-0.9.7-maven-src\royale-compiler/src/main/script/prerequisiteCheck.groovy
I verified that the groovy plugin was being called in both case and was being 
fed backslashes as well as forward slashes in both cases. Also, both have the 
same version: 2.1.1




From: Piotr Zarzycki 
Sent: Monday, May 4, 2020 6:35:22 PM
To: Apache Royale Development 
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Something cut the message. Could you paste here  https://paste.apache.org/

pon., 4 maj 2020 o 17:32 Yishay Weiss  napisał(a):

> This means though, that it’s still failing on Windows after Alex’s
> changes, as I’ve verified. I’m getting a bit lost trying to debug this.
>
> Running from the SVN dist repo
>
> C:\dev\dist\dist\dev\royale\0.9.7\rc3\apache-royale-0.9.7-maven-src\royale-compiler>
> mvn clean install
>
> Fails with the below message,
>
> But running the same command from the git repo
>
> C:\dev\flexjs\royale-compiler [release/0.9.7 =]> mvn clean install
>
> Does not fail.
>
> Any ideas?
>
>
>
>
> From: Yishay Weiss<mailto:yishayj...@hotmail.com>
> Sent: Monday, May 4, 2020 3:04 PM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.7
>
> Good catch Chris. I was focusing on the wrong message.
>
> From: Christofer Dutz<mailto:christofer.d...@c-ware.de>
> Sent: Monday, May 4, 2020 2:09 PM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7
>
> Just some input from the sidelines:
> - It shouldn't have any impact on the build if you enable/disable profiles
> that don't exist. All you get is a warning that tells you the profiles
> don't exist.
>
> - The actual failure is because the the path to the prerequisiteCheck
> script is windows-encoded (Backslashs) ... strange thing is that this
> didn't fail for normal Windows executions both for Royale same as in PLC4X
> ... we've got the identical setup for 2-3 years now and haven't heard of
> any issues with it. I would guess the build is started somewhat differently
> than others ... perhaps it could be fixed by removing the
> "${project.basedir}/" prefix and using relative paths instead.
>
> And just a little explanation what this script does:
> It's a goovy script that is executed and checks if all required tools are
> available in the right versions and if all required environment-variables
> are set and are set to valid values. As soon as you run a Maven build it
> outputs a list of thigs it checked and if checks fail, it quickly fails the
> build with a list of findings the user has to address first.
>
> Hope that helps.
>
> Chris
>
>
>
> Am 04.05.20, 11:45 schrieb "Carlos Rovira" :
>
> Hi Alex and Yishay,
>
> first, congrats for the hard work to reach to this point. I think many
> issues has been fixed and only that just is worth the time you guys
> invested on it :)
>
> regarding voting. I'm confident that my check will report a +1 since, I
> consider all the points for a normal Apache release, but thinking in
> the
> current problem with running maven from ant with old profiles... why
> the
> need to make ANT run maven again. both are different build tools and
> both
> need to work separately, but don't understand why one should run the
> other.
> And if that's the case, why just make ant run maven? why not make
> maven run
> ant too? I think it should be all or nothing
>
> The other point I don't understand is about why to continue vote if you
> detect the problems stated in this thread. For me is completely ok,
> but if
> you worked hard to make all this complex release process, don't
> understand
> that you finally consider green

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-04 Thread Piotr Zarzycki

Something cut the message. Could you paste here  https://paste.apache.org/

pon., 4 maj 2020 o 17:32 Yishay Weiss  napisał(a):

> This means though, that it’s still failing on Windows after Alex’s
> changes, as I’ve verified. I’m getting a bit lost trying to debug this.
>
> Running from the SVN dist repo
>
> C:\dev\dist\dist\dev\royale\0.9.7\rc3\apache-royale-0.9.7-maven-src\royale-compiler>
> mvn clean install
>
> Fails with the below message,
>
> But running the same command from the git repo
>
> C:\dev\flexjs\royale-compiler [release/0.9.7 =]> mvn clean install
>
> Does not fail.
>
> Any ideas?
>
>
>
>
> From: Yishay Weiss<mailto:yishayj...@hotmail.com>
> Sent: Monday, May 4, 2020 3:04 PM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.7
>
> Good catch Chris. I was focusing on the wrong message.
>
> From: Christofer Dutz<mailto:christofer.d...@c-ware.de>
> Sent: Monday, May 4, 2020 2:09 PM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7
>
> Just some input from the sidelines:
> - It shouldn't have any impact on the build if you enable/disable profiles
> that don't exist. All you get is a warning that tells you the profiles
> don't exist.
>
> - The actual failure is because the the path to the prerequisiteCheck
> script is windows-encoded (Backslashs) ... strange thing is that this
> didn't fail for normal Windows executions both for Royale same as in PLC4X
> ... we've got the identical setup for 2-3 years now and haven't heard of
> any issues with it. I would guess the build is started somewhat differently
> than others ... perhaps it could be fixed by removing the
> "${project.basedir}/" prefix and using relative paths instead.
>
> And just a little explanation what this script does:
> It's a goovy script that is executed and checks if all required tools are
> available in the right versions and if all required environment-variables
> are set and are set to valid values. As soon as you run a Maven build it
> outputs a list of thigs it checked and if checks fail, it quickly fails the
> build with a list of findings the user has to address first.
>
> Hope that helps.
>
> Chris
>
>
>
> Am 04.05.20, 11:45 schrieb "Carlos Rovira" :
>
> Hi Alex and Yishay,
>
> first, congrats for the hard work to reach to this point. I think many
> issues has been fixed and only that just is worth the time you guys
> invested on it :)
>
> regarding voting. I'm confident that my check will report a +1 since, I
> consider all the points for a normal Apache release, but thinking in
> the
> current problem with running maven from ant with old profiles... why
> the
> need to make ANT run maven again. both are different build tools and
> both
> need to work separately, but don't understand why one should run the
> other.
> And if that's the case, why just make ant run maven? why not make
> maven run
> ant too? I think it should be all or nothing
>
> The other point I don't understand is about why to continue vote if you
> detect the problems stated in this thread. For me is completely ok,
> but if
> you worked hard to make all this complex release process, don't
> understand
> that you finally consider green light when that approval script is
> failing.
> For me that means that all that complication was not needed, and people
> must check on its own that is something normal in an apache release,
> so no
> problem at all with that.
>
> if you consider it's ok to vote, for me is ok, since all seems to
> consider
> the real minimum requirements, people is waiting long time, and I'm not
> interested in discuss it, since is clear you see it necessary for your
> release process, but just one to state it so we can all stop and take a
> bird sight on all of it and help us to visualize. Sometimes we use to
> loose perspective when we're working many time and hard in something.
>
> Anyway, I'll wait to have clear if is time to try release and vote to
> not
> waste time if it's not ok finally.
>
> Thanks!
>
> Carlos
>
>
>
>
>
>
> El lun., 4 may. 2020 a las 9:11, Alex Harui ( >)
> escribió:
>
> > I just quickly reviewed the various
> RELEASE_NOTES/README/LICENSE/NOTICE
> > files.  I guess nobody had done that earlier.  The biggest problem
> is that
> > there were 3 missing binary package dependencies in the LICENSE in
> the
> > binary pack

RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-04 Thread Yishay Weiss

This means though, that it’s still failing on Windows after Alex’s changes, as 
I’ve verified. I’m getting a bit lost trying to debug this.

Running from the SVN dist repo

C:\dev\dist\dist\dev\royale\0.9.7\rc3\apache-royale-0.9.7-maven-src\royale-compiler>
 mvn clean install

Fails with the below message,

But running the same command from the git repo

C:\dev\flexjs\royale-compiler [release/0.9.7 =]> mvn clean install

Does not fail.

Any ideas?

From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Monday, May 4, 2020 3:04 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

Good catch Chris. I was focusing on the wrong message.

From: Christofer Dutz<mailto:christofer.d...@c-ware.de>
Sent: Monday, May 4, 2020 2:09 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Just some input from the sidelines:
- It shouldn't have any impact on the build if you enable/disable profiles that 
don't exist. All you get is a warning that tells you the profiles don't exist.

- The actual failure is because the the path to the prerequisiteCheck script is 
windows-encoded (Backslashs) ... strange thing is that this didn't fail for 
normal Windows executions both for Royale same as in PLC4X ... we've got the 
identical setup for 2-3 years now and haven't heard of any issues with it. I 
would guess the build is started somewhat differently than others ... perhaps 
it could be fixed by removing the "${project.basedir}/" prefix and using 
relative paths instead.

And just a little explanation what this script does:
It's a goovy script that is executed and checks if all required tools are 
available in the right versions and if all required environment-variables are 
set and are set to valid values. As soon as you run a Maven build it outputs a 
list of thigs it checked and if checks fail, it quickly fails the build with a 
list of findings the user has to address first.

Hope that helps.

Chris

Am 04.05.20, 11:45 schrieb "Carlos Rovira" :

Hi Alex and Yishay,

first, congrats for the hard work to reach to this point. I think many
issues has been fixed and only that just is worth the time you guys
invested on it :)

regarding voting. I'm confident that my check will report a +1 since, I
consider all the points for a normal Apache release, but thinking in the
current problem with running maven from ant with old profiles... why the
need to make ANT run maven again. both are different build tools and both
need to work separately, but don't understand why one should run the other.
And if that's the case, why just make ant run maven? why not make maven run
ant too? I think it should be all or nothing

The other point I don't understand is about why to continue vote if you
detect the problems stated in this thread. For me is completely ok, but if
you worked hard to make all this complex release process, don't understand
that you finally consider green light when that approval script is failing.
For me that means that all that complication was not needed, and people
must check on its own that is something normal in an apache release, so no
problem at all with that.

if you consider it's ok to vote, for me is ok, since all seems to consider
the real minimum requirements, people is waiting long time, and I'm not
interested in discuss it, since is clear you see it necessary for your
release process, but just one to state it so we can all stop and take a
bird sight on all of it and help us to visualize. Sometimes we use to
loose perspective when we're working many time and hard in something.

Anyway, I'll wait to have clear if is time to try release and vote to not
waste time if it's not ok finally.

Thanks!

Carlos

El lun., 4 may. 2020 a las 9:11, Alex Harui ()
escribió:

> I just quickly reviewed the various RELEASE_NOTES/README/LICENSE/NOTICE
> files.  I guess nobody had done that earlier.  The biggest problem is that
> there were 3 missing binary package dependencies in the LICENSE in the
> binary package.
>
> I noticed the copyright year in the various NOTICE.* files is still 2019
> but did not update it because I am running out of time.  I've heard
> different opinions on how important that is.
>
> The URL to the online Release Notes is in the
> royale-asjs/RELEASE_NOTES.md.  This might be a good time to create the 
wiki
> page if it doesn't already exist.
>
> I'm stopping work for tonight.
> -Alex
>
> On 5/3/20, 11:58 PM, "Yishay Weiss"  wrote:
>
> Ik, online release notes sounds like a good compromise. Thank for the
> fixes. Let the votes begin!
>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-04 Thread Piotr Zarzycki

In order to try Maven build I just need run it manually separately - Am I
understand correctly ?

pon., 4 maj 2020 o 17:19 Alex Harui  napisał(a):

> The approval script in the rc3 folder has been adjusted to not try the
> Maven build from the ant sources so you should be able to use it to
> validate RC3.
>
> -Alex
>
> On 5/4/20, 8:13 AM, "Piotr Zarzycki"  wrote:
>
> I have to admit approval script was very convenient and helpful with
> checking all stuff, but let's proceed with current RC. Let's move
> forward
> with release.
>
> pon., 4 maj 2020 o 13:54 Yishay Weiss 
> napisał(a):
>
> > Hi Carols,
> >
> > As I understood it, the approval script was failing because it
> hadn’t been
> > updated, not because it found a problem with the artifacts. That’s
> why I
> > thought it was ok to proceed with the release and fix the script for
> the
> > next version. Alex has since found more problems
> > RELEASE_NOTES/README/LICENSE/NOTICE which I had overlooked, so it
> could be
> > there’s enough evidence gathering to require another RC.
> >
> > So far I’ve heard Carlos say he wants to vote, and Alex say a release
> > should be ok unless there’s a problem in the jars and swcs. Does
> anyone
> > else have an opinion?  Another RC would require some work from me,
> but I
> > expect it to go much more smoothly because we’ve fixing the process
> as we
> > went along, so don’t be worried about the time I’ll need to spend on
> this.
> >
> > Thanks,
> > Yishay
> >
> >
> >
>     > From: Carlos Rovira<mailto:carlosrov...@apache.org>
> > Sent: Monday, May 4, 2020 12:45 PM
> > To: Apache Royale Development<mailto:dev@royale.apache.org>
> > Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7
> >
> > Hi Alex and Yishay,
> >
> > first, congrats for the hard work to reach to this point. I think
> many
> > issues has been fixed and only that just is worth the time you guys
> > invested on it :)
> >
> > regarding voting. I'm confident that my check will report a +1
> since, I
> > consider all the points for a normal Apache release, but thinking in
> the
> > current problem with running maven from ant with old profiles... why
> the
> > need to make ANT run maven again. both are different build tools and
> both
> > need to work separately, but don't understand why one should run the
> other.
> > And if that's the case, why just make ant run maven? why not make
> maven run
> > ant too? I think it should be all or nothing
> >
> > The other point I don't understand is about why to continue vote if
> you
> > detect the problems stated in this thread. For me is completely ok,
> but if
> > you worked hard to make all this complex release process, don't
> understand
> > that you finally consider green light when that approval script is
> failing.
> > For me that means that all that complication was not needed, and
> people
> > must check on its own that is something normal in an apache release,
> so no
> > problem at all with that.
> >
> > if you consider it's ok to vote, for me is ok, since all seems to
> consider
> > the real minimum requirements, people is waiting long time, and I'm
> not
> > interested in discuss it, since is clear you see it necessary for
> your
> > release process, but just one to state it so we can all stop and
> take a
> > bird sight on all of it and help us to visualize. Sometimes we use to
> > loose perspective when we're working many time and hard in something.
> >
> > Anyway, I'll wait to have clear if is time to try release and vote
> to not
> > waste time if it's not ok finally.
> >
> > Thanks!
> >
> > Carlos
> >
> >
> >
> >
> >
> >
> > El lun., 4 may. 2020 a las 9:11, Alex Harui
> ()
> > escribió:
> >
> > > I just quickly reviewed the various
> RELEASE_NOTES/README/LICENSE/NOTICE
> > > files.  I guess nobody had done that earlier.  The biggest problem
> is
> > that
> > > there were 3 missing binary package dependencies in the LICENSE in
> the
> > > binary package.
> > >
> > > I noticed the copyright year in the various N

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-04 Thread Alex Harui

The approval script in the rc3 folder has been adjusted to not try the Maven 
build from the ant sources so you should be able to use it to validate RC3.

-Alex

On 5/4/20, 8:13 AM, "Piotr Zarzycki"  wrote:

I have to admit approval script was very convenient and helpful with
checking all stuff, but let's proceed with current RC. Let's move forward
with release.

pon., 4 maj 2020 o 13:54 Yishay Weiss  napisał(a):

> Hi Carols,
>
> As I understood it, the approval script was failing because it hadn’t been
> updated, not because it found a problem with the artifacts. That’s why I
> thought it was ok to proceed with the release and fix the script for the
> next version. Alex has since found more problems
> RELEASE_NOTES/README/LICENSE/NOTICE which I had overlooked, so it could be
> there’s enough evidence gathering to require another RC.
>
> So far I’ve heard Carlos say he wants to vote, and Alex say a release
> should be ok unless there’s a problem in the jars and swcs. Does anyone
> else have an opinion?  Another RC would require some work from me, but I
> expect it to go much more smoothly because we’ve fixing the process as we
> went along, so don’t be worried about the time I’ll need to spend on this.
>
> Thanks,
> Yishay
>
>
>
> From: Carlos Rovira<mailto:carlosrov...@apache.org>
> Sent: Monday, May 4, 2020 12:45 PM
    > To: Apache Royale Development<mailto:dev@royale.apache.org>
> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7
>
> Hi Alex and Yishay,
>
> first, congrats for the hard work to reach to this point. I think many
> issues has been fixed and only that just is worth the time you guys
> invested on it :)
>
> regarding voting. I'm confident that my check will report a +1 since, I
> consider all the points for a normal Apache release, but thinking in the
> current problem with running maven from ant with old profiles... why the
> need to make ANT run maven again. both are different build tools and both
> need to work separately, but don't understand why one should run the 
other.
> And if that's the case, why just make ant run maven? why not make maven 
run
> ant too? I think it should be all or nothing
>
> The other point I don't understand is about why to continue vote if you
> detect the problems stated in this thread. For me is completely ok, but if
> you worked hard to make all this complex release process, don't understand
> that you finally consider green light when that approval script is 
failing.
> For me that means that all that complication was not needed, and people
> must check on its own that is something normal in an apache release, so no
> problem at all with that.
>
> if you consider it's ok to vote, for me is ok, since all seems to consider
> the real minimum requirements, people is waiting long time, and I'm not
> interested in discuss it, since is clear you see it necessary for your
> release process, but just one to state it so we can all stop and take a
> bird sight on all of it and help us to visualize. Sometimes we use to
> loose perspective when we're working many time and hard in something.
>
> Anyway, I'll wait to have clear if is time to try release and vote to not
> waste time if it's not ok finally.
>
> Thanks!
>
> Carlos
>
>
>
>
>
>
> El lun., 4 may. 2020 a las 9:11, Alex Harui ()
> escribió:
>
> > I just quickly reviewed the various RELEASE_NOTES/README/LICENSE/NOTICE
> > files.  I guess nobody had done that earlier.  The biggest problem is
> that
> > there were 3 missing binary package dependencies in the LICENSE in the
> > binary package.
> >
> > I noticed the copyright year in the various NOTICE.* files is still 2019
> > but did not update it because I am running out of time.  I've heard
> > different opinions on how important that is.
> >
> > The URL to the online Release Notes is in the
> > royale-asjs/RELEASE_NOTES.md.  This might be a good time to create the
> wiki
> > page if it doesn't already exist.
> >
> > I'm stopping work for tonight.
> > -Alex
> >
> > On 5/3/20, 11:58 PM, "Yishay Weiss"  wrote:
> >
> > Ik, online release notes sounds like a good compromise. Thank for 
the
> > fixes. Let the votes begin!
> > 
> > From: Alex Harui 
&g

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-04 Thread Piotr Zarzycki

I have to admit approval script was very convenient and helpful with
checking all stuff, but let's proceed with current RC. Let's move forward
with release.

pon., 4 maj 2020 o 13:54 Yishay Weiss  napisał(a):

> Hi Carols,
>
> As I understood it, the approval script was failing because it hadn’t been
> updated, not because it found a problem with the artifacts. That’s why I
> thought it was ok to proceed with the release and fix the script for the
> next version. Alex has since found more problems
> RELEASE_NOTES/README/LICENSE/NOTICE which I had overlooked, so it could be
> there’s enough evidence gathering to require another RC.
>
> So far I’ve heard Carlos say he wants to vote, and Alex say a release
> should be ok unless there’s a problem in the jars and swcs. Does anyone
> else have an opinion?  Another RC would require some work from me, but I
> expect it to go much more smoothly because we’ve fixing the process as we
> went along, so don’t be worried about the time I’ll need to spend on this.
>
> Thanks,
> Yishay
>
>
>
> From: Carlos Rovira<mailto:carlosrov...@apache.org>
> Sent: Monday, May 4, 2020 12:45 PM
> To: Apache Royale Development<mailto:dev@royale.apache.org>
> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7
>
> Hi Alex and Yishay,
>
> first, congrats for the hard work to reach to this point. I think many
> issues has been fixed and only that just is worth the time you guys
> invested on it :)
>
> regarding voting. I'm confident that my check will report a +1 since, I
> consider all the points for a normal Apache release, but thinking in the
> current problem with running maven from ant with old profiles... why the
> need to make ANT run maven again. both are different build tools and both
> need to work separately, but don't understand why one should run the other.
> And if that's the case, why just make ant run maven? why not make maven run
> ant too? I think it should be all or nothing
>
> The other point I don't understand is about why to continue vote if you
> detect the problems stated in this thread. For me is completely ok, but if
> you worked hard to make all this complex release process, don't understand
> that you finally consider green light when that approval script is failing.
> For me that means that all that complication was not needed, and people
> must check on its own that is something normal in an apache release, so no
> problem at all with that.
>
> if you consider it's ok to vote, for me is ok, since all seems to consider
> the real minimum requirements, people is waiting long time, and I'm not
> interested in discuss it, since is clear you see it necessary for your
> release process, but just one to state it so we can all stop and take a
> bird sight on all of it and help us to visualize. Sometimes we use to
> loose perspective when we're working many time and hard in something.
>
> Anyway, I'll wait to have clear if is time to try release and vote to not
> waste time if it's not ok finally.
>
> Thanks!
>
> Carlos
>
>
>
>
>
>
> El lun., 4 may. 2020 a las 9:11, Alex Harui ()
> escribió:
>
> > I just quickly reviewed the various RELEASE_NOTES/README/LICENSE/NOTICE
> > files.  I guess nobody had done that earlier.  The biggest problem is
> that
> > there were 3 missing binary package dependencies in the LICENSE in the
> > binary package.
> >
> > I noticed the copyright year in the various NOTICE.* files is still 2019
> > but did not update it because I am running out of time.  I've heard
> > different opinions on how important that is.
> >
> > The URL to the online Release Notes is in the
> > royale-asjs/RELEASE_NOTES.md.  This might be a good time to create the
> wiki
> > page if it doesn't already exist.
> >
> > I'm stopping work for tonight.
> > -Alex
> >
> > On 5/3/20, 11:58 PM, "Yishay Weiss"  wrote:
> >
> > Ik, online release notes sounds like a good compromise. Thank for the
> > fixes. Let the votes begin!
> > 
> > From: Alex Harui 
> > Sent: Monday, May 4, 2020 6:00 AM
> > To: dev@royale.apache.org 
> > Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7
> >
> > Not sure I understood you.  We can't release a changed README in
> > royale-compiler without starting an RC4.  The updated README has been
> > committed to the release branch.  We have to revert some commits on the
> > release branches that change the versions to 0.9.8 snapshot before
> starting
> > over.
> >
> > If you have the time to re-run most of the steps, that would be best,
>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-04 Thread Christofer Dutz

It seems these "afdesign" files are the source-projects Carlos used to create 
the SVG's in that blog post with.
So generally they could be deleted and the example would still work, but I 
think it's good they are there, cause this way someone could open them in 
"Affinity Designer" and modify them.

I guess I wouldn't vote -1 on it, if they are in there. But I would probably 
move them outside the "resources" directory into some "src/main/affinity" 
directory to make their use clearer and to not have them included in the final 
application/library ... but this could easily be done for the next release.

Chris

Am 04.05.20, 13:54 schrieb "Yishay Weiss" :

Hi Carols,

As I understood it, the approval script was failing because it hadn’t been 
updated, not because it found a problem with the artifacts. That’s why I 
thought it was ok to proceed with the release and fix the script for the next 
version. Alex has since found more problems RELEASE_NOTES/README/LICENSE/NOTICE 
which I had overlooked, so it could be there’s enough evidence gathering to 
require another RC.

So far I’ve heard Carlos say he wants to vote, and Alex say a release 
should be ok unless there’s a problem in the jars and swcs. Does anyone else 
have an opinion?  Another RC would require some work from me, but I expect it 
to go much more smoothly because we’ve fixing the process as we went along, so 
don’t be worried about the time I’ll need to spend on this.

Thanks,
Yishay

From: Carlos Rovira<mailto:carlosrov...@apache.org>
Sent: Monday, May 4, 2020 12:45 PM
To: Apache Royale Development<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Hi Alex and Yishay,

first, congrats for the hard work to reach to this point. I think many
issues has been fixed and only that just is worth the time you guys
invested on it :)

regarding voting. I'm confident that my check will report a +1 since, I
consider all the points for a normal Apache release, but thinking in the
current problem with running maven from ant with old profiles... why the
need to make ANT run maven again. both are different build tools and both
need to work separately, but don't understand why one should run the other.
And if that's the case, why just make ant run maven? why not make maven run
ant too? I think it should be all or nothing

The other point I don't understand is about why to continue vote if you
detect the problems stated in this thread. For me is completely ok, but if
you worked hard to make all this complex release process, don't understand
that you finally consider green light when that approval script is failing.
For me that means that all that complication was not needed, and people
must check on its own that is something normal in an apache release, so no
problem at all with that.

if you consider it's ok to vote, for me is ok, since all seems to consider
the real minimum requirements, people is waiting long time, and I'm not
interested in discuss it, since is clear you see it necessary for your
release process, but just one to state it so we can all stop and take a
bird sight on all of it and help us to visualize. Sometimes we use to
loose perspective when we're working many time and hard in something.

Anyway, I'll wait to have clear if is time to try release and vote to not
waste time if it's not ok finally.

Thanks!

Carlos

El lun., 4 may. 2020 a las 9:11, Alex Harui ()
escribió:

> I just quickly reviewed the various RELEASE_NOTES/README/LICENSE/NOTICE
> files.  I guess nobody had done that earlier.  The biggest problem is that
> there were 3 missing binary package dependencies in the LICENSE in the
> binary package.
>
> I noticed the copyright year in the various NOTICE.* files is still 2019
> but did not update it because I am running out of time.  I've heard
> different opinions on how important that is.
>
> The URL to the online Release Notes is in the
> royale-asjs/RELEASE_NOTES.md.  This might be a good time to create the 
wiki
> page if it doesn't already exist.
>
> I'm stopping work for tonight.
> -Alex
>
> On 5/3/20, 11:58 PM, "Yishay Weiss"  wrote:
>
> Ik, online release notes sounds like a good compromise. Thank for the
> fixes. Let the votes begin!
> ________
> From: Alex Harui 
>     Sent: Monday, May 4, 2020 6:00 AM
> To: dev@royale.apache.org 
> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7
>
> Not sure I understood you.  We can't release a changed README in
> royale-compiler without starting an RC4.  The up

RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-04 Thread Yishay Weiss

Good catch Chris. I was focusing on the wrong message.

From: Christofer Dutz<mailto:christofer.d...@c-ware.de>
Sent: Monday, May 4, 2020 2:09 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Just some input from the sidelines:
- It shouldn't have any impact on the build if you enable/disable profiles that 
don't exist. All you get is a warning that tells you the profiles don't exist.

- The actual failure is because the the path to the prerequisiteCheck script is 
windows-encoded (Backslashs) ... strange thing is that this didn't fail for 
normal Windows executions both for Royale same as in PLC4X ... we've got the 
identical setup for 2-3 years now and haven't heard of any issues with it. I 
would guess the build is started somewhat differently than others ... perhaps 
it could be fixed by removing the "${project.basedir}/" prefix and using 
relative paths instead.

And just a little explanation what this script does:
It's a goovy script that is executed and checks if all required tools are 
available in the right versions and if all required environment-variables are 
set and are set to valid values. As soon as you run a Maven build it outputs a 
list of thigs it checked and if checks fail, it quickly fails the build with a 
list of findings the user has to address first.

Hope that helps.

Chris

Am 04.05.20, 11:45 schrieb "Carlos Rovira" :

Hi Alex and Yishay,

first, congrats for the hard work to reach to this point. I think many
issues has been fixed and only that just is worth the time you guys
invested on it :)

regarding voting. I'm confident that my check will report a +1 since, I
consider all the points for a normal Apache release, but thinking in the
current problem with running maven from ant with old profiles... why the
need to make ANT run maven again. both are different build tools and both
need to work separately, but don't understand why one should run the other.
And if that's the case, why just make ant run maven? why not make maven run
ant too? I think it should be all or nothing

The other point I don't understand is about why to continue vote if you
detect the problems stated in this thread. For me is completely ok, but if
you worked hard to make all this complex release process, don't understand
that you finally consider green light when that approval script is failing.
For me that means that all that complication was not needed, and people
must check on its own that is something normal in an apache release, so no
problem at all with that.

if you consider it's ok to vote, for me is ok, since all seems to consider
the real minimum requirements, people is waiting long time, and I'm not
interested in discuss it, since is clear you see it necessary for your
release process, but just one to state it so we can all stop and take a
bird sight on all of it and help us to visualize. Sometimes we use to
loose perspective when we're working many time and hard in something.

Anyway, I'll wait to have clear if is time to try release and vote to not
waste time if it's not ok finally.

Thanks!

Carlos

El lun., 4 may. 2020 a las 9:11, Alex Harui ()
escribió:

> I just quickly reviewed the various RELEASE_NOTES/README/LICENSE/NOTICE
> files.  I guess nobody had done that earlier.  The biggest problem is that
> there were 3 missing binary package dependencies in the LICENSE in the
> binary package.
>
> I noticed the copyright year in the various NOTICE.* files is still 2019
> but did not update it because I am running out of time.  I've heard
> different opinions on how important that is.
>
> The URL to the online Release Notes is in the
> royale-asjs/RELEASE_NOTES.md.  This might be a good time to create the 
wiki
> page if it doesn't already exist.
>
> I'm stopping work for tonight.
> -Alex
>
> On 5/3/20, 11:58 PM, "Yishay Weiss"  wrote:
>
> Ik, online release notes sounds like a good compromise. Thank for the
> fixes. Let the votes begin!
> 
> From: Alex Harui 
> Sent: Monday, May 4, 2020 6:00 AM
> To: dev@royale.apache.org 
> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7
>
> Not sure I understood you.  We can't release a changed README in
> royale-compiler without starting an RC4.  The updated README has been
> committed to the release branch.  We have to revert some commits on the
> release branches that change the versions to 0.9.8 snapshot before 
starting
> over.
>
> If you have the time to re-run most of the steps, that would be best,
&g

RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-04 Thread Yishay Weiss

Hi Carols,

As I understood it, the approval script was failing because it hadn’t been 
updated, not because it found a problem with the artifacts. That’s why I 
thought it was ok to proceed with the release and fix the script for the next 
version. Alex has since found more problems RELEASE_NOTES/README/LICENSE/NOTICE 
which I had overlooked, so it could be there’s enough evidence gathering to 
require another RC.

So far I’ve heard Carlos say he wants to vote, and Alex say a release should be 
ok unless there’s a problem in the jars and swcs. Does anyone else have an 
opinion?  Another RC would require some work from me, but I expect it to go 
much more smoothly because we’ve fixing the process as we went along, so don’t 
be worried about the time I’ll need to spend on this.

Thanks,
Yishay

From: Carlos Rovira<mailto:carlosrov...@apache.org>
Sent: Monday, May 4, 2020 12:45 PM
To: Apache Royale Development<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Hi Alex and Yishay,

first, congrats for the hard work to reach to this point. I think many
issues has been fixed and only that just is worth the time you guys
invested on it :)

regarding voting. I'm confident that my check will report a +1 since, I
consider all the points for a normal Apache release, but thinking in the
current problem with running maven from ant with old profiles... why the
need to make ANT run maven again. both are different build tools and both
need to work separately, but don't understand why one should run the other.
And if that's the case, why just make ant run maven? why not make maven run
ant too? I think it should be all or nothing

The other point I don't understand is about why to continue vote if you
detect the problems stated in this thread. For me is completely ok, but if
you worked hard to make all this complex release process, don't understand
that you finally consider green light when that approval script is failing.
For me that means that all that complication was not needed, and people
must check on its own that is something normal in an apache release, so no
problem at all with that.

if you consider it's ok to vote, for me is ok, since all seems to consider
the real minimum requirements, people is waiting long time, and I'm not
interested in discuss it, since is clear you see it necessary for your
release process, but just one to state it so we can all stop and take a
bird sight on all of it and help us to visualize. Sometimes we use to
loose perspective when we're working many time and hard in something.

Anyway, I'll wait to have clear if is time to try release and vote to not
waste time if it's not ok finally.

Thanks!

Carlos

El lun., 4 may. 2020 a las 9:11, Alex Harui ()
escribió:

> I just quickly reviewed the various RELEASE_NOTES/README/LICENSE/NOTICE
> files.  I guess nobody had done that earlier.  The biggest problem is that
> there were 3 missing binary package dependencies in the LICENSE in the
> binary package.
>
> I noticed the copyright year in the various NOTICE.* files is still 2019
> but did not update it because I am running out of time.  I've heard
> different opinions on how important that is.
>
> The URL to the online Release Notes is in the
> royale-asjs/RELEASE_NOTES.md.  This might be a good time to create the wiki
> page if it doesn't already exist.
>
> I'm stopping work for tonight.
> -Alex
>
> On 5/3/20, 11:58 PM, "Yishay Weiss"  wrote:
>
> Ik, online release notes sounds like a good compromise. Thank for the
> fixes. Let the votes begin!
> 
> From: Alex Harui 
> Sent: Monday, May 4, 2020 6:00 AM
>     To: dev@royale.apache.org 
> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7
>
> Not sure I understood you.  We can't release a changed README in
> royale-compiler without starting an RC4.  The updated README has been
> committed to the release branch.  We have to revert some commits on the
> release branches that change the versions to 0.9.8 snapshot before starting
> over.
>
> If you have the time to re-run most of the steps, that would be best,
> but will delay the release and I'm not sure it is worth it.  We have online
> release notes to make corrections.
>
> I think it is mostly up to you though.
> -Alex
>
> On 5/3/20, 10:42 PM, "Yishay Weiss"  wrote:
>
> I think we should continue the vote. If more problems are
> discovered I can start another release candidate. I think we should at
> least fix the compile README to not use -main.
>
> From: Alex Harui<mailto:aha...@adobe.com.INVALID>
> Sent: Sunday, May 3, 2020 10:06 PM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> Subject: Re: [DISCUSS] Discuss Releas

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-04 Thread Christofer Dutz

Just some input from the sidelines:
- It shouldn't have any impact on the build if you enable/disable profiles that 
don't exist. All you get is a warning that tells you the profiles don't exist.

- The actual failure is because the the path to the prerequisiteCheck script is 
windows-encoded (Backslashs) ... strange thing is that this didn't fail for 
normal Windows executions both for Royale same as in PLC4X ... we've got the 
identical setup for 2-3 years now and haven't heard of any issues with it. I 
would guess the build is started somewhat differently than others ... perhaps 
it could be fixed by removing the "${project.basedir}/" prefix and using 
relative paths instead.

And just a little explanation what this script does: 
It's a goovy script that is executed and checks if all required tools are 
available in the right versions and if all required environment-variables are 
set and are set to valid values. As soon as you run a Maven build it outputs a 
list of thigs it checked and if checks fail, it quickly fails the build with a 
list of findings the user has to address first.

Hope that helps.

Chris

Am 04.05.20, 11:45 schrieb "Carlos Rovira" :

Hi Alex and Yishay,

first, congrats for the hard work to reach to this point. I think many
issues has been fixed and only that just is worth the time you guys
invested on it :)

regarding voting. I'm confident that my check will report a +1 since, I
consider all the points for a normal Apache release, but thinking in the
current problem with running maven from ant with old profiles... why the
need to make ANT run maven again. both are different build tools and both
need to work separately, but don't understand why one should run the other.
And if that's the case, why just make ant run maven? why not make maven run
ant too? I think it should be all or nothing

The other point I don't understand is about why to continue vote if you
detect the problems stated in this thread. For me is completely ok, but if
you worked hard to make all this complex release process, don't understand
that you finally consider green light when that approval script is failing.
For me that means that all that complication was not needed, and people
must check on its own that is something normal in an apache release, so no
problem at all with that.

if you consider it's ok to vote, for me is ok, since all seems to consider
the real minimum requirements, people is waiting long time, and I'm not
interested in discuss it, since is clear you see it necessary for your
release process, but just one to state it so we can all stop and take a
bird sight on all of it and help us to visualize. Sometimes we use to
loose perspective when we're working many time and hard in something.

Anyway, I'll wait to have clear if is time to try release and vote to not
waste time if it's not ok finally.

Thanks!

Carlos

El lun., 4 may. 2020 a las 9:11, Alex Harui ()
escribió:

> I just quickly reviewed the various RELEASE_NOTES/README/LICENSE/NOTICE
> files.  I guess nobody had done that earlier.  The biggest problem is that
> there were 3 missing binary package dependencies in the LICENSE in the
> binary package.
>
> I noticed the copyright year in the various NOTICE.* files is still 2019
> but did not update it because I am running out of time.  I've heard
> different opinions on how important that is.
>
> The URL to the online Release Notes is in the
> royale-asjs/RELEASE_NOTES.md.  This might be a good time to create the 
wiki
> page if it doesn't already exist.
>
> I'm stopping work for tonight.
> -Alex
>
> On 5/3/20, 11:58 PM, "Yishay Weiss"  wrote:
>
> Ik, online release notes sounds like a good compromise. Thank for the
> fixes. Let the votes begin!
> 
> From: Alex Harui 
> Sent: Monday, May 4, 2020 6:00 AM
    > To: dev@royale.apache.org 
> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7
>
> Not sure I understood you.  We can't release a changed README in
> royale-compiler without starting an RC4.  The updated README has been
> committed to the release branch.  We have to revert some commits on the
> release branches that change the versions to 0.9.8 snapshot before 
starting
> over.
>
> If you have the time to re-run most of the steps, that would be best,
> but will delay the release and I'm not sure it is worth it.  We have 
online
> release notes to make corrections.
>
> I think it is mostly up to you though.
> -Alex
>
> On 5/3/20, 10:42 PM, "Yishay Weiss"

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-04 Thread Carlos Rovira

Hi Alex and Yishay,

first, congrats for the hard work to reach to this point. I think many
issues has been fixed and only that just is worth the time you guys
invested on it :)

regarding voting. I'm confident that my check will report a +1 since, I
consider all the points for a normal Apache release, but thinking in the
current problem with running maven from ant with old profiles... why the
need to make ANT run maven again. both are different build tools and both
need to work separately, but don't understand why one should run the other.
And if that's the case, why just make ant run maven? why not make maven run
ant too? I think it should be all or nothing

The other point I don't understand is about why to continue vote if you
detect the problems stated in this thread. For me is completely ok, but if
you worked hard to make all this complex release process, don't understand
that you finally consider green light when that approval script is failing.
For me that means that all that complication was not needed, and people
must check on its own that is something normal in an apache release, so no
problem at all with that.

if you consider it's ok to vote, for me is ok, since all seems to consider
the real minimum requirements, people is waiting long time, and I'm not
interested in discuss it, since is clear you see it necessary for your
release process, but just one to state it so we can all stop and take a
bird sight on all of it and help us to visualize. Sometimes we use to
loose perspective when we're working many time and hard in something.

Anyway, I'll wait to have clear if is time to try release and vote to not
waste time if it's not ok finally.

Thanks!

Carlos

El lun., 4 may. 2020 a las 9:11, Alex Harui ()
escribió:

> I just quickly reviewed the various RELEASE_NOTES/README/LICENSE/NOTICE
> files.  I guess nobody had done that earlier.  The biggest problem is that
> there were 3 missing binary package dependencies in the LICENSE in the
> binary package.
>
> I noticed the copyright year in the various NOTICE.* files is still 2019
> but did not update it because I am running out of time.  I've heard
> different opinions on how important that is.
>
> The URL to the online Release Notes is in the
> royale-asjs/RELEASE_NOTES.md.  This might be a good time to create the wiki
> page if it doesn't already exist.
>
> I'm stopping work for tonight.
> -Alex
>
> On 5/3/20, 11:58 PM, "Yishay Weiss"  wrote:
>
> Ik, online release notes sounds like a good compromise. Thank for the
> fixes. Let the votes begin!
> 
> From: Alex Harui 
> Sent: Monday, May 4, 2020 6:00 AM
>     To: dev@royale.apache.org 
> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7
>
> Not sure I understood you.  We can't release a changed README in
> royale-compiler without starting an RC4.  The updated README has been
> committed to the release branch.  We have to revert some commits on the
> release branches that change the versions to 0.9.8 snapshot before starting
> over.
>
> If you have the time to re-run most of the steps, that would be best,
> but will delay the release and I'm not sure it is worth it.  We have online
> release notes to make corrections.
>
> I think it is mostly up to you though.
> -Alex
>
> On 5/3/20, 10:42 PM, "Yishay Weiss"  wrote:
>
> I think we should continue the vote. If more problems are
> discovered I can start another release candidate. I think we should at
> least fix the compile README to not use -main.
>
> From: Alex Harui<mailto:aha...@adobe.com.INVALID>
>     Sent: Sunday, May 3, 2020 10:06 PM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7
>
> Bummer.   Lots of little things flushed out late in the game.
>
> -There are .afdesign binary files checked into our repos.  These
> are binary files that aren't the common types (.PNG, .JPG, etc).
> -New required folders (src/main) were added to the Maven build for
> royale-compiler and royale-asjs but not added to the Ant source packaging
> -The uses of -main that Yishay found.
>
> IMO, quickest way to a release is to not start over with an RC4
> unless we find a more major problem with RC3.  I've updated several files
> in the branch.  I'm going to skip releasecandidate.xml for now until
> someone wants to cut a release locally and use Ant to type fewer commands.
>
> The Approval script will fail testing if the Ant source can be
> used by Maven.  Assuming the Maven distribution is working, this is less
> important.  So I think that we skip that test for this RC.  I put an
> ApproveR

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-04 Thread Alex Harui

I just quickly reviewed the various RELEASE_NOTES/README/LICENSE/NOTICE files.  
I guess nobody had done that earlier.  The biggest problem is that there were 3 
missing binary package dependencies in the LICENSE in the binary package.

I noticed the copyright year in the various NOTICE.* files is still 2019 but 
did not update it because I am running out of time.  I've heard different 
opinions on how important that is.

The URL to the online Release Notes is in the royale-asjs/RELEASE_NOTES.md.  
This might be a good time to create the wiki page if it doesn't already exist.

I'm stopping work for tonight.
-Alex

On 5/3/20, 11:58 PM, "Yishay Weiss"  wrote:

Ik, online release notes sounds like a good compromise. Thank for the 
fixes. Let the votes begin!

From: Alex Harui 
Sent: Monday, May 4, 2020 6:00 AM
To: dev@royale.apache.org 
    Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Not sure I understood you.  We can't release a changed README in 
royale-compiler without starting an RC4.  The updated README has been committed 
to the release branch.  We have to revert some commits on the release branches 
that change the versions to 0.9.8 snapshot before starting over.

If you have the time to re-run most of the steps, that would be best, but 
will delay the release and I'm not sure it is worth it.  We have online release 
notes to make corrections.

I think it is mostly up to you though.
-Alex

On 5/3/20, 10:42 PM, "Yishay Weiss"  wrote:

I think we should continue the vote. If more problems are discovered I 
can start another release candidate. I think we should at least fix the compile 
README to not use -main.

From: Alex Harui<mailto:aha...@adobe.com.INVALID>
Sent: Sunday, May 3, 2020 10:06 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
    Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Bummer.   Lots of little things flushed out late in the game.

-There are .afdesign binary files checked into our repos.  These are 
binary files that aren't the common types (.PNG, .JPG, etc).
-New required folders (src/main) were added to the Maven build for 
royale-compiler and royale-asjs but not added to the Ant source packaging
-The uses of -main that Yishay found.

IMO, quickest way to a release is to not start over with an RC4 unless 
we find a more major problem with RC3.  I've updated several files in the 
branch.  I'm going to skip releasecandidate.xml for now until someone wants to 
cut a release locally and use Ant to type fewer commands.

The Approval script will fail testing if the Ant source can be used by 
Maven.  Assuming the Maven distribution is working, this is less important.  So 
I think that we skip that test for this RC.  I put an ApproveRoyale.xml on dist 
that skips that test and then the approval script completed successfully.  I 
also manually tested that if we have the two missing folders that the 
ApproveRoyale.xml I checked into the release branch will build the Maven 
artifacts from the Ant source.

So, IMO, I think the packages are good enough for now and we should 
release unless we find something is broken in the jars and swcs.

My 2 cents,
-Alex

On 5/3/20, 8:08 AM, "Alex Harui"  wrote:

I will look into it.

-Alex

On 5/3/20, 7:35 AM, "Yishay Weiss"  wrote:

Whatever the fix is, it will also need to be applied in these 
files:

C:\dev\flexjs\royale-asjs [release/0.9.7 =]> git grep 
"main,utils"
ApproveRoyale.xml:
releasecandidate.xml:
releasecandidate.xml:
releasemgr/README:royale-compiler:  mvn clean install -P 
-main,utils
C:\dev\flexjs\royale-asjs [release/0.9.7 =]> cd ..
C:\dev\flexjs> cd .\royale-compiler\
C:\dev\flexjs\royale-compiler [release/0.9.7 =]> git grep 
"main,utils"
Jenkinsfile:bat "mvn -U clean ${mavenGoal} 
${mavenLocalRepo} -s C:\\.m2\\settings.xml -P -main,utils 
-Dcom.adobe.systemIdsForWhichTheTermsOfTheA
dobeLicenseAgreementAreAccepted=3c9041a9,3872fc1e"
README:mvn clean install -P -main,utils

From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Sunday, May 3, 2020 5:06 PM
        To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-04 Thread Yishay Weiss

Ik, online release notes sounds like a good compromise. Thank for the fixes. 
Let the votes begin!

From: Alex Harui 
Sent: Monday, May 4, 2020 6:00 AM
To: dev@royale.apache.org 
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Not sure I understood you.  We can't release a changed README in 
royale-compiler without starting an RC4.  The updated README has been committed 
to the release branch.  We have to revert some commits on the release branches 
that change the versions to 0.9.8 snapshot before starting over.

If you have the time to re-run most of the steps, that would be best, but will 
delay the release and I'm not sure it is worth it.  We have online release 
notes to make corrections.

I think it is mostly up to you though.
-Alex

On 5/3/20, 10:42 PM, "Yishay Weiss"  wrote:

I think we should continue the vote. If more problems are discovered I can 
start another release candidate. I think we should at least fix the compile 
README to not use -main.

From: Alex Harui<mailto:aha...@adobe.com.INVALID>
Sent: Sunday, May 3, 2020 10:06 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
    Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Bummer.   Lots of little things flushed out late in the game.

-There are .afdesign binary files checked into our repos.  These are binary 
files that aren't the common types (.PNG, .JPG, etc).
-New required folders (src/main) were added to the Maven build for 
royale-compiler and royale-asjs but not added to the Ant source packaging
-The uses of -main that Yishay found.

IMO, quickest way to a release is to not start over with an RC4 unless we 
find a more major problem with RC3.  I've updated several files in the branch.  
I'm going to skip releasecandidate.xml for now until someone wants to cut a 
release locally and use Ant to type fewer commands.

The Approval script will fail testing if the Ant source can be used by 
Maven.  Assuming the Maven distribution is working, this is less important.  So 
I think that we skip that test for this RC.  I put an ApproveRoyale.xml on dist 
that skips that test and then the approval script completed successfully.  I 
also manually tested that if we have the two missing folders that the 
ApproveRoyale.xml I checked into the release branch will build the Maven 
artifacts from the Ant source.

So, IMO, I think the packages are good enough for now and we should release 
unless we find something is broken in the jars and swcs.

My 2 cents,
-Alex

On 5/3/20, 8:08 AM, "Alex Harui"  wrote:

I will look into it.

-Alex

On 5/3/20, 7:35 AM, "Yishay Weiss"  wrote:

Whatever the fix is, it will also need to be applied in these files:

C:\dev\flexjs\royale-asjs [release/0.9.7 =]> git grep "main,utils"
ApproveRoyale.xml:
releasecandidate.xml:
releasecandidate.xml:
releasemgr/README:royale-compiler:  mvn clean install -P -main,utils
C:\dev\flexjs\royale-asjs [release/0.9.7 =]> cd ..
C:\dev\flexjs> cd .\royale-compiler\
C:\dev\flexjs\royale-compiler [release/0.9.7 =]> git grep 
"main,utils"
Jenkinsfile:bat "mvn -U clean ${mavenGoal} 
${mavenLocalRepo} -s C:\\.m2\\settings.xml -P -main,utils 
-Dcom.adobe.systemIdsForWhichTheTermsOfTheA
dobeLicenseAgreementAreAccepted=3c9041a9,3872fc1e"
README:mvn clean install -P -main,utils

From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Sunday, May 3, 2020 5:06 PM
        To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

Looks like the profiles in ApproveRoyale.xml need to be updated 
after Chris’s refactor. Can someone fix this?

From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Sunday, May 3, 2020 5:02 PM
        To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

Oops, may have been premature to start the vote.

I’m getting this [1] when running ApproveRoyale.xml.

RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-03 Thread Yishay Weiss

I think we should continue the vote. If more problems are discovered I can 
start another release candidate. I think we should at least fix the compile 
README to not use -main.

From: Alex Harui<mailto:aha...@adobe.com.INVALID>
Sent: Sunday, May 3, 2020 10:06 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Bummer.   Lots of little things flushed out late in the game.

-There are .afdesign binary files checked into our repos.  These are binary 
files that aren't the common types (.PNG, .JPG, etc).
-New required folders (src/main) were added to the Maven build for 
royale-compiler and royale-asjs but not added to the Ant source packaging
-The uses of -main that Yishay found.

IMO, quickest way to a release is to not start over with an RC4 unless we find 
a more major problem with RC3.  I've updated several files in the branch.  I'm 
going to skip releasecandidate.xml for now until someone wants to cut a release 
locally and use Ant to type fewer commands.

The Approval script will fail testing if the Ant source can be used by Maven.  
Assuming the Maven distribution is working, this is less important.  So I think 
that we skip that test for this RC.  I put an ApproveRoyale.xml on dist that 
skips that test and then the approval script completed successfully.  I also 
manually tested that if we have the two missing folders that the 
ApproveRoyale.xml I checked into the release branch will build the Maven 
artifacts from the Ant source.

So, IMO, I think the packages are good enough for now and we should release 
unless we find something is broken in the jars and swcs.

My 2 cents,
-Alex

On 5/3/20, 8:08 AM, "Alex Harui"  wrote:

I will look into it.

-Alex

On 5/3/20, 7:35 AM, "Yishay Weiss"  wrote:

Whatever the fix is, it will also need to be applied in these files:

C:\dev\flexjs\royale-asjs [release/0.9.7 =]> git grep "main,utils"
ApproveRoyale.xml:
releasecandidate.xml:
releasecandidate.xml:
releasemgr/README:royale-compiler:  mvn clean install -P -main,utils
C:\dev\flexjs\royale-asjs [release/0.9.7 =]> cd ..
C:\dev\flexjs> cd .\royale-compiler\
C:\dev\flexjs\royale-compiler [release/0.9.7 =]> git grep "main,utils"
Jenkinsfile:bat "mvn -U clean ${mavenGoal} 
${mavenLocalRepo} -s C:\\.m2\\settings.xml -P -main,utils 
-Dcom.adobe.systemIdsForWhichTheTermsOfTheA
dobeLicenseAgreementAreAccepted=3c9041a9,3872fc1e"
README:mvn clean install -P -main,utils

From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Sunday, May 3, 2020 5:06 PM
        To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

Looks like the profiles in ApproveRoyale.xml need to be updated after 
Chris’s refactor. Can someone fix this?

From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Sunday, May 3, 2020 5:02 PM
    To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

Oops, may have been premature to start the vote.

I’m getting this [1] when running ApproveRoyale.xml. Any ideas?

[1]
build_maven:
 [echo] Path is 
C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program
 Files\Intel\WiFi\bin\;C:\Prog
ram Files\Common 
Files\Intel\WirelessCommon\;C:\dev\maven\apache-maven-3.6.1\bin;C:\dev\ant\apache-ant-1.10.1\bin;C:\Program
 Files (x86)\Vim\vim82;C:\Program Fi
les\Git\cmd;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\Microsoft VS 
Code\bin;C:\Program 
Files\PuTTY\;C:\Users\Yishay\AppData\Local\Microsoft\WindowsApps;C:\U

sers\Yishay\AppData\Roaming\npm;C:\adb;C:\Users\Yishay\.windows-build-tools\python27;C:\Program
 Files\nodejs\;C:\Program Files\Java\jdk1.8.0_212\bin;C:\WINDOWS\

system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;;C:\Program
 Files (x86)\Gpg4win\..\GnuPG\b
in;C:\Program 
Files\SlikSvn\bin;C:\Users\Yishay\AppData\Local\Microsoft\WindowsApps;C:\Users\Yishay\AppData\Roaming\npm;;C:\Program
 F

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-03 Thread Alex Harui

Bummer.   Lots of little things flushed out late in the game.

-There are .afdesign binary files checked into our repos.  These are binary 
files that aren't the common types (.PNG, .JPG, etc).
-New required folders (src/main) were added to the Maven build for 
royale-compiler and royale-asjs but not added to the Ant source packaging
-The uses of -main that Yishay found.

IMO, quickest way to a release is to not start over with an RC4 unless we find 
a more major problem with RC3.  I've updated several files in the branch.  I'm 
going to skip releasecandidate.xml for now until someone wants to cut a release 
locally and use Ant to type fewer commands.

The Approval script will fail testing if the Ant source can be used by Maven.  
Assuming the Maven distribution is working, this is less important.  So I think 
that we skip that test for this RC.  I put an ApproveRoyale.xml on dist that 
skips that test and then the approval script completed successfully.  I also 
manually tested that if we have the two missing folders that the 
ApproveRoyale.xml I checked into the release branch will build the Maven 
artifacts from the Ant source.

So, IMO, I think the packages are good enough for now and we should release 
unless we find something is broken in the jars and swcs.

My 2 cents,
-Alex

On 5/3/20, 8:08 AM, "Alex Harui"  wrote:

I will look into it.

-Alex

On 5/3/20, 7:35 AM, "Yishay Weiss"  wrote:

Whatever the fix is, it will also need to be applied in these files:

C:\dev\flexjs\royale-asjs [release/0.9.7 =]> git grep "main,utils"
ApproveRoyale.xml:
releasecandidate.xml:
releasecandidate.xml:
releasemgr/README:royale-compiler:  mvn clean install -P -main,utils
C:\dev\flexjs\royale-asjs [release/0.9.7 =]> cd ..
C:\dev\flexjs> cd .\royale-compiler\
C:\dev\flexjs\royale-compiler [release/0.9.7 =]> git grep "main,utils"
Jenkinsfile:bat "mvn -U clean ${mavenGoal} 
${mavenLocalRepo} -s C:\\.m2\\settings.xml -P -main,utils 
-Dcom.adobe.systemIdsForWhichTheTermsOfTheA
dobeLicenseAgreementAreAccepted=3c9041a9,3872fc1e"
README:mvn clean install -P -main,utils

From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Sunday, May 3, 2020 5:06 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

Looks like the profiles in ApproveRoyale.xml need to be updated after 
Chris’s refactor. Can someone fix this?

   























From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Sunday, May 3, 2020 5:02 PM
        To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

Oops, may have been premature to start the vote.

I’m getting this [1] when running ApproveRoyale.xml. Any ideas?

[1]
build_maven:
 [echo] Path is 
C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program
 Files\Intel\WiFi\bin\;C:\Prog
ram Files\Common 
Files\Intel\WirelessCommon\;C:\dev\maven\apache-maven-3.6.1\bin;C:\dev\ant\apache-ant-1.10.1\bin;C:\Program
 Files (x86)\Vim\vim82;C:\Program Fi
les\Git\cmd;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\Microsoft VS 
Code\bin;C:\Program 
Files\PuTTY\;C:\Users\Yishay\AppData\Local\Microsoft\WindowsApps;C:\U

sers\Yishay\AppData\Roaming\npm;C:\adb;C:\Users\Yishay\.windows-build-tools\python27;C:\Program
 Files\nodejs\;C:\Program Files\Java\jdk1.8.0_212\bin;C:\WINDOWS\

system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;;C:\Program
 Files (x86)\Gpg4win\..\GnuPG\b
in;C:\Program 
Files\SlikSvn\bin;C:\Users\Yishay\AppData\Local\Microsoft\WindowsApps;C:\Users\Yishay\AppData\Roaming\npm;;C:\Program
 Files (x86)\Vim\vim82
 [exec] [INFO] Scanning for projects...
 [exec] [INFO] 

 [exec] [INFO] Reactor Build Order:
 [exec] [INFO]
 [exec] [INFO] Apache Royale: Compiler: Parent  
  [pom]
 [exec] [INFO] Apache

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-03 Thread Alex Harui

I will look into it.

-Alex

On 5/3/20, 7:35 AM, "Yishay Weiss"  wrote:

Whatever the fix is, it will also need to be applied in these files:

C:\dev\flexjs\royale-asjs [release/0.9.7 =]> git grep "main,utils"
ApproveRoyale.xml:
releasecandidate.xml:
releasecandidate.xml:
releasemgr/README:royale-compiler:  mvn clean install -P -main,utils
C:\dev\flexjs\royale-asjs [release/0.9.7 =]> cd ..
C:\dev\flexjs> cd .\royale-compiler\
C:\dev\flexjs\royale-compiler [release/0.9.7 =]> git grep "main,utils"
Jenkinsfile:bat "mvn -U clean ${mavenGoal} 
${mavenLocalRepo} -s C:\\.m2\\settings.xml -P -main,utils 
-Dcom.adobe.systemIdsForWhichTheTermsOfTheA
dobeLicenseAgreementAreAccepted=3c9041a9,3872fc1e"
README:mvn clean install -P -main,utils

From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Sunday, May 3, 2020 5:06 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

Looks like the profiles in ApproveRoyale.xml need to be updated after 
Chris’s refactor. Can someone fix this?

   























From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Sunday, May 3, 2020 5:02 PM
    To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

Oops, may have been premature to start the vote.

I’m getting this [1] when running ApproveRoyale.xml. Any ideas?

[1]
build_maven:
 [echo] Path is 
C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program
 Files\Intel\WiFi\bin\;C:\Prog
ram Files\Common 
Files\Intel\WirelessCommon\;C:\dev\maven\apache-maven-3.6.1\bin;C:\dev\ant\apache-ant-1.10.1\bin;C:\Program
 Files (x86)\Vim\vim82;C:\Program Fi
les\Git\cmd;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\Microsoft VS 
Code\bin;C:\Program 
Files\PuTTY\;C:\Users\Yishay\AppData\Local\Microsoft\WindowsApps;C:\U

sers\Yishay\AppData\Roaming\npm;C:\adb;C:\Users\Yishay\.windows-build-tools\python27;C:\Program
 Files\nodejs\;C:\Program Files\Java\jdk1.8.0_212\bin;C:\WINDOWS\

system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;;C:\Program
 Files (x86)\Gpg4win\..\GnuPG\b
in;C:\Program 
Files\SlikSvn\bin;C:\Users\Yishay\AppData\Local\Microsoft\WindowsApps;C:\Users\Yishay\AppData\Roaming\npm;;C:\Program
 Files (x86)\Vim\vim82
 [exec] [INFO] Scanning for projects...
 [exec] [INFO] 

 [exec] [INFO] Reactor Build Order:
 [exec] [INFO]
 [exec] [INFO] Apache Royale: Compiler: Parent  
  [pom]
 [exec] [INFO] Apache Royale: Compiler: Compiler-Common 
  [jar]
 [exec] [INFO] Apache Royale: Compiler: Test Utils  
  [jar]
 [exec] [INFO] Apache Royale: Compiler: Externc 
  [jar]
 [exec] [INFO] Apache Royale: Compiler: Compiler
  [jar]
 [exec] [INFO] Apache Royale: Compiler: Compiler-JX 
  [jar]
 [exec] [INFO] Apache Royale: Compiler: SWFUtils
  [jar]
 [exec] [INFO] Apache Royale: Compiler: Debugger
  [jar]
 [exec] [INFO] Apache Royale: Compiler: OEM Layer   
  [jar]
 [exec] [INFO] Apache Royale: Royale Ant Tasks  
  [jar]
 [exec] [INFO] Apache Royale: RoyaleUnit Ant Tasks  
  [jar]
 [exec] [INFO] Apache Royale: Royale Maven Plugin   
 [maven-plugin]
 [exec] [INFO]
 [exec] [INFO] -< 
org.apache.royale.compiler:royale-compiler-parent >--
 [exec] [INFO] Building Apache Royale: Compiler: Parent 0.9.8-SNAPSHOT  
 [1/12]
 [exec] [INFO] [ pom 
]-
 [exec] [INFO]
 [exec] [INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ 
royale-compiler-parent ---
 [exec] [INFO]
 [exec] [INFO] --- maven-enforcer-plugin:1.4.1:enforce 
(enforce-maven-version) @ royale-compiler-parent ---
 [exec] [INFO]

RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-03 Thread Yishay Weiss

Whatever the fix is, it will also need to be applied in these files:

C:\dev\flexjs\royale-asjs [release/0.9.7 =]> git grep "main,utils"
ApproveRoyale.xml:
releasecandidate.xml:
releasecandidate.xml:
releasemgr/README:royale-compiler:  mvn clean install -P -main,utils
C:\dev\flexjs\royale-asjs [release/0.9.7 =]> cd ..
C:\dev\flexjs> cd .\royale-compiler\
C:\dev\flexjs\royale-compiler [release/0.9.7 =]> git grep "main,utils"
Jenkinsfile:bat "mvn -U clean ${mavenGoal} ${mavenLocalRepo} -s 
C:\\.m2\\settings.xml -P -main,utils -Dcom.adobe.systemIdsForWhichTheTermsOfTheA
dobeLicenseAgreementAreAccepted=3c9041a9,3872fc1e"
README:mvn clean install -P -main,utils

From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Sunday, May 3, 2020 5:06 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

Looks like the profiles in ApproveRoyale.xml need to be updated after Chris’s 
refactor. Can someone fix this?

   























From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Sunday, May 3, 2020 5:02 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

Oops, may have been premature to start the vote.

I’m getting this [1] when running ApproveRoyale.xml. Any ideas?

[1]
build_maven:
 [echo] Path is 
C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program
 Files\Intel\WiFi\bin\;C:\Prog
ram Files\Common 
Files\Intel\WirelessCommon\;C:\dev\maven\apache-maven-3.6.1\bin;C:\dev\ant\apache-ant-1.10.1\bin;C:\Program
 Files (x86)\Vim\vim82;C:\Program Fi
les\Git\cmd;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\Microsoft VS 
Code\bin;C:\Program 
Files\PuTTY\;C:\Users\Yishay\AppData\Local\Microsoft\WindowsApps;C:\U
sers\Yishay\AppData\Roaming\npm;C:\adb;C:\Users\Yishay\.windows-build-tools\python27;C:\Program
 Files\nodejs\;C:\Program Files\Java\jdk1.8.0_212\bin;C:\WINDOWS\
system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;;C:\Program
 Files (x86)\Gpg4win\..\GnuPG\b
in;C:\Program 
Files\SlikSvn\bin;C:\Users\Yishay\AppData\Local\Microsoft\WindowsApps;C:\Users\Yishay\AppData\Roaming\npm;;C:\Program
 Files (x86)\Vim\vim82
 [exec] [INFO] Scanning for projects...
 [exec] [INFO] 

 [exec] [INFO] Reactor Build Order:
 [exec] [INFO]
 [exec] [INFO] Apache Royale: Compiler: Parent  
  [pom]
 [exec] [INFO] Apache Royale: Compiler: Compiler-Common 
  [jar]
 [exec] [INFO] Apache Royale: Compiler: Test Utils  
  [jar]
 [exec] [INFO] Apache Royale: Compiler: Externc 
  [jar]
 [exec] [INFO] Apache Royale: Compiler: Compiler
  [jar]
 [exec] [INFO] Apache Royale: Compiler: Compiler-JX 
  [jar]
 [exec] [INFO] Apache Royale: Compiler: SWFUtils
  [jar]
 [exec] [INFO] Apache Royale: Compiler: Debugger
  [jar]
 [exec] [INFO] Apache Royale: Compiler: OEM Layer   
  [jar]
 [exec] [INFO] Apache Royale: Royale Ant Tasks  
  [jar]
 [exec] [INFO] Apache Royale: RoyaleUnit Ant Tasks  
  [jar]
 [exec] [INFO] Apache Royale: Royale Maven Plugin
[maven-plugin]
 [exec] [INFO]
 [exec] [INFO] -< org.apache.royale.compiler:royale-compiler-parent 
>--
 [exec] [INFO] Building Apache Royale: Compiler: Parent 0.9.8-SNAPSHOT  
 [1/12]
 [exec] [INFO] [ pom 
]-
 [exec] [INFO]
 [exec] [INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ 
royale-compiler-parent ---
 [exec] [INFO]
 [exec] [INFO] --- maven-enforcer-plugin:1.4.1:enforce 
(enforce-maven-version) @ royale-compiler-parent ---
 [exec] [INFO]
 [exec] [INFO] --- groovy-maven-plugin:2.1.1:execute (prerequisite-check) @ 
royale-compiler-parent ---
 [exec] [INFO] 

 [exec] [INFO] Reactor Summary for Apache Royale: Compiler: Parent 
0.9.8-SNAPSHOT:
 [exec] [INFO]
 [exec] [INFO] Apache Royale: Compiler: Parent  FAILURE 
[  3.938 s]
 [exec] [INFO] Apache Royale:

RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-03 Thread Yishay Weiss

Looks like the profiles in ApproveRoyale.xml need to be updated after Chris’s 
refactor. Can someone fix this?

   























From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Sunday, May 3, 2020 5:02 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

Oops, may have been premature to start the vote.

I’m getting this [1] when running ApproveRoyale.xml. Any ideas?

[1]
build_maven:
 [echo] Path is 
C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program
 Files\Intel\WiFi\bin\;C:\Prog
ram Files\Common 
Files\Intel\WirelessCommon\;C:\dev\maven\apache-maven-3.6.1\bin;C:\dev\ant\apache-ant-1.10.1\bin;C:\Program
 Files (x86)\Vim\vim82;C:\Program Fi
les\Git\cmd;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\Microsoft VS 
Code\bin;C:\Program 
Files\PuTTY\;C:\Users\Yishay\AppData\Local\Microsoft\WindowsApps;C:\U
sers\Yishay\AppData\Roaming\npm;C:\adb;C:\Users\Yishay\.windows-build-tools\python27;C:\Program
 Files\nodejs\;C:\Program Files\Java\jdk1.8.0_212\bin;C:\WINDOWS\
system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;;C:\Program
 Files (x86)\Gpg4win\..\GnuPG\b
in;C:\Program 
Files\SlikSvn\bin;C:\Users\Yishay\AppData\Local\Microsoft\WindowsApps;C:\Users\Yishay\AppData\Roaming\npm;;C:\Program
 Files (x86)\Vim\vim82
 [exec] [INFO] Scanning for projects...
 [exec] [INFO] 

 [exec] [INFO] Reactor Build Order:
 [exec] [INFO]
 [exec] [INFO] Apache Royale: Compiler: Parent  
  [pom]
 [exec] [INFO] Apache Royale: Compiler: Compiler-Common 
  [jar]
 [exec] [INFO] Apache Royale: Compiler: Test Utils  
  [jar]
 [exec] [INFO] Apache Royale: Compiler: Externc 
  [jar]
 [exec] [INFO] Apache Royale: Compiler: Compiler
  [jar]
 [exec] [INFO] Apache Royale: Compiler: Compiler-JX 
  [jar]
 [exec] [INFO] Apache Royale: Compiler: SWFUtils
  [jar]
 [exec] [INFO] Apache Royale: Compiler: Debugger
  [jar]
 [exec] [INFO] Apache Royale: Compiler: OEM Layer   
  [jar]
 [exec] [INFO] Apache Royale: Royale Ant Tasks  
  [jar]
 [exec] [INFO] Apache Royale: RoyaleUnit Ant Tasks  
  [jar]
 [exec] [INFO] Apache Royale: Royale Maven Plugin
[maven-plugin]
 [exec] [INFO]
 [exec] [INFO] -< org.apache.royale.compiler:royale-compiler-parent 
>--
 [exec] [INFO] Building Apache Royale: Compiler: Parent 0.9.8-SNAPSHOT  
 [1/12]
 [exec] [INFO] [ pom 
]-
 [exec] [INFO]
 [exec] [INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ 
royale-compiler-parent ---
 [exec] [INFO]
 [exec] [INFO] --- maven-enforcer-plugin:1.4.1:enforce 
(enforce-maven-version) @ royale-compiler-parent ---
 [exec] [INFO]
 [exec] [INFO] --- groovy-maven-plugin:2.1.1:execute (prerequisite-check) @ 
royale-compiler-parent ---
 [exec] [INFO] 

 [exec] [INFO] Reactor Summary for Apache Royale: Compiler: Parent 
0.9.8-SNAPSHOT:
 [exec] [INFO]
 [exec] [INFO] Apache Royale: Compiler: Parent  FAILURE 
[  3.938 s]
 [exec] [INFO] Apache Royale: Compiler: Compiler-Common ... SKIPPED
 [exec] [INFO] Apache Royale: Compiler: Test Utils  SKIPPED
 [exec] [INFO] Apache Royale: Compiler: Externc ... SKIPPED
 [exec] [INFO] Apache Royale: Compiler: Compiler .. SKIPPED
 [exec] [INFO] Apache Royale: Compiler: Compiler-JX ... SKIPPED
 [exec] [INFO] Apache Royale: Compiler: SWFUtils .. SKIPPED
 [exec] [INFO] Apache Royale: Compiler: Debugger .. SKIPPED
 [exec] [INFO] Apache Royale: Compiler: OEM Layer . SKIPPED
 [exec] [INFO] Apache Royale: Royale Ant Tasks  SKIPPED
 [exec] [INFO] Apache Royale: RoyaleUnit Ant Tasks  SKIPPED
 [exec] [INFO] Apache Royale: Royale Maven Plugin . SKIPPED
 [exec] [INFO] 

 [exec] [INFO] BUILD FAILURE

RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

2020-05-03 Thread Yishay Weiss

Oops, may have been premature to start the vote.

I’m getting this [1] when running ApproveRoyale.xml. Any ideas?

[1]
build_maven:
 [echo] Path is 
C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program
 Files\Intel\WiFi\bin\;C:\Prog
ram Files\Common 
Files\Intel\WirelessCommon\;C:\dev\maven\apache-maven-3.6.1\bin;C:\dev\ant\apache-ant-1.10.1\bin;C:\Program
 Files (x86)\Vim\vim82;C:\Program Fi
les\Git\cmd;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\Microsoft VS 
Code\bin;C:\Program 
Files\PuTTY\;C:\Users\Yishay\AppData\Local\Microsoft\WindowsApps;C:\U
sers\Yishay\AppData\Roaming\npm;C:\adb;C:\Users\Yishay\.windows-build-tools\python27;C:\Program
 Files\nodejs\;C:\Program Files\Java\jdk1.8.0_212\bin;C:\WINDOWS\
system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;;C:\Program
 Files (x86)\Gpg4win\..\GnuPG\b
in;C:\Program 
Files\SlikSvn\bin;C:\Users\Yishay\AppData\Local\Microsoft\WindowsApps;C:\Users\Yishay\AppData\Roaming\npm;;C:\Program
 Files (x86)\Vim\vim82
 [exec] [INFO] Scanning for projects...
 [exec] [INFO] 

 [exec] [INFO] Reactor Build Order:
 [exec] [INFO]
 [exec] [INFO] Apache Royale: Compiler: Parent  
  [pom]
 [exec] [INFO] Apache Royale: Compiler: Compiler-Common 
  [jar]
 [exec] [INFO] Apache Royale: Compiler: Test Utils  
  [jar]
 [exec] [INFO] Apache Royale: Compiler: Externc 
  [jar]
 [exec] [INFO] Apache Royale: Compiler: Compiler
  [jar]
 [exec] [INFO] Apache Royale: Compiler: Compiler-JX 
  [jar]
 [exec] [INFO] Apache Royale: Compiler: SWFUtils
  [jar]
 [exec] [INFO] Apache Royale: Compiler: Debugger
  [jar]
 [exec] [INFO] Apache Royale: Compiler: OEM Layer   
  [jar]
 [exec] [INFO] Apache Royale: Royale Ant Tasks  
  [jar]
 [exec] [INFO] Apache Royale: RoyaleUnit Ant Tasks  
  [jar]
 [exec] [INFO] Apache Royale: Royale Maven Plugin
[maven-plugin]
 [exec] [INFO]
 [exec] [INFO] -< org.apache.royale.compiler:royale-compiler-parent 
>--
 [exec] [INFO] Building Apache Royale: Compiler: Parent 0.9.8-SNAPSHOT  
 [1/12]
 [exec] [INFO] [ pom 
]-
 [exec] [INFO]
 [exec] [INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ 
royale-compiler-parent ---
 [exec] [INFO]
 [exec] [INFO] --- maven-enforcer-plugin:1.4.1:enforce 
(enforce-maven-version) @ royale-compiler-parent ---
 [exec] [INFO]
 [exec] [INFO] --- groovy-maven-plugin:2.1.1:execute (prerequisite-check) @ 
royale-compiler-parent ---
 [exec] [INFO] 

 [exec] [INFO] Reactor Summary for Apache Royale: Compiler: Parent 
0.9.8-SNAPSHOT:
 [exec] [INFO]
 [exec] [INFO] Apache Royale: Compiler: Parent  FAILURE 
[  3.938 s]
 [exec] [INFO] Apache Royale: Compiler: Compiler-Common ... SKIPPED
 [exec] [INFO] Apache Royale: Compiler: Test Utils  SKIPPED
 [exec] [INFO] Apache Royale: Compiler: Externc ... SKIPPED
 [exec] [INFO] Apache Royale: Compiler: Compiler .. SKIPPED
 [exec] [INFO] Apache Royale: Compiler: Compiler-JX ... SKIPPED
 [exec] [INFO] Apache Royale: Compiler: SWFUtils .. SKIPPED
 [exec] [INFO] Apache Royale: Compiler: Debugger .. SKIPPED
 [exec] [INFO] Apache Royale: Compiler: OEM Layer . SKIPPED
 [exec] [INFO] Apache Royale: Royale Ant Tasks  SKIPPED
 [exec] [INFO] Apache Royale: RoyaleUnit Ant Tasks  SKIPPED
 [exec] [INFO] Apache Royale: Royale Maven Plugin . SKIPPED
 [exec] [INFO] 

 [exec] [INFO] BUILD FAILURE
 [exec] [INFO] 

 [exec] [INFO] Total time:  5.067 s
 [exec] [INFO] Finished at: 2020-05-03T16:52:27+03:00
 [exec] [INFO] 

 [exec] [WARNING] The requested profile "utils" could not be activated 
because it does not exist.
 [exec] [ERROR] Failed to execute goal 
org.codehaus.gmaven:groovy-maven-plugin:2.1.1:execute (prerequisite-check) on 
project royale-compiler-parent: Executi
on prerequisite-check of goal

97 matches

Mail list logo