RE: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Yishay Weiss]

Maybe this [1] can help?



[1] 
http://apache-flex-development.247.n4.nabble.com/FlexJS-Unit-Tests-Not-Running-td62371.html#a62380




From: Piotr Zarzycki 
Sent: Thursday, November 22, 2018 12:23:14 PM
To: dev@royale.apache.org
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

Hi Alex,

Fortunately I have sources, so I tried and in the logs you can see what
version of SWC I'm using. [1]

[1] https://paste.apache.org/1I3p

Piotr


wt., 20 lis 2018 o 20:18 Alex Harui  napisał(a):

> Piotr,
>
> I just pushed changes to royale-asjs develop branch to be explicit about
> which FlexUnit swcs get used (instead of relying on timestamps in the
> SWCs).  If you still have the source package for 0.9.4 and can overlay the
> four build.xml files onto your source package and see if the build runs to
> completion then we will know whether it is more likely it will work for you
> in the next release or whether there is still some other issue.
>
> The four files are:
> frameworks/projects/Basic/src/test/royale/build.xml
> frameworks/projects/Core/src/test/royale/build.xml
> frameworks/projects/HTML/src/test/royale/build.xml
> frameworks/projects/Testing/src/test/royale/build.xml
>
> Note that it is the src/test/ path, not src/main
>
> Thanks,
> -Alex
>
> On 11/16/18, 11:33 AM, "Piotr Zarzycki" 
> wrote:
>
> Sources where downloaded by ApprovalScript.
>
> Ok in the other words I'm ok with that failing example.
>
> I just need to get to the stage where FlexUnit tests are working. I'm
> wondering is there any chance to run only part which are failing for
> me?
> Trying everything from scratch is a time consuming.
>
> Piotr
>
> On Fri, Nov 16, 2018, 8:13 PM Alex Harui 
> wrote:
>
> > Hi Piotr,
> >
> > If you build one of the Royale examples, like
> > examples/royale/DataBindingExample, the POM tries to use artifacts
> from
> > examples-tests.  If you are building your own app, your POM probably
> > doesn't care about examples-tests.
> >
> > Where did you download sources from?
> >
> > When the artifacts are only on the staging server, and not in your
> local
> > repo (by building the entire source package which by default does not
> > include examples), then I think you have to redirect your poms to the
> > staging server.  See:
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmaven.apache.org%2Fguides%2Fdevelopment%2Fguide-testing-releases.htmldata=02%7C01%7Caharui%40adobe.com%7Cc8e6e5458886453f685608d64bfa7006%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779936326108233sdata=eky3JTT4tMT%2FQ4QHL2XdoyFBDyyvcG%2BL1biq0%2FF79iI%3Dreserved=0
> >
> > IMO, if you plan to be an RM, you should not be satisfied with a +0
> vote
> > because things are not working for you.  Otherwise, you are just
> setting
> > yourself up for others to be in the same situation and when you are
> the RM,
> > you will get a bunch of +0 votes.
> >
> > Thanks,
> > -Alex
> >
> > On 11/16/18, 10:53 AM, "Piotr Zarzycki" 
> > wrote:
> >
> > Hi Alex,
> >
> > Once my build failed with that timeout I went to downloaded
> sources
> > directly in order to run Maven build and see whether it's
> working. I
> > was
> > able to build it - with similar issue as other with airglobal. -
> I have
> > manually add that part to my Maven cache.
> >
> > Part 2 of the test was simply build example using your staged
> > artifacts -
> > It doesn't connected whether I build examples/examples-tests or
> not -
> > Am I
> > wrong? Let's imagine that I have clean machine, created Royale
> project
> > -
> > I'm trying to build my project with Maven and your artifacts -
> Do I
> > need
> > that org.apache.royale.examples:examples-tests:jar ?
> >
> > If answer is NO - That's ok - it is an requirements for build our
> > example
> > and I can vote +0.
> >
> > *Please verify that FlexUnit is working in your repo and then
> compare
> > the
> > FlexUnit jars it is using against the ones that the RC
> downloaded.  Or
> > investigate the difference between the SWFs generated by the repo
> > build vs
> > the RC build.  If we don't figure out why things fail, then we
> are
> > doomed
> >

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[piotrz]

Hi Alex,

I don't have enough time to check and answer to all of your questions. I
will do this during/after the weekend. However I did quick check with Flash
Player and opening FlexUnitRoyaleApplication.swf. I couldn't do that - I was
getting an error.


 

I went to the system settings and wanted to associate Flash Player and I
couldn't!  Even if I choose nothing happened and selection was cleared.

 

I will investigate this farther. Maybe the reason is that my
FLASHPLAYER_DEBUGGER=D:\Work\player\flashplayer.exe is on a separate
partition. 

Thanks,
Piotr



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Alex Harui]

Hi Piotr,

Does the Flash Player Debugger window show up?  Try going to File Explorer and 
double-clicking on the FlexUnitRoyaleApplication.swf.  And see if you can 
figure out what version of Flash Player Debugger you are running.

Have you rebooted your system?  Maybe something is using port 1024 already.

When you build from the repo, are the ports used and the rundll32 command the 
same?

Post the SWF so we can download it and try running it on our computers.

Thanks,
-Alex

On 11/22/18, 2:23 AM, "Piotr Zarzycki"  wrote:

Hi Alex,

Fortunately I have sources, so I tried and in the logs you can see what
version of SWC I'm using. [1]

[1] 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F1I3pdata=02%7C01%7Caharui%40adobe.com%7C72ea531238bf412221bf08d6506492d3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636784790224854058sdata=UfR0MbD%2FVay9BccUjbycJEA4ihFJ7qBqRgtffP6i%2Ff4%3Dreserved=0

Piotr


wt., 20 lis 2018 o 20:18 Alex Harui  napisał(a):

> Piotr,
>
> I just pushed changes to royale-asjs develop branch to be explicit about
> which FlexUnit swcs get used (instead of relying on timestamps in the
> SWCs).  If you still have the source package for 0.9.4 and can overlay the
> four build.xml files onto your source package and see if the build runs to
> completion then we will know whether it is more likely it will work for 
you
> in the next release or whether there is still some other issue.
>
> The four files are:
> frameworks/projects/Basic/src/test/royale/build.xml
> frameworks/projects/Core/src/test/royale/build.xml
> frameworks/projects/HTML/src/test/royale/build.xml
> frameworks/projects/Testing/src/test/royale/build.xml
>
> Note that it is the src/test/ path, not src/main
>
> Thanks,
> -Alex
>
> On 11/16/18, 11:33 AM, "Piotr Zarzycki" 
> wrote:
>
> Sources where downloaded by ApprovalScript.
>
> Ok in the other words I'm ok with that failing example.
>
> I just need to get to the stage where FlexUnit tests are working. I'm
> wondering is there any chance to run only part which are failing for
> me?
> Trying everything from scratch is a time consuming.
>
> Piotr
>
> On Fri, Nov 16, 2018, 8:13 PM Alex Harui 
> wrote:
>
> > Hi Piotr,
> >
> > If you build one of the Royale examples, like
> > examples/royale/DataBindingExample, the POM tries to use artifacts
> from
> > examples-tests.  If you are building your own app, your POM probably
> > doesn't care about examples-tests.
> >
> > Where did you download sources from?
> >
> > When the artifacts are only on the staging server, and not in your
> local
> > repo (by building the entire source package which by default does 
not
> > include examples), then I think you have to redirect your poms to 
the
> > staging server.  See:
> >
> 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmaven.apache.org%2Fguides%2Fdevelopment%2Fguide-testing-releases.htmldata=02%7C01%7Caharui%40adobe.com%7C72ea531238bf412221bf08d6506492d3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636784790224854058sdata=xT9c7e8vLq18Al0SPZCSndwFsPcT3QcNxYSWtJWt41o%3Dreserved=0
> >
> > IMO, if you plan to be an RM, you should not be satisfied with a +0
> vote
> > because things are not working for you.  Otherwise, you are just
> setting
> > yourself up for others to be in the same situation and when you are
> the RM,
> > you will get a bunch of +0 votes.
> >
> > Thanks,
> > -Alex
> >
> > On 11/16/18, 10:53 AM, "Piotr Zarzycki" 
> > wrote:
> >
> > Hi Alex,
> >
> > Once my build failed with that timeout I went to downloaded
> sources
> > directly in order to run Maven build and see whether it's
> working. I
> > was
> > able to build it - with similar issue as other with airglobal. -
> I have
> > manually add that part to my Maven cache.
> >
> > Part 2 of the test was simply build example using your staged
> > artifacts -
> > It doesn't connected whether I build examples/examples-tests or
> not -
> > Am I
> > wrong? Let's imagine that I have clean machine, created Royale
> project
> > -
> > I'm trying to build my project with Maven and your artifacts -
> Do I
> > need
> > that org.apache.royale.examples:examples-tests:jar ?
> >
> > If answer is NO - That's ok - it is an requirements for build 
our
> > example
> > and I can vote +0.
> >
> > 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Piotr Zarzycki]

Hi Alex,

Fortunately I have sources, so I tried and in the logs you can see what
version of SWC I'm using. [1]

[1] https://paste.apache.org/1I3p

Piotr


wt., 20 lis 2018 o 20:18 Alex Harui  napisał(a):

> Piotr,
>
> I just pushed changes to royale-asjs develop branch to be explicit about
> which FlexUnit swcs get used (instead of relying on timestamps in the
> SWCs).  If you still have the source package for 0.9.4 and can overlay the
> four build.xml files onto your source package and see if the build runs to
> completion then we will know whether it is more likely it will work for you
> in the next release or whether there is still some other issue.
>
> The four files are:
> frameworks/projects/Basic/src/test/royale/build.xml
> frameworks/projects/Core/src/test/royale/build.xml
> frameworks/projects/HTML/src/test/royale/build.xml
> frameworks/projects/Testing/src/test/royale/build.xml
>
> Note that it is the src/test/ path, not src/main
>
> Thanks,
> -Alex
>
> On 11/16/18, 11:33 AM, "Piotr Zarzycki" 
> wrote:
>
> Sources where downloaded by ApprovalScript.
>
> Ok in the other words I'm ok with that failing example.
>
> I just need to get to the stage where FlexUnit tests are working. I'm
> wondering is there any chance to run only part which are failing for
> me?
> Trying everything from scratch is a time consuming.
>
> Piotr
>
> On Fri, Nov 16, 2018, 8:13 PM Alex Harui 
> wrote:
>
> > Hi Piotr,
> >
> > If you build one of the Royale examples, like
> > examples/royale/DataBindingExample, the POM tries to use artifacts
> from
> > examples-tests.  If you are building your own app, your POM probably
> > doesn't care about examples-tests.
> >
> > Where did you download sources from?
> >
> > When the artifacts are only on the staging server, and not in your
> local
> > repo (by building the entire source package which by default does not
> > include examples), then I think you have to redirect your poms to the
> > staging server.  See:
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmaven.apache.org%2Fguides%2Fdevelopment%2Fguide-testing-releases.htmldata=02%7C01%7Caharui%40adobe.com%7Cc8e6e5458886453f685608d64bfa7006%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779936326108233sdata=eky3JTT4tMT%2FQ4QHL2XdoyFBDyyvcG%2BL1biq0%2FF79iI%3Dreserved=0
> >
> > IMO, if you plan to be an RM, you should not be satisfied with a +0
> vote
> > because things are not working for you.  Otherwise, you are just
> setting
> > yourself up for others to be in the same situation and when you are
> the RM,
> > you will get a bunch of +0 votes.
> >
> > Thanks,
> > -Alex
> >
> > On 11/16/18, 10:53 AM, "Piotr Zarzycki" 
> > wrote:
> >
> > Hi Alex,
> >
> > Once my build failed with that timeout I went to downloaded
> sources
> > directly in order to run Maven build and see whether it's
> working. I
> > was
> > able to build it - with similar issue as other with airglobal. -
> I have
> > manually add that part to my Maven cache.
> >
> > Part 2 of the test was simply build example using your staged
> > artifacts -
> > It doesn't connected whether I build examples/examples-tests or
> not -
> > Am I
> > wrong? Let's imagine that I have clean machine, created Royale
> project
> > -
> > I'm trying to build my project with Maven and your artifacts -
> Do I
> > need
> > that org.apache.royale.examples:examples-tests:jar ?
> >
> > If answer is NO - That's ok - it is an requirements for build our
> > example
> > and I can vote +0.
> >
> > *Please verify that FlexUnit is working in your repo and then
> compare
> > the
> > FlexUnit jars it is using against the ones that the RC
> downloaded.  Or
> > investigate the difference between the SWFs generated by the repo
> > build vs
> > the RC build.  If we don't figure out why things fail, then we
> are
> > doomed
> > to keep hitting these failure points.  *
> >
> > Above part requires from me a lot of time probably - If I found
> it
> > before
> > to be next RM I will do this for sure.
> >
> > Piotr
> >
> > pt., 16 lis 2018 o 19:10 Alex Harui 
> > napisał(a):
> >
> > > Piotr,
> > >
> > > Did you build the examples/examples-tests folder first?
> > >
> > > If you used the ApproveRoyale script then it would have done
> all of
> > that
> > > for you.  If you plan to be an RM, it is worth your time to
> find out
> > why
> > > the approval script is not working for you, as it is expected
> that
> > the RM
> > > has run the approval script before posting the vote threads in
> order
> > to
> > > save everyone time.
> >

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Carlos Rovira]

Hi Alex,

maybe this was that what affect some of us when trying to generate a local
SDK.
I think I put a line to remove the flex version of flex unit that was
giving us trouble, I can try to remove the line and see if now all work ok,
hopefully tomorrow when rebuild all
thanks

El mar., 20 nov. 2018 a las 20:18, Alex Harui ()
escribió:

> Piotr,
>
> I just pushed changes to royale-asjs develop branch to be explicit about
> which FlexUnit swcs get used (instead of relying on timestamps in the
> SWCs).  If you still have the source package for 0.9.4 and can overlay the
> four build.xml files onto your source package and see if the build runs to
> completion then we will know whether it is more likely it will work for you
> in the next release or whether there is still some other issue.
>
> The four files are:
> frameworks/projects/Basic/src/test/royale/build.xml
> frameworks/projects/Core/src/test/royale/build.xml
> frameworks/projects/HTML/src/test/royale/build.xml
> frameworks/projects/Testing/src/test/royale/build.xml
>
> Note that it is the src/test/ path, not src/main
>
> Thanks,
> -Alex
>
> On 11/16/18, 11:33 AM, "Piotr Zarzycki" 
> wrote:
>
> Sources where downloaded by ApprovalScript.
>
> Ok in the other words I'm ok with that failing example.
>
> I just need to get to the stage where FlexUnit tests are working. I'm
> wondering is there any chance to run only part which are failing for
> me?
> Trying everything from scratch is a time consuming.
>
> Piotr
>
> On Fri, Nov 16, 2018, 8:13 PM Alex Harui 
> wrote:
>
> > Hi Piotr,
> >
> > If you build one of the Royale examples, like
> > examples/royale/DataBindingExample, the POM tries to use artifacts
> from
> > examples-tests.  If you are building your own app, your POM probably
> > doesn't care about examples-tests.
> >
> > Where did you download sources from?
> >
> > When the artifacts are only on the staging server, and not in your
> local
> > repo (by building the entire source package which by default does not
> > include examples), then I think you have to redirect your poms to the
> > staging server.  See:
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmaven.apache.org%2Fguides%2Fdevelopment%2Fguide-testing-releases.htmldata=02%7C01%7Caharui%40adobe.com%7Cc8e6e5458886453f685608d64bfa7006%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779936326108233sdata=eky3JTT4tMT%2FQ4QHL2XdoyFBDyyvcG%2BL1biq0%2FF79iI%3Dreserved=0
> >
> > IMO, if you plan to be an RM, you should not be satisfied with a +0
> vote
> > because things are not working for you.  Otherwise, you are just
> setting
> > yourself up for others to be in the same situation and when you are
> the RM,
> > you will get a bunch of +0 votes.
> >
> > Thanks,
> > -Alex
> >
> > On 11/16/18, 10:53 AM, "Piotr Zarzycki" 
> > wrote:
> >
> > Hi Alex,
> >
> > Once my build failed with that timeout I went to downloaded
> sources
> > directly in order to run Maven build and see whether it's
> working. I
> > was
> > able to build it - with similar issue as other with airglobal. -
> I have
> > manually add that part to my Maven cache.
> >
> > Part 2 of the test was simply build example using your staged
> > artifacts -
> > It doesn't connected whether I build examples/examples-tests or
> not -
> > Am I
> > wrong? Let's imagine that I have clean machine, created Royale
> project
> > -
> > I'm trying to build my project with Maven and your artifacts -
> Do I
> > need
> > that org.apache.royale.examples:examples-tests:jar ?
> >
> > If answer is NO - That's ok - it is an requirements for build our
> > example
> > and I can vote +0.
> >
> > *Please verify that FlexUnit is working in your repo and then
> compare
> > the
> > FlexUnit jars it is using against the ones that the RC
> downloaded.  Or
> > investigate the difference between the SWFs generated by the repo
> > build vs
> > the RC build.  If we don't figure out why things fail, then we
> are
> > doomed
> > to keep hitting these failure points.  *
> >
> > Above part requires from me a lot of time probably - If I found
> it
> > before
> > to be next RM I will do this for sure.
> >
> > Piotr
> >
> > pt., 16 lis 2018 o 19:10 Alex Harui 
> > napisał(a):
> >
> > > Piotr,
> > >
> > > Did you build the examples/examples-tests folder first?
> > >
> > > If you used the ApproveRoyale script then it would have done
> all of
> > that
> > > for you.  If you plan to be an RM, it is worth your time to
> find out
> > why
> > > the approval script is not working for you, as it is expected
> that
> > the RM
> 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Alex Harui]

Piotr,

I just pushed changes to royale-asjs develop branch to be explicit about which 
FlexUnit swcs get used (instead of relying on timestamps in the SWCs).  If you 
still have the source package for 0.9.4 and can overlay the four build.xml 
files onto your source package and see if the build runs to completion then we 
will know whether it is more likely it will work for you in the next release or 
whether there is still some other issue.

The four files are:
frameworks/projects/Basic/src/test/royale/build.xml
frameworks/projects/Core/src/test/royale/build.xml
frameworks/projects/HTML/src/test/royale/build.xml
frameworks/projects/Testing/src/test/royale/build.xml

Note that it is the src/test/ path, not src/main

Thanks,
-Alex

On 11/16/18, 11:33 AM, "Piotr Zarzycki"  wrote:

Sources where downloaded by ApprovalScript.

Ok in the other words I'm ok with that failing example.

I just need to get to the stage where FlexUnit tests are working. I'm
wondering is there any chance to run only part which are failing for me?
Trying everything from scratch is a time consuming.

Piotr

On Fri, Nov 16, 2018, 8:13 PM Alex Harui  wrote:

> Hi Piotr,
>
> If you build one of the Royale examples, like
> examples/royale/DataBindingExample, the POM tries to use artifacts from
> examples-tests.  If you are building your own app, your POM probably
> doesn't care about examples-tests.
>
> Where did you download sources from?
>
> When the artifacts are only on the staging server, and not in your local
> repo (by building the entire source package which by default does not
> include examples), then I think you have to redirect your poms to the
> staging server.  See:
> 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmaven.apache.org%2Fguides%2Fdevelopment%2Fguide-testing-releases.htmldata=02%7C01%7Caharui%40adobe.com%7Cc8e6e5458886453f685608d64bfa7006%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779936326108233sdata=eky3JTT4tMT%2FQ4QHL2XdoyFBDyyvcG%2BL1biq0%2FF79iI%3Dreserved=0
>
> IMO, if you plan to be an RM, you should not be satisfied with a +0 vote
> because things are not working for you.  Otherwise, you are just setting
> yourself up for others to be in the same situation and when you are the 
RM,
> you will get a bunch of +0 votes.
>
> Thanks,
> -Alex
>
> On 11/16/18, 10:53 AM, "Piotr Zarzycki" 
> wrote:
>
> Hi Alex,
>
> Once my build failed with that timeout I went to downloaded sources
> directly in order to run Maven build and see whether it's working. I
> was
> able to build it - with similar issue as other with airglobal. - I 
have
> manually add that part to my Maven cache.
>
> Part 2 of the test was simply build example using your staged
> artifacts -
> It doesn't connected whether I build examples/examples-tests or not -
> Am I
> wrong? Let's imagine that I have clean machine, created Royale project
> -
> I'm trying to build my project with Maven and your artifacts - Do I
> need
> that org.apache.royale.examples:examples-tests:jar ?
>
> If answer is NO - That's ok - it is an requirements for build our
> example
> and I can vote +0.
>
> *Please verify that FlexUnit is working in your repo and then compare
> the
> FlexUnit jars it is using against the ones that the RC downloaded.  Or
> investigate the difference between the SWFs generated by the repo
> build vs
> the RC build.  If we don't figure out why things fail, then we are
> doomed
> to keep hitting these failure points.  *
>
> Above part requires from me a lot of time probably - If I found it
> before
> to be next RM I will do this for sure.
>
> Piotr
>
> pt., 16 lis 2018 o 19:10 Alex Harui 
> napisał(a):
>
> > Piotr,
> >
> > Did you build the examples/examples-tests folder first?
> >
> > If you used the ApproveRoyale script then it would have done all of
> that
> > for you.  If you plan to be an RM, it is worth your time to find out
> why
> > the approval script is not working for you, as it is expected that
> the RM
> > has run the approval script before posting the vote threads in order
> to
> > save everyone time.
> >
> > Please verify that FlexUnit is working in your repo and then compare
> the
> > FlexUnit jars it is using against the ones that the RC downloaded.
> Or
> > investigate the difference between the SWFs generated by the repo
> build vs
> > the RC build.  If we don't figure out why things fail, then we are
> doomed
> > to keep hitting these failure points.
> >
> > 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Olaf Krueger]

> In PowerShell, you need to wrap arguments that contain the . character with
quotes: 

Yees, it is running now, Thanks Josh!!

Olaf



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Josh Tynjala]

In PowerShell, you need to wrap arguments that contain the . character with 
quotes:

ant -e -f ApproveRoyale.xml "-Drelease.version=0.9.4" -Drc=2

- Josh

On 2018/11/16 22:49:44, Olaf Krueger  wrote: 
> Hi, 
> I run the approval script, but it fails immediately [1]. 
> Do I miss something? 
> (I am using ant 1.10.1) 
> 
> Thanks, 
> Olaf 
> 
> [1] 
> PS C:\local\apache-royale\vote_0_9_4_RC2> ant -e -f ApproveRoyale.xml 
> -Drelease.version=0.9.4 -Drc=2 
> Buildfile: C:\local\apache-royale\vote_0_9_4_RC2\ApproveRoyale.xml 
> 
> BUILD FAILED 
> C:\local\apache-royale\vote_0_9_4_RC2\ApproveRoyale.xml:121: The release 
> version is not set.  Specify -Drelease.version= 3.2, etc)> 
> 
> Total time: 0 seconds 
> 
> 
> 
> --
> Sent from: http://apache-royale-development.20373.n8.nabble.com/
> 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Olaf Krueger]

Hi, 
I run the approval script, but it fails immediately [1]. 
Do I miss something? 
(I am using ant 1.10.1) 

Thanks, 
Olaf 

[1] 
PS C:\local\apache-royale\vote_0_9_4_RC2> ant -e -f ApproveRoyale.xml 
-Drelease.version=0.9.4 -Drc=2 
Buildfile: C:\local\apache-royale\vote_0_9_4_RC2\ApproveRoyale.xml 

BUILD FAILED 
C:\local\apache-royale\vote_0_9_4_RC2\ApproveRoyale.xml:121: The release 
version is not set.  Specify -Drelease.version= 

Total time: 0 seconds 



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[OmPrakash Muppirala]

Hahaha you set traps to catch lazy ppl.  Although in my defense I checked
everything the first time, but the build failed after that.  The second I
kept hitting enter without reading.  TIL.

Thanks,
Om

On Fri, Nov 16, 2018 at 11:41 AM Alex Harui 
wrote:

> The default answer for some of the rat checks is "n".  So that means you
> can't just hit "Enter" all the way through the script.  I had a good reason
> for doing that, but I can't remember why.  Maybe it was just to make sure
> people were actually looking at the output instead of just hitting Enter.
>
> -Alex
>
> On 11/16/18, 11:29 AM, "OmPrakash Muppirala" 
> wrote:
>
> Hmm interesting.  I am getting this output from the approval script:
>
> approve:
>
>
> -1
>
> Package
>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc2%2Fapache-royale-0.9.4-src.tar.gzdata=02%7C01%7Caharui%40adobe.com%7C8c3cb407a16444958a6608d64bf9caa6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779933553764185sdata=Tthv90BnjMScTq%2BhUibnA6jkwG4lixaZMcljf1XFFRA%3Dreserved=0
>
> Java 1.8
>
> OS: Mac OS X x86_64 10.13.6
>
> Source kit signatures match: y
>
> Source kit builds: y
>
> README is ok: y
>
> RELEASE_NOTES is ok: y
>
> NOTICE is ok: y
>
> LICENSE is ok: y
>
> No unapproved licenses or archives: y
>
> No unapproved binaries: n
>
>
> Package
>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc2%2Fbinaries%2Fapache-royale-0.9.4-bin-js-swf.tar.gzdata=02%7C01%7Caharui%40adobe.com%7C8c3cb407a16444958a6608d64bf9caa6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779933553764185sdata=tFHKiRf0Q9O1pljLLcak7fweZmV1C%2BZ3n0eEgmtd9R4%3Dreserved=0
>
> Binary kit signatures match: y
>
> NOTICE is ok: y
>
> LICENSE is ok: y
>
> No unapproved licenses or archives in binary package: y
>
> No unapproved binaries in binary package: n
>
>
>
>
> BUILD FAILED
>
> /Users/om/p/os/royale/rc/ApproveRoyale.xml:1103: condition satisfied
>
>
> Looking at the rat report, I do see these files marked as B which
> might be
> causing this?
>
>   B
>
> /Users/om/p/os/royale/rc/apache-royale-0.9.4-bin-js-swf/royale-asjs/examples/mxroyale/tourdeflexmodules/src/favicon.ico
>
>   B
>
> /Users/om/p/os/royale/rc/apache-royale-0.9.4-bin-js-swf/royale-asjs/examples/mxroyale/tourdeflexmodules/src/mx/controls/assets/flexinstaller.mp4
>
>   B
>
> /Users/om/p/os/royale/rc/apache-royale-0.9.4-bin-js-swf/royale-asjs/examples/mxroyale/tourdeflexmodules/src/mx/effects/assets/OpenSans-Regular.ttf
>
>   B
>
> /Users/om/p/os/royale/rc/apache-royale-0.9.4-bin-js-swf/royale-asjs/examples/mxroyale/tourdeflexmodules/src/spark/components/assets/FlexInstaller.mp4
>
>   B
>
> /Users/om/p/os/royale/rc/apache-royale-0.9.4-bin-js-swf/royale-asjs/examples/mxroyale/tourdeflexmodules/src/spark/controls/assets/FlexInstaller.mp4
>
>   B
>
> /Users/om/p/os/royale/rc/apache-royale-0.9.4-bin-js-swf/royale-asjs/examples/mxroyale/tourdeflexmodules/src/spark/tlf/textEditBar/assets/icon_align_end.PNG
>
>   B
>
> /Users/om/p/os/royale/rc/apache-royale-0.9.4-bin-js-swf/royale-asjs/examples/mxroyale/tourdeflexmodules/src/spark/tlf/textEditBar/assets/icon_align_start.PNG
>
> On Fri, Nov 16, 2018 at 11:13 AM Alex Harui 
> wrote:
>
> > Hi Piotr,
> >
> > If you build one of the Royale examples, like
> > examples/royale/DataBindingExample, the POM tries to use artifacts
> from
> > examples-tests.  If you are building your own app, your POM probably
> > doesn't care about examples-tests.
> >
> > Where did you download sources from?
> >
> > When the artifacts are only on the staging server, and not in your
> local
> > repo (by building the entire source package which by default does not
> > include examples), then I think you have to redirect your poms to the
> > staging server.  See:
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmaven.apache.org%2Fguides%2Fdevelopment%2Fguide-testing-releases.htmldata=02%7C01%7Caharui%40adobe.com%7C8c3cb407a16444958a6608d64bf9caa6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779933553764185sdata=Xu12pHIo1Wk%2B5EolVMSK%2BOgTlkueYL68XbVqBKH0lx4%3Dreserved=0
> >
> > IMO, if you plan to be an RM, you should not be satisfied with a +0
> vote
> > because things are not working for you.  Otherwise, you are just
> setting
> > yourself up for others to be in the same situation and when you are
> the RM,
> > you will get a bunch of +0 votes.
> >
> > Thanks,
> > -Alex
> >
> > On 11/16/18, 10:53 AM, "Piotr Zarzycki" 
> > wrote:
> >
> > Hi Alex,
> >
> > Once my build failed with that timeout I went to downloaded
> sources
> > directly in order to run Maven build and see whether it's
> working. I

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Alex Harui]

The default answer for some of the rat checks is "n".  So that means you can't 
just hit "Enter" all the way through the script.  I had a good reason for doing 
that, but I can't remember why.  Maybe it was just to make sure people were 
actually looking at the output instead of just hitting Enter.

-Alex

On 11/16/18, 11:29 AM, "OmPrakash Muppirala"  wrote:

Hmm interesting.  I am getting this output from the approval script:

approve:


-1

Package

https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc2%2Fapache-royale-0.9.4-src.tar.gzdata=02%7C01%7Caharui%40adobe.com%7C8c3cb407a16444958a6608d64bf9caa6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779933553764185sdata=Tthv90BnjMScTq%2BhUibnA6jkwG4lixaZMcljf1XFFRA%3Dreserved=0

Java 1.8

OS: Mac OS X x86_64 10.13.6

Source kit signatures match: y

Source kit builds: y

README is ok: y

RELEASE_NOTES is ok: y

NOTICE is ok: y

LICENSE is ok: y

No unapproved licenses or archives: y

No unapproved binaries: n


Package

https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc2%2Fbinaries%2Fapache-royale-0.9.4-bin-js-swf.tar.gzdata=02%7C01%7Caharui%40adobe.com%7C8c3cb407a16444958a6608d64bf9caa6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779933553764185sdata=tFHKiRf0Q9O1pljLLcak7fweZmV1C%2BZ3n0eEgmtd9R4%3Dreserved=0

Binary kit signatures match: y

NOTICE is ok: y

LICENSE is ok: y

No unapproved licenses or archives in binary package: y

No unapproved binaries in binary package: n




BUILD FAILED

/Users/om/p/os/royale/rc/ApproveRoyale.xml:1103: condition satisfied


Looking at the rat report, I do see these files marked as B which might be
causing this?

  B

/Users/om/p/os/royale/rc/apache-royale-0.9.4-bin-js-swf/royale-asjs/examples/mxroyale/tourdeflexmodules/src/favicon.ico

  B

/Users/om/p/os/royale/rc/apache-royale-0.9.4-bin-js-swf/royale-asjs/examples/mxroyale/tourdeflexmodules/src/mx/controls/assets/flexinstaller.mp4

  B

/Users/om/p/os/royale/rc/apache-royale-0.9.4-bin-js-swf/royale-asjs/examples/mxroyale/tourdeflexmodules/src/mx/effects/assets/OpenSans-Regular.ttf

  B

/Users/om/p/os/royale/rc/apache-royale-0.9.4-bin-js-swf/royale-asjs/examples/mxroyale/tourdeflexmodules/src/spark/components/assets/FlexInstaller.mp4

  B

/Users/om/p/os/royale/rc/apache-royale-0.9.4-bin-js-swf/royale-asjs/examples/mxroyale/tourdeflexmodules/src/spark/controls/assets/FlexInstaller.mp4

  B

/Users/om/p/os/royale/rc/apache-royale-0.9.4-bin-js-swf/royale-asjs/examples/mxroyale/tourdeflexmodules/src/spark/tlf/textEditBar/assets/icon_align_end.PNG

  B

/Users/om/p/os/royale/rc/apache-royale-0.9.4-bin-js-swf/royale-asjs/examples/mxroyale/tourdeflexmodules/src/spark/tlf/textEditBar/assets/icon_align_start.PNG

On Fri, Nov 16, 2018 at 11:13 AM Alex Harui 
wrote:

> Hi Piotr,
>
> If you build one of the Royale examples, like
> examples/royale/DataBindingExample, the POM tries to use artifacts from
> examples-tests.  If you are building your own app, your POM probably
> doesn't care about examples-tests.
>
> Where did you download sources from?
>
> When the artifacts are only on the staging server, and not in your local
> repo (by building the entire source package which by default does not
> include examples), then I think you have to redirect your poms to the
> staging server.  See:
> 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmaven.apache.org%2Fguides%2Fdevelopment%2Fguide-testing-releases.htmldata=02%7C01%7Caharui%40adobe.com%7C8c3cb407a16444958a6608d64bf9caa6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779933553764185sdata=Xu12pHIo1Wk%2B5EolVMSK%2BOgTlkueYL68XbVqBKH0lx4%3Dreserved=0
>
> IMO, if you plan to be an RM, you should not be satisfied with a +0 vote
> because things are not working for you.  Otherwise, you are just setting
> yourself up for others to be in the same situation and when you are the 
RM,
> you will get a bunch of +0 votes.
>
> Thanks,
> -Alex
>
> On 11/16/18, 10:53 AM, "Piotr Zarzycki" 
> wrote:
>
> Hi Alex,
>
> Once my build failed with that timeout I went to downloaded sources
> directly in order to run Maven build and see whether it's working. I
> was
> able to build it - with similar issue as other with airglobal. - I 
have
> manually add that part to my Maven cache.
>
> Part 2 of the test was simply build example using your staged
> artifacts -
> It doesn't connected whether I build 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Alex Harui]

In theory, the SWF it compiled should still be in a folder.  Plus you should be 
able to change current directory to that folder and run Ant in that folder.

-Alex

On 11/16/18, 11:33 AM, "Piotr Zarzycki"  wrote:

Sources where downloaded by ApprovalScript.

Ok in the other words I'm ok with that failing example.

I just need to get to the stage where FlexUnit tests are working. I'm
wondering is there any chance to run only part which are failing for me?
Trying everything from scratch is a time consuming.

Piotr

On Fri, Nov 16, 2018, 8:13 PM Alex Harui  wrote:

> Hi Piotr,
>
> If you build one of the Royale examples, like
> examples/royale/DataBindingExample, the POM tries to use artifacts from
> examples-tests.  If you are building your own app, your POM probably
> doesn't care about examples-tests.
>
> Where did you download sources from?
>
> When the artifacts are only on the staging server, and not in your local
> repo (by building the entire source package which by default does not
> include examples), then I think you have to redirect your poms to the
> staging server.  See:
> 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmaven.apache.org%2Fguides%2Fdevelopment%2Fguide-testing-releases.htmldata=02%7C01%7Caharui%40adobe.com%7Cc8e6e5458886453f685608d64bfa7006%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779936326108233sdata=eky3JTT4tMT%2FQ4QHL2XdoyFBDyyvcG%2BL1biq0%2FF79iI%3Dreserved=0
>
> IMO, if you plan to be an RM, you should not be satisfied with a +0 vote
> because things are not working for you.  Otherwise, you are just setting
> yourself up for others to be in the same situation and when you are the 
RM,
> you will get a bunch of +0 votes.
>
> Thanks,
> -Alex
>
> On 11/16/18, 10:53 AM, "Piotr Zarzycki" 
> wrote:
>
> Hi Alex,
>
> Once my build failed with that timeout I went to downloaded sources
> directly in order to run Maven build and see whether it's working. I
> was
> able to build it - with similar issue as other with airglobal. - I 
have
> manually add that part to my Maven cache.
>
> Part 2 of the test was simply build example using your staged
> artifacts -
> It doesn't connected whether I build examples/examples-tests or not -
> Am I
> wrong? Let's imagine that I have clean machine, created Royale project
> -
> I'm trying to build my project with Maven and your artifacts - Do I
> need
> that org.apache.royale.examples:examples-tests:jar ?
>
> If answer is NO - That's ok - it is an requirements for build our
> example
> and I can vote +0.
>
> *Please verify that FlexUnit is working in your repo and then compare
> the
> FlexUnit jars it is using against the ones that the RC downloaded.  Or
> investigate the difference between the SWFs generated by the repo
> build vs
> the RC build.  If we don't figure out why things fail, then we are
> doomed
> to keep hitting these failure points.  *
>
> Above part requires from me a lot of time probably - If I found it
> before
> to be next RM I will do this for sure.
>
> Piotr
>
> pt., 16 lis 2018 o 19:10 Alex Harui 
> napisał(a):
>
> > Piotr,
> >
> > Did you build the examples/examples-tests folder first?
> >
> > If you used the ApproveRoyale script then it would have done all of
> that
> > for you.  If you plan to be an RM, it is worth your time to find out
> why
> > the approval script is not working for you, as it is expected that
> the RM
> > has run the approval script before posting the vote threads in order
> to
> > save everyone time.
> >
> > Please verify that FlexUnit is working in your repo and then compare
> the
> > FlexUnit jars it is using against the ones that the RC downloaded.
> Or
> > investigate the difference between the SWFs generated by the repo
> build vs
> > the RC build.  If we don't figure out why things fail, then we are
> doomed
> > to keep hitting these failure points.
> >
> > Thanks,
> > -Alex
> >
> > On 11/16/18, 4:47 AM, "Piotr Zarzycki" 
> wrote:
> >
> > Here is the steps:
> >
> > 1) You are preparing Maven settings file which pointing to 
staged
> > artifacts
> > [1]
> > 2) Pickup one of the example and for simplicity place there
> prepared
> > file
> > 3) Build example with following command:  mvn -s
> settings-template.xml
> > clean install
> >
> > [1]
> >
> 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Dave Fisher]

Hi - 

All is good. I made some edits to the page to be more specific that this is a 
Maven issue. If they cannot find airglobal.swc then I suggest either switching 
to Ant or downloading Adobe Air.

Regards,
Dave

> On Nov 16, 2018, at 10:55 AM, Dave Fisher  wrote:
> 
> Something unique to my id. I missed a step in the past on gitbox setup.
> 
> I’ll see soon about it.
> 
>> On Nov 16, 2018, at 10:45 AM, Alex Harui  wrote:
>> 
>> Hmm.  Have you been active on Royale's GitHub before?  I wonder if there is 
>> a per-project permission we have to provide, or if you have to go through 
>> some sync up via GitBox per project.
>> 
>> -Alex
>> 
>> On 11/16/18, 10:28 AM, "Dave Fisher"  wrote:
>> 
>> 
>> 
>>> On Nov 16, 2018, at 10:05 AM, Alex Harui  wrote:
>>> 
>>> Hi Dave,
>>> 
>>> I updated the online release notes (which are referenced from the packaged 
>>> RELEASE_NOTES) with your suggestions.  Feel free to make edits.
>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Notes-0.9.4data=02%7C01%7Caharui%40adobe.com%7Ca479a284bbfc45f11c9008d64bf13cc8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636779896835985170sdata=V3Uy1JRZoZT%2FNEQXhuz%2Bfb%2B9YebyrLd77GzEhwRfwpE%3Dreserved=0
>> 
>>   I feel free to do so, but Github.com is not giving me the opportunity. I 
>> should have proper permissions. Sigh. It’s close enough so I won’t bother.
>> 
>> 
>>> 
>>> There are two Ant convenience binary packages.  One is for SWF and JS 
>>> output, and one is for JS output.  The latter does not require AIR/Flash.  
>>> If you don't need SWF output, you don't need AIR/Flash and the compiler 
>>> will transpile just fine, proving that Royale no longer has any 
>>> requirements on Adobe runtimes.   The JS-only package simply doesn't 
>>> reference the AIR/Flash SWCs and tells the compiler to not try to output 
>>> SWF.  This is easy in Ant because Ant and command-line and IDE builds 
>>> generally use a single central config file like 
>>> frameworks/royale-config.xml so changing that one file creates a different 
>>> set of defaults for all projects.
>>> 
>>> I have not put any energy towards trying to figure out how to make 
>>> Flash/AIR optional in Maven.  I know there are Maven profiles that could do 
>>> this, but it clutters the poms.  I think there are other tasks that are 
>>> higher priority for me.  Volunteers are welcome to do work on it.
>> 
>>   I’ll see if I can figure this out, but if it takes too long I’ll likely 
>> punt.
>> 
>>   Regards,
>>   Dave
>> 
>> 
>>> 
>>> -Alex
>>> 
>>> On 11/16/18, 8:32 AM, "Dave Fisher"  wrote:
>>> 
>>> 
>>> 
 On Nov 16, 2018, at 12:28 AM, Greg Dove  wrote:
 
 I had that issue when I first set up again on my new machine last month. At
 the time I manually installed the swcs in my local .m2
>>> 
>>>  My org/adobe/air/framework/airglobal/20.0 repository was messed up and I 
>>> manually installed the src and pom. The build then worked.
>>> 
>>>  What does Ant do to locate the SWC? I think it uses a fake one?
>>> 
>>>  I think we are missing instructions for Air setup including installing 
>>> using:
>>> 
>>> mvn install:install-file -DgroupId=com.adobe.air.framework 
>>> -DartifactId=airglobal -Dversion=20.0 -Dpackaging=swc -Dfile=/path/to/file
>>> 
>>>  Regards,
>>>  Dave
>>> 
 
 If I recall correctly I also looked at the MavenTestAdapter to try to
 figure out what was wrong at the time. I think if it has one thing defined
 and not another it was sending js actionscript to test on swf and giving an
 error saying the the Document class was not Sprite (or something similar).
 I figured it was just me at the time, and I think it went away after I have
 the air/playerglobal swcs installed in .m2
 
 I today's build I got the 'super-download' sequence that took ages, and
 maven put all that stuff there, and also did prompt me for licence
 acceptance.
 It offered a setting for the future:
 -Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=
 
 Followed by a pregenerated hash representing the machine I am now using.
 
 So I guess it would be possible to use that in the future, but I imagine
 that now they are in my local .m2 cache, I will not need to anyway.
 
 Don't know if there's anything helpful there, hope it might be
 
 
 
 
 On Fri, Nov 16, 2018 at 8:30 PM Alex Harui  
 wrote:
 
> I looked at MavenTestAdapter.  It looks like it uses environment variables
> for FLASHPLAYER_DEBUGGER, but it is expecting to find playerglobal as an
> artifact in the local maven repo.
> 
> I put a link to the files I think you need on private@.  I can't put it
> on dev@ because Adobe wants folks to accept licensing terms first.  I'm
> assuming you've already accepted those terms bringing down Adobe bits for
> Ant or Flex.  If users need to get 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Piotr Zarzycki]

Sources where downloaded by ApprovalScript.

Ok in the other words I'm ok with that failing example.

I just need to get to the stage where FlexUnit tests are working. I'm
wondering is there any chance to run only part which are failing for me?
Trying everything from scratch is a time consuming.

Piotr

On Fri, Nov 16, 2018, 8:13 PM Alex Harui  wrote:

> Hi Piotr,
>
> If you build one of the Royale examples, like
> examples/royale/DataBindingExample, the POM tries to use artifacts from
> examples-tests.  If you are building your own app, your POM probably
> doesn't care about examples-tests.
>
> Where did you download sources from?
>
> When the artifacts are only on the staging server, and not in your local
> repo (by building the entire source package which by default does not
> include examples), then I think you have to redirect your poms to the
> staging server.  See:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> IMO, if you plan to be an RM, you should not be satisfied with a +0 vote
> because things are not working for you.  Otherwise, you are just setting
> yourself up for others to be in the same situation and when you are the RM,
> you will get a bunch of +0 votes.
>
> Thanks,
> -Alex
>
> On 11/16/18, 10:53 AM, "Piotr Zarzycki" 
> wrote:
>
> Hi Alex,
>
> Once my build failed with that timeout I went to downloaded sources
> directly in order to run Maven build and see whether it's working. I
> was
> able to build it - with similar issue as other with airglobal. - I have
> manually add that part to my Maven cache.
>
> Part 2 of the test was simply build example using your staged
> artifacts -
> It doesn't connected whether I build examples/examples-tests or not -
> Am I
> wrong? Let's imagine that I have clean machine, created Royale project
> -
> I'm trying to build my project with Maven and your artifacts - Do I
> need
> that org.apache.royale.examples:examples-tests:jar ?
>
> If answer is NO - That's ok - it is an requirements for build our
> example
> and I can vote +0.
>
> *Please verify that FlexUnit is working in your repo and then compare
> the
> FlexUnit jars it is using against the ones that the RC downloaded.  Or
> investigate the difference between the SWFs generated by the repo
> build vs
> the RC build.  If we don't figure out why things fail, then we are
> doomed
> to keep hitting these failure points.  *
>
> Above part requires from me a lot of time probably - If I found it
> before
> to be next RM I will do this for sure.
>
> Piotr
>
> pt., 16 lis 2018 o 19:10 Alex Harui 
> napisał(a):
>
> > Piotr,
> >
> > Did you build the examples/examples-tests folder first?
> >
> > If you used the ApproveRoyale script then it would have done all of
> that
> > for you.  If you plan to be an RM, it is worth your time to find out
> why
> > the approval script is not working for you, as it is expected that
> the RM
> > has run the approval script before posting the vote threads in order
> to
> > save everyone time.
> >
> > Please verify that FlexUnit is working in your repo and then compare
> the
> > FlexUnit jars it is using against the ones that the RC downloaded.
> Or
> > investigate the difference between the SWFs generated by the repo
> build vs
> > the RC build.  If we don't figure out why things fail, then we are
> doomed
> > to keep hitting these failure points.
> >
> > Thanks,
> > -Alex
> >
> > On 11/16/18, 4:47 AM, "Piotr Zarzycki" 
> wrote:
> >
> > Here is the steps:
> >
> > 1) You are preparing Maven settings file which pointing to staged
> > artifacts
> > [1]
> > 2) Pickup one of the example and for simplicity place there
> prepared
> > file
> > 3) Build example with following command:  mvn -s
> settings-template.xml
> > clean install
> >
> > [1]
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2FMUADdata=02%7C01%7Caharui%40adobe.com%7C5f6a285c3f6a4147f88f08d64bf4da54%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779912346752062sdata=dhwVb5SBKH55hRXcfoA8kGM0XGBG3Tn3O3UojQZ0msc%3Dreserved=0
> >
> > Piotr
> >
> > pt., 16 lis 2018 o 13:32 Harbs 
> napisał(a):
> >
> > > > Do you mean trust folder for Flash Player ?
> > >
> > > Yes.
> > >
> > > I’m able to compile a project using the ant build locally.
> > >
> > > I have no idea how to build using the Maven artifacts, so I
> can’t
> > test
> > > that…
> > >
> > > > On Nov 16, 2018, at 2:18 PM, Piotr Zarzycki <
> > piotrzarzyck...@gmail.com>
> > > wrote:
> > > >
> > > > Hi Harbs,
> > > >
> > > > Do you mean trust folder for Flash Player ? Maybe trusting
> whole
> > folder

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[OmPrakash Muppirala]

Hmm interesting.  I am getting this output from the approval script:

approve:


-1

Package
https://dist.apache.org/repos/dist/dev/royale/0.9.4/rc2/apache-royale-0.9.4-src.tar.gz

Java 1.8

OS: Mac OS X x86_64 10.13.6

Source kit signatures match: y

Source kit builds: y

README is ok: y

RELEASE_NOTES is ok: y

NOTICE is ok: y

LICENSE is ok: y

No unapproved licenses or archives: y

No unapproved binaries: n


Package
https://dist.apache.org/repos/dist/dev/royale/0.9.4/rc2/binaries/apache-royale-0.9.4-bin-js-swf.tar.gz

Binary kit signatures match: y

NOTICE is ok: y

LICENSE is ok: y

No unapproved licenses or archives in binary package: y

No unapproved binaries in binary package: n




BUILD FAILED

/Users/om/p/os/royale/rc/ApproveRoyale.xml:1103: condition satisfied


Looking at the rat report, I do see these files marked as B which might be
causing this?

  B
/Users/om/p/os/royale/rc/apache-royale-0.9.4-bin-js-swf/royale-asjs/examples/mxroyale/tourdeflexmodules/src/favicon.ico

  B
/Users/om/p/os/royale/rc/apache-royale-0.9.4-bin-js-swf/royale-asjs/examples/mxroyale/tourdeflexmodules/src/mx/controls/assets/flexinstaller.mp4

  B
/Users/om/p/os/royale/rc/apache-royale-0.9.4-bin-js-swf/royale-asjs/examples/mxroyale/tourdeflexmodules/src/mx/effects/assets/OpenSans-Regular.ttf

  B
/Users/om/p/os/royale/rc/apache-royale-0.9.4-bin-js-swf/royale-asjs/examples/mxroyale/tourdeflexmodules/src/spark/components/assets/FlexInstaller.mp4

  B
/Users/om/p/os/royale/rc/apache-royale-0.9.4-bin-js-swf/royale-asjs/examples/mxroyale/tourdeflexmodules/src/spark/controls/assets/FlexInstaller.mp4

  B
/Users/om/p/os/royale/rc/apache-royale-0.9.4-bin-js-swf/royale-asjs/examples/mxroyale/tourdeflexmodules/src/spark/tlf/textEditBar/assets/icon_align_end.PNG

  B
/Users/om/p/os/royale/rc/apache-royale-0.9.4-bin-js-swf/royale-asjs/examples/mxroyale/tourdeflexmodules/src/spark/tlf/textEditBar/assets/icon_align_start.PNG

On Fri, Nov 16, 2018 at 11:13 AM Alex Harui 
wrote:

> Hi Piotr,
>
> If you build one of the Royale examples, like
> examples/royale/DataBindingExample, the POM tries to use artifacts from
> examples-tests.  If you are building your own app, your POM probably
> doesn't care about examples-tests.
>
> Where did you download sources from?
>
> When the artifacts are only on the staging server, and not in your local
> repo (by building the entire source package which by default does not
> include examples), then I think you have to redirect your poms to the
> staging server.  See:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> IMO, if you plan to be an RM, you should not be satisfied with a +0 vote
> because things are not working for you.  Otherwise, you are just setting
> yourself up for others to be in the same situation and when you are the RM,
> you will get a bunch of +0 votes.
>
> Thanks,
> -Alex
>
> On 11/16/18, 10:53 AM, "Piotr Zarzycki" 
> wrote:
>
> Hi Alex,
>
> Once my build failed with that timeout I went to downloaded sources
> directly in order to run Maven build and see whether it's working. I
> was
> able to build it - with similar issue as other with airglobal. - I have
> manually add that part to my Maven cache.
>
> Part 2 of the test was simply build example using your staged
> artifacts -
> It doesn't connected whether I build examples/examples-tests or not -
> Am I
> wrong? Let's imagine that I have clean machine, created Royale project
> -
> I'm trying to build my project with Maven and your artifacts - Do I
> need
> that org.apache.royale.examples:examples-tests:jar ?
>
> If answer is NO - That's ok - it is an requirements for build our
> example
> and I can vote +0.
>
> *Please verify that FlexUnit is working in your repo and then compare
> the
> FlexUnit jars it is using against the ones that the RC downloaded.  Or
> investigate the difference between the SWFs generated by the repo
> build vs
> the RC build.  If we don't figure out why things fail, then we are
> doomed
> to keep hitting these failure points.  *
>
> Above part requires from me a lot of time probably - If I found it
> before
> to be next RM I will do this for sure.
>
> Piotr
>
> pt., 16 lis 2018 o 19:10 Alex Harui 
> napisał(a):
>
> > Piotr,
> >
> > Did you build the examples/examples-tests folder first?
> >
> > If you used the ApproveRoyale script then it would have done all of
> that
> > for you.  If you plan to be an RM, it is worth your time to find out
> why
> > the approval script is not working for you, as it is expected that
> the RM
> > has run the approval script before posting the vote threads in order
> to
> > save everyone time.
> >
> > Please verify that FlexUnit is working in your repo and then compare
> the
> > FlexUnit jars it is using against the ones that the RC downloaded.
> Or
> > investigate the difference between the SWFs generated by 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Alex Harui]

Hi Piotr,

If you build one of the Royale examples, like 
examples/royale/DataBindingExample, the POM tries to use artifacts from 
examples-tests.  If you are building your own app, your POM probably doesn't 
care about examples-tests.

Where did you download sources from?

When the artifacts are only on the staging server, and not in your local repo 
(by building the entire source package which by default does not include 
examples), then I think you have to redirect your poms to the staging server.  
See:
https://maven.apache.org/guides/development/guide-testing-releases.html

IMO, if you plan to be an RM, you should not be satisfied with a +0 vote 
because things are not working for you.  Otherwise, you are just setting 
yourself up for others to be in the same situation and when you are the RM, you 
will get a bunch of +0 votes.

Thanks,
-Alex

On 11/16/18, 10:53 AM, "Piotr Zarzycki"  wrote:

Hi Alex,

Once my build failed with that timeout I went to downloaded sources
directly in order to run Maven build and see whether it's working. I was
able to build it - with similar issue as other with airglobal. - I have
manually add that part to my Maven cache.

Part 2 of the test was simply build example using your staged artifacts -
It doesn't connected whether I build examples/examples-tests or not - Am I
wrong? Let's imagine that I have clean machine, created Royale project -
I'm trying to build my project with Maven and your artifacts - Do I need
that org.apache.royale.examples:examples-tests:jar ?

If answer is NO - That's ok - it is an requirements for build our example
and I can vote +0.

*Please verify that FlexUnit is working in your repo and then compare the
FlexUnit jars it is using against the ones that the RC downloaded.  Or
investigate the difference between the SWFs generated by the repo build vs
the RC build.  If we don't figure out why things fail, then we are doomed
to keep hitting these failure points.  *

Above part requires from me a lot of time probably - If I found it before
to be next RM I will do this for sure.

Piotr

pt., 16 lis 2018 o 19:10 Alex Harui  napisał(a):

> Piotr,
>
> Did you build the examples/examples-tests folder first?
>
> If you used the ApproveRoyale script then it would have done all of that
> for you.  If you plan to be an RM, it is worth your time to find out why
> the approval script is not working for you, as it is expected that the RM
> has run the approval script before posting the vote threads in order to
> save everyone time.
>
> Please verify that FlexUnit is working in your repo and then compare the
> FlexUnit jars it is using against the ones that the RC downloaded.  Or
> investigate the difference between the SWFs generated by the repo build vs
> the RC build.  If we don't figure out why things fail, then we are doomed
> to keep hitting these failure points.
>
> Thanks,
> -Alex
>
> On 11/16/18, 4:47 AM, "Piotr Zarzycki"  wrote:
>
> Here is the steps:
>
> 1) You are preparing Maven settings file which pointing to staged
> artifacts
> [1]
> 2) Pickup one of the example and for simplicity place there prepared
> file
> 3) Build example with following command:  mvn -s settings-template.xml
> clean install
>
> [1]
> 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2FMUADdata=02%7C01%7Caharui%40adobe.com%7C5f6a285c3f6a4147f88f08d64bf4da54%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779912346752062sdata=dhwVb5SBKH55hRXcfoA8kGM0XGBG3Tn3O3UojQZ0msc%3Dreserved=0
>
> Piotr
>
> pt., 16 lis 2018 o 13:32 Harbs  napisał(a):
>
> > > Do you mean trust folder for Flash Player ?
> >
> > Yes.
> >
> > I’m able to compile a project using the ant build locally.
> >
> > I have no idea how to build using the Maven artifacts, so I can’t
> test
> > that…
> >
> > > On Nov 16, 2018, at 2:18 PM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> > wrote:
> > >
> > > Hi Harbs,
> > >
> > > Do you mean trust folder for Flash Player ? Maybe trusting whole
> folder
> > is
> > > a good idea, but I got Maven build working. However building 
simple
> > project
> > > is not working so that is the issue which I'm more concern right
> now.
> > >
> > > Cause you guys proof that Ant is working on your machines, Maven 
is
> > working
> > > on mine, that's fine for me to give +0. However examples should
> also work
> > > with artifacts.
> > >
> > > Piotr
> > >
> > > pt., 16 lis 2018 o 13:10 Harbs  napisał(a):
> > >
   

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Dave Fisher]

Something unique to my id. I missed a step in the past on gitbox setup.

I’ll see soon about it.

> On Nov 16, 2018, at 10:45 AM, Alex Harui  wrote:
> 
> Hmm.  Have you been active on Royale's GitHub before?  I wonder if there is a 
> per-project permission we have to provide, or if you have to go through some 
> sync up via GitBox per project.
> 
> -Alex
> 
> On 11/16/18, 10:28 AM, "Dave Fisher"  wrote:
> 
> 
> 
>> On Nov 16, 2018, at 10:05 AM, Alex Harui  wrote:
>> 
>> Hi Dave,
>> 
>> I updated the online release notes (which are referenced from the packaged 
>> RELEASE_NOTES) with your suggestions.  Feel free to make edits.
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Notes-0.9.4data=02%7C01%7Caharui%40adobe.com%7Ca479a284bbfc45f11c9008d64bf13cc8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636779896835985170sdata=V3Uy1JRZoZT%2FNEQXhuz%2Bfb%2B9YebyrLd77GzEhwRfwpE%3Dreserved=0
> 
>I feel free to do so, but Github.com is not giving me the opportunity. I 
> should have proper permissions. Sigh. It’s close enough so I won’t bother.
> 
> 
>> 
>> There are two Ant convenience binary packages.  One is for SWF and JS 
>> output, and one is for JS output.  The latter does not require AIR/Flash.  
>> If you don't need SWF output, you don't need AIR/Flash and the compiler will 
>> transpile just fine, proving that Royale no longer has any requirements on 
>> Adobe runtimes.   The JS-only package simply doesn't reference the AIR/Flash 
>> SWCs and tells the compiler to not try to output SWF.  This is easy in Ant 
>> because Ant and command-line and IDE builds generally use a single central 
>> config file like frameworks/royale-config.xml so changing that one file 
>> creates a different set of defaults for all projects.
>> 
>> I have not put any energy towards trying to figure out how to make Flash/AIR 
>> optional in Maven.  I know there are Maven profiles that could do this, but 
>> it clutters the poms.  I think there are other tasks that are higher 
>> priority for me.  Volunteers are welcome to do work on it.
> 
>I’ll see if I can figure this out, but if it takes too long I’ll likely 
> punt.
> 
>Regards,
>Dave
> 
> 
>> 
>> -Alex
>> 
>> On 11/16/18, 8:32 AM, "Dave Fisher"  wrote:
>> 
>> 
>> 
>>> On Nov 16, 2018, at 12:28 AM, Greg Dove  wrote:
>>> 
>>> I had that issue when I first set up again on my new machine last month. At
>>> the time I manually installed the swcs in my local .m2
>> 
>>   My org/adobe/air/framework/airglobal/20.0 repository was messed up and I 
>> manually installed the src and pom. The build then worked.
>> 
>>   What does Ant do to locate the SWC? I think it uses a fake one?
>> 
>>   I think we are missing instructions for Air setup including installing 
>> using:
>> 
>>  mvn install:install-file -DgroupId=com.adobe.air.framework 
>> -DartifactId=airglobal -Dversion=20.0 -Dpackaging=swc -Dfile=/path/to/file
>> 
>>   Regards,
>>   Dave
>> 
>>> 
>>> If I recall correctly I also looked at the MavenTestAdapter to try to
>>> figure out what was wrong at the time. I think if it has one thing defined
>>> and not another it was sending js actionscript to test on swf and giving an
>>> error saying the the Document class was not Sprite (or something similar).
>>> I figured it was just me at the time, and I think it went away after I have
>>> the air/playerglobal swcs installed in .m2
>>> 
>>> I today's build I got the 'super-download' sequence that took ages, and
>>> maven put all that stuff there, and also did prompt me for licence
>>> acceptance.
>>> It offered a setting for the future:
>>> -Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=
>>> 
>>> Followed by a pregenerated hash representing the machine I am now using.
>>> 
>>> So I guess it would be possible to use that in the future, but I imagine
>>> that now they are in my local .m2 cache, I will not need to anyway.
>>> 
>>> Don't know if there's anything helpful there, hope it might be
>>> 
>>> 
>>> 
>>> 
>>> On Fri, Nov 16, 2018 at 8:30 PM Alex Harui  wrote:
>>> 
 I looked at MavenTestAdapter.  It looks like it uses environment variables
 for FLASHPLAYER_DEBUGGER, but it is expecting to find playerglobal as an
 artifact in the local maven repo.
 
 I put a link to the files I think you need on private@.  I can't put it
 on dev@ because Adobe wants folks to accept licensing terms first.  I'm
 assuming you've already accepted those terms bringing down Adobe bits for
 Ant or Flex.  If users need to get around this then we'll spend more time
 figuring out why it isn't working for some folks.  I seem to recall that
 some more recent version of Maven was needed to launch the Mavenizer
 automatically, but I can't find information on what version.  IIRC, older
 versions of Maven can build all of Royale but can't automate the Adobe
 downloads.
 
 HTH,
 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Piotr Zarzycki]

Hi Alex,

Once my build failed with that timeout I went to downloaded sources
directly in order to run Maven build and see whether it's working. I was
able to build it - with similar issue as other with airglobal. - I have
manually add that part to my Maven cache.

Part 2 of the test was simply build example using your staged artifacts -
It doesn't connected whether I build examples/examples-tests or not - Am I
wrong? Let's imagine that I have clean machine, created Royale project -
I'm trying to build my project with Maven and your artifacts - Do I need
that org.apache.royale.examples:examples-tests:jar ?

If answer is NO - That's ok - it is an requirements for build our example
and I can vote +0.

*Please verify that FlexUnit is working in your repo and then compare the
FlexUnit jars it is using against the ones that the RC downloaded.  Or
investigate the difference between the SWFs generated by the repo build vs
the RC build.  If we don't figure out why things fail, then we are doomed
to keep hitting these failure points.  *

Above part requires from me a lot of time probably - If I found it before
to be next RM I will do this for sure.

Piotr

pt., 16 lis 2018 o 19:10 Alex Harui  napisał(a):

> Piotr,
>
> Did you build the examples/examples-tests folder first?
>
> If you used the ApproveRoyale script then it would have done all of that
> for you.  If you plan to be an RM, it is worth your time to find out why
> the approval script is not working for you, as it is expected that the RM
> has run the approval script before posting the vote threads in order to
> save everyone time.
>
> Please verify that FlexUnit is working in your repo and then compare the
> FlexUnit jars it is using against the ones that the RC downloaded.  Or
> investigate the difference between the SWFs generated by the repo build vs
> the RC build.  If we don't figure out why things fail, then we are doomed
> to keep hitting these failure points.
>
> Thanks,
> -Alex
>
> On 11/16/18, 4:47 AM, "Piotr Zarzycki"  wrote:
>
> Here is the steps:
>
> 1) You are preparing Maven settings file which pointing to staged
> artifacts
> [1]
> 2) Pickup one of the example and for simplicity place there prepared
> file
> 3) Build example with following command:  mvn -s settings-template.xml
> clean install
>
> [1]
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2FMUADdata=02%7C01%7Caharui%40adobe.com%7C39975fb0dc1e44d8dc9408d64bc1ad21%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779692539144991sdata=Q0BIfl5E4ClKrqbptLo56Chmmf6Olno7r7Kapjx8XZ4%3Dreserved=0
>
> Piotr
>
> pt., 16 lis 2018 o 13:32 Harbs  napisał(a):
>
> > > Do you mean trust folder for Flash Player ?
> >
> > Yes.
> >
> > I’m able to compile a project using the ant build locally.
> >
> > I have no idea how to build using the Maven artifacts, so I can’t
> test
> > that…
> >
> > > On Nov 16, 2018, at 2:18 PM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> > wrote:
> > >
> > > Hi Harbs,
> > >
> > > Do you mean trust folder for Flash Player ? Maybe trusting whole
> folder
> > is
> > > a good idea, but I got Maven build working. However building simple
> > project
> > > is not working so that is the issue which I'm more concern right
> now.
> > >
> > > Cause you guys proof that Ant is working on your machines, Maven is
> > working
> > > on mine, that's fine for me to give +0. However examples should
> also work
> > > with artifacts.
> > >
> > > Piotr
> > >
> > > pt., 16 lis 2018 o 13:10 Harbs  napisał(a):
> > >
> > >> What do you have in the trust files? I generally build from the
> same
> > >> parent folder as the repo and I have the whole folder trusted. The
> > >> auto-generated trust files do not always work for me.
> > >>
> > >>> On Nov 16, 2018, at 10:32 AM, Piotr Zarzycki <
> > piotrzarzyck...@gmail.com>
> > >> wrote:
> > >>>
> > >>> I got again the same timeout, so no option for me build project
> by ant
> > >> [1].
> > >>> I will try Maven.
> > >>>
> > >>> [1]
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F6UPtdata=02%7C01%7Caharui%40adobe.com%7C39975fb0dc1e44d8dc9408d64bc1ad21%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779692539144991sdata=zsEViovGTCj519MQTZjTWC5HUL7O9TxGuNbtFzemdUA%3Dreserved=0
> > >>>
> > >>> pt., 16 lis 2018 o 09:28 Greg Dove 
> napisał(a):
> > >>>
> >  I had that issue when I first set up again on my new machine
> last
> > >> month. At
> >  the time I manually installed the swcs in my local .m2
> > 
> >  If I recall correctly I also looked at the MavenTestAdapter to
> try to
> >  figure out what was wrong at the time. I think if it has one
> thing
> > >> defined
> >  and not another it was sending js actionscript 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Alex Harui]

Hmm.  Have you been active on Royale's GitHub before?  I wonder if there is a 
per-project permission we have to provide, or if you have to go through some 
sync up via GitBox per project.

-Alex

On 11/16/18, 10:28 AM, "Dave Fisher"  wrote:



> On Nov 16, 2018, at 10:05 AM, Alex Harui  wrote:
> 
> Hi Dave,
> 
> I updated the online release notes (which are referenced from the 
packaged RELEASE_NOTES) with your suggestions.  Feel free to make edits.
> 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Notes-0.9.4data=02%7C01%7Caharui%40adobe.com%7Ca479a284bbfc45f11c9008d64bf13cc8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636779896835985170sdata=V3Uy1JRZoZT%2FNEQXhuz%2Bfb%2B9YebyrLd77GzEhwRfwpE%3Dreserved=0

I feel free to do so, but Github.com is not giving me the opportunity. I 
should have proper permissions. Sigh. It’s close enough so I won’t bother.


> 
> There are two Ant convenience binary packages.  One is for SWF and JS 
output, and one is for JS output.  The latter does not require AIR/Flash.  If 
you don't need SWF output, you don't need AIR/Flash and the compiler will 
transpile just fine, proving that Royale no longer has any requirements on 
Adobe runtimes.   The JS-only package simply doesn't reference the AIR/Flash 
SWCs and tells the compiler to not try to output SWF.  This is easy in Ant 
because Ant and command-line and IDE builds generally use a single central 
config file like frameworks/royale-config.xml so changing that one file creates 
a different set of defaults for all projects.
> 
> I have not put any energy towards trying to figure out how to make 
Flash/AIR optional in Maven.  I know there are Maven profiles that could do 
this, but it clutters the poms.  I think there are other tasks that are higher 
priority for me.  Volunteers are welcome to do work on it.

I’ll see if I can figure this out, but if it takes too long I’ll likely 
punt.

Regards,
Dave


> 
> -Alex
> 
> On 11/16/18, 8:32 AM, "Dave Fisher"  wrote:
> 
> 
> 
>> On Nov 16, 2018, at 12:28 AM, Greg Dove  wrote:
>> 
>> I had that issue when I first set up again on my new machine last month. 
At
>> the time I manually installed the swcs in my local .m2
> 
>My org/adobe/air/framework/airglobal/20.0 repository was messed up and 
I manually installed the src and pom. The build then worked.
> 
>What does Ant do to locate the SWC? I think it uses a fake one?
> 
>I think we are missing instructions for Air setup including installing 
using:
> 
>   mvn install:install-file -DgroupId=com.adobe.air.framework 
-DartifactId=airglobal -Dversion=20.0 -Dpackaging=swc -Dfile=/path/to/file
> 
>Regards,
>Dave
> 
>> 
>> If I recall correctly I also looked at the MavenTestAdapter to try to
>> figure out what was wrong at the time. I think if it has one thing 
defined
>> and not another it was sending js actionscript to test on swf and giving 
an
>> error saying the the Document class was not Sprite (or something 
similar).
>> I figured it was just me at the time, and I think it went away after I 
have
>> the air/playerglobal swcs installed in .m2
>> 
>> I today's build I got the 'super-download' sequence that took ages, and
>> maven put all that stuff there, and also did prompt me for licence
>> acceptance.
>> It offered a setting for the future:
>> 
-Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=
>> 
>> Followed by a pregenerated hash representing the machine I am now using.
>> 
>> So I guess it would be possible to use that in the future, but I imagine
>> that now they are in my local .m2 cache, I will not need to anyway.
>> 
>> Don't know if there's anything helpful there, hope it might be
>> 
>> 
>> 
>> 
>> On Fri, Nov 16, 2018 at 8:30 PM Alex Harui  
wrote:
>> 
>>> I looked at MavenTestAdapter.  It looks like it uses environment 
variables
>>> for FLASHPLAYER_DEBUGGER, but it is expecting to find playerglobal as an
>>> artifact in the local maven repo.
>>> 
>>> I put a link to the files I think you need on private@.  I can't put it
>>> on dev@ because Adobe wants folks to accept licensing terms first.  I'm
>>> assuming you've already accepted those terms bringing down Adobe bits 
for
>>> Ant or Flex.  If users need to get around this then we'll spend more 
time
>>> figuring out why it isn't working for some folks.  I seem to recall that
>>> some more recent version of Maven was needed to launch the Mavenizer
>>> automatically, but I can't find information on what version.  IIRC, 
older
>>> versions of Maven can build all of Royale but can't automate the Adobe
>>> 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Dave Fisher]

> On Nov 16, 2018, at 10:05 AM, Alex Harui  wrote:
> 
> Hi Dave,
> 
> I updated the online release notes (which are referenced from the packaged 
> RELEASE_NOTES) with your suggestions.  Feel free to make edits.
> https://github.com/apache/royale-asjs/wiki/Release-Notes-0.9.4

I feel free to do so, but Github.com is not giving me the opportunity. I should 
have proper permissions. Sigh. It’s close enough so I won’t bother.


> 
> There are two Ant convenience binary packages.  One is for SWF and JS output, 
> and one is for JS output.  The latter does not require AIR/Flash.  If you 
> don't need SWF output, you don't need AIR/Flash and the compiler will 
> transpile just fine, proving that Royale no longer has any requirements on 
> Adobe runtimes.   The JS-only package simply doesn't reference the AIR/Flash 
> SWCs and tells the compiler to not try to output SWF.  This is easy in Ant 
> because Ant and command-line and IDE builds generally use a single central 
> config file like frameworks/royale-config.xml so changing that one file 
> creates a different set of defaults for all projects.
> 
> I have not put any energy towards trying to figure out how to make Flash/AIR 
> optional in Maven.  I know there are Maven profiles that could do this, but 
> it clutters the poms.  I think there are other tasks that are higher priority 
> for me.  Volunteers are welcome to do work on it.

I’ll see if I can figure this out, but if it takes too long I’ll likely punt.

Regards,
Dave


> 
> -Alex
> 
> On 11/16/18, 8:32 AM, "Dave Fisher"  wrote:
> 
> 
> 
>> On Nov 16, 2018, at 12:28 AM, Greg Dove  wrote:
>> 
>> I had that issue when I first set up again on my new machine last month. At
>> the time I manually installed the swcs in my local .m2
> 
>My org/adobe/air/framework/airglobal/20.0 repository was messed up and I 
> manually installed the src and pom. The build then worked.
> 
>What does Ant do to locate the SWC? I think it uses a fake one?
> 
>I think we are missing instructions for Air setup including installing 
> using:
> 
>   mvn install:install-file -DgroupId=com.adobe.air.framework 
> -DartifactId=airglobal -Dversion=20.0 -Dpackaging=swc -Dfile=/path/to/file
> 
>Regards,
>Dave
> 
>> 
>> If I recall correctly I also looked at the MavenTestAdapter to try to
>> figure out what was wrong at the time. I think if it has one thing defined
>> and not another it was sending js actionscript to test on swf and giving an
>> error saying the the Document class was not Sprite (or something similar).
>> I figured it was just me at the time, and I think it went away after I have
>> the air/playerglobal swcs installed in .m2
>> 
>> I today's build I got the 'super-download' sequence that took ages, and
>> maven put all that stuff there, and also did prompt me for licence
>> acceptance.
>> It offered a setting for the future:
>> -Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=
>> 
>> Followed by a pregenerated hash representing the machine I am now using.
>> 
>> So I guess it would be possible to use that in the future, but I imagine
>> that now they are in my local .m2 cache, I will not need to anyway.
>> 
>> Don't know if there's anything helpful there, hope it might be
>> 
>> 
>> 
>> 
>> On Fri, Nov 16, 2018 at 8:30 PM Alex Harui  wrote:
>> 
>>> I looked at MavenTestAdapter.  It looks like it uses environment variables
>>> for FLASHPLAYER_DEBUGGER, but it is expecting to find playerglobal as an
>>> artifact in the local maven repo.
>>> 
>>> I put a link to the files I think you need on private@.  I can't put it
>>> on dev@ because Adobe wants folks to accept licensing terms first.  I'm
>>> assuming you've already accepted those terms bringing down Adobe bits for
>>> Ant or Flex.  If users need to get around this then we'll spend more time
>>> figuring out why it isn't working for some folks.  I seem to recall that
>>> some more recent version of Maven was needed to launch the Mavenizer
>>> automatically, but I can't find information on what version.  IIRC, older
>>> versions of Maven can build all of Royale but can't automate the Adobe
>>> downloads.
>>> 
>>> HTH,
>>> -Alex
>>> 
>>> On 11/15/18, 10:41 PM, "Harbs"  wrote:
>>> 
>>>   There are the env variables I’m using for all my builds:
>>> 
>>>   #!/bin/sh
>>> 
>>>   export ROYALE_COMPILER_REPO=/Apache/royale-compiler
>>>   export FLEX_SDK_HOME=/FlexSDK/4.14.1
>>>   export AIR_HOME=/Apache/frameworks/AIRSDK_Compiler
>>>   export PLAYERGLOBAL_HOME=/Apache/frameworks/libs/player
>>>   export FLASHPLAYER_DEBUGGER=/Apache/frameworks/Flash\ Player\
>>> Debugger.app/Contents/MacOS/Flash\ Player\ Debugger
>>>   export ROYALE_HOME=/Apache/royale-asjs
>>> 
>>>   The Ant build seems to succeed. I thought Maven does not use
>>> environment variables?
>>> 
>>>   Either way, I think I can vote for this RC. The fact that Maven is
>>> failing is nothing new on my end… ;-)
>>> 
>>>   Harbs
>>> 
 On Nov 16, 2018, at 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Alex Harui]

Piotr,

Did you build the examples/examples-tests folder first?

If you used the ApproveRoyale script then it would have done all of that for 
you.  If you plan to be an RM, it is worth your time to find out why the 
approval script is not working for you, as it is expected that the RM has run 
the approval script before posting the vote threads in order to save everyone 
time.

Please verify that FlexUnit is working in your repo and then compare the 
FlexUnit jars it is using against the ones that the RC downloaded.  Or 
investigate the difference between the SWFs generated by the repo build vs the 
RC build.  If we don't figure out why things fail, then we are doomed to keep 
hitting these failure points.

Thanks,
-Alex

On 11/16/18, 4:47 AM, "Piotr Zarzycki"  wrote:

Here is the steps:

1) You are preparing Maven settings file which pointing to staged artifacts
[1]
2) Pickup one of the example and for simplicity place there prepared file
3) Build example with following command:  mvn -s settings-template.xml
clean install

[1] 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2FMUADdata=02%7C01%7Caharui%40adobe.com%7C39975fb0dc1e44d8dc9408d64bc1ad21%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779692539144991sdata=Q0BIfl5E4ClKrqbptLo56Chmmf6Olno7r7Kapjx8XZ4%3Dreserved=0

Piotr

pt., 16 lis 2018 o 13:32 Harbs  napisał(a):

> > Do you mean trust folder for Flash Player ?
>
> Yes.
>
> I’m able to compile a project using the ant build locally.
>
> I have no idea how to build using the Maven artifacts, so I can’t test
> that…
>
> > On Nov 16, 2018, at 2:18 PM, Piotr Zarzycki 
> wrote:
> >
> > Hi Harbs,
> >
> > Do you mean trust folder for Flash Player ? Maybe trusting whole folder
> is
> > a good idea, but I got Maven build working. However building simple
> project
> > is not working so that is the issue which I'm more concern right now.
> >
> > Cause you guys proof that Ant is working on your machines, Maven is
> working
> > on mine, that's fine for me to give +0. However examples should also 
work
> > with artifacts.
> >
> > Piotr
> >
> > pt., 16 lis 2018 o 13:10 Harbs  napisał(a):
> >
> >> What do you have in the trust files? I generally build from the same
> >> parent folder as the repo and I have the whole folder trusted. The
> >> auto-generated trust files do not always work for me.
> >>
> >>> On Nov 16, 2018, at 10:32 AM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> >> wrote:
> >>>
> >>> I got again the same timeout, so no option for me build project by ant
> >> [1].
> >>> I will try Maven.
> >>>
> >>> [1] 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F6UPtdata=02%7C01%7Caharui%40adobe.com%7C39975fb0dc1e44d8dc9408d64bc1ad21%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779692539144991sdata=zsEViovGTCj519MQTZjTWC5HUL7O9TxGuNbtFzemdUA%3Dreserved=0
> >>>
> >>> pt., 16 lis 2018 o 09:28 Greg Dove  napisał(a):
> >>>
>  I had that issue when I first set up again on my new machine last
> >> month. At
>  the time I manually installed the swcs in my local .m2
> 
>  If I recall correctly I also looked at the MavenTestAdapter to try to
>  figure out what was wrong at the time. I think if it has one thing
> >> defined
>  and not another it was sending js actionscript to test on swf and
> >> giving an
>  error saying the the Document class was not Sprite (or something
> >> similar).
>  I figured it was just me at the time, and I think it went away after 
I
> >> have
>  the air/playerglobal swcs installed in .m2
> 
>  I today's build I got the 'super-download' sequence that took ages,
> and
>  maven put all that stuff there, and also did prompt me for licence
>  acceptance.
>  It offered a setting for the future:
> 
> >>
> 
-Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=
> 
>  Followed by a pregenerated hash representing the machine I am now
> using.
> 
>  So I guess it would be possible to use that in the future, but I
> imagine
>  that now they are in my local .m2 cache, I will not need to anyway.
> 
>  Don't know if there's anything helpful there, hope it might be
> 
> 
> 
> 
>  On Fri, Nov 16, 2018 at 8:30 PM Alex Harui 
>  wrote:
> 
> > I looked at MavenTestAdapter.  It looks like it uses environment
>  variables
> > for FLASHPLAYER_DEBUGGER, but it is expecting to find playerglobal 
as
> >> an
> > artifact in the local maven repo.
> >
> > I put a 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Alex Harui]

Hi Dave,

I updated the online release notes (which are referenced from the packaged 
RELEASE_NOTES) with your suggestions.  Feel free to make edits.
https://github.com/apache/royale-asjs/wiki/Release-Notes-0.9.4

There are two Ant convenience binary packages.  One is for SWF and JS output, 
and one is for JS output.  The latter does not require AIR/Flash.  If you don't 
need SWF output, you don't need AIR/Flash and the compiler will transpile just 
fine, proving that Royale no longer has any requirements on Adobe runtimes.   
The JS-only package simply doesn't reference the AIR/Flash SWCs and tells the 
compiler to not try to output SWF.  This is easy in Ant because Ant and 
command-line and IDE builds generally use a single central config file like 
frameworks/royale-config.xml so changing that one file creates a different set 
of defaults for all projects.

I have not put any energy towards trying to figure out how to make Flash/AIR 
optional in Maven.  I know there are Maven profiles that could do this, but it 
clutters the poms.  I think there are other tasks that are higher priority for 
me.  Volunteers are welcome to do work on it.

-Alex

On 11/16/18, 8:32 AM, "Dave Fisher"  wrote:



> On Nov 16, 2018, at 12:28 AM, Greg Dove  wrote:
> 
> I had that issue when I first set up again on my new machine last month. 
At
> the time I manually installed the swcs in my local .m2

My org/adobe/air/framework/airglobal/20.0 repository was messed up and I 
manually installed the src and pom. The build then worked.

What does Ant do to locate the SWC? I think it uses a fake one?

I think we are missing instructions for Air setup including installing 
using:

   mvn install:install-file -DgroupId=com.adobe.air.framework 
-DartifactId=airglobal -Dversion=20.0 -Dpackaging=swc -Dfile=/path/to/file

Regards,
Dave

> 
> If I recall correctly I also looked at the MavenTestAdapter to try to
> figure out what was wrong at the time. I think if it has one thing defined
> and not another it was sending js actionscript to test on swf and giving 
an
> error saying the the Document class was not Sprite (or something similar).
> I figured it was just me at the time, and I think it went away after I 
have
> the air/playerglobal swcs installed in .m2
> 
> I today's build I got the 'super-download' sequence that took ages, and
> maven put all that stuff there, and also did prompt me for licence
> acceptance.
> It offered a setting for the future:
> 
-Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=
> 
> Followed by a pregenerated hash representing the machine I am now using.
> 
> So I guess it would be possible to use that in the future, but I imagine
> that now they are in my local .m2 cache, I will not need to anyway.
> 
> Don't know if there's anything helpful there, hope it might be
> 
> 
> 
> 
> On Fri, Nov 16, 2018 at 8:30 PM Alex Harui  
wrote:
> 
>> I looked at MavenTestAdapter.  It looks like it uses environment 
variables
>> for FLASHPLAYER_DEBUGGER, but it is expecting to find playerglobal as an
>> artifact in the local maven repo.
>> 
>> I put a link to the files I think you need on private@.  I can't put it
>> on dev@ because Adobe wants folks to accept licensing terms first.  I'm
>> assuming you've already accepted those terms bringing down Adobe bits for
>> Ant or Flex.  If users need to get around this then we'll spend more time
>> figuring out why it isn't working for some folks.  I seem to recall that
>> some more recent version of Maven was needed to launch the Mavenizer
>> automatically, but I can't find information on what version.  IIRC, older
>> versions of Maven can build all of Royale but can't automate the Adobe
>> downloads.
>> 
>> HTH,
>> -Alex
>> 
>> On 11/15/18, 10:41 PM, "Harbs"  wrote:
>> 
>>There are the env variables I’m using for all my builds:
>> 
>>#!/bin/sh
>> 
>>export ROYALE_COMPILER_REPO=/Apache/royale-compiler
>>export FLEX_SDK_HOME=/FlexSDK/4.14.1
>>export AIR_HOME=/Apache/frameworks/AIRSDK_Compiler
>>export PLAYERGLOBAL_HOME=/Apache/frameworks/libs/player
>>export FLASHPLAYER_DEBUGGER=/Apache/frameworks/Flash\ Player\
>> Debugger.app/Contents/MacOS/Flash\ Player\ Debugger
>>export ROYALE_HOME=/Apache/royale-asjs
>> 
>>The Ant build seems to succeed. I thought Maven does not use
>> environment variables?
>> 
>>Either way, I think I can vote for this RC. The fact that Maven is
>> failing is nothing new on my end… ;-)
>> 
>>Harbs
>> 
>>> On Nov 16, 2018, at 6:21 AM, Alex Harui 
>> wrote:
>>> 
>>> It appears that there is something mixed up with your environment
>> 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Dave Fisher]

> On Nov 16, 2018, at 12:28 AM, Greg Dove  wrote:
> 
> I had that issue when I first set up again on my new machine last month. At
> the time I manually installed the swcs in my local .m2

My org/adobe/air/framework/airglobal/20.0 repository was messed up and I 
manually installed the src and pom. The build then worked.

What does Ant do to locate the SWC? I think it uses a fake one?

I think we are missing instructions for Air setup including installing using:

   mvn install:install-file -DgroupId=com.adobe.air.framework 
-DartifactId=airglobal -Dversion=20.0 -Dpackaging=swc -Dfile=/path/to/file

Regards,
Dave

> 
> If I recall correctly I also looked at the MavenTestAdapter to try to
> figure out what was wrong at the time. I think if it has one thing defined
> and not another it was sending js actionscript to test on swf and giving an
> error saying the the Document class was not Sprite (or something similar).
> I figured it was just me at the time, and I think it went away after I have
> the air/playerglobal swcs installed in .m2
> 
> I today's build I got the 'super-download' sequence that took ages, and
> maven put all that stuff there, and also did prompt me for licence
> acceptance.
> It offered a setting for the future:
> -Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=
> 
> Followed by a pregenerated hash representing the machine I am now using.
> 
> So I guess it would be possible to use that in the future, but I imagine
> that now they are in my local .m2 cache, I will not need to anyway.
> 
> Don't know if there's anything helpful there, hope it might be
> 
> 
> 
> 
> On Fri, Nov 16, 2018 at 8:30 PM Alex Harui  wrote:
> 
>> I looked at MavenTestAdapter.  It looks like it uses environment variables
>> for FLASHPLAYER_DEBUGGER, but it is expecting to find playerglobal as an
>> artifact in the local maven repo.
>> 
>> I put a link to the files I think you need on private@.  I can't put it
>> on dev@ because Adobe wants folks to accept licensing terms first.  I'm
>> assuming you've already accepted those terms bringing down Adobe bits for
>> Ant or Flex.  If users need to get around this then we'll spend more time
>> figuring out why it isn't working for some folks.  I seem to recall that
>> some more recent version of Maven was needed to launch the Mavenizer
>> automatically, but I can't find information on what version.  IIRC, older
>> versions of Maven can build all of Royale but can't automate the Adobe
>> downloads.
>> 
>> HTH,
>> -Alex
>> 
>> On 11/15/18, 10:41 PM, "Harbs"  wrote:
>> 
>>There are the env variables I’m using for all my builds:
>> 
>>#!/bin/sh
>> 
>>export ROYALE_COMPILER_REPO=/Apache/royale-compiler
>>export FLEX_SDK_HOME=/FlexSDK/4.14.1
>>export AIR_HOME=/Apache/frameworks/AIRSDK_Compiler
>>export PLAYERGLOBAL_HOME=/Apache/frameworks/libs/player
>>export FLASHPLAYER_DEBUGGER=/Apache/frameworks/Flash\ Player\
>> Debugger.app/Contents/MacOS/Flash\ Player\ Debugger
>>export ROYALE_HOME=/Apache/royale-asjs
>> 
>>The Ant build seems to succeed. I thought Maven does not use
>> environment variables?
>> 
>>Either way, I think I can vote for this RC. The fact that Maven is
>> failing is nothing new on my end… ;-)
>> 
>>Harbs
>> 
>>> On Nov 16, 2018, at 6:21 AM, Alex Harui 
>> wrote:
>>> 
>>> It appears that there is something mixed up with your environment
>> variables.
>>> 
>>> The tests check for PLAYERGLOBAL_HOME, AIR_HOME, and
>> FLASHPLAYER_DEBUGGER.  I think all 3 have to be set or none have to be
>> set.  If some are set, it can confuse the tests.  If all 3 are set, the
>> tests should use playerglobal/airglobal and generate a SWF and run it in
>> the debugger player.  If none are set, the tests should use js.swc to
>> generate a swf, but the swf is not run (since it wouldn't work without
>> playerglobal).  Instead, it is swfdump'd and the output is compared against
>> a prior swfdump.
>>> 
>>> The output shows that js.swc is being used in the compile, but the
>> swf is being run in the debugger player.
>>> 
>>> HTH,
>>> -Alex
>>> 
>>> On 11/15/18, 4:59 PM, "Harbs"  wrote:
>>> 
>>> 
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2FyBNfdata=02%7C01%7Caharui%40adobe.com%7C7931243fa0004c78011308d64b8e89f6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779472910908290sdata=EzNAtqfkryWkRDjATNbf6rxN1TfudGCWR6qW5uOeIlQ%3Dreserved=0
>>> 
 On Nov 16, 2018, at 2:27 AM, Alex Harui 
>> wrote:
 
 Look in compiler/target/failsafe-reports and see what tests
>> failed.  I have to step away from my computer for about 3 hours.
 
 -Alex
 
 On 11/15/18, 4:18 PM, "Harbs"  wrote:
 
  The ant build passed, but the Maven build failed:
 
  [INFO] --- maven-dependency-plugin:3.0.0:analyze-only (analyze) @
>> compiler ---
  [WARNING] Used undeclared dependencies found:
  [WARNING]org.antlr:antlr-runtime:jar:3.3:compile
  

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Piotr Zarzycki]

Here is the steps:

1) You are preparing Maven settings file which pointing to staged artifacts
[1]
2) Pickup one of the example and for simplicity place there prepared file
3) Build example with following command:  mvn -s settings-template.xml
clean install

[1] https://paste.apache.org/MUAD

Piotr

pt., 16 lis 2018 o 13:32 Harbs  napisał(a):

> > Do you mean trust folder for Flash Player ?
>
> Yes.
>
> I’m able to compile a project using the ant build locally.
>
> I have no idea how to build using the Maven artifacts, so I can’t test
> that…
>
> > On Nov 16, 2018, at 2:18 PM, Piotr Zarzycki 
> wrote:
> >
> > Hi Harbs,
> >
> > Do you mean trust folder for Flash Player ? Maybe trusting whole folder
> is
> > a good idea, but I got Maven build working. However building simple
> project
> > is not working so that is the issue which I'm more concern right now.
> >
> > Cause you guys proof that Ant is working on your machines, Maven is
> working
> > on mine, that's fine for me to give +0. However examples should also work
> > with artifacts.
> >
> > Piotr
> >
> > pt., 16 lis 2018 o 13:10 Harbs  napisał(a):
> >
> >> What do you have in the trust files? I generally build from the same
> >> parent folder as the repo and I have the whole folder trusted. The
> >> auto-generated trust files do not always work for me.
> >>
> >>> On Nov 16, 2018, at 10:32 AM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> >> wrote:
> >>>
> >>> I got again the same timeout, so no option for me build project by ant
> >> [1].
> >>> I will try Maven.
> >>>
> >>> [1] https://paste.apache.org/6UPt
> >>>
> >>> pt., 16 lis 2018 o 09:28 Greg Dove  napisał(a):
> >>>
>  I had that issue when I first set up again on my new machine last
> >> month. At
>  the time I manually installed the swcs in my local .m2
> 
>  If I recall correctly I also looked at the MavenTestAdapter to try to
>  figure out what was wrong at the time. I think if it has one thing
> >> defined
>  and not another it was sending js actionscript to test on swf and
> >> giving an
>  error saying the the Document class was not Sprite (or something
> >> similar).
>  I figured it was just me at the time, and I think it went away after I
> >> have
>  the air/playerglobal swcs installed in .m2
> 
>  I today's build I got the 'super-download' sequence that took ages,
> and
>  maven put all that stuff there, and also did prompt me for licence
>  acceptance.
>  It offered a setting for the future:
> 
> >>
> -Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=
> 
>  Followed by a pregenerated hash representing the machine I am now
> using.
> 
>  So I guess it would be possible to use that in the future, but I
> imagine
>  that now they are in my local .m2 cache, I will not need to anyway.
> 
>  Don't know if there's anything helpful there, hope it might be
> 
> 
> 
> 
>  On Fri, Nov 16, 2018 at 8:30 PM Alex Harui 
>  wrote:
> 
> > I looked at MavenTestAdapter.  It looks like it uses environment
>  variables
> > for FLASHPLAYER_DEBUGGER, but it is expecting to find playerglobal as
> >> an
> > artifact in the local maven repo.
> >
> > I put a link to the files I think you need on private@.  I can't put
> >> it
> > on dev@ because Adobe wants folks to accept licensing terms first.
> >> I'm
> > assuming you've already accepted those terms bringing down Adobe bits
> >> for
> > Ant or Flex.  If users need to get around this then we'll spend more
> >> time
> > figuring out why it isn't working for some folks.  I seem to recall
> >> that
> > some more recent version of Maven was needed to launch the Mavenizer
> > automatically, but I can't find information on what version.  IIRC,
> >> older
> > versions of Maven can build all of Royale but can't automate the
> Adobe
> > downloads.
> >
> > HTH,
> > -Alex
> >
> > On 11/15/18, 10:41 PM, "Harbs"  wrote:
> >
> >   There are the env variables I’m using for all my builds:
> >
> >   #!/bin/sh
> >
> >   export ROYALE_COMPILER_REPO=/Apache/royale-compiler
> >   export FLEX_SDK_HOME=/FlexSDK/4.14.1
> >   export AIR_HOME=/Apache/frameworks/AIRSDK_Compiler
> >   export PLAYERGLOBAL_HOME=/Apache/frameworks/libs/player
> >   export FLASHPLAYER_DEBUGGER=/Apache/frameworks/Flash\ Player\
> > Debugger.app/Contents/MacOS/Flash\ Player\ Debugger
> >   export ROYALE_HOME=/Apache/royale-asjs
> >
> >   The Ant build seems to succeed. I thought Maven does not use
> > environment variables?
> >
> >   Either way, I think I can vote for this RC. The fact that Maven is
> > failing is nothing new on my end… ;-)
> >
> >   Harbs
> >
> >> On Nov 16, 2018, at 6:21 AM, Alex Harui 
> > wrote:
> >>
> >> It appears that there is something mixed up with your environment

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Harbs]

> Do you mean trust folder for Flash Player ?

Yes.

I’m able to compile a project using the ant build locally.

I have no idea how to build using the Maven artifacts, so I can’t test that…

> On Nov 16, 2018, at 2:18 PM, Piotr Zarzycki  wrote:
> 
> Hi Harbs,
> 
> Do you mean trust folder for Flash Player ? Maybe trusting whole folder is
> a good idea, but I got Maven build working. However building simple project
> is not working so that is the issue which I'm more concern right now.
> 
> Cause you guys proof that Ant is working on your machines, Maven is working
> on mine, that's fine for me to give +0. However examples should also work
> with artifacts.
> 
> Piotr
> 
> pt., 16 lis 2018 o 13:10 Harbs  napisał(a):
> 
>> What do you have in the trust files? I generally build from the same
>> parent folder as the repo and I have the whole folder trusted. The
>> auto-generated trust files do not always work for me.
>> 
>>> On Nov 16, 2018, at 10:32 AM, Piotr Zarzycki 
>> wrote:
>>> 
>>> I got again the same timeout, so no option for me build project by ant
>> [1].
>>> I will try Maven.
>>> 
>>> [1] https://paste.apache.org/6UPt
>>> 
>>> pt., 16 lis 2018 o 09:28 Greg Dove  napisał(a):
>>> 
 I had that issue when I first set up again on my new machine last
>> month. At
 the time I manually installed the swcs in my local .m2
 
 If I recall correctly I also looked at the MavenTestAdapter to try to
 figure out what was wrong at the time. I think if it has one thing
>> defined
 and not another it was sending js actionscript to test on swf and
>> giving an
 error saying the the Document class was not Sprite (or something
>> similar).
 I figured it was just me at the time, and I think it went away after I
>> have
 the air/playerglobal swcs installed in .m2
 
 I today's build I got the 'super-download' sequence that took ages, and
 maven put all that stuff there, and also did prompt me for licence
 acceptance.
 It offered a setting for the future:
 
>> -Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=
 
 Followed by a pregenerated hash representing the machine I am now using.
 
 So I guess it would be possible to use that in the future, but I imagine
 that now they are in my local .m2 cache, I will not need to anyway.
 
 Don't know if there's anything helpful there, hope it might be
 
 
 
 
 On Fri, Nov 16, 2018 at 8:30 PM Alex Harui 
 wrote:
 
> I looked at MavenTestAdapter.  It looks like it uses environment
 variables
> for FLASHPLAYER_DEBUGGER, but it is expecting to find playerglobal as
>> an
> artifact in the local maven repo.
> 
> I put a link to the files I think you need on private@.  I can't put
>> it
> on dev@ because Adobe wants folks to accept licensing terms first.
>> I'm
> assuming you've already accepted those terms bringing down Adobe bits
>> for
> Ant or Flex.  If users need to get around this then we'll spend more
>> time
> figuring out why it isn't working for some folks.  I seem to recall
>> that
> some more recent version of Maven was needed to launch the Mavenizer
> automatically, but I can't find information on what version.  IIRC,
>> older
> versions of Maven can build all of Royale but can't automate the Adobe
> downloads.
> 
> HTH,
> -Alex
> 
> On 11/15/18, 10:41 PM, "Harbs"  wrote:
> 
>   There are the env variables I’m using for all my builds:
> 
>   #!/bin/sh
> 
>   export ROYALE_COMPILER_REPO=/Apache/royale-compiler
>   export FLEX_SDK_HOME=/FlexSDK/4.14.1
>   export AIR_HOME=/Apache/frameworks/AIRSDK_Compiler
>   export PLAYERGLOBAL_HOME=/Apache/frameworks/libs/player
>   export FLASHPLAYER_DEBUGGER=/Apache/frameworks/Flash\ Player\
> Debugger.app/Contents/MacOS/Flash\ Player\ Debugger
>   export ROYALE_HOME=/Apache/royale-asjs
> 
>   The Ant build seems to succeed. I thought Maven does not use
> environment variables?
> 
>   Either way, I think I can vote for this RC. The fact that Maven is
> failing is nothing new on my end… ;-)
> 
>   Harbs
> 
>> On Nov 16, 2018, at 6:21 AM, Alex Harui 
> wrote:
>> 
>> It appears that there is something mixed up with your environment
> variables.
>> 
>> The tests check for PLAYERGLOBAL_HOME, AIR_HOME, and
> FLASHPLAYER_DEBUGGER.  I think all 3 have to be set or none have to be
> set.  If some are set, it can confuse the tests.  If all 3 are set, the
> tests should use playerglobal/airglobal and generate a SWF and run it
>> in
> the debugger player.  If none are set, the tests should use js.swc to
> generate a swf, but the swf is not run (since it wouldn't work without
> playerglobal).  Instead, it is swfdump'd and the output is compared
 against
> a prior swfdump.
>> 
>> The 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Piotr Zarzycki]

Hi Harbs,

Do you mean trust folder for Flash Player ? Maybe trusting whole folder is
a good idea, but I got Maven build working. However building simple project
is not working so that is the issue which I'm more concern right now.

Cause you guys proof that Ant is working on your machines, Maven is working
on mine, that's fine for me to give +0. However examples should also work
with artifacts.

Piotr

pt., 16 lis 2018 o 13:10 Harbs  napisał(a):

> What do you have in the trust files? I generally build from the same
> parent folder as the repo and I have the whole folder trusted. The
> auto-generated trust files do not always work for me.
>
> > On Nov 16, 2018, at 10:32 AM, Piotr Zarzycki 
> wrote:
> >
> > I got again the same timeout, so no option for me build project by ant
> [1].
> > I will try Maven.
> >
> > [1] https://paste.apache.org/6UPt
> >
> > pt., 16 lis 2018 o 09:28 Greg Dove  napisał(a):
> >
> >> I had that issue when I first set up again on my new machine last
> month. At
> >> the time I manually installed the swcs in my local .m2
> >>
> >> If I recall correctly I also looked at the MavenTestAdapter to try to
> >> figure out what was wrong at the time. I think if it has one thing
> defined
> >> and not another it was sending js actionscript to test on swf and
> giving an
> >> error saying the the Document class was not Sprite (or something
> similar).
> >> I figured it was just me at the time, and I think it went away after I
> have
> >> the air/playerglobal swcs installed in .m2
> >>
> >> I today's build I got the 'super-download' sequence that took ages, and
> >> maven put all that stuff there, and also did prompt me for licence
> >> acceptance.
> >> It offered a setting for the future:
> >>
> -Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=
> >>
> >> Followed by a pregenerated hash representing the machine I am now using.
> >>
> >> So I guess it would be possible to use that in the future, but I imagine
> >> that now they are in my local .m2 cache, I will not need to anyway.
> >>
> >> Don't know if there's anything helpful there, hope it might be
> >>
> >>
> >>
> >>
> >> On Fri, Nov 16, 2018 at 8:30 PM Alex Harui 
> >> wrote:
> >>
> >>> I looked at MavenTestAdapter.  It looks like it uses environment
> >> variables
> >>> for FLASHPLAYER_DEBUGGER, but it is expecting to find playerglobal as
> an
> >>> artifact in the local maven repo.
> >>>
> >>> I put a link to the files I think you need on private@.  I can't put
> it
> >>> on dev@ because Adobe wants folks to accept licensing terms first.
> I'm
> >>> assuming you've already accepted those terms bringing down Adobe bits
> for
> >>> Ant or Flex.  If users need to get around this then we'll spend more
> time
> >>> figuring out why it isn't working for some folks.  I seem to recall
> that
> >>> some more recent version of Maven was needed to launch the Mavenizer
> >>> automatically, but I can't find information on what version.  IIRC,
> older
> >>> versions of Maven can build all of Royale but can't automate the Adobe
> >>> downloads.
> >>>
> >>> HTH,
> >>> -Alex
> >>>
> >>> On 11/15/18, 10:41 PM, "Harbs"  wrote:
> >>>
> >>>There are the env variables I’m using for all my builds:
> >>>
> >>>#!/bin/sh
> >>>
> >>>export ROYALE_COMPILER_REPO=/Apache/royale-compiler
> >>>export FLEX_SDK_HOME=/FlexSDK/4.14.1
> >>>export AIR_HOME=/Apache/frameworks/AIRSDK_Compiler
> >>>export PLAYERGLOBAL_HOME=/Apache/frameworks/libs/player
> >>>export FLASHPLAYER_DEBUGGER=/Apache/frameworks/Flash\ Player\
> >>> Debugger.app/Contents/MacOS/Flash\ Player\ Debugger
> >>>export ROYALE_HOME=/Apache/royale-asjs
> >>>
> >>>The Ant build seems to succeed. I thought Maven does not use
> >>> environment variables?
> >>>
> >>>Either way, I think I can vote for this RC. The fact that Maven is
> >>> failing is nothing new on my end… ;-)
> >>>
> >>>Harbs
> >>>
>  On Nov 16, 2018, at 6:21 AM, Alex Harui 
> >>> wrote:
> 
>  It appears that there is something mixed up with your environment
> >>> variables.
> 
>  The tests check for PLAYERGLOBAL_HOME, AIR_HOME, and
> >>> FLASHPLAYER_DEBUGGER.  I think all 3 have to be set or none have to be
> >>> set.  If some are set, it can confuse the tests.  If all 3 are set, the
> >>> tests should use playerglobal/airglobal and generate a SWF and run it
> in
> >>> the debugger player.  If none are set, the tests should use js.swc to
> >>> generate a swf, but the swf is not run (since it wouldn't work without
> >>> playerglobal).  Instead, it is swfdump'd and the output is compared
> >> against
> >>> a prior swfdump.
> 
>  The output shows that js.swc is being used in the compile, but the
> >>> swf is being run in the debugger player.
> 
>  HTH,
>  -Alex
> 
>  On 11/15/18, 4:59 PM, "Harbs"  wrote:
> 
> 
> >>>
> >>
> 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Harbs]

What do you have in the trust files? I generally build from the same parent 
folder as the repo and I have the whole folder trusted. The auto-generated 
trust files do not always work for me.

> On Nov 16, 2018, at 10:32 AM, Piotr Zarzycki  
> wrote:
> 
> I got again the same timeout, so no option for me build project by ant [1].
> I will try Maven.
> 
> [1] https://paste.apache.org/6UPt
> 
> pt., 16 lis 2018 o 09:28 Greg Dove  napisał(a):
> 
>> I had that issue when I first set up again on my new machine last month. At
>> the time I manually installed the swcs in my local .m2
>> 
>> If I recall correctly I also looked at the MavenTestAdapter to try to
>> figure out what was wrong at the time. I think if it has one thing defined
>> and not another it was sending js actionscript to test on swf and giving an
>> error saying the the Document class was not Sprite (or something similar).
>> I figured it was just me at the time, and I think it went away after I have
>> the air/playerglobal swcs installed in .m2
>> 
>> I today's build I got the 'super-download' sequence that took ages, and
>> maven put all that stuff there, and also did prompt me for licence
>> acceptance.
>> It offered a setting for the future:
>> -Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=
>> 
>> Followed by a pregenerated hash representing the machine I am now using.
>> 
>> So I guess it would be possible to use that in the future, but I imagine
>> that now they are in my local .m2 cache, I will not need to anyway.
>> 
>> Don't know if there's anything helpful there, hope it might be
>> 
>> 
>> 
>> 
>> On Fri, Nov 16, 2018 at 8:30 PM Alex Harui 
>> wrote:
>> 
>>> I looked at MavenTestAdapter.  It looks like it uses environment
>> variables
>>> for FLASHPLAYER_DEBUGGER, but it is expecting to find playerglobal as an
>>> artifact in the local maven repo.
>>> 
>>> I put a link to the files I think you need on private@.  I can't put it
>>> on dev@ because Adobe wants folks to accept licensing terms first.  I'm
>>> assuming you've already accepted those terms bringing down Adobe bits for
>>> Ant or Flex.  If users need to get around this then we'll spend more time
>>> figuring out why it isn't working for some folks.  I seem to recall that
>>> some more recent version of Maven was needed to launch the Mavenizer
>>> automatically, but I can't find information on what version.  IIRC, older
>>> versions of Maven can build all of Royale but can't automate the Adobe
>>> downloads.
>>> 
>>> HTH,
>>> -Alex
>>> 
>>> On 11/15/18, 10:41 PM, "Harbs"  wrote:
>>> 
>>>There are the env variables I’m using for all my builds:
>>> 
>>>#!/bin/sh
>>> 
>>>export ROYALE_COMPILER_REPO=/Apache/royale-compiler
>>>export FLEX_SDK_HOME=/FlexSDK/4.14.1
>>>export AIR_HOME=/Apache/frameworks/AIRSDK_Compiler
>>>export PLAYERGLOBAL_HOME=/Apache/frameworks/libs/player
>>>export FLASHPLAYER_DEBUGGER=/Apache/frameworks/Flash\ Player\
>>> Debugger.app/Contents/MacOS/Flash\ Player\ Debugger
>>>export ROYALE_HOME=/Apache/royale-asjs
>>> 
>>>The Ant build seems to succeed. I thought Maven does not use
>>> environment variables?
>>> 
>>>Either way, I think I can vote for this RC. The fact that Maven is
>>> failing is nothing new on my end… ;-)
>>> 
>>>Harbs
>>> 
 On Nov 16, 2018, at 6:21 AM, Alex Harui 
>>> wrote:
 
 It appears that there is something mixed up with your environment
>>> variables.
 
 The tests check for PLAYERGLOBAL_HOME, AIR_HOME, and
>>> FLASHPLAYER_DEBUGGER.  I think all 3 have to be set or none have to be
>>> set.  If some are set, it can confuse the tests.  If all 3 are set, the
>>> tests should use playerglobal/airglobal and generate a SWF and run it in
>>> the debugger player.  If none are set, the tests should use js.swc to
>>> generate a swf, but the swf is not run (since it wouldn't work without
>>> playerglobal).  Instead, it is swfdump'd and the output is compared
>> against
>>> a prior swfdump.
 
 The output shows that js.swc is being used in the compile, but the
>>> swf is being run in the debugger player.
 
 HTH,
 -Alex
 
 On 11/15/18, 4:59 PM, "Harbs"  wrote:
 
 
>>> 
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2FyBNfdata=02%7C01%7Caharui%40adobe.com%7C7931243fa0004c78011308d64b8e89f6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779472910908290sdata=EzNAtqfkryWkRDjATNbf6rxN1TfudGCWR6qW5uOeIlQ%3Dreserved=0
 
> On Nov 16, 2018, at 2:27 AM, Alex Harui >> 
>>> wrote:
> 
> Look in compiler/target/failsafe-reports and see what tests
>>> failed.  I have to step away from my computer for about 3 hours.
> 
> -Alex
> 
> On 11/15/18, 4:18 PM, "Harbs"  wrote:
> 
>  The ant build passed, but the Maven build failed:
> 
>  [INFO] --- maven-dependency-plugin:3.0.0:analyze-only (analyze)
>> @
>>> compiler ---
>  [WARNING] Used undeclared 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Piotr Zarzycki]

If you think that above error is rather minor and I can overcome it somehow
I can vote for that release maximum +0 - If not I'm -1 due to above
problems.

pt., 16 lis 2018 o 11:28 Piotr Zarzycki 
napisał(a):

> I was able to build sources using Maven. It did failed for me for the
> first time with missing airglobal, but I have added it manually to maven
> cache and second attempt went fine.
> Later I decided to give a try and use staged artefacts to build one of the
> example. I have prepared settings file [1] and run build
> of DataBindingExample. I'm getting following error [2].
>
>
>1. Could not resolve dependencies for project org.apache.royale.
>examples:DataBindingExample:swf:0.9.4:
>2. Could not find artifact org.apache.royale.examples:examples-tests:
>jar:0.9.4
>3. in apache-releasecan (https://repository.apache.org/content/
>repositories/orgapacheroyale-1025/) -> [Help 1]
>4. [ERROR]
>
>
> [1] https://paste.apache.org/MUAD
> [2] https://paste.apache.org/O5C8
>
> Piotr
>
> pt., 16 lis 2018 o 10:06 Piotr Zarzycki 
> napisał(a):
>
>> I run those tests when I was trying to be RM previously and they were
>> working as far as I remember - From the repo.
>>
>> pt., 16 lis 2018 o 09:55 Alex Harui 
>> napisał(a):
>>
>>> Do the FlexUnit tests run when you build from the repo?
>>>
>>> Compare the FlexUnit being downloaded by the release with the one used
>>> by the repo tests.
>>>
>>> -Alex
>>>
>>> On 11/16/18, 12:32 AM, "Piotr Zarzycki" 
>>> wrote:
>>>
>>> I got again the same timeout, so no option for me build project by
>>> ant [1].
>>> I will try Maven.
>>>
>>> [1]
>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F6UPtdata=02%7C01%7Caharui%40adobe.com%7Cd8b9ff82ff9c481a23ff08d64b9e0feb%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779539571723668sdata=KOqUjui3kMSnFwGPfP8VDqgd2SF%2FrJSEXANq%2BFGaCE0%3Dreserved=0
>>>
>>> pt., 16 lis 2018 o 09:28 Greg Dove  napisał(a):
>>>
>>> > I had that issue when I first set up again on my new machine last
>>> month. At
>>> > the time I manually installed the swcs in my local .m2
>>> >
>>> > If I recall correctly I also looked at the MavenTestAdapter to try
>>> to
>>> > figure out what was wrong at the time. I think if it has one thing
>>> defined
>>> > and not another it was sending js actionscript to test on swf and
>>> giving an
>>> > error saying the the Document class was not Sprite (or something
>>> similar).
>>> > I figured it was just me at the time, and I think it went away
>>> after I have
>>> > the air/playerglobal swcs installed in .m2
>>> >
>>> > I today's build I got the 'super-download' sequence that took
>>> ages, and
>>> > maven put all that stuff there, and also did prompt me for licence
>>> > acceptance.
>>> > It offered a setting for the future:
>>> >
>>> -Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=
>>> >
>>> > Followed by a pregenerated hash representing the machine I am now
>>> using.
>>> >
>>> > So I guess it would be possible to use that in the future, but I
>>> imagine
>>> > that now they are in my local .m2 cache, I will not need to anyway.
>>> >
>>> > Don't know if there's anything helpful there, hope it might be
>>> >
>>> >
>>> >
>>> >
>>> > On Fri, Nov 16, 2018 at 8:30 PM Alex Harui
>>> 
>>> > wrote:
>>> >
>>> > > I looked at MavenTestAdapter.  It looks like it uses environment
>>> > variables
>>> > > for FLASHPLAYER_DEBUGGER, but it is expecting to find
>>> playerglobal as an
>>> > > artifact in the local maven repo.
>>> > >
>>> > > I put a link to the files I think you need on private@.  I
>>> can't put it
>>> > > on dev@ because Adobe wants folks to accept licensing terms
>>> first.  I'm
>>> > > assuming you've already accepted those terms bringing down Adobe
>>> bits for
>>> > > Ant or Flex.  If users need to get around this then we'll spend
>>> more time
>>> > > figuring out why it isn't working for some folks.  I seem to
>>> recall that
>>> > > some more recent version of Maven was needed to launch the
>>> Mavenizer
>>> > > automatically, but I can't find information on what version.
>>> IIRC, older
>>> > > versions of Maven can build all of Royale but can't automate the
>>> Adobe
>>> > > downloads.
>>> > >
>>> > > HTH,
>>> > > -Alex
>>> > >
>>> > > On 11/15/18, 10:41 PM, "Harbs"  wrote:
>>> > >
>>> > > There are the env variables I’m using for all my builds:
>>> > >
>>> > > #!/bin/sh
>>> > >
>>> > > export ROYALE_COMPILER_REPO=/Apache/royale-compiler
>>> > > export FLEX_SDK_HOME=/FlexSDK/4.14.1
>>> > > export AIR_HOME=/Apache/frameworks/AIRSDK_Compiler
>>> > > export PLAYERGLOBAL_HOME=/Apache/frameworks/libs/player
>>> > > export 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Piotr Zarzycki]

I was able to build sources using Maven. It did failed for me for the first
time with missing airglobal, but I have added it manually to maven cache
and second attempt went fine.
Later I decided to give a try and use staged artefacts to build one of the
example. I have prepared settings file [1] and run build
of DataBindingExample. I'm getting following error [2].


   1. Could not resolve dependencies for project org.apache.royale.examples:
   DataBindingExample:swf:0.9.4:
   2. Could not find artifact org.apache.royale.examples:examples-tests:jar:
   0.9.4
   3. in apache-releasecan (https://repository.apache.org/content/
   repositories/orgapacheroyale-1025/) -> [Help 1]
   4. [ERROR]


[1] https://paste.apache.org/MUAD
[2] https://paste.apache.org/O5C8

Piotr

pt., 16 lis 2018 o 10:06 Piotr Zarzycki 
napisał(a):

> I run those tests when I was trying to be RM previously and they were
> working as far as I remember - From the repo.
>
> pt., 16 lis 2018 o 09:55 Alex Harui  napisał(a):
>
>> Do the FlexUnit tests run when you build from the repo?
>>
>> Compare the FlexUnit being downloaded by the release with the one used by
>> the repo tests.
>>
>> -Alex
>>
>> On 11/16/18, 12:32 AM, "Piotr Zarzycki" 
>> wrote:
>>
>> I got again the same timeout, so no option for me build project by
>> ant [1].
>> I will try Maven.
>>
>> [1]
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F6UPtdata=02%7C01%7Caharui%40adobe.com%7Cd8b9ff82ff9c481a23ff08d64b9e0feb%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779539571723668sdata=KOqUjui3kMSnFwGPfP8VDqgd2SF%2FrJSEXANq%2BFGaCE0%3Dreserved=0
>>
>> pt., 16 lis 2018 o 09:28 Greg Dove  napisał(a):
>>
>> > I had that issue when I first set up again on my new machine last
>> month. At
>> > the time I manually installed the swcs in my local .m2
>> >
>> > If I recall correctly I also looked at the MavenTestAdapter to try
>> to
>> > figure out what was wrong at the time. I think if it has one thing
>> defined
>> > and not another it was sending js actionscript to test on swf and
>> giving an
>> > error saying the the Document class was not Sprite (or something
>> similar).
>> > I figured it was just me at the time, and I think it went away
>> after I have
>> > the air/playerglobal swcs installed in .m2
>> >
>> > I today's build I got the 'super-download' sequence that took ages,
>> and
>> > maven put all that stuff there, and also did prompt me for licence
>> > acceptance.
>> > It offered a setting for the future:
>> >
>> -Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=
>> >
>> > Followed by a pregenerated hash representing the machine I am now
>> using.
>> >
>> > So I guess it would be possible to use that in the future, but I
>> imagine
>> > that now they are in my local .m2 cache, I will not need to anyway.
>> >
>> > Don't know if there's anything helpful there, hope it might be
>> >
>> >
>> >
>> >
>> > On Fri, Nov 16, 2018 at 8:30 PM Alex Harui > >
>> > wrote:
>> >
>> > > I looked at MavenTestAdapter.  It looks like it uses environment
>> > variables
>> > > for FLASHPLAYER_DEBUGGER, but it is expecting to find
>> playerglobal as an
>> > > artifact in the local maven repo.
>> > >
>> > > I put a link to the files I think you need on private@.  I can't
>> put it
>> > > on dev@ because Adobe wants folks to accept licensing terms
>> first.  I'm
>> > > assuming you've already accepted those terms bringing down Adobe
>> bits for
>> > > Ant or Flex.  If users need to get around this then we'll spend
>> more time
>> > > figuring out why it isn't working for some folks.  I seem to
>> recall that
>> > > some more recent version of Maven was needed to launch the
>> Mavenizer
>> > > automatically, but I can't find information on what version.
>> IIRC, older
>> > > versions of Maven can build all of Royale but can't automate the
>> Adobe
>> > > downloads.
>> > >
>> > > HTH,
>> > > -Alex
>> > >
>> > > On 11/15/18, 10:41 PM, "Harbs"  wrote:
>> > >
>> > > There are the env variables I’m using for all my builds:
>> > >
>> > > #!/bin/sh
>> > >
>> > > export ROYALE_COMPILER_REPO=/Apache/royale-compiler
>> > > export FLEX_SDK_HOME=/FlexSDK/4.14.1
>> > > export AIR_HOME=/Apache/frameworks/AIRSDK_Compiler
>> > > export PLAYERGLOBAL_HOME=/Apache/frameworks/libs/player
>> > > export FLASHPLAYER_DEBUGGER=/Apache/frameworks/Flash\ Player\
>> > > Debugger.app/Contents/MacOS/Flash\ Player\ Debugger
>> > > export ROYALE_HOME=/Apache/royale-asjs
>> > >
>> > > The Ant build seems to succeed. I thought Maven does not use
>> > > environment variables?
>> > >
>> > > Either way, I think I can vote for this RC. The fact that
>> Maven is

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Piotr Zarzycki]

I run those tests when I was trying to be RM previously and they were
working as far as I remember - From the repo.

pt., 16 lis 2018 o 09:55 Alex Harui  napisał(a):

> Do the FlexUnit tests run when you build from the repo?
>
> Compare the FlexUnit being downloaded by the release with the one used by
> the repo tests.
>
> -Alex
>
> On 11/16/18, 12:32 AM, "Piotr Zarzycki" 
> wrote:
>
> I got again the same timeout, so no option for me build project by ant
> [1].
> I will try Maven.
>
> [1]
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F6UPtdata=02%7C01%7Caharui%40adobe.com%7Cd8b9ff82ff9c481a23ff08d64b9e0feb%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779539571723668sdata=KOqUjui3kMSnFwGPfP8VDqgd2SF%2FrJSEXANq%2BFGaCE0%3Dreserved=0
>
> pt., 16 lis 2018 o 09:28 Greg Dove  napisał(a):
>
> > I had that issue when I first set up again on my new machine last
> month. At
> > the time I manually installed the swcs in my local .m2
> >
> > If I recall correctly I also looked at the MavenTestAdapter to try to
> > figure out what was wrong at the time. I think if it has one thing
> defined
> > and not another it was sending js actionscript to test on swf and
> giving an
> > error saying the the Document class was not Sprite (or something
> similar).
> > I figured it was just me at the time, and I think it went away after
> I have
> > the air/playerglobal swcs installed in .m2
> >
> > I today's build I got the 'super-download' sequence that took ages,
> and
> > maven put all that stuff there, and also did prompt me for licence
> > acceptance.
> > It offered a setting for the future:
> >
> -Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=
> >
> > Followed by a pregenerated hash representing the machine I am now
> using.
> >
> > So I guess it would be possible to use that in the future, but I
> imagine
> > that now they are in my local .m2 cache, I will not need to anyway.
> >
> > Don't know if there's anything helpful there, hope it might be
> >
> >
> >
> >
> > On Fri, Nov 16, 2018 at 8:30 PM Alex Harui  >
> > wrote:
> >
> > > I looked at MavenTestAdapter.  It looks like it uses environment
> > variables
> > > for FLASHPLAYER_DEBUGGER, but it is expecting to find playerglobal
> as an
> > > artifact in the local maven repo.
> > >
> > > I put a link to the files I think you need on private@.  I can't
> put it
> > > on dev@ because Adobe wants folks to accept licensing terms
> first.  I'm
> > > assuming you've already accepted those terms bringing down Adobe
> bits for
> > > Ant or Flex.  If users need to get around this then we'll spend
> more time
> > > figuring out why it isn't working for some folks.  I seem to
> recall that
> > > some more recent version of Maven was needed to launch the
> Mavenizer
> > > automatically, but I can't find information on what version.
> IIRC, older
> > > versions of Maven can build all of Royale but can't automate the
> Adobe
> > > downloads.
> > >
> > > HTH,
> > > -Alex
> > >
> > > On 11/15/18, 10:41 PM, "Harbs"  wrote:
> > >
> > > There are the env variables I’m using for all my builds:
> > >
> > > #!/bin/sh
> > >
> > > export ROYALE_COMPILER_REPO=/Apache/royale-compiler
> > > export FLEX_SDK_HOME=/FlexSDK/4.14.1
> > > export AIR_HOME=/Apache/frameworks/AIRSDK_Compiler
> > > export PLAYERGLOBAL_HOME=/Apache/frameworks/libs/player
> > > export FLASHPLAYER_DEBUGGER=/Apache/frameworks/Flash\ Player\
> > > Debugger.app/Contents/MacOS/Flash\ Player\ Debugger
> > > export ROYALE_HOME=/Apache/royale-asjs
> > >
> > > The Ant build seems to succeed. I thought Maven does not use
> > > environment variables?
> > >
> > > Either way, I think I can vote for this RC. The fact that
> Maven is
> > > failing is nothing new on my end… ;-)
> > >
> > > Harbs
> > >
> > > > On Nov 16, 2018, at 6:21 AM, Alex Harui
> 
> > > wrote:
> > > >
> > > > It appears that there is something mixed up with your
> environment
> > > variables.
> > > >
> > > > The tests check for PLAYERGLOBAL_HOME, AIR_HOME, and
> > > FLASHPLAYER_DEBUGGER.  I think all 3 have to be set or none have
> to be
> > > set.  If some are set, it can confuse the tests.  If all 3 are
> set, the
> > > tests should use playerglobal/airglobal and generate a SWF and run
> it in
> > > the debugger player.  If none are set, the tests should use js.swc
> to
> > > generate a swf, but the swf is not run (since it wouldn't work
> without
> > > playerglobal).  Instead, it is swfdump'd and the output is compared
> > against
> > > a prior swfdump.
> > > >
> > > > The 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Alex Harui]

Do the FlexUnit tests run when you build from the repo?

Compare the FlexUnit being downloaded by the release with the one used by the 
repo tests.

-Alex

On 11/16/18, 12:32 AM, "Piotr Zarzycki"  wrote:

I got again the same timeout, so no option for me build project by ant [1].
I will try Maven.

[1] 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F6UPtdata=02%7C01%7Caharui%40adobe.com%7Cd8b9ff82ff9c481a23ff08d64b9e0feb%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779539571723668sdata=KOqUjui3kMSnFwGPfP8VDqgd2SF%2FrJSEXANq%2BFGaCE0%3Dreserved=0

pt., 16 lis 2018 o 09:28 Greg Dove  napisał(a):

> I had that issue when I first set up again on my new machine last month. 
At
> the time I manually installed the swcs in my local .m2
>
> If I recall correctly I also looked at the MavenTestAdapter to try to
> figure out what was wrong at the time. I think if it has one thing defined
> and not another it was sending js actionscript to test on swf and giving 
an
> error saying the the Document class was not Sprite (or something similar).
> I figured it was just me at the time, and I think it went away after I 
have
> the air/playerglobal swcs installed in .m2
>
> I today's build I got the 'super-download' sequence that took ages, and
> maven put all that stuff there, and also did prompt me for licence
> acceptance.
> It offered a setting for the future:
> 
-Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=
>
> Followed by a pregenerated hash representing the machine I am now using.
>
> So I guess it would be possible to use that in the future, but I imagine
> that now they are in my local .m2 cache, I will not need to anyway.
>
> Don't know if there's anything helpful there, hope it might be
>
>
>
>
> On Fri, Nov 16, 2018 at 8:30 PM Alex Harui 
> wrote:
>
> > I looked at MavenTestAdapter.  It looks like it uses environment
> variables
> > for FLASHPLAYER_DEBUGGER, but it is expecting to find playerglobal as an
> > artifact in the local maven repo.
> >
> > I put a link to the files I think you need on private@.  I can't put it
> > on dev@ because Adobe wants folks to accept licensing terms first.  I'm
> > assuming you've already accepted those terms bringing down Adobe bits 
for
> > Ant or Flex.  If users need to get around this then we'll spend more 
time
> > figuring out why it isn't working for some folks.  I seem to recall that
> > some more recent version of Maven was needed to launch the Mavenizer
> > automatically, but I can't find information on what version.  IIRC, 
older
> > versions of Maven can build all of Royale but can't automate the Adobe
> > downloads.
> >
> > HTH,
> > -Alex
> >
> > On 11/15/18, 10:41 PM, "Harbs"  wrote:
> >
> > There are the env variables I’m using for all my builds:
> >
> > #!/bin/sh
> >
> > export ROYALE_COMPILER_REPO=/Apache/royale-compiler
> > export FLEX_SDK_HOME=/FlexSDK/4.14.1
> > export AIR_HOME=/Apache/frameworks/AIRSDK_Compiler
> > export PLAYERGLOBAL_HOME=/Apache/frameworks/libs/player
> > export FLASHPLAYER_DEBUGGER=/Apache/frameworks/Flash\ Player\
> > Debugger.app/Contents/MacOS/Flash\ Player\ Debugger
> > export ROYALE_HOME=/Apache/royale-asjs
> >
> > The Ant build seems to succeed. I thought Maven does not use
> > environment variables?
> >
> > Either way, I think I can vote for this RC. The fact that Maven is
> > failing is nothing new on my end… ;-)
> >
> > Harbs
> >
> > > On Nov 16, 2018, at 6:21 AM, Alex Harui 
> > wrote:
> > >
> > > It appears that there is something mixed up with your environment
> > variables.
> > >
> > > The tests check for PLAYERGLOBAL_HOME, AIR_HOME, and
> > FLASHPLAYER_DEBUGGER.  I think all 3 have to be set or none have to be
> > set.  If some are set, it can confuse the tests.  If all 3 are set, the
> > tests should use playerglobal/airglobal and generate a SWF and run it in
> > the debugger player.  If none are set, the tests should use js.swc to
> > generate a swf, but the swf is not run (since it wouldn't work without
> > playerglobal).  Instead, it is swfdump'd and the output is compared
> against
> > a prior swfdump.
> > >
> > > The output shows that js.swc is being used in the compile, but the
> > swf is being run in the debugger player.
> > >
> > > HTH,
> > > -Alex
> > >
> > > On 11/15/18, 4:59 PM, "Harbs"  wrote:
> > >
> > >
> >
> 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Harbs]

Replacing my adobe folder did the trick. I’m not sure which were the files 
which did it though. I’ll send you my original folder privately. Maybe that’ll 
help pinpoint the problem…

Harbs

> On Nov 16, 2018, at 9:30 AM, Alex Harui  wrote:
> 
> I looked at MavenTestAdapter.  It looks like it uses environment variables 
> for FLASHPLAYER_DEBUGGER, but it is expecting to find playerglobal as an 
> artifact in the local maven repo.
> 
> I put a link to the files I think you need on private@.  I can't put it on 
> dev@ because Adobe wants folks to accept licensing terms first.  I'm assuming 
> you've already accepted those terms bringing down Adobe bits for Ant or Flex. 
>  If users need to get around this then we'll spend more time figuring out why 
> it isn't working for some folks.  I seem to recall that some more recent 
> version of Maven was needed to launch the Mavenizer automatically, but I 
> can't find information on what version.  IIRC, older versions of Maven can 
> build all of Royale but can't automate the Adobe downloads.
> 
> HTH,
> -Alex
> 
> On 11/15/18, 10:41 PM, "Harbs"  > wrote:
> 
>There are the env variables I’m using for all my builds:
> 
>#!/bin/sh
> 
>export ROYALE_COMPILER_REPO=/Apache/royale-compiler
>export FLEX_SDK_HOME=/FlexSDK/4.14.1 
>export AIR_HOME=/Apache/frameworks/AIRSDK_Compiler
>export PLAYERGLOBAL_HOME=/Apache/frameworks/libs/player 
>export FLASHPLAYER_DEBUGGER=/Apache/frameworks/Flash\ Player\ 
> Debugger.app/Contents/MacOS/Flash\ Player\ Debugger
>export ROYALE_HOME=/Apache/royale-asjs
> 
>The Ant build seems to succeed. I thought Maven does not use environment 
> variables?
> 
>Either way, I think I can vote for this RC. The fact that Maven is failing 
> is nothing new on my end… ;-)
> 
>Harbs
> 
>> On Nov 16, 2018, at 6:21 AM, Alex Harui  wrote:
>> 
>> It appears that there is something mixed up with your environment variables.
>> 
>> The tests check for PLAYERGLOBAL_HOME, AIR_HOME, and FLASHPLAYER_DEBUGGER.  
>> I think all 3 have to be set or none have to be set.  If some are set, it 
>> can confuse the tests.  If all 3 are set, the tests should use 
>> playerglobal/airglobal and generate a SWF and run it in the debugger player. 
>>  If none are set, the tests should use js.swc to generate a swf, but the swf 
>> is not run (since it wouldn't work without playerglobal).  Instead, it is 
>> swfdump'd and the output is compared against a prior swfdump.
>> 
>> The output shows that js.swc is being used in the compile, but the swf is 
>> being run in the debugger player.
>> 
>> HTH,
>> -Alex
>> 
>> On 11/15/18, 4:59 PM, "Harbs"  wrote:
>> 
>>   
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2FyBNfdata=02%7C01%7Caharui%40adobe.com%7C7931243fa0004c78011308d64b8e89f6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779472910908290sdata=EzNAtqfkryWkRDjATNbf6rxN1TfudGCWR6qW5uOeIlQ%3Dreserved=0
>>  
>> 
>> 
>>> On Nov 16, 2018, at 2:27 AM, Alex Harui >> > wrote:
>>> 
>>> Look in compiler/target/failsafe-reports and see what tests failed.  I have 
>>> to step away from my computer for about 3 hours.
>>> 
>>> -Alex
>>> 
>>> On 11/15/18, 4:18 PM, "Harbs" >> > wrote:
>>> 
>>>  The ant build passed, but the Maven build failed:
>>> 
>>>  [INFO] --- maven-dependency-plugin:3.0.0:analyze-only (analyze) @ compiler 
>>> ---
>>>  [WARNING] Used undeclared dependencies found:
>>>  [WARNING]org.antlr:antlr-runtime:jar:3.3:compile
>>>  [WARNING]antlr:antlr:jar:2.7.7:compile
>>>  [WARNING] Unused declared dependencies found:
>>>  [WARNING]de.jflex:jflex:jar:1.6.0:compile
>>>  [WARNING]org.antlr:antlr:jar:3.3:compile
>>>  [WARNING]net.sourceforge.jburg:jburg:jar:1.10.3:compile
>>>  [WARNING]
>>> org.apache.royale.compiler:compiler-jburg-types:jar:1.0.0:compile
>>>  [WARNING]org.apache.royale.compiler:compiler-externc:jar:0.9.4:compile
>>>  [INFO] 
>>>  [INFO] --- maven-failsafe-plugin:2.18.1:verify (default) @ compiler ---
>>>  [INFO] Failsafe report directory: 
>>> /Apache/approve/apache-royale-0.9.4-maven-src/royale-compiler/compiler/target/failsafe-reports
>>>  [INFO] 
>>> 
>>>  [INFO] Reactor Summary:
>>>  [INFO] 
>>>  [INFO] Apache Royale: Compiler: Parent  SUCCESS [  
>>> 4.354 s]
>>>  [INFO] Apache Royale: Compiler: Compiler-Common ... SUCCESS [  
>>> 8.928 s]
>>>  [INFO] Apache Royale: Compiler: Test Utils  SUCCESS [  
>>> 0.945 s]
>>>  [INFO] Apache Royale: Compiler: Externc 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Piotr Zarzycki]

I got again the same timeout, so no option for me build project by ant [1].
I will try Maven.

[1] https://paste.apache.org/6UPt

pt., 16 lis 2018 o 09:28 Greg Dove  napisał(a):

> I had that issue when I first set up again on my new machine last month. At
> the time I manually installed the swcs in my local .m2
>
> If I recall correctly I also looked at the MavenTestAdapter to try to
> figure out what was wrong at the time. I think if it has one thing defined
> and not another it was sending js actionscript to test on swf and giving an
> error saying the the Document class was not Sprite (or something similar).
> I figured it was just me at the time, and I think it went away after I have
> the air/playerglobal swcs installed in .m2
>
> I today's build I got the 'super-download' sequence that took ages, and
> maven put all that stuff there, and also did prompt me for licence
> acceptance.
> It offered a setting for the future:
> -Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=
>
> Followed by a pregenerated hash representing the machine I am now using.
>
> So I guess it would be possible to use that in the future, but I imagine
> that now they are in my local .m2 cache, I will not need to anyway.
>
> Don't know if there's anything helpful there, hope it might be
>
>
>
>
> On Fri, Nov 16, 2018 at 8:30 PM Alex Harui 
> wrote:
>
> > I looked at MavenTestAdapter.  It looks like it uses environment
> variables
> > for FLASHPLAYER_DEBUGGER, but it is expecting to find playerglobal as an
> > artifact in the local maven repo.
> >
> > I put a link to the files I think you need on private@.  I can't put it
> > on dev@ because Adobe wants folks to accept licensing terms first.  I'm
> > assuming you've already accepted those terms bringing down Adobe bits for
> > Ant or Flex.  If users need to get around this then we'll spend more time
> > figuring out why it isn't working for some folks.  I seem to recall that
> > some more recent version of Maven was needed to launch the Mavenizer
> > automatically, but I can't find information on what version.  IIRC, older
> > versions of Maven can build all of Royale but can't automate the Adobe
> > downloads.
> >
> > HTH,
> > -Alex
> >
> > On 11/15/18, 10:41 PM, "Harbs"  wrote:
> >
> > There are the env variables I’m using for all my builds:
> >
> > #!/bin/sh
> >
> > export ROYALE_COMPILER_REPO=/Apache/royale-compiler
> > export FLEX_SDK_HOME=/FlexSDK/4.14.1
> > export AIR_HOME=/Apache/frameworks/AIRSDK_Compiler
> > export PLAYERGLOBAL_HOME=/Apache/frameworks/libs/player
> > export FLASHPLAYER_DEBUGGER=/Apache/frameworks/Flash\ Player\
> > Debugger.app/Contents/MacOS/Flash\ Player\ Debugger
> > export ROYALE_HOME=/Apache/royale-asjs
> >
> > The Ant build seems to succeed. I thought Maven does not use
> > environment variables?
> >
> > Either way, I think I can vote for this RC. The fact that Maven is
> > failing is nothing new on my end… ;-)
> >
> > Harbs
> >
> > > On Nov 16, 2018, at 6:21 AM, Alex Harui 
> > wrote:
> > >
> > > It appears that there is something mixed up with your environment
> > variables.
> > >
> > > The tests check for PLAYERGLOBAL_HOME, AIR_HOME, and
> > FLASHPLAYER_DEBUGGER.  I think all 3 have to be set or none have to be
> > set.  If some are set, it can confuse the tests.  If all 3 are set, the
> > tests should use playerglobal/airglobal and generate a SWF and run it in
> > the debugger player.  If none are set, the tests should use js.swc to
> > generate a swf, but the swf is not run (since it wouldn't work without
> > playerglobal).  Instead, it is swfdump'd and the output is compared
> against
> > a prior swfdump.
> > >
> > > The output shows that js.swc is being used in the compile, but the
> > swf is being run in the debugger player.
> > >
> > > HTH,
> > > -Alex
> > >
> > > On 11/15/18, 4:59 PM, "Harbs"  wrote:
> > >
> > >
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2FyBNfdata=02%7C01%7Caharui%40adobe.com%7C7931243fa0004c78011308d64b8e89f6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779472910908290sdata=EzNAtqfkryWkRDjATNbf6rxN1TfudGCWR6qW5uOeIlQ%3Dreserved=0
> > >
> > >> On Nov 16, 2018, at 2:27 AM, Alex Harui  >
> > wrote:
> > >>
> > >> Look in compiler/target/failsafe-reports and see what tests
> > failed.  I have to step away from my computer for about 3 hours.
> > >>
> > >> -Alex
> > >>
> > >> On 11/15/18, 4:18 PM, "Harbs"  wrote:
> > >>
> > >>   The ant build passed, but the Maven build failed:
> > >>
> > >>   [INFO] --- maven-dependency-plugin:3.0.0:analyze-only (analyze)
> @
> > compiler ---
> > >>   [WARNING] Used undeclared dependencies found:
> > >>   [WARNING]org.antlr:antlr-runtime:jar:3.3:compile
> > >>   [WARNING]antlr:antlr:jar:2.7.7:compile
> > >>   [WARNING] Unused declared 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Greg Dove]

I had that issue when I first set up again on my new machine last month. At
the time I manually installed the swcs in my local .m2

If I recall correctly I also looked at the MavenTestAdapter to try to
figure out what was wrong at the time. I think if it has one thing defined
and not another it was sending js actionscript to test on swf and giving an
error saying the the Document class was not Sprite (or something similar).
I figured it was just me at the time, and I think it went away after I have
the air/playerglobal swcs installed in .m2

I today's build I got the 'super-download' sequence that took ages, and
maven put all that stuff there, and also did prompt me for licence
acceptance.
It offered a setting for the future:
-Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=

Followed by a pregenerated hash representing the machine I am now using.

So I guess it would be possible to use that in the future, but I imagine
that now they are in my local .m2 cache, I will not need to anyway.

Don't know if there's anything helpful there, hope it might be




On Fri, Nov 16, 2018 at 8:30 PM Alex Harui  wrote:

> I looked at MavenTestAdapter.  It looks like it uses environment variables
> for FLASHPLAYER_DEBUGGER, but it is expecting to find playerglobal as an
> artifact in the local maven repo.
>
> I put a link to the files I think you need on private@.  I can't put it
> on dev@ because Adobe wants folks to accept licensing terms first.  I'm
> assuming you've already accepted those terms bringing down Adobe bits for
> Ant or Flex.  If users need to get around this then we'll spend more time
> figuring out why it isn't working for some folks.  I seem to recall that
> some more recent version of Maven was needed to launch the Mavenizer
> automatically, but I can't find information on what version.  IIRC, older
> versions of Maven can build all of Royale but can't automate the Adobe
> downloads.
>
> HTH,
> -Alex
>
> On 11/15/18, 10:41 PM, "Harbs"  wrote:
>
> There are the env variables I’m using for all my builds:
>
> #!/bin/sh
>
> export ROYALE_COMPILER_REPO=/Apache/royale-compiler
> export FLEX_SDK_HOME=/FlexSDK/4.14.1
> export AIR_HOME=/Apache/frameworks/AIRSDK_Compiler
> export PLAYERGLOBAL_HOME=/Apache/frameworks/libs/player
> export FLASHPLAYER_DEBUGGER=/Apache/frameworks/Flash\ Player\
> Debugger.app/Contents/MacOS/Flash\ Player\ Debugger
> export ROYALE_HOME=/Apache/royale-asjs
>
> The Ant build seems to succeed. I thought Maven does not use
> environment variables?
>
> Either way, I think I can vote for this RC. The fact that Maven is
> failing is nothing new on my end… ;-)
>
> Harbs
>
> > On Nov 16, 2018, at 6:21 AM, Alex Harui 
> wrote:
> >
> > It appears that there is something mixed up with your environment
> variables.
> >
> > The tests check for PLAYERGLOBAL_HOME, AIR_HOME, and
> FLASHPLAYER_DEBUGGER.  I think all 3 have to be set or none have to be
> set.  If some are set, it can confuse the tests.  If all 3 are set, the
> tests should use playerglobal/airglobal and generate a SWF and run it in
> the debugger player.  If none are set, the tests should use js.swc to
> generate a swf, but the swf is not run (since it wouldn't work without
> playerglobal).  Instead, it is swfdump'd and the output is compared against
> a prior swfdump.
> >
> > The output shows that js.swc is being used in the compile, but the
> swf is being run in the debugger player.
> >
> > HTH,
> > -Alex
> >
> > On 11/15/18, 4:59 PM, "Harbs"  wrote:
> >
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2FyBNfdata=02%7C01%7Caharui%40adobe.com%7C7931243fa0004c78011308d64b8e89f6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779472910908290sdata=EzNAtqfkryWkRDjATNbf6rxN1TfudGCWR6qW5uOeIlQ%3Dreserved=0
> >
> >> On Nov 16, 2018, at 2:27 AM, Alex Harui 
> wrote:
> >>
> >> Look in compiler/target/failsafe-reports and see what tests
> failed.  I have to step away from my computer for about 3 hours.
> >>
> >> -Alex
> >>
> >> On 11/15/18, 4:18 PM, "Harbs"  wrote:
> >>
> >>   The ant build passed, but the Maven build failed:
> >>
> >>   [INFO] --- maven-dependency-plugin:3.0.0:analyze-only (analyze) @
> compiler ---
> >>   [WARNING] Used undeclared dependencies found:
> >>   [WARNING]org.antlr:antlr-runtime:jar:3.3:compile
> >>   [WARNING]antlr:antlr:jar:2.7.7:compile
> >>   [WARNING] Unused declared dependencies found:
> >>   [WARNING]de.jflex:jflex:jar:1.6.0:compile
> >>   [WARNING]org.antlr:antlr:jar:3.3:compile
> >>   [WARNING]net.sourceforge.jburg:jburg:jar:1.10.3:compile
> >>   [WARNING]
> org.apache.royale.compiler:compiler-jburg-types:jar:1.0.0:compile
> >>   [WARNING]
> org.apache.royale.compiler:compiler-externc:jar:0.9.4:compile
> >>   [INFO]
> >>   [INFO] 

Re: Lets talk a bit about the release process (was Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2)

[Carlos Rovira]

I think publish Apache Royale release artifacts is a must. In my case maven
is a must and I think to have success in the IT world (that is where Flex
had success) will be a must as well.

Just my 2...

El vie., 16 nov. 2018 a las 1:02, Alex Harui ()
escribió:

> As many of you know, Maven makes a lot of assumptions and does a fair
> amount of work in each assumption.  So, for example, when you run "mvn
> install", it runs several steps including the build and copies it to the
> local repo.  Imagine the number of lines of Ant code required to do the
> same.
>
> I am told that the app that you run when you go to the ASF Maven Staging
> Repo in your browser (repository.a.o)  also has a pile of assumptions.  So
> when we copy artifacts up there and tell the app to  "close" a staging
> repository, it runs several steps that would amount to a huge pile of Ant
> scripting.  And later, when it is time to push it all to Maven Central, it
> can do that as well.
>
> Similarly, Maven's "release" plugin makes assumptions that the ASF Maven
> Staging Repo expects.  So it packages up sources, makes checksums, signs
> artifacts and pushes them to the staging repo.  That would also require a
> lot of Ant scripting to do, although some of it, like a source artifact
> per-jar, IMO, is not absolutely required.
>
> So, that's why I think it is the right thing, assuming we want to publish
> Maven artifacts for our releases, which I think we do want to do.  It is
> far less work on the RM to maintain less verbose Ant scripts which are
> already pretty long.  The assumption that you have reliable high-speed
> internet connections shouldn't be that hard to meet these days, but the
> Repo server did seem to care, or maybe it was my home router that got
> overwhelmed and dropped packets.  Not sure.  All I know is that I saw it
> work without tweaking any network settings.
>
> HTH,
> -Alex
>
> On 11/15/18, 11:37 AM, "OmPrakash Muppirala" 
> wrote:
>
> On Thu, Nov 15, 2018 at 2:02 AM Alex Harui 
> wrote:
>
> > To be clear:  the process DOES NOT upload artifacts to Maven
> Central.  It
> > uploads to the ASF staging repo.  Only after we approve the release
> do the
> > artifacts get pushed to Maven Central.  One of the RMs got an error
> > DOWNLOADING a Maven plugin from Maven Central.  There is nothing
> wrong with
> > doing that.
> >
>
> Sorry, I misspoke.  But the question remains.  Why do we need to
> upload it
> to the staging server during building or testing a release candidate?
> Can
> we not just use the local m2 repository for this?
>
> In other words, what aspect of the release are we actually testing by
> uploading stuff to the staging repo?
>
>
>
> >
> > Any volunteer is welcome to re-do the release scripts.  What we have
> now
> > is what I think was the simplest sequence for creating both Maven and
> > non-Maven artifacts.  Maven was the number 1 asked for feature in
> Adobe
> > Flex.  IIRC, it had 100 votes and 2nd place was 12 votes.  So we
> support
> > Maven in hopes that the customers we want to attract are using
> Maven, plus
> > at least Carlos prefers to use Maven.
> >
> > Just like any other code or script in Royale, there can be bugs and
> room
> > for improvement in the release process.  I found and fixed some
> issues, and
> > hopefully the next RM will try the scripts after a month or so
> instead of 6
> > months so fewer things will have become stale and broken.  In fact,
> I
> > think I will say that RC2 is my last RC for a while.  If we need an
> RC3,
> > someone else should create it since the know the scripts recently
> worked
> > for me.  And since it is fresh in my mind, I might be able to help
> the next
> > RM better.  I think the problems Piotr and Yishay hit have been
> addressed.
> > The only remaining issue is upload/download issues.
> >
>
> Thanks for getting the scripts to this shape!
>
> Regards,
> Om
>
>
> >
> > Thanks,
> > -Alex
> >
> > On 11/14/18, 10:36 PM, "OmPrakash Muppirala" 
> > wrote:
> >
> > Personally, I am not sure why we are uploading stuff to maven
> central
> > as
> > part of the RC process.  Can we simply bundle the source files
> and
> > create a
> > release candidate?  Folks who want to test maven can run the
> maven
> > scripts
> > locally which would copy stuff to the local .m2 repo instead.
> > That way we dont force maven on folks who dont need it.
> >
> > Thoughts?
> >
> > Thanks,
> > Om
> >
> >
> >
> > On Wed, Nov 14, 2018 at 12:54 PM Carlos Rovira <
> > carlosrov...@apache.org>
> > wrote:
> >
> > > Hi Alex,
> > >
> > > first congrats to reach to this point. After many months is
> great to
> > > finally can release :)
> > >
> > > I forked the 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Alex Harui]

I looked at MavenTestAdapter.  It looks like it uses environment variables for 
FLASHPLAYER_DEBUGGER, but it is expecting to find playerglobal as an artifact 
in the local maven repo.

I put a link to the files I think you need on private@.  I can't put it on dev@ 
because Adobe wants folks to accept licensing terms first.  I'm assuming you've 
already accepted those terms bringing down Adobe bits for Ant or Flex.  If 
users need to get around this then we'll spend more time figuring out why it 
isn't working for some folks.  I seem to recall that some more recent version 
of Maven was needed to launch the Mavenizer automatically, but I can't find 
information on what version.  IIRC, older versions of Maven can build all of 
Royale but can't automate the Adobe downloads.

HTH,
-Alex

On 11/15/18, 10:41 PM, "Harbs"  wrote:

There are the env variables I’m using for all my builds:

#!/bin/sh

export ROYALE_COMPILER_REPO=/Apache/royale-compiler
export FLEX_SDK_HOME=/FlexSDK/4.14.1 
export AIR_HOME=/Apache/frameworks/AIRSDK_Compiler
export PLAYERGLOBAL_HOME=/Apache/frameworks/libs/player 
export FLASHPLAYER_DEBUGGER=/Apache/frameworks/Flash\ Player\ 
Debugger.app/Contents/MacOS/Flash\ Player\ Debugger
export ROYALE_HOME=/Apache/royale-asjs

The Ant build seems to succeed. I thought Maven does not use environment 
variables?

Either way, I think I can vote for this RC. The fact that Maven is failing 
is nothing new on my end… ;-)

Harbs

> On Nov 16, 2018, at 6:21 AM, Alex Harui  wrote:
> 
> It appears that there is something mixed up with your environment 
variables.
> 
> The tests check for PLAYERGLOBAL_HOME, AIR_HOME, and 
FLASHPLAYER_DEBUGGER.  I think all 3 have to be set or none have to be set.  If 
some are set, it can confuse the tests.  If all 3 are set, the tests should use 
playerglobal/airglobal and generate a SWF and run it in the debugger player.  
If none are set, the tests should use js.swc to generate a swf, but the swf is 
not run (since it wouldn't work without playerglobal).  Instead, it is 
swfdump'd and the output is compared against a prior swfdump.
> 
> The output shows that js.swc is being used in the compile, but the swf is 
being run in the debugger player.
> 
> HTH,
> -Alex
> 
> On 11/15/18, 4:59 PM, "Harbs"  wrote:
> 
>
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2FyBNfdata=02%7C01%7Caharui%40adobe.com%7C7931243fa0004c78011308d64b8e89f6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779472910908290sdata=EzNAtqfkryWkRDjATNbf6rxN1TfudGCWR6qW5uOeIlQ%3Dreserved=0
> 
>> On Nov 16, 2018, at 2:27 AM, Alex Harui  wrote:
>> 
>> Look in compiler/target/failsafe-reports and see what tests failed.  I 
have to step away from my computer for about 3 hours.
>> 
>> -Alex
>> 
>> On 11/15/18, 4:18 PM, "Harbs"  wrote:
>> 
>>   The ant build passed, but the Maven build failed:
>> 
>>   [INFO] --- maven-dependency-plugin:3.0.0:analyze-only (analyze) @ 
compiler ---
>>   [WARNING] Used undeclared dependencies found:
>>   [WARNING]org.antlr:antlr-runtime:jar:3.3:compile
>>   [WARNING]antlr:antlr:jar:2.7.7:compile
>>   [WARNING] Unused declared dependencies found:
>>   [WARNING]de.jflex:jflex:jar:1.6.0:compile
>>   [WARNING]org.antlr:antlr:jar:3.3:compile
>>   [WARNING]net.sourceforge.jburg:jburg:jar:1.10.3:compile
>>   [WARNING]
org.apache.royale.compiler:compiler-jburg-types:jar:1.0.0:compile
>>   [WARNING]
org.apache.royale.compiler:compiler-externc:jar:0.9.4:compile
>>   [INFO] 
>>   [INFO] --- maven-failsafe-plugin:2.18.1:verify (default) @ compiler ---
>>   [INFO] Failsafe report directory: 
/Apache/approve/apache-royale-0.9.4-maven-src/royale-compiler/compiler/target/failsafe-reports
>>   [INFO] 

>>   [INFO] Reactor Summary:
>>   [INFO] 
>>   [INFO] Apache Royale: Compiler: Parent  SUCCESS [  
4.354 s]
>>   [INFO] Apache Royale: Compiler: Compiler-Common ... SUCCESS [  
8.928 s]
>>   [INFO] Apache Royale: Compiler: Test Utils  SUCCESS [  
0.945 s]
>>   [INFO] Apache Royale: Compiler: Externc ... SUCCESS [ 
16.463 s]
>>   [INFO] Apache Royale: Compiler: Compiler .. FAILURE 
[05:27 min]
>>   [INFO] Apache Royale: Compiler: Compiler-JX ... SKIPPED
>>   [INFO] Apache Royale: Compiler: SWFUtils .. SKIPPED
>>   [INFO] Apache Royale: Compiler: Debugger .. SKIPPED
>>   [INFO] Apache Royale: Compiler: OEM Layer . SKIPPED
>>   [INFO] Apache Royale: Royale Ant Tasks  SKIPPED
>>   [INFO] Apache Royale: Royale Maven Plugin . 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Piotr Zarzycki]

Harbs,

Maybe it's not the Maven who uses variables. Maybe tests itselfs are using
it.
It would be great that you finally get the moment where Maven build is
working for you it's been years since your reporting problems with that.. :/

Piotr

On Fri, Nov 16, 2018, 7:41 AM Harbs  wrote:

> There are the env variables I’m using for all my builds:
>
> #!/bin/sh
>
> export ROYALE_COMPILER_REPO=/Apache/royale-compiler
> export FLEX_SDK_HOME=/FlexSDK/4.14.1
> export AIR_HOME=/Apache/frameworks/AIRSDK_Compiler
> export PLAYERGLOBAL_HOME=/Apache/frameworks/libs/player
> export FLASHPLAYER_DEBUGGER=/Apache/frameworks/Flash\ Player\
> Debugger.app/Contents/MacOS/Flash\ Player\ Debugger
> export ROYALE_HOME=/Apache/royale-asjs
>
> The Ant build seems to succeed. I thought Maven does not use environment
> variables?
>
> Either way, I think I can vote for this RC. The fact that Maven is failing
> is nothing new on my end… ;-)
>
> Harbs
>
> > On Nov 16, 2018, at 6:21 AM, Alex Harui 
> wrote:
> >
> > It appears that there is something mixed up with your environment
> variables.
> >
> > The tests check for PLAYERGLOBAL_HOME, AIR_HOME, and
> FLASHPLAYER_DEBUGGER.  I think all 3 have to be set or none have to be
> set.  If some are set, it can confuse the tests.  If all 3 are set, the
> tests should use playerglobal/airglobal and generate a SWF and run it in
> the debugger player.  If none are set, the tests should use js.swc to
> generate a swf, but the swf is not run (since it wouldn't work without
> playerglobal).  Instead, it is swfdump'd and the output is compared against
> a prior swfdump.
> >
> > The output shows that js.swc is being used in the compile, but the swf
> is being run in the debugger player.
> >
> > HTH,
> > -Alex
> >
> > On 11/15/18, 4:59 PM, "Harbs"  wrote:
> >
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2FyBNfdata=02%7C01%7Caharui%40adobe.com%7C5d7586aaa49244ce973408d64b5eb81f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779267525698959sdata=3INBLYsz21jjU8%2BwMFKiECE%2BAnLqEhRjidZswpnUyHg%3Dreserved=0
> >
> >> On Nov 16, 2018, at 2:27 AM, Alex Harui 
> wrote:
> >>
> >> Look in compiler/target/failsafe-reports and see what tests failed.  I
> have to step away from my computer for about 3 hours.
> >>
> >> -Alex
> >>
> >> On 11/15/18, 4:18 PM, "Harbs"  wrote:
> >>
> >>   The ant build passed, but the Maven build failed:
> >>
> >>   [INFO] --- maven-dependency-plugin:3.0.0:analyze-only (analyze) @
> compiler ---
> >>   [WARNING] Used undeclared dependencies found:
> >>   [WARNING]org.antlr:antlr-runtime:jar:3.3:compile
> >>   [WARNING]antlr:antlr:jar:2.7.7:compile
> >>   [WARNING] Unused declared dependencies found:
> >>   [WARNING]de.jflex:jflex:jar:1.6.0:compile
> >>   [WARNING]org.antlr:antlr:jar:3.3:compile
> >>   [WARNING]net.sourceforge.jburg:jburg:jar:1.10.3:compile
> >>   [WARNING]
> org.apache.royale.compiler:compiler-jburg-types:jar:1.0.0:compile
> >>   [WARNING]
> org.apache.royale.compiler:compiler-externc:jar:0.9.4:compile
> >>   [INFO]
> >>   [INFO] --- maven-failsafe-plugin:2.18.1:verify (default) @ compiler
> ---
> >>   [INFO] Failsafe report directory:
> /Apache/approve/apache-royale-0.9.4-maven-src/royale-compiler/compiler/target/failsafe-reports
> >>   [INFO]
> 
> >>   [INFO] Reactor Summary:
> >>   [INFO]
> >>   [INFO] Apache Royale: Compiler: Parent  SUCCESS
> [  4.354 s]
> >>   [INFO] Apache Royale: Compiler: Compiler-Common ... SUCCESS
> [  8.928 s]
> >>   [INFO] Apache Royale: Compiler: Test Utils  SUCCESS
> [  0.945 s]
> >>   [INFO] Apache Royale: Compiler: Externc ... SUCCESS [
> 16.463 s]
> >>   [INFO] Apache Royale: Compiler: Compiler .. FAILURE
> [05:27 min]
> >>   [INFO] Apache Royale: Compiler: Compiler-JX ... SKIPPED
> >>   [INFO] Apache Royale: Compiler: SWFUtils .. SKIPPED
> >>   [INFO] Apache Royale: Compiler: Debugger .. SKIPPED
> >>   [INFO] Apache Royale: Compiler: OEM Layer . SKIPPED
> >>   [INFO] Apache Royale: Royale Ant Tasks  SKIPPED
> >>   [INFO] Apache Royale: Royale Maven Plugin . SKIPPED
> >>   [INFO]
> 
> >>   [INFO] BUILD FAILURE
> >>   [INFO]
> 
> >>   [INFO] Total time: 05:58 min
> >>   [INFO] Finished at: 2018-11-16T02:06:07+02:00
> >>   [INFO] Final Memory: 85M/1443M
> >>   [INFO]
> 
> >>   [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-failsafe-plugin:2.18.1:verify (default) on
> project compiler: There are test failures.
> >>   [ERROR]
> >>   [ERROR] Please refer to
> 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Harbs]

There are the env variables I’m using for all my builds:

#!/bin/sh

export ROYALE_COMPILER_REPO=/Apache/royale-compiler
export FLEX_SDK_HOME=/FlexSDK/4.14.1 
export AIR_HOME=/Apache/frameworks/AIRSDK_Compiler
export PLAYERGLOBAL_HOME=/Apache/frameworks/libs/player 
export FLASHPLAYER_DEBUGGER=/Apache/frameworks/Flash\ Player\ 
Debugger.app/Contents/MacOS/Flash\ Player\ Debugger
export ROYALE_HOME=/Apache/royale-asjs

The Ant build seems to succeed. I thought Maven does not use environment 
variables?

Either way, I think I can vote for this RC. The fact that Maven is failing is 
nothing new on my end… ;-)

Harbs

> On Nov 16, 2018, at 6:21 AM, Alex Harui  wrote:
> 
> It appears that there is something mixed up with your environment variables.
> 
> The tests check for PLAYERGLOBAL_HOME, AIR_HOME, and FLASHPLAYER_DEBUGGER.  I 
> think all 3 have to be set or none have to be set.  If some are set, it can 
> confuse the tests.  If all 3 are set, the tests should use 
> playerglobal/airglobal and generate a SWF and run it in the debugger player.  
> If none are set, the tests should use js.swc to generate a swf, but the swf 
> is not run (since it wouldn't work without playerglobal).  Instead, it is 
> swfdump'd and the output is compared against a prior swfdump.
> 
> The output shows that js.swc is being used in the compile, but the swf is 
> being run in the debugger player.
> 
> HTH,
> -Alex
> 
> On 11/15/18, 4:59 PM, "Harbs"  wrote:
> 
>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2FyBNfdata=02%7C01%7Caharui%40adobe.com%7C5d7586aaa49244ce973408d64b5eb81f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779267525698959sdata=3INBLYsz21jjU8%2BwMFKiECE%2BAnLqEhRjidZswpnUyHg%3Dreserved=0
> 
>> On Nov 16, 2018, at 2:27 AM, Alex Harui  wrote:
>> 
>> Look in compiler/target/failsafe-reports and see what tests failed.  I have 
>> to step away from my computer for about 3 hours.
>> 
>> -Alex
>> 
>> On 11/15/18, 4:18 PM, "Harbs"  wrote:
>> 
>>   The ant build passed, but the Maven build failed:
>> 
>>   [INFO] --- maven-dependency-plugin:3.0.0:analyze-only (analyze) @ compiler 
>> ---
>>   [WARNING] Used undeclared dependencies found:
>>   [WARNING]org.antlr:antlr-runtime:jar:3.3:compile
>>   [WARNING]antlr:antlr:jar:2.7.7:compile
>>   [WARNING] Unused declared dependencies found:
>>   [WARNING]de.jflex:jflex:jar:1.6.0:compile
>>   [WARNING]org.antlr:antlr:jar:3.3:compile
>>   [WARNING]net.sourceforge.jburg:jburg:jar:1.10.3:compile
>>   [WARNING]
>> org.apache.royale.compiler:compiler-jburg-types:jar:1.0.0:compile
>>   [WARNING]org.apache.royale.compiler:compiler-externc:jar:0.9.4:compile
>>   [INFO] 
>>   [INFO] --- maven-failsafe-plugin:2.18.1:verify (default) @ compiler ---
>>   [INFO] Failsafe report directory: 
>> /Apache/approve/apache-royale-0.9.4-maven-src/royale-compiler/compiler/target/failsafe-reports
>>   [INFO] 
>> 
>>   [INFO] Reactor Summary:
>>   [INFO] 
>>   [INFO] Apache Royale: Compiler: Parent  SUCCESS [  
>> 4.354 s]
>>   [INFO] Apache Royale: Compiler: Compiler-Common ... SUCCESS [  
>> 8.928 s]
>>   [INFO] Apache Royale: Compiler: Test Utils  SUCCESS [  
>> 0.945 s]
>>   [INFO] Apache Royale: Compiler: Externc ... SUCCESS [ 
>> 16.463 s]
>>   [INFO] Apache Royale: Compiler: Compiler .. FAILURE [05:27 
>> min]
>>   [INFO] Apache Royale: Compiler: Compiler-JX ... SKIPPED
>>   [INFO] Apache Royale: Compiler: SWFUtils .. SKIPPED
>>   [INFO] Apache Royale: Compiler: Debugger .. SKIPPED
>>   [INFO] Apache Royale: Compiler: OEM Layer . SKIPPED
>>   [INFO] Apache Royale: Royale Ant Tasks  SKIPPED
>>   [INFO] Apache Royale: Royale Maven Plugin . SKIPPED
>>   [INFO] 
>> 
>>   [INFO] BUILD FAILURE
>>   [INFO] 
>> 
>>   [INFO] Total time: 05:58 min
>>   [INFO] Finished at: 2018-11-16T02:06:07+02:00
>>   [INFO] Final Memory: 85M/1443M
>>   [INFO] 
>> 
>>   [ERROR] Failed to execute goal 
>> org.apache.maven.plugins:maven-failsafe-plugin:2.18.1:verify (default) on 
>> project compiler: There are test failures.
>>   [ERROR] 
>>   [ERROR] Please refer to 
>> /Apache/approve/apache-royale-0.9.4-maven-src/royale-compiler/compiler/target/failsafe-reports
>>  for the individual test results.
>>   [ERROR] -> [Help 1]
>>   [ERROR] 
>>   [ERROR] To see the full stack trace of the errors, re-run Maven with the 
>> -e switch.
>>   [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>   [ERROR] 
>>   [ERROR] For more information about the errors and possible solutions, 
>> 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Alex Harui]

It appears that there is something mixed up with your environment variables.

The tests check for PLAYERGLOBAL_HOME, AIR_HOME, and FLASHPLAYER_DEBUGGER.  I 
think all 3 have to be set or none have to be set.  If some are set, it can 
confuse the tests.  If all 3 are set, the tests should use 
playerglobal/airglobal and generate a SWF and run it in the debugger player.  
If none are set, the tests should use js.swc to generate a swf, but the swf is 
not run (since it wouldn't work without playerglobal).  Instead, it is 
swfdump'd and the output is compared against a prior swfdump.

The output shows that js.swc is being used in the compile, but the swf is being 
run in the debugger player.

HTH,
-Alex

On 11/15/18, 4:59 PM, "Harbs"  wrote:


https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2FyBNfdata=02%7C01%7Caharui%40adobe.com%7C5d7586aaa49244ce973408d64b5eb81f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779267525698959sdata=3INBLYsz21jjU8%2BwMFKiECE%2BAnLqEhRjidZswpnUyHg%3Dreserved=0

> On Nov 16, 2018, at 2:27 AM, Alex Harui  wrote:
> 
> Look in compiler/target/failsafe-reports and see what tests failed.  I 
have to step away from my computer for about 3 hours.
> 
> -Alex
> 
> On 11/15/18, 4:18 PM, "Harbs"  wrote:
> 
>The ant build passed, but the Maven build failed:
> 
>[INFO] --- maven-dependency-plugin:3.0.0:analyze-only (analyze) @ 
compiler ---
>[WARNING] Used undeclared dependencies found:
>[WARNING]org.antlr:antlr-runtime:jar:3.3:compile
>[WARNING]antlr:antlr:jar:2.7.7:compile
>[WARNING] Unused declared dependencies found:
>[WARNING]de.jflex:jflex:jar:1.6.0:compile
>[WARNING]org.antlr:antlr:jar:3.3:compile
>[WARNING]net.sourceforge.jburg:jburg:jar:1.10.3:compile
>[WARNING]
org.apache.royale.compiler:compiler-jburg-types:jar:1.0.0:compile
>[WARNING]
org.apache.royale.compiler:compiler-externc:jar:0.9.4:compile
>[INFO] 
>[INFO] --- maven-failsafe-plugin:2.18.1:verify (default) @ compiler ---
>[INFO] Failsafe report directory: 
/Apache/approve/apache-royale-0.9.4-maven-src/royale-compiler/compiler/target/failsafe-reports
>[INFO] 

>[INFO] Reactor Summary:
>[INFO] 
>[INFO] Apache Royale: Compiler: Parent  SUCCESS [  
4.354 s]
>[INFO] Apache Royale: Compiler: Compiler-Common ... SUCCESS [  
8.928 s]
>[INFO] Apache Royale: Compiler: Test Utils  SUCCESS [  
0.945 s]
>[INFO] Apache Royale: Compiler: Externc ... SUCCESS [ 
16.463 s]
>[INFO] Apache Royale: Compiler: Compiler .. FAILURE 
[05:27 min]
>[INFO] Apache Royale: Compiler: Compiler-JX ... SKIPPED
>[INFO] Apache Royale: Compiler: SWFUtils .. SKIPPED
>[INFO] Apache Royale: Compiler: Debugger .. SKIPPED
>[INFO] Apache Royale: Compiler: OEM Layer . SKIPPED
>[INFO] Apache Royale: Royale Ant Tasks  SKIPPED
>[INFO] Apache Royale: Royale Maven Plugin . SKIPPED
>[INFO] 

>[INFO] BUILD FAILURE
>[INFO] 

>[INFO] Total time: 05:58 min
>[INFO] Finished at: 2018-11-16T02:06:07+02:00
>[INFO] Final Memory: 85M/1443M
>[INFO] 

>[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-failsafe-plugin:2.18.1:verify (default) on 
project compiler: There are test failures.
>[ERROR] 
>[ERROR] Please refer to 
/Apache/approve/apache-royale-0.9.4-maven-src/royale-compiler/compiler/target/failsafe-reports
 for the individual test results.
>[ERROR] -> [Help 1]
>[ERROR] 
>[ERROR] To see the full stack trace of the errors, re-run Maven with 
the -e switch.
>[ERROR] Re-run Maven using the -X switch to enable full debug logging.
>[ERROR] 
>[ERROR] For more information about the errors and possible solutions, 
please read the following articles:
>[ERROR] [Help 1] 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FMAVEN%2FMojoFailureExceptiondata=02%7C01%7Caharui%40adobe.com%7C5d7586aaa49244ce973408d64b5eb81f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779267525698959sdata=jatFLly%2FbRQ7oAUVyCk7ClhMPObkEkFtM0NC9kQqHZ0%3Dreserved=0
>[ERROR] 
>[ERROR] After correcting the problems, you can resume the build with 
the command
>[ERROR]   mvn  -rf :compiler
> 
>BUILD FAILED

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Harbs]

https://paste.apache.org/yBNf

> On Nov 16, 2018, at 2:27 AM, Alex Harui  wrote:
> 
> Look in compiler/target/failsafe-reports and see what tests failed.  I have 
> to step away from my computer for about 3 hours.
> 
> -Alex
> 
> On 11/15/18, 4:18 PM, "Harbs"  wrote:
> 
>The ant build passed, but the Maven build failed:
> 
>[INFO] --- maven-dependency-plugin:3.0.0:analyze-only (analyze) @ compiler 
> ---
>[WARNING] Used undeclared dependencies found:
>[WARNING]org.antlr:antlr-runtime:jar:3.3:compile
>[WARNING]antlr:antlr:jar:2.7.7:compile
>[WARNING] Unused declared dependencies found:
>[WARNING]de.jflex:jflex:jar:1.6.0:compile
>[WARNING]org.antlr:antlr:jar:3.3:compile
>[WARNING]net.sourceforge.jburg:jburg:jar:1.10.3:compile
>[WARNING]
> org.apache.royale.compiler:compiler-jburg-types:jar:1.0.0:compile
>[WARNING]org.apache.royale.compiler:compiler-externc:jar:0.9.4:compile
>[INFO] 
>[INFO] --- maven-failsafe-plugin:2.18.1:verify (default) @ compiler ---
>[INFO] Failsafe report directory: 
> /Apache/approve/apache-royale-0.9.4-maven-src/royale-compiler/compiler/target/failsafe-reports
>[INFO] 
> 
>[INFO] Reactor Summary:
>[INFO] 
>[INFO] Apache Royale: Compiler: Parent  SUCCESS [  
> 4.354 s]
>[INFO] Apache Royale: Compiler: Compiler-Common ... SUCCESS [  
> 8.928 s]
>[INFO] Apache Royale: Compiler: Test Utils  SUCCESS [  
> 0.945 s]
>[INFO] Apache Royale: Compiler: Externc ... SUCCESS [ 
> 16.463 s]
>[INFO] Apache Royale: Compiler: Compiler .. FAILURE [05:27 
> min]
>[INFO] Apache Royale: Compiler: Compiler-JX ... SKIPPED
>[INFO] Apache Royale: Compiler: SWFUtils .. SKIPPED
>[INFO] Apache Royale: Compiler: Debugger .. SKIPPED
>[INFO] Apache Royale: Compiler: OEM Layer . SKIPPED
>[INFO] Apache Royale: Royale Ant Tasks  SKIPPED
>[INFO] Apache Royale: Royale Maven Plugin . SKIPPED
>[INFO] 
> 
>[INFO] BUILD FAILURE
>[INFO] 
> 
>[INFO] Total time: 05:58 min
>[INFO] Finished at: 2018-11-16T02:06:07+02:00
>[INFO] Final Memory: 85M/1443M
>[INFO] 
> 
>[ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-failsafe-plugin:2.18.1:verify (default) on 
> project compiler: There are test failures.
>[ERROR] 
>[ERROR] Please refer to 
> /Apache/approve/apache-royale-0.9.4-maven-src/royale-compiler/compiler/target/failsafe-reports
>  for the individual test results.
>[ERROR] -> [Help 1]
>[ERROR] 
>[ERROR] To see the full stack trace of the errors, re-run Maven with the 
> -e switch.
>[ERROR] Re-run Maven using the -X switch to enable full debug logging.
>[ERROR] 
>[ERROR] For more information about the errors and possible solutions, 
> please read the following articles:
>[ERROR] [Help 1] 
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FMAVEN%2FMojoFailureExceptiondata=02%7C01%7Caharui%40adobe.com%7Cfdb408f38dee452083e908d64b5914b7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779243301438183sdata=CKZU%2F3FUYJjjyKFN7AV4LXkjVUsI7qpugMbaApimY6Q%3Dreserved=0
>[ERROR] 
>[ERROR] After correcting the problems, you can resume the build with the 
> command
>[ERROR]   mvn  -rf :compiler
> 
>BUILD FAILED
>/Apache/approve/ApproveRoyale.xml:775: The following error occurred while 
> executing this line:
>/Apache/approve/ApproveRoyale.xml:786: exec returned: 1
> 
>Total time: 47 minutes 57 seconds
>> On Nov 16, 2018, at 12:48 AM, Alex Harui  wrote:
>> 
>> It's also part of the ApprovalScript so if run it on this RC you can get 
>> some early info.
>> 
>> -Alex
>> 
>> On 11/15/18, 2:44 PM, "Harbs"  wrote:
>> 
>>   It’s been a while and I don’t remember off-hand.
>> 
>>   I’ll probably take a stab at being RM in a few weeks and I imagine I’ll 
>> need to figure it out then… ;-)
>> 
>>   Harbs
>> 
>>> On Nov 16, 2018, at 12:32 AM, Alex Harui  wrote:
>>> 
>>> What errors do you get with Maven?
>> 
>> 
>> 
> 
> 
> 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Alex Harui]

Look in compiler/target/failsafe-reports and see what tests failed.  I have to 
step away from my computer for about 3 hours.

-Alex

On 11/15/18, 4:18 PM, "Harbs"  wrote:

The ant build passed, but the Maven build failed:

[INFO] --- maven-dependency-plugin:3.0.0:analyze-only (analyze) @ compiler 
---
[WARNING] Used undeclared dependencies found:
[WARNING]org.antlr:antlr-runtime:jar:3.3:compile
[WARNING]antlr:antlr:jar:2.7.7:compile
[WARNING] Unused declared dependencies found:
[WARNING]de.jflex:jflex:jar:1.6.0:compile
[WARNING]org.antlr:antlr:jar:3.3:compile
[WARNING]net.sourceforge.jburg:jburg:jar:1.10.3:compile
[WARNING]
org.apache.royale.compiler:compiler-jburg-types:jar:1.0.0:compile
[WARNING]org.apache.royale.compiler:compiler-externc:jar:0.9.4:compile
[INFO] 
[INFO] --- maven-failsafe-plugin:2.18.1:verify (default) @ compiler ---
[INFO] Failsafe report directory: 
/Apache/approve/apache-royale-0.9.4-maven-src/royale-compiler/compiler/target/failsafe-reports
[INFO] 

[INFO] Reactor Summary:
[INFO] 
[INFO] Apache Royale: Compiler: Parent  SUCCESS [  
4.354 s]
[INFO] Apache Royale: Compiler: Compiler-Common ... SUCCESS [  
8.928 s]
[INFO] Apache Royale: Compiler: Test Utils  SUCCESS [  
0.945 s]
[INFO] Apache Royale: Compiler: Externc ... SUCCESS [ 
16.463 s]
[INFO] Apache Royale: Compiler: Compiler .. FAILURE [05:27 
min]
[INFO] Apache Royale: Compiler: Compiler-JX ... SKIPPED
[INFO] Apache Royale: Compiler: SWFUtils .. SKIPPED
[INFO] Apache Royale: Compiler: Debugger .. SKIPPED
[INFO] Apache Royale: Compiler: OEM Layer . SKIPPED
[INFO] Apache Royale: Royale Ant Tasks  SKIPPED
[INFO] Apache Royale: Royale Maven Plugin . SKIPPED
[INFO] 

[INFO] BUILD FAILURE
[INFO] 

[INFO] Total time: 05:58 min
[INFO] Finished at: 2018-11-16T02:06:07+02:00
[INFO] Final Memory: 85M/1443M
[INFO] 

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-failsafe-plugin:2.18.1:verify (default) on 
project compiler: There are test failures.
[ERROR] 
[ERROR] Please refer to 
/Apache/approve/apache-royale-0.9.4-maven-src/royale-compiler/compiler/target/failsafe-reports
 for the individual test results.
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, 
please read the following articles:
[ERROR] [Help 1] 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FMAVEN%2FMojoFailureExceptiondata=02%7C01%7Caharui%40adobe.com%7Cfdb408f38dee452083e908d64b5914b7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779243301438183sdata=CKZU%2F3FUYJjjyKFN7AV4LXkjVUsI7qpugMbaApimY6Q%3Dreserved=0
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the 
command
[ERROR]   mvn  -rf :compiler

BUILD FAILED
/Apache/approve/ApproveRoyale.xml:775: The following error occurred while 
executing this line:
/Apache/approve/ApproveRoyale.xml:786: exec returned: 1

Total time: 47 minutes 57 seconds
> On Nov 16, 2018, at 12:48 AM, Alex Harui  wrote:
> 
> It's also part of the ApprovalScript so if run it on this RC you can get 
some early info.
> 
> -Alex
> 
> On 11/15/18, 2:44 PM, "Harbs"  wrote:
> 
>It’s been a while and I don’t remember off-hand.
> 
>I’ll probably take a stab at being RM in a few weeks and I imagine 
I’ll need to figure it out then… ;-)
> 
>Harbs
> 
>> On Nov 16, 2018, at 12:32 AM, Alex Harui  
wrote:
>> 
>> What errors do you get with Maven?
> 
> 
> 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Harbs]

The ant build passed, but the Maven build failed:

[INFO] --- maven-dependency-plugin:3.0.0:analyze-only (analyze) @ compiler ---
[WARNING] Used undeclared dependencies found:
[WARNING]org.antlr:antlr-runtime:jar:3.3:compile
[WARNING]antlr:antlr:jar:2.7.7:compile
[WARNING] Unused declared dependencies found:
[WARNING]de.jflex:jflex:jar:1.6.0:compile
[WARNING]org.antlr:antlr:jar:3.3:compile
[WARNING]net.sourceforge.jburg:jburg:jar:1.10.3:compile
[WARNING]org.apache.royale.compiler:compiler-jburg-types:jar:1.0.0:compile
[WARNING]org.apache.royale.compiler:compiler-externc:jar:0.9.4:compile
[INFO] 
[INFO] --- maven-failsafe-plugin:2.18.1:verify (default) @ compiler ---
[INFO] Failsafe report directory: 
/Apache/approve/apache-royale-0.9.4-maven-src/royale-compiler/compiler/target/failsafe-reports
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache Royale: Compiler: Parent  SUCCESS [  4.354 s]
[INFO] Apache Royale: Compiler: Compiler-Common ... SUCCESS [  8.928 s]
[INFO] Apache Royale: Compiler: Test Utils  SUCCESS [  0.945 s]
[INFO] Apache Royale: Compiler: Externc ... SUCCESS [ 16.463 s]
[INFO] Apache Royale: Compiler: Compiler .. FAILURE [05:27 min]
[INFO] Apache Royale: Compiler: Compiler-JX ... SKIPPED
[INFO] Apache Royale: Compiler: SWFUtils .. SKIPPED
[INFO] Apache Royale: Compiler: Debugger .. SKIPPED
[INFO] Apache Royale: Compiler: OEM Layer . SKIPPED
[INFO] Apache Royale: Royale Ant Tasks  SKIPPED
[INFO] Apache Royale: Royale Maven Plugin . SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 05:58 min
[INFO] Finished at: 2018-11-16T02:06:07+02:00
[INFO] Final Memory: 85M/1443M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-failsafe-plugin:2.18.1:verify (default) on 
project compiler: There are test failures.
[ERROR] 
[ERROR] Please refer to 
/Apache/approve/apache-royale-0.9.4-maven-src/royale-compiler/compiler/target/failsafe-reports
 for the individual test results.
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :compiler

BUILD FAILED
/Apache/approve/ApproveRoyale.xml:775: The following error occurred while 
executing this line:
/Apache/approve/ApproveRoyale.xml:786: exec returned: 1

Total time: 47 minutes 57 seconds
> On Nov 16, 2018, at 12:48 AM, Alex Harui  wrote:
> 
> It's also part of the ApprovalScript so if run it on this RC you can get some 
> early info.
> 
> -Alex
> 
> On 11/15/18, 2:44 PM, "Harbs"  wrote:
> 
>It’s been a while and I don’t remember off-hand.
> 
>I’ll probably take a stab at being RM in a few weeks and I imagine I’ll 
> need to figure it out then… ;-)
> 
>Harbs
> 
>> On Nov 16, 2018, at 12:32 AM, Alex Harui  wrote:
>> 
>> What errors do you get with Maven?
> 
> 
> 

Re: Lets talk a bit about the release process (was Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2)

[Alex Harui]

As many of you know, Maven makes a lot of assumptions and does a fair amount of 
work in each assumption.  So, for example, when you run "mvn install", it runs 
several steps including the build and copies it to the local repo.  Imagine the 
number of lines of Ant code required to do the same.

I am told that the app that you run when you go to the ASF Maven Staging Repo 
in your browser (repository.a.o)  also has a pile of assumptions.  So when we 
copy artifacts up there and tell the app to  "close" a staging repository, it 
runs several steps that would amount to a huge pile of Ant scripting.  And 
later, when it is time to push it all to Maven Central, it can do that as well.

Similarly, Maven's "release" plugin makes assumptions that the ASF Maven 
Staging Repo expects.  So it packages up sources, makes checksums, signs 
artifacts and pushes them to the staging repo.  That would also require a lot 
of Ant scripting to do, although some of it, like a source artifact per-jar, 
IMO, is not absolutely required.

So, that's why I think it is the right thing, assuming we want to publish Maven 
artifacts for our releases, which I think we do want to do.  It is far less 
work on the RM to maintain less verbose Ant scripts which are already pretty 
long.  The assumption that you have reliable high-speed internet connections 
shouldn't be that hard to meet these days, but the Repo server did seem to 
care, or maybe it was my home router that got overwhelmed and dropped packets.  
Not sure.  All I know is that I saw it work without tweaking any network 
settings.

HTH,
-Alex

On 11/15/18, 11:37 AM, "OmPrakash Muppirala"  wrote:

On Thu, Nov 15, 2018 at 2:02 AM Alex Harui  wrote:

> To be clear:  the process DOES NOT upload artifacts to Maven Central.  It
> uploads to the ASF staging repo.  Only after we approve the release do the
> artifacts get pushed to Maven Central.  One of the RMs got an error
> DOWNLOADING a Maven plugin from Maven Central.  There is nothing wrong 
with
> doing that.
>

Sorry, I misspoke.  But the question remains.  Why do we need to upload it
to the staging server during building or testing a release candidate?  Can
we not just use the local m2 repository for this?

In other words, what aspect of the release are we actually testing by
uploading stuff to the staging repo?



>
> Any volunteer is welcome to re-do the release scripts.  What we have now
> is what I think was the simplest sequence for creating both Maven and
> non-Maven artifacts.  Maven was the number 1 asked for feature in Adobe
> Flex.  IIRC, it had 100 votes and 2nd place was 12 votes.  So we support
> Maven in hopes that the customers we want to attract are using Maven, plus
> at least Carlos prefers to use Maven.
>
> Just like any other code or script in Royale, there can be bugs and room
> for improvement in the release process.  I found and fixed some issues, 
and
> hopefully the next RM will try the scripts after a month or so instead of 
6
> months so fewer things will have become stale and broken.  In fact,  I
> think I will say that RC2 is my last RC for a while.  If we need an RC3,
> someone else should create it since the know the scripts recently worked
> for me.  And since it is fresh in my mind, I might be able to help the 
next
> RM better.  I think the problems Piotr and Yishay hit have been addressed.
> The only remaining issue is upload/download issues.
>

Thanks for getting the scripts to this shape!

Regards,
Om


>
> Thanks,
> -Alex
>
> On 11/14/18, 10:36 PM, "OmPrakash Muppirala" 
> wrote:
>
> Personally, I am not sure why we are uploading stuff to maven central
> as
> part of the RC process.  Can we simply bundle the source files and
> create a
> release candidate?  Folks who want to test maven can run the maven
> scripts
> locally which would copy stuff to the local .m2 repo instead.
> That way we dont force maven on folks who dont need it.
>
> Thoughts?
>
> Thanks,
> Om
>
>
>
> On Wed, Nov 14, 2018 at 12:54 PM Carlos Rovira <
> carlosrov...@apache.org>
> wrote:
>
> > Hi Alex,
> >
> > first congrats to reach to this point. After many months is great to
> > finally can release :)
> >
> > I forked the thread to avoid mixing topics and let the discuss
> thread to
> > just discuss the RC2
> >
> > I'll try RC2 soon, but first I want to talk about the inherent
> problem. I
> > know we are all here making a huge effort to make Royale work and
> shine,
> > and be release manager is to spend many hours working in that task,
> so
> > first I want to express as well a huge recognition 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Alex Harui]

I think this file is missing from the source kit.  I didn't catch it because I 
think it is only needed for first-timers.

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

Dave, try putting that file in a .mvn folder in the royale-asjs folder and see 
if things start to work.

-Alex

On 11/15/18, 3:08 PM, "Piotr Zarzycki"  wrote:

Dave,

You just made me realize that I probably saw that issue a while back. You
should be asked during source build to for license approve and download
playerglobal. I saw that sometimes it doesn't work and you got something
like you. I don't know why. I will try tomorrow on my sight.

Piotr

On Fri, Nov 16, 2018, 12:02 AM Dave Fisher  wrote:

> I am on Maven 3.5.0
>
> I get this error:
>
> >  [ERROR] Failed to execute goal
> org.apache.royale.compiler:royale-maven-plugin:0.9.4:compile-as
> (default-compile-as) on project Core: Could not resolve dependencies for
> project org.apache.royale.framework:Core:swc:0.9.4: Failure to find
> com.adobe.air.framework:airglobal:swc:20.0 in
> 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Freleasesdata=02%7C01%7Caharui%40adobe.com%7Cb364a443384642d3cc1e08d64b4f4883%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779201220453312sdata=%2BI5LblnCQiheDN5OgUb0roLYWJYH6%2BxTvEM%2Bhq2b258%3Dreserved=0
> <
> 
https://na01.safelinks.protection.outlook.com/?url=https://repository.apache.org/content/repositories/releasesdata=02|01|aha...@adobe.com|f9bcbd2877134b95ef8508d64b447b84|fa7b1b5a7b34438794aed2c178decee1|0|0|636779154848452934sdata=km1iZjKngu54/FDvN6mYZVmHhqIfx+h6ls6nftiKEt4=reserved=0
> 
>
> was cached in the local repository, resolution will not be reattempted
> until the update interval of apache-release has elapsed or updates are
> forced -> [Help 1]
> >   [ERROR]
> >   [ERROR] To see the full stack trace of the errors, re-run Maven with
> the -e switch.
> >   [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> >   [ERROR]
> >   [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> >   [ERROR] [Help 1]
> 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FMAVEN%2FMojoExecutionExceptiondata=02%7C01%7Caharui%40adobe.com%7Cb364a443384642d3cc1e08d64b4f4883%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779201220453312sdata=Vnm8YTZC%2FSxjykGGjRy7cizifbqCHR0%2B3fHoTqu%2B5dg%3Dreserved=0
> <
> 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FMAVEN%2FMojoExecutionExceptiondata=02%7C01%7Caharui%40adobe.com%7Cb364a443384642d3cc1e08d64b4f4883%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779201220453312sdata=Vnm8YTZC%2FSxjykGGjRy7cizifbqCHR0%2B3fHoTqu%2B5dg%3Dreserved=0
> >
>
> I think that there must be a missing part:
>
> $ pwd
> /Users/davewave/.m2/repository/org/apache/royale/compiler
> $ ls -1
> compiler
> compiler-build-tools
> compiler-common
> compiler-externc
> compiler-jburg-types
> compiler-jx
> compiler-test-utils
> debugger
> flex-compiler-oem
> maven-metadata-local.xml
> royale-ant-tasks
> royale-compiler-parent
> royale-maven-plugin
> swfutils
>
> $ pwd
> /Users/davewave/.m2/repository/org/apache/royale/framework
> Daves-MacBook-Pro:framework davewave$ ls -1
> Fonts
> frameworks
> projects
> royale-framework-parent
>
> This pom:
> ./framework/projects/0.9.4/projects-0.9.4.pom
>
> Has
> 
>   com.adobe.air.framework
>   airglobal
>   ${air.version}
>   swc
>   provided
> 
>
> Am I missing ${air.version}?
>
> Is “provided” incorrect?
>
> Regards,
> Dave
>
> > On Nov 15, 2018, at 2:34 PM, Harbs  wrote:
> >
> > It’s been a while and I don’t remember off-hand.
> >
> > I’ll probably take a stab at being RM in a few weeks and I imagine I’ll
> need to figure it out then… ;-)
> >
> > Harbs
> >
> >> On Nov 16, 2018, at 12:32 AM, Alex Harui 
> wrote:
> >>
> >> What errors do you get with Maven?
> >
>
>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Piotr Zarzycki]

Dave,

You just made me realize that I probably saw that issue a while back. You
should be asked during source build to for license approve and download
playerglobal. I saw that sometimes it doesn't work and you got something
like you. I don't know why. I will try tomorrow on my sight.

Piotr

On Fri, Nov 16, 2018, 12:02 AM Dave Fisher  wrote:

> I am on Maven 3.5.0
>
> I get this error:
>
> >  [ERROR] Failed to execute goal
> org.apache.royale.compiler:royale-maven-plugin:0.9.4:compile-as
> (default-compile-as) on project Core: Could not resolve dependencies for
> project org.apache.royale.framework:Core:swc:0.9.4: Failure to find
> com.adobe.air.framework:airglobal:swc:20.0 in
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Freleasesdata=02%7C01%7Caharui%40adobe.com%7Cf9bcbd2877134b95ef8508d64b447b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779154848452934sdata=km1iZjKngu54%2FFDvN6mYZVmHhqIfx%2Bh6ls6nftiKEt4%3Dreserved=0
> <
> https://na01.safelinks.protection.outlook.com/?url=https://repository.apache.org/content/repositories/releasesdata=02|01|aha...@adobe.com|f9bcbd2877134b95ef8508d64b447b84|fa7b1b5a7b34438794aed2c178decee1|0|0|636779154848452934sdata=km1iZjKngu54/FDvN6mYZVmHhqIfx+h6ls6nftiKEt4=reserved=0
> >
> was cached in the local repository, resolution will not be reattempted
> until the update interval of apache-release has elapsed or updates are
> forced -> [Help 1]
> >   [ERROR]
> >   [ERROR] To see the full stack trace of the errors, re-run Maven with
> the -e switch.
> >   [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> >   [ERROR]
> >   [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> >   [ERROR] [Help 1]
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FMAVEN%2FMojoExecutionExceptiondata=02%7C01%7Caharui%40adobe.com%7Cf9bcbd2877134b95ef8508d64b447b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779154848452934sdata=l0CgXdhlLZ5Bki6pWE8j9kFJT%2Fw0HRVJRT5weguQxCE%3Dreserved=0
> <
> https://na01.safelinks.protection.outlook.com/?url=http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionExceptiondata=02|01|aha...@adobe.com|f9bcbd2877134b95ef8508d64b447b84|fa7b1b5a7b34438794aed2c178decee1|0|0|636779154848452934sdata=l0CgXdhlLZ5Bki6pWE8j9kFJT/w0HRVJRT5weguQxCE=reserved=0
> >
>
> I think that there must be a missing part:
>
> $ pwd
> /Users/davewave/.m2/repository/org/apache/royale/compiler
> $ ls -1
> compiler
> compiler-build-tools
> compiler-common
> compiler-externc
> compiler-jburg-types
> compiler-jx
> compiler-test-utils
> debugger
> flex-compiler-oem
> maven-metadata-local.xml
> royale-ant-tasks
> royale-compiler-parent
> royale-maven-plugin
> swfutils
>
> $ pwd
> /Users/davewave/.m2/repository/org/apache/royale/framework
> Daves-MacBook-Pro:framework davewave$ ls -1
> Fonts
> frameworks
> projects
> royale-framework-parent
>
> This pom:
> ./framework/projects/0.9.4/projects-0.9.4.pom
>
> Has
> 
>   com.adobe.air.framework
>   airglobal
>   ${air.version}
>   swc
>   provided
> 
>
> Am I missing ${air.version}?
>
> Is “provided” incorrect?
>
> Regards,
> Dave
>
> > On Nov 15, 2018, at 2:34 PM, Harbs  wrote:
> >
> > It’s been a while and I don’t remember off-hand.
> >
> > I’ll probably take a stab at being RM in a few weeks and I imagine I’ll
> need to figure it out then… ;-)
> >
> > Harbs
> >
> >> On Nov 16, 2018, at 12:32 AM, Alex Harui 
> wrote:
> >>
> >> What errors do you get with Maven?
> >
>
>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Dave Fisher]

I am on Maven 3.5.0

I get this error:

>  [ERROR] Failed to execute goal 
> org.apache.royale.compiler:royale-maven-plugin:0.9.4:compile-as 
> (default-compile-as) on project Core: Could not resolve dependencies for 
> project org.apache.royale.framework:Core:swc:0.9.4: Failure to find 
> com.adobe.air.framework:airglobal:swc:20.0 in 
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Freleasesdata=02%7C01%7Caharui%40adobe.com%7Cf9bcbd2877134b95ef8508d64b447b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779154848452934sdata=km1iZjKngu54%2FFDvN6mYZVmHhqIfx%2Bh6ls6nftiKEt4%3Dreserved=0
>  
> 
>  was cached in the local repository, resolution will not be reattempted until 
> the update interval of apache-release has elapsed or updates are forced -> 
> [Help 1]
>   [ERROR] 
>   [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
>   [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>   [ERROR] 
>   [ERROR] For more information about the errors and possible solutions, 
> please read the following articles:
>   [ERROR] [Help 1] 
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FMAVEN%2FMojoExecutionExceptiondata=02%7C01%7Caharui%40adobe.com%7Cf9bcbd2877134b95ef8508d64b447b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779154848452934sdata=l0CgXdhlLZ5Bki6pWE8j9kFJT%2Fw0HRVJRT5weguQxCE%3Dreserved=0
>  
> 

I think that there must be a missing part:

$ pwd
/Users/davewave/.m2/repository/org/apache/royale/compiler
$ ls -1
compiler
compiler-build-tools
compiler-common
compiler-externc
compiler-jburg-types
compiler-jx
compiler-test-utils
debugger
flex-compiler-oem
maven-metadata-local.xml
royale-ant-tasks
royale-compiler-parent
royale-maven-plugin
swfutils

$ pwd
/Users/davewave/.m2/repository/org/apache/royale/framework
Daves-MacBook-Pro:framework davewave$ ls -1
Fonts
frameworks
projects
royale-framework-parent

This pom:
./framework/projects/0.9.4/projects-0.9.4.pom

Has 

  com.adobe.air.framework
  airglobal
  ${air.version}
  swc
  provided


Am I missing ${air.version}?

Is “provided” incorrect?

Regards,
Dave

> On Nov 15, 2018, at 2:34 PM, Harbs  wrote:
> 
> It’s been a while and I don’t remember off-hand.
> 
> I’ll probably take a stab at being RM in a few weeks and I imagine I’ll need 
> to figure it out then… ;-)
> 
> Harbs
> 
>> On Nov 16, 2018, at 12:32 AM, Alex Harui  wrote:
>> 
>> What errors do you get with Maven?
> 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Alex Harui]

It's also part of the ApprovalScript so if run it on this RC you can get some 
early info.

-Alex

On 11/15/18, 2:44 PM, "Harbs"  wrote:

It’s been a while and I don’t remember off-hand.

I’ll probably take a stab at being RM in a few weeks and I imagine I’ll 
need to figure it out then… ;-)

Harbs

> On Nov 16, 2018, at 12:32 AM, Alex Harui  wrote:
> 
> What errors do you get with Maven?

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Harbs]

It’s been a while and I don’t remember off-hand.

I’ll probably take a stab at being RM in a few weeks and I imagine I’ll need to 
figure it out then… ;-)

Harbs

> On Nov 16, 2018, at 12:32 AM, Alex Harui  wrote:
> 
> What errors do you get with Maven?

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Alex Harui]

Sorry, I missed a ">".  3.3.x or greater.  There is some older versions that 
will not pick up the Mavenizer.  I'd have to go through the archives to find 
out which one, which I'd rather not do.

What errors do you get with Maven?

-Alex

On 11/15/18, 2:19 PM, "Harbs"  wrote:

Why is that?

I have 3.5.2 installed. Is that why Maven never works for me?

Harbs

> On Nov 16, 2018, at 12:17 AM, Alex Harui  wrote:
> 
> Dave, 
> 
> What version of Maven are you running?  I think it has to be 3.3.x.
> 
> -Alex

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Harbs]

Why is that?

I have 3.5.2 installed. Is that why Maven never works for me?

Harbs

> On Nov 16, 2018, at 12:17 AM, Alex Harui  wrote:
> 
> Dave, 
> 
> What version of Maven are you running?  I think it has to be 3.3.x.
> 
> -Alex

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Alex Harui]

Dave, 

What version of Maven are you running?  I think it has to be 3.3.x.

-Alex

On 11/15/18, 2:07 PM, "Dave Fisher"  wrote:

Hi -

> On Nov 15, 2018, at 1:59 PM, Alex Harui  wrote:
> 
> Hi Dave,
> 
> 1) Thanks for checking.  You are right about lots of downloads, but we 
have reports that it does succeed in non-US places.
> 
> 2) That usually means you don’t' already have Flex artifacts.  Try 
building with: 
>mvn -s settings-template.xml clean install

No joy, same error.

Regards,
Dave

> 
> Thanks,
> -Alex
> 
> On 11/15/18, 1:51 PM, "Dave Fisher"  wrote:
> 
>Hi -
> 
>I did some validation on the release and have some observations 
particularly on the Maven build.
> 
>(1) It downloads a huge number of files from repository.apache.org and 
maven.repo.apache.org. This could be a source of trouble for people on 
different continents.
> 
>(2) It fails in asks with:
>[ERROR] Failed to execute goal 
org.apache.royale.compiler:royale-maven-plugin:0.9.4:compile-as 
(default-compile-as) on project Core: Could not resolve dependencies for 
project org.apache.royale.framework:Core:swc:0.9.4: Failure to find 
com.adobe.air.framework:airglobal:swc:20.0 in 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Freleasesdata=02%7C01%7Caharui%40adobe.com%7C7e0c5ac43a1e4af2d77608d64b46c842%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779164709402959sdata=Ze7FENzckxrSEMxpmg7jkVVo6aN27EAGXErgSepRg64%3Dreserved=0
 was cached in the local repository, resolution will not be reattempted until 
the update interval of apache-release has elapsed or updates are forced -> 
[Help 1]
>[ERROR] 
>[ERROR] To see the full stack trace of the errors, re-run Maven with 
the -e switch.
>[ERROR] Re-run Maven using the -X switch to enable full debug logging.
>[ERROR] 
>[ERROR] For more information about the errors and possible solutions, 
please read the following articles:
>[ERROR] [Help 1] 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FMAVEN%2FMojoExecutionExceptiondata=02%7C01%7Caharui%40adobe.com%7C7e0c5ac43a1e4af2d77608d64b46c842%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779164709402959sdata=ZBJs0Ug96nJuJVZsLHbE3HeS5TpRZHQftLeswqSqrPc%3Dreserved=0
> 
>This looks like a real problem with the Maven build
> 
>(3) The ant build worked fine although I was asked a couple of 
questions during the processing and that might confuse some people.
> 
>Regards,
>Dave
> 
> 
>> On Nov 15, 2018, at 12:57 PM, Dave Fisher  wrote:
>> 
>> To report back to the community. This is a very trivial issue and can be 
addressed easily in the NEXT release. Please do not let it distract you.
>> 
>> 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2Fbb24f08024e55a0e99da4a113dab438fe81a9eef5e3550b748e940c0%40%253Clegal-discuss.apache.org%253Edata=02%7C01%7Caharui%40adobe.com%7C7e0c5ac43a1e4af2d77608d64b46c842%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779164709402959sdata=%2B9FRnrqlmCohFtzC%2FxkaywLmDOcGXGpQkhMh46Msv2g%3Dreserved=0
>> 
>> Regards,
>> Dave
>> 
>>> On Nov 14, 2018, at 11:01 PM, Justin Mclean  
wrote:
>>> 
>>> Hi,
>>> 
>>> Re the modified non binary inclusion of CC BY-SA 3.0 licensed content 
I’ve asked on legal discuss as the resolved answered asks to do. [1]
>>> 
>>> Thanks,
>>> Justin
>>> 
>>> 1. 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Flegal%2Fresolved.html%23cc-sadata=02%7C01%7Caharui%40adobe.com%7C7e0c5ac43a1e4af2d77608d64b46c842%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779164709412968sdata=VQGs4B5xz0O5uHvWXFo%2BwtbluMKJaKTcUQS%2FFwP9XOU%3Dreserved=0
>> 
> 
> 
> 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Dave Fisher]

Hi -

> On Nov 15, 2018, at 1:59 PM, Alex Harui  wrote:
> 
> Hi Dave,
> 
> 1) Thanks for checking.  You are right about lots of downloads, but we have 
> reports that it does succeed in non-US places.
> 
> 2) That usually means you don’t' already have Flex artifacts.  Try building 
> with: 
>mvn -s settings-template.xml clean install

No joy, same error.

Regards,
Dave

> 
> Thanks,
> -Alex
> 
> On 11/15/18, 1:51 PM, "Dave Fisher"  wrote:
> 
>Hi -
> 
>I did some validation on the release and have some observations 
> particularly on the Maven build.
> 
>(1) It downloads a huge number of files from repository.apache.org and 
> maven.repo.apache.org. This could be a source of trouble for people on 
> different continents.
> 
>(2) It fails in asks with:
>[ERROR] Failed to execute goal 
> org.apache.royale.compiler:royale-maven-plugin:0.9.4:compile-as 
> (default-compile-as) on project Core: Could not resolve dependencies for 
> project org.apache.royale.framework:Core:swc:0.9.4: Failure to find 
> com.adobe.air.framework:airglobal:swc:20.0 in 
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Freleasesdata=02%7C01%7Caharui%40adobe.com%7Cf9bcbd2877134b95ef8508d64b447b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779154848452934sdata=km1iZjKngu54%2FFDvN6mYZVmHhqIfx%2Bh6ls6nftiKEt4%3Dreserved=0
>  was cached in the local repository, resolution will not be reattempted until 
> the update interval of apache-release has elapsed or updates are forced -> 
> [Help 1]
>[ERROR] 
>[ERROR] To see the full stack trace of the errors, re-run Maven with the 
> -e switch.
>[ERROR] Re-run Maven using the -X switch to enable full debug logging.
>[ERROR] 
>[ERROR] For more information about the errors and possible solutions, 
> please read the following articles:
>[ERROR] [Help 1] 
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FMAVEN%2FMojoExecutionExceptiondata=02%7C01%7Caharui%40adobe.com%7Cf9bcbd2877134b95ef8508d64b447b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779154848452934sdata=l0CgXdhlLZ5Bki6pWE8j9kFJT%2Fw0HRVJRT5weguQxCE%3Dreserved=0
> 
>This looks like a real problem with the Maven build
> 
>(3) The ant build worked fine although I was asked a couple of questions 
> during the processing and that might confuse some people.
> 
>Regards,
>Dave
> 
> 
>> On Nov 15, 2018, at 12:57 PM, Dave Fisher  wrote:
>> 
>> To report back to the community. This is a very trivial issue and can be 
>> addressed easily in the NEXT release. Please do not let it distract you.
>> 
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2Fbb24f08024e55a0e99da4a113dab438fe81a9eef5e3550b748e940c0%40%253Clegal-discuss.apache.org%253Edata=02%7C01%7Caharui%40adobe.com%7Cf9bcbd2877134b95ef8508d64b447b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779154848452934sdata=BcKDUjWXiFdCYPqC%2B6liRNNU3YRHgcGs9zA10SDAJgE%3Dreserved=0
>> 
>> Regards,
>> Dave
>> 
>>> On Nov 14, 2018, at 11:01 PM, Justin Mclean  
>>> wrote:
>>> 
>>> Hi,
>>> 
>>> Re the modified non binary inclusion of CC BY-SA 3.0 licensed content I’ve 
>>> asked on legal discuss as the resolved answered asks to do. [1]
>>> 
>>> Thanks,
>>> Justin
>>> 
>>> 1. 
>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Flegal%2Fresolved.html%23cc-sadata=02%7C01%7Caharui%40adobe.com%7Cf9bcbd2877134b95ef8508d64b447b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779154848452934sdata=ZIMuX4jNL3q7a2TXnSNUVCKCTJ%2FRDgCckhF8FwYzapU%3Dreserved=0
>> 
> 
> 
> 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Piotr Zarzycki]

Ahh! You have tried to build sources :) My mistake, so it should probably
work with Alex's suggestion.

On Thu, Nov 15, 2018, 11:03 PM Piotr Zarzycki 
wrote:

> Hi Dave, Alex,
>
> I think it is important to remember that in order to test those artifacts
> you need to put link in the settings in Maven to staging area.
>
> Piotr
>
> On Thu, Nov 15, 2018, 10:59 PM Alex Harui 
> wrote:
>
>> Hi Dave,
>>
>> 1) Thanks for checking.  You are right about lots of downloads, but we
>> have reports that it does succeed in non-US places.
>>
>> 2) That usually means you don’t' already have Flex artifacts.  Try
>> building with:
>> mvn -s settings-template.xml clean install
>>
>> Thanks,
>> -Alex
>>
>> On 11/15/18, 1:51 PM, "Dave Fisher"  wrote:
>>
>> Hi -
>>
>> I did some validation on the release and have some observations
>> particularly on the Maven build.
>>
>> (1) It downloads a huge number of files from repository.apache.org
>> and maven.repo.apache.org. This could be a source of trouble for people
>> on different continents.
>>
>> (2) It fails in asks with:
>> [ERROR] Failed to execute goal
>> org.apache.royale.compiler:royale-maven-plugin:0.9.4:compile-as
>> (default-compile-as) on project Core: Could not resolve dependencies for
>> project org.apache.royale.framework:Core:swc:0.9.4: Failure to find
>> com.adobe.air.framework:airglobal:swc:20.0 in
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Freleasesdata=02%7C01%7Caharui%40adobe.com%7Cf9bcbd2877134b95ef8508d64b447b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779154848452934sdata=km1iZjKngu54%2FFDvN6mYZVmHhqIfx%2Bh6ls6nftiKEt4%3Dreserved=0
>> was cached in the local repository, resolution will not be reattempted
>> until the update interval of apache-release has elapsed or updates are
>> forced -> [Help 1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with
>> the -e switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [ERROR]
>> [ERROR] For more information about the errors and possible solutions,
>> please read the following articles:
>> [ERROR] [Help 1]
>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FMAVEN%2FMojoExecutionExceptiondata=02%7C01%7Caharui%40adobe.com%7Cf9bcbd2877134b95ef8508d64b447b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779154848452934sdata=l0CgXdhlLZ5Bki6pWE8j9kFJT%2Fw0HRVJRT5weguQxCE%3Dreserved=0
>>
>> This looks like a real problem with the Maven build
>>
>> (3) The ant build worked fine although I was asked a couple of
>> questions during the processing and that might confuse some people.
>>
>> Regards,
>> Dave
>>
>>
>> > On Nov 15, 2018, at 12:57 PM, Dave Fisher 
>> wrote:
>> >
>> > To report back to the community. This is a very trivial issue and
>> can be addressed easily in the NEXT release. Please do not let it distract
>> you.
>> >
>> >
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2Fbb24f08024e55a0e99da4a113dab438fe81a9eef5e3550b748e940c0%40%253Clegal-discuss.apache.org%253Edata=02%7C01%7Caharui%40adobe.com%7Cf9bcbd2877134b95ef8508d64b447b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779154848452934sdata=BcKDUjWXiFdCYPqC%2B6liRNNU3YRHgcGs9zA10SDAJgE%3Dreserved=0
>> >
>> > Regards,
>> > Dave
>> >
>> >> On Nov 14, 2018, at 11:01 PM, Justin Mclean <
>> jus...@classsoftware.com> wrote:
>> >>
>> >> Hi,
>> >>
>> >> Re the modified non binary inclusion of CC BY-SA 3.0 licensed
>> content I’ve asked on legal discuss as the resolved answered asks to do. [1]
>> >>
>> >> Thanks,
>> >> Justin
>> >>
>> >> 1.
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Flegal%2Fresolved.html%23cc-sadata=02%7C01%7Caharui%40adobe.com%7Cf9bcbd2877134b95ef8508d64b447b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779154848452934sdata=ZIMuX4jNL3q7a2TXnSNUVCKCTJ%2FRDgCckhF8FwYzapU%3Dreserved=0
>> >
>>
>>
>>
>>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Piotr Zarzycki]

Hi Dave, Alex,

I think it is important to remember that in order to test those artifacts
you need to put link in the settings in Maven to staging area.

Piotr

On Thu, Nov 15, 2018, 10:59 PM Alex Harui  wrote:

> Hi Dave,
>
> 1) Thanks for checking.  You are right about lots of downloads, but we
> have reports that it does succeed in non-US places.
>
> 2) That usually means you don’t' already have Flex artifacts.  Try
> building with:
> mvn -s settings-template.xml clean install
>
> Thanks,
> -Alex
>
> On 11/15/18, 1:51 PM, "Dave Fisher"  wrote:
>
> Hi -
>
> I did some validation on the release and have some observations
> particularly on the Maven build.
>
> (1) It downloads a huge number of files from repository.apache.org
> and maven.repo.apache.org. This could be a source of trouble for people
> on different continents.
>
> (2) It fails in asks with:
> [ERROR] Failed to execute goal
> org.apache.royale.compiler:royale-maven-plugin:0.9.4:compile-as
> (default-compile-as) on project Core: Could not resolve dependencies for
> project org.apache.royale.framework:Core:swc:0.9.4: Failure to find
> com.adobe.air.framework:airglobal:swc:20.0 in
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Freleasesdata=02%7C01%7Caharui%40adobe.com%7Cf9bcbd2877134b95ef8508d64b447b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779154848452934sdata=km1iZjKngu54%2FFDvN6mYZVmHhqIfx%2Bh6ls6nftiKEt4%3Dreserved=0
> was cached in the local repository, resolution will not be reattempted
> until the update interval of apache-release has elapsed or updates are
> forced -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with
> the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FMAVEN%2FMojoExecutionExceptiondata=02%7C01%7Caharui%40adobe.com%7Cf9bcbd2877134b95ef8508d64b447b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779154848452934sdata=l0CgXdhlLZ5Bki6pWE8j9kFJT%2Fw0HRVJRT5weguQxCE%3Dreserved=0
>
> This looks like a real problem with the Maven build
>
> (3) The ant build worked fine although I was asked a couple of
> questions during the processing and that might confuse some people.
>
> Regards,
> Dave
>
>
> > On Nov 15, 2018, at 12:57 PM, Dave Fisher 
> wrote:
> >
> > To report back to the community. This is a very trivial issue and
> can be addressed easily in the NEXT release. Please do not let it distract
> you.
> >
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2Fbb24f08024e55a0e99da4a113dab438fe81a9eef5e3550b748e940c0%40%253Clegal-discuss.apache.org%253Edata=02%7C01%7Caharui%40adobe.com%7Cf9bcbd2877134b95ef8508d64b447b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779154848452934sdata=BcKDUjWXiFdCYPqC%2B6liRNNU3YRHgcGs9zA10SDAJgE%3Dreserved=0
> >
> > Regards,
> > Dave
> >
> >> On Nov 14, 2018, at 11:01 PM, Justin Mclean <
> jus...@classsoftware.com> wrote:
> >>
> >> Hi,
> >>
> >> Re the modified non binary inclusion of CC BY-SA 3.0 licensed
> content I’ve asked on legal discuss as the resolved answered asks to do. [1]
> >>
> >> Thanks,
> >> Justin
> >>
> >> 1.
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Flegal%2Fresolved.html%23cc-sadata=02%7C01%7Caharui%40adobe.com%7Cf9bcbd2877134b95ef8508d64b447b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779154848452934sdata=ZIMuX4jNL3q7a2TXnSNUVCKCTJ%2FRDgCckhF8FwYzapU%3Dreserved=0
> >
>
>
>
>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Alex Harui]

Hi Dave,

1) Thanks for checking.  You are right about lots of downloads, but we have 
reports that it does succeed in non-US places.

2) That usually means you don’t' already have Flex artifacts.  Try building 
with: 
mvn -s settings-template.xml clean install

Thanks,
-Alex

On 11/15/18, 1:51 PM, "Dave Fisher"  wrote:

Hi -

I did some validation on the release and have some observations 
particularly on the Maven build.

(1) It downloads a huge number of files from repository.apache.org and 
maven.repo.apache.org. This could be a source of trouble for people on 
different continents.

(2) It fails in asks with:
[ERROR] Failed to execute goal 
org.apache.royale.compiler:royale-maven-plugin:0.9.4:compile-as 
(default-compile-as) on project Core: Could not resolve dependencies for 
project org.apache.royale.framework:Core:swc:0.9.4: Failure to find 
com.adobe.air.framework:airglobal:swc:20.0 in 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Freleasesdata=02%7C01%7Caharui%40adobe.com%7Cf9bcbd2877134b95ef8508d64b447b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779154848452934sdata=km1iZjKngu54%2FFDvN6mYZVmHhqIfx%2Bh6ls6nftiKEt4%3Dreserved=0
 was cached in the local repository, resolution will not be reattempted until 
the update interval of apache-release has elapsed or updates are forced -> 
[Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, 
please read the following articles:
[ERROR] [Help 1] 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FMAVEN%2FMojoExecutionExceptiondata=02%7C01%7Caharui%40adobe.com%7Cf9bcbd2877134b95ef8508d64b447b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779154848452934sdata=l0CgXdhlLZ5Bki6pWE8j9kFJT%2Fw0HRVJRT5weguQxCE%3Dreserved=0

This looks like a real problem with the Maven build

(3) The ant build worked fine although I was asked a couple of questions 
during the processing and that might confuse some people.

Regards,
Dave


> On Nov 15, 2018, at 12:57 PM, Dave Fisher  wrote:
> 
> To report back to the community. This is a very trivial issue and can be 
addressed easily in the NEXT release. Please do not let it distract you.
> 
> 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2Fbb24f08024e55a0e99da4a113dab438fe81a9eef5e3550b748e940c0%40%253Clegal-discuss.apache.org%253Edata=02%7C01%7Caharui%40adobe.com%7Cf9bcbd2877134b95ef8508d64b447b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779154848452934sdata=BcKDUjWXiFdCYPqC%2B6liRNNU3YRHgcGs9zA10SDAJgE%3Dreserved=0
> 
> Regards,
> Dave
> 
>> On Nov 14, 2018, at 11:01 PM, Justin Mclean  
wrote:
>> 
>> Hi,
>> 
>> Re the modified non binary inclusion of CC BY-SA 3.0 licensed content 
I’ve asked on legal discuss as the resolved answered asks to do. [1]
>> 
>> Thanks,
>> Justin
>> 
>> 1. 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Flegal%2Fresolved.html%23cc-sadata=02%7C01%7Caharui%40adobe.com%7Cf9bcbd2877134b95ef8508d64b447b84%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779154848452934sdata=ZIMuX4jNL3q7a2TXnSNUVCKCTJ%2FRDgCckhF8FwYzapU%3Dreserved=0
> 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Dave Fisher]

Hi -

I did some validation on the release and have some observations particularly on 
the Maven build.

(1) It downloads a huge number of files from repository.apache.org and 
maven.repo.apache.org. This could be a source of trouble for people on 
different continents.

(2) It fails in asks with:
[ERROR] Failed to execute goal 
org.apache.royale.compiler:royale-maven-plugin:0.9.4:compile-as 
(default-compile-as) on project Core: Could not resolve dependencies for 
project org.apache.royale.framework:Core:swc:0.9.4: Failure to find 
com.adobe.air.framework:airglobal:swc:20.0 in 
https://repository.apache.org/content/repositories/releases was cached in the 
local repository, resolution will not be reattempted until the update interval 
of apache-release has elapsed or updates are forced -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

This looks like a real problem with the Maven build

(3) The ant build worked fine although I was asked a couple of questions during 
the processing and that might confuse some people.

Regards,
Dave


> On Nov 15, 2018, at 12:57 PM, Dave Fisher  wrote:
> 
> To report back to the community. This is a very trivial issue and can be 
> addressed easily in the NEXT release. Please do not let it distract you.
> 
> https://lists.apache.org/thread.html/bb24f08024e55a0e99da4a113dab438fe81a9eef5e3550b748e940c0@%3Clegal-discuss.apache.org%3E
> 
> Regards,
> Dave
> 
>> On Nov 14, 2018, at 11:01 PM, Justin Mclean  wrote:
>> 
>> Hi,
>> 
>> Re the modified non binary inclusion of CC BY-SA 3.0 licensed content I’ve 
>> asked on legal discuss as the resolved answered asks to do. [1]
>> 
>> Thanks,
>> Justin
>> 
>> 1. https://www.apache.org/legal/resolved.html#cc-sa
> 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Dave Fisher]

To report back to the community. This is a very trivial issue and can be 
addressed easily in the NEXT release. Please do not let it distract you.

https://lists.apache.org/thread.html/bb24f08024e55a0e99da4a113dab438fe81a9eef5e3550b748e940c0@%3Clegal-discuss.apache.org%3E

Regards,
Dave

> On Nov 14, 2018, at 11:01 PM, Justin Mclean  wrote:
> 
> Hi,
> 
> Re the modified non binary inclusion of CC BY-SA 3.0 licensed content I’ve 
> asked on legal discuss as the resolved answered asks to do. [1]
> 
> Thanks,
> Justin
> 
> 1. https://www.apache.org/legal/resolved.html#cc-sa

Re: Lets talk a bit about the release process (was Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2)

[OmPrakash Muppirala]

On Thu, Nov 15, 2018 at 2:02 AM Alex Harui  wrote:

> To be clear:  the process DOES NOT upload artifacts to Maven Central.  It
> uploads to the ASF staging repo.  Only after we approve the release do the
> artifacts get pushed to Maven Central.  One of the RMs got an error
> DOWNLOADING a Maven plugin from Maven Central.  There is nothing wrong with
> doing that.
>

Sorry, I misspoke.  But the question remains.  Why do we need to upload it
to the staging server during building or testing a release candidate?  Can
we not just use the local m2 repository for this?

In other words, what aspect of the release are we actually testing by
uploading stuff to the staging repo?



>
> Any volunteer is welcome to re-do the release scripts.  What we have now
> is what I think was the simplest sequence for creating both Maven and
> non-Maven artifacts.  Maven was the number 1 asked for feature in Adobe
> Flex.  IIRC, it had 100 votes and 2nd place was 12 votes.  So we support
> Maven in hopes that the customers we want to attract are using Maven, plus
> at least Carlos prefers to use Maven.
>
> Just like any other code or script in Royale, there can be bugs and room
> for improvement in the release process.  I found and fixed some issues, and
> hopefully the next RM will try the scripts after a month or so instead of 6
> months so fewer things will have become stale and broken.  In fact,  I
> think I will say that RC2 is my last RC for a while.  If we need an RC3,
> someone else should create it since the know the scripts recently worked
> for me.  And since it is fresh in my mind, I might be able to help the next
> RM better.  I think the problems Piotr and Yishay hit have been addressed.
> The only remaining issue is upload/download issues.
>

Thanks for getting the scripts to this shape!

Regards,
Om


>
> Thanks,
> -Alex
>
> On 11/14/18, 10:36 PM, "OmPrakash Muppirala" 
> wrote:
>
> Personally, I am not sure why we are uploading stuff to maven central
> as
> part of the RC process.  Can we simply bundle the source files and
> create a
> release candidate?  Folks who want to test maven can run the maven
> scripts
> locally which would copy stuff to the local .m2 repo instead.
> That way we dont force maven on folks who dont need it.
>
> Thoughts?
>
> Thanks,
> Om
>
>
>
> On Wed, Nov 14, 2018 at 12:54 PM Carlos Rovira <
> carlosrov...@apache.org>
> wrote:
>
> > Hi Alex,
> >
> > first congrats to reach to this point. After many months is great to
> > finally can release :)
> >
> > I forked the thread to avoid mixing topics and let the discuss
> thread to
> > just discuss the RC2
> >
> > I'll try RC2 soon, but first I want to talk about the inherent
> problem. I
> > know we are all here making a huge effort to make Royale work and
> shine,
> > and be release manager is to spend many hours working in that task,
> so
> > first I want to express as well a huge recognition to all RMs that
> tried to
> > make this happen before you. I still didn't try to make myself a
> release,
> > so I'm talking without the knowledge you all guys have, so sorry if
> I say
> > something inconvenient now, but just want to talk about the elephant
> in the
> > room, so we can improve the process from now own.
> >
> > My perception, from a person that is still outside the release
> process,
> > still does not have all the knowledge and never was a RM is that the
> > process is not reliable. Again hope nobody feels that talk about
> this is
> > any kind of attack, just that if we agree on that, we could try to
> improve
> > for the better. Right now seems that only Alex can make a release
> happen
> > due to his machine configuration. I assume all RMs execute the RM
> > instructions, so the problem is not related to the instructions, but
> seems
> > more to the nature of how we build.
> >
> > So, my question is, what we could change to ensure scripts and
> process are
> > reliable in all machines and doable by any of us?
> > Is the process a mix of maven and ant what is making this so hard to
> do?
> > Just a comment, could be the nature of ant (more single separated
> scripting
> > based on computer environment config vs structured building based on
> > building framework and servers) a problem?
> >
> > I want to be a RM soon (hope to be available for this task around
> Feb-Mar
> > 2019), so its clear I still can say a word about the process just
> start
> > this thread and hoping no one feels this as an attack (since I
> recognize
> > the huge effort done to reach this point), but just a way to start
> trying
> > to think with open mind and see that we have at least a thing to
> solve so
> > any of us can make the same as Alex do
> >
> > Thanks in advance for your thoughts :)
> >
> > Carlos
> >
> >
> >
> >
> >
> 

Re: Lets talk a bit about the release process (was Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2)

[Carlos Rovira]

Ok seems reasonable.
Thanks Alex

El jue., 15 nov. 2018 a las 18:50, Alex Harui ()
escribió:

> If we don't need another RC, then I hope someone volunteers to be the RM
> for 0.9.5 in December, before so many changes go in that the scripts may
> need fixing.
>
> On 11/15/18, 2:20 AM, "Carlos Rovira"  wrote:
>
> Ok Alex,
>
> so if Piotr, Om, or Yashay could try next RC maybe we could check it
> works
> for all. As soon as we have 2 different persons running successfully
> in two
> different machines I think will got it. Although maybe we don't need
> other
> RC... maybe could be good to try a new RC just for the purpose of
> check
> all the process, always taking into account that someone of the latest
> RMs
> have the time? I think getting success on this will make all of us more
> confident that we get finally a release process 1.0
>
> thanks!
>
> Carlos
>
>
>
> El jue., 15 nov. 2018 a las 11:02, Alex Harui
> ()
> escribió:
>
> > To be clear:  the process DOES NOT upload artifacts to Maven
> Central.  It
> > uploads to the ASF staging repo.  Only after we approve the release
> do the
> > artifacts get pushed to Maven Central.  One of the RMs got an error
> > DOWNLOADING a Maven plugin from Maven Central.  There is nothing
> wrong with
> > doing that.
> >
> > Any volunteer is welcome to re-do the release scripts.  What we have
> now
> > is what I think was the simplest sequence for creating both Maven and
> > non-Maven artifacts.  Maven was the number 1 asked for feature in
> Adobe
> > Flex.  IIRC, it had 100 votes and 2nd place was 12 votes.  So we
> support
> > Maven in hopes that the customers we want to attract are using
> Maven, plus
> > at least Carlos prefers to use Maven.
> >
> > Just like any other code or script in Royale, there can be bugs and
> room
> > for improvement in the release process.  I found and fixed some
> issues, and
> > hopefully the next RM will try the scripts after a month or so
> instead of 6
> > months so fewer things will have become stale and broken.  In fact,
> I
> > think I will say that RC2 is my last RC for a while.  If we need an
> RC3,
> > someone else should create it since the know the scripts recently
> worked
> > for me.  And since it is fresh in my mind, I might be able to help
> the next
> > RM better.  I think the problems Piotr and Yishay hit have been
> addressed.
> > The only remaining issue is upload/download issues.
> >
> > Thanks,
> > -Alex
> >
> > On 11/14/18, 10:36 PM, "OmPrakash Muppirala" 
> > wrote:
> >
> > Personally, I am not sure why we are uploading stuff to maven
> central
> > as
> > part of the RC process.  Can we simply bundle the source files
> and
> > create a
> > release candidate?  Folks who want to test maven can run the
> maven
> > scripts
> > locally which would copy stuff to the local .m2 repo instead.
> > That way we dont force maven on folks who dont need it.
> >
> > Thoughts?
> >
> > Thanks,
> > Om
> >
> >
> >
> > On Wed, Nov 14, 2018 at 12:54 PM Carlos Rovira <
> > carlosrov...@apache.org>
> > wrote:
> >
> > > Hi Alex,
> > >
> > > first congrats to reach to this point. After many months is
> great to
> > > finally can release :)
> > >
> > > I forked the thread to avoid mixing topics and let the discuss
> > thread to
> > > just discuss the RC2
> > >
> > > I'll try RC2 soon, but first I want to talk about the inherent
> > problem. I
> > > know we are all here making a huge effort to make Royale work
> and
> > shine,
> > > and be release manager is to spend many hours working in that
> task,
> > so
> > > first I want to express as well a huge recognition to all RMs
> that
> > tried to
> > > make this happen before you. I still didn't try to make myself
> a
> > release,
> > > so I'm talking without the knowledge you all guys have, so
> sorry if
> > I say
> > > something inconvenient now, but just want to talk about the
> elephant
> > in the
> > > room, so we can improve the process from now own.
> > >
> > > My perception, from a person that is still outside the release
> > process,
> > > still does not have all the knowledge and never was a RM is
> that the
> > > process is not reliable. Again hope nobody feels that talk
> about
> > this is
> > > any kind of attack, just that if we agree on that, we could
> try to
> > improve
> > > for the better. Right now seems that only Alex can make a
> release
> > happen
> > > due to his machine configuration. I assume all RMs execute the
> RM
> > > instructions, so the problem is 

Re: Lets talk a bit about the release process (was Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2)

[Alex Harui]

If we don't need another RC, then I hope someone volunteers to be the RM for 
0.9.5 in December, before so many changes go in that the scripts may need 
fixing.

On 11/15/18, 2:20 AM, "Carlos Rovira"  wrote:

Ok Alex,

so if Piotr, Om, or Yashay could try next RC maybe we could check it works
for all. As soon as we have 2 different persons running successfully in two
different machines I think will got it. Although maybe we don't need other
RC... maybe could be good to try a new RC just for the purpose of  check
all the process, always taking into account that someone of the latest RMs
have the time? I think getting success on this will make all of us more
confident that we get finally a release process 1.0

thanks!

Carlos



El jue., 15 nov. 2018 a las 11:02, Alex Harui ()
escribió:

> To be clear:  the process DOES NOT upload artifacts to Maven Central.  It
> uploads to the ASF staging repo.  Only after we approve the release do the
> artifacts get pushed to Maven Central.  One of the RMs got an error
> DOWNLOADING a Maven plugin from Maven Central.  There is nothing wrong 
with
> doing that.
>
> Any volunteer is welcome to re-do the release scripts.  What we have now
> is what I think was the simplest sequence for creating both Maven and
> non-Maven artifacts.  Maven was the number 1 asked for feature in Adobe
> Flex.  IIRC, it had 100 votes and 2nd place was 12 votes.  So we support
> Maven in hopes that the customers we want to attract are using Maven, plus
> at least Carlos prefers to use Maven.
>
> Just like any other code or script in Royale, there can be bugs and room
> for improvement in the release process.  I found and fixed some issues, 
and
> hopefully the next RM will try the scripts after a month or so instead of 
6
> months so fewer things will have become stale and broken.  In fact,  I
> think I will say that RC2 is my last RC for a while.  If we need an RC3,
> someone else should create it since the know the scripts recently worked
> for me.  And since it is fresh in my mind, I might be able to help the 
next
> RM better.  I think the problems Piotr and Yishay hit have been addressed.
> The only remaining issue is upload/download issues.
>
> Thanks,
> -Alex
>
> On 11/14/18, 10:36 PM, "OmPrakash Muppirala" 
> wrote:
>
> Personally, I am not sure why we are uploading stuff to maven central
> as
> part of the RC process.  Can we simply bundle the source files and
> create a
> release candidate?  Folks who want to test maven can run the maven
> scripts
> locally which would copy stuff to the local .m2 repo instead.
> That way we dont force maven on folks who dont need it.
>
> Thoughts?
>
> Thanks,
> Om
>
>
>
> On Wed, Nov 14, 2018 at 12:54 PM Carlos Rovira <
> carlosrov...@apache.org>
> wrote:
>
> > Hi Alex,
> >
> > first congrats to reach to this point. After many months is great to
> > finally can release :)
> >
> > I forked the thread to avoid mixing topics and let the discuss
> thread to
> > just discuss the RC2
> >
> > I'll try RC2 soon, but first I want to talk about the inherent
> problem. I
> > know we are all here making a huge effort to make Royale work and
> shine,
> > and be release manager is to spend many hours working in that task,
> so
> > first I want to express as well a huge recognition to all RMs that
> tried to
> > make this happen before you. I still didn't try to make myself a
> release,
> > so I'm talking without the knowledge you all guys have, so sorry if
> I say
> > something inconvenient now, but just want to talk about the elephant
> in the
> > room, so we can improve the process from now own.
> >
> > My perception, from a person that is still outside the release
> process,
> > still does not have all the knowledge and never was a RM is that the
> > process is not reliable. Again hope nobody feels that talk about
> this is
> > any kind of attack, just that if we agree on that, we could try to
> improve
> > for the better. Right now seems that only Alex can make a release
> happen
> > due to his machine configuration. I assume all RMs execute the RM
> > instructions, so the problem is not related to the instructions, but
> seems
> > more to the nature of how we build.
> >
> > So, my question is, what we could change to ensure scripts and
> process are
> > reliable in all machines and doable by any of us?
> > Is the process a mix of maven and ant what is making this so hard 

Re: Lets talk a bit about the release process (was Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2)

[Alex Harui]

I don't know if plugins remain on Apache's maven repo after they are pushed to 
Maven Central, but for me, I was having trouble pushing the artifacts to 
Apache's maven repo if my network was too busy.  No matter what, we have to get 
the bits from the developer's machine to some server, and that communication 
can fail.  IIRC, that communication to the Apache maven repo was way more 
likely to fail than downloads from Maven Central, but if we are going to make 
Maven artifacts available, which I think we should, we pretty much have to 
communicate with that server.  Hopefully the next people to try it will try to 
have less going on in their network, but also, we know that there is nothing 
wrong with the "process" so problems like these can be investigated as a server 
communication problem and not a problem with the scripts.

My 2 cents,
-Alex

On 11/15/18, 8:50 AM, "Guild, Jason A (DOT)"  wrote:

Any dependency on a public repository, even just for downloading, is 
problematic from a consistency POV because the repo could be down/slow 
or suddenly resolve to wrong/missing artifacts.

Maybe all plugins needed by the build could just be mirrored from 
Apache's maven repository?

On 11/15/2018 1:02 AM, Alex Harui wrote:
> Only after we approve the release do the artifacts get pushed to Maven 
Central.  One of the RMs got an error DOWNLOADING a Maven plugin from Maven 
Central.  There is nothing wrong with doing that.

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Piotr Zarzycki]

I tried build RC, but got timeout [1] during tests run. I will try tomorrow
again.

[1] https://paste.apache.org/vQps

Thanks,
Piotr


czw., 15 lis 2018 o 08:01 Justin Mclean 
napisał(a):

> Hi,
>
> Re the modified non binary inclusion of CC BY-SA 3.0 licensed content I’ve
> asked on legal discuss as the resolved answered asks to do. [1]
>
> Thanks,
> Justin
>
> 1. https://www.apache.org/legal/resolved.html#cc-sa



-- 

Piotr Zarzycki

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

Re: Lets talk a bit about the release process (was Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2)

[Guild, Jason A (DOT)]

Any dependency on a public repository, even just for downloading, is 
problematic from a consistency POV because the repo could be down/slow 
or suddenly resolve to wrong/missing artifacts.

Maybe all plugins needed by the build could just be mirrored from 
Apache's maven repository?

On 11/15/2018 1:02 AM, Alex Harui wrote:
> Only after we approve the release do the artifacts get pushed to Maven 
> Central.  One of the RMs got an error DOWNLOADING a Maven plugin from Maven 
> Central.  There is nothing wrong with doing that.

Re: Lets talk a bit about the release process (was Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2)

[Carlos Rovira]

Ok Alex,

so if Piotr, Om, or Yashay could try next RC maybe we could check it works
for all. As soon as we have 2 different persons running successfully in two
different machines I think will got it. Although maybe we don't need other
RC... maybe could be good to try a new RC just for the purpose of  check
all the process, always taking into account that someone of the latest RMs
have the time? I think getting success on this will make all of us more
confident that we get finally a release process 1.0

thanks!

Carlos



El jue., 15 nov. 2018 a las 11:02, Alex Harui ()
escribió:

> To be clear:  the process DOES NOT upload artifacts to Maven Central.  It
> uploads to the ASF staging repo.  Only after we approve the release do the
> artifacts get pushed to Maven Central.  One of the RMs got an error
> DOWNLOADING a Maven plugin from Maven Central.  There is nothing wrong with
> doing that.
>
> Any volunteer is welcome to re-do the release scripts.  What we have now
> is what I think was the simplest sequence for creating both Maven and
> non-Maven artifacts.  Maven was the number 1 asked for feature in Adobe
> Flex.  IIRC, it had 100 votes and 2nd place was 12 votes.  So we support
> Maven in hopes that the customers we want to attract are using Maven, plus
> at least Carlos prefers to use Maven.
>
> Just like any other code or script in Royale, there can be bugs and room
> for improvement in the release process.  I found and fixed some issues, and
> hopefully the next RM will try the scripts after a month or so instead of 6
> months so fewer things will have become stale and broken.  In fact,  I
> think I will say that RC2 is my last RC for a while.  If we need an RC3,
> someone else should create it since the know the scripts recently worked
> for me.  And since it is fresh in my mind, I might be able to help the next
> RM better.  I think the problems Piotr and Yishay hit have been addressed.
> The only remaining issue is upload/download issues.
>
> Thanks,
> -Alex
>
> On 11/14/18, 10:36 PM, "OmPrakash Muppirala" 
> wrote:
>
> Personally, I am not sure why we are uploading stuff to maven central
> as
> part of the RC process.  Can we simply bundle the source files and
> create a
> release candidate?  Folks who want to test maven can run the maven
> scripts
> locally which would copy stuff to the local .m2 repo instead.
> That way we dont force maven on folks who dont need it.
>
> Thoughts?
>
> Thanks,
> Om
>
>
>
> On Wed, Nov 14, 2018 at 12:54 PM Carlos Rovira <
> carlosrov...@apache.org>
> wrote:
>
> > Hi Alex,
> >
> > first congrats to reach to this point. After many months is great to
> > finally can release :)
> >
> > I forked the thread to avoid mixing topics and let the discuss
> thread to
> > just discuss the RC2
> >
> > I'll try RC2 soon, but first I want to talk about the inherent
> problem. I
> > know we are all here making a huge effort to make Royale work and
> shine,
> > and be release manager is to spend many hours working in that task,
> so
> > first I want to express as well a huge recognition to all RMs that
> tried to
> > make this happen before you. I still didn't try to make myself a
> release,
> > so I'm talking without the knowledge you all guys have, so sorry if
> I say
> > something inconvenient now, but just want to talk about the elephant
> in the
> > room, so we can improve the process from now own.
> >
> > My perception, from a person that is still outside the release
> process,
> > still does not have all the knowledge and never was a RM is that the
> > process is not reliable. Again hope nobody feels that talk about
> this is
> > any kind of attack, just that if we agree on that, we could try to
> improve
> > for the better. Right now seems that only Alex can make a release
> happen
> > due to his machine configuration. I assume all RMs execute the RM
> > instructions, so the problem is not related to the instructions, but
> seems
> > more to the nature of how we build.
> >
> > So, my question is, what we could change to ensure scripts and
> process are
> > reliable in all machines and doable by any of us?
> > Is the process a mix of maven and ant what is making this so hard to
> do?
> > Just a comment, could be the nature of ant (more single separated
> scripting
> > based on computer environment config vs structured building based on
> > building framework and servers) a problem?
> >
> > I want to be a RM soon (hope to be available for this task around
> Feb-Mar
> > 2019), so its clear I still can say a word about the process just
> start
> > this thread and hoping no one feels this as an attack (since I
> recognize
> > the huge effort done to reach this point), but just a way to start
> trying
> > to think with open mind and see that we have at least a thing to
> solve so
> > 

Re: Lets talk a bit about the release process (was Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2)

[Alex Harui]

To be clear:  the process DOES NOT upload artifacts to Maven Central.  It 
uploads to the ASF staging repo.  Only after we approve the release do the 
artifacts get pushed to Maven Central.  One of the RMs got an error DOWNLOADING 
a Maven plugin from Maven Central.  There is nothing wrong with doing that.

Any volunteer is welcome to re-do the release scripts.  What we have now is 
what I think was the simplest sequence for creating both Maven and non-Maven 
artifacts.  Maven was the number 1 asked for feature in Adobe Flex.  IIRC, it 
had 100 votes and 2nd place was 12 votes.  So we support Maven in hopes that 
the customers we want to attract are using Maven, plus at least Carlos prefers 
to use Maven.

Just like any other code or script in Royale, there can be bugs and room for 
improvement in the release process.  I found and fixed some issues, and 
hopefully the next RM will try the scripts after a month or so instead of 6 
months so fewer things will have become stale and broken.  In fact,  I think I 
will say that RC2 is my last RC for a while.  If we need an RC3, someone else 
should create it since the know the scripts recently worked for me.  And since 
it is fresh in my mind, I might be able to help the next RM better.  I think 
the problems Piotr and Yishay hit have been addressed.  The only remaining 
issue is upload/download issues.

Thanks,
-Alex

On 11/14/18, 10:36 PM, "OmPrakash Muppirala"  wrote:

Personally, I am not sure why we are uploading stuff to maven central as
part of the RC process.  Can we simply bundle the source files and create a
release candidate?  Folks who want to test maven can run the maven scripts
locally which would copy stuff to the local .m2 repo instead.
That way we dont force maven on folks who dont need it.

Thoughts?

Thanks,
Om



On Wed, Nov 14, 2018 at 12:54 PM Carlos Rovira 
wrote:

> Hi Alex,
>
> first congrats to reach to this point. After many months is great to
> finally can release :)
>
> I forked the thread to avoid mixing topics and let the discuss thread to
> just discuss the RC2
>
> I'll try RC2 soon, but first I want to talk about the inherent problem. I
> know we are all here making a huge effort to make Royale work and shine,
> and be release manager is to spend many hours working in that task, so
> first I want to express as well a huge recognition to all RMs that tried 
to
> make this happen before you. I still didn't try to make myself a release,
> so I'm talking without the knowledge you all guys have, so sorry if I say
> something inconvenient now, but just want to talk about the elephant in 
the
> room, so we can improve the process from now own.
>
> My perception, from a person that is still outside the release process,
> still does not have all the knowledge and never was a RM is that the
> process is not reliable. Again hope nobody feels that talk about this is
> any kind of attack, just that if we agree on that, we could try to improve
> for the better. Right now seems that only Alex can make a release happen
> due to his machine configuration. I assume all RMs execute the RM
> instructions, so the problem is not related to the instructions, but seems
> more to the nature of how we build.
>
> So, my question is, what we could change to ensure scripts and process are
> reliable in all machines and doable by any of us?
> Is the process a mix of maven and ant what is making this so hard to do?
> Just a comment, could be the nature of ant (more single separated 
scripting
> based on computer environment config vs structured building based on
> building framework and servers) a problem?
>
> I want to be a RM soon (hope to be available for this task around Feb-Mar
> 2019), so its clear I still can say a word about the process just start
> this thread and hoping no one feels this as an attack (since I recognize
> the huge effort done to reach this point), but just a way to start trying
> to think with open mind and see that we have at least a thing to solve so
> any of us can make the same as Alex do
>
> Thanks in advance for your thoughts :)
>
> Carlos
>
>
>
>
>
> El mié., 14 nov. 2018 a las 19:46, Alex Harui ()
> escribió:
>
> > This is the discussion thread.   RC1 was never put up for vote because
> > there
> > were issues with the notice files and build scripts when running from 
the
> > packages and not the repo.
> >
> > Interestingly, the scripts ran just fine for me on my home Windows
> > computer.
> > I did not have the problems Om, Piotr, and Yishay had when uploading or
> > downloading Maven artifacts.  Except when I tried watching videos while
> > waiting for the scripts to run (the "maven" target takes 2 hours in
> > 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Justin Mclean]

Hi,

Re the modified non binary inclusion of CC BY-SA 3.0 licensed content I’ve 
asked on legal discuss as the resolved answered asks to do. [1]

Thanks,
Justin

1. https://www.apache.org/legal/resolved.html#cc-sa

Re: Lets talk a bit about the release process (was Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2)

[Carlos Rovira]

Hi Om,

(again talking from my no experience in the process), can this be the
problem that make RMs fail on the process? From the external point of a
viewer, this seems more related to scripting/manual issues. Normally Maven
steps are hard to get working, but once you got it, use to work for all
people. It seems to me like a more "industrial" process that should ensure
independence of platform and custom configurations.

Thanks for sharing

Carlos


El jue., 15 nov. 2018 a las 7:36, OmPrakash Muppirala ()
escribió:

> Personally, I am not sure why we are uploading stuff to maven central as
> part of the RC process.  Can we simply bundle the source files and create a
> release candidate?  Folks who want to test maven can run the maven scripts
> locally which would copy stuff to the local .m2 repo instead.
> That way we dont force maven on folks who dont need it.
>
> Thoughts?
>
> Thanks,
> Om
>
>
>
> On Wed, Nov 14, 2018 at 12:54 PM Carlos Rovira 
> wrote:
>
> > Hi Alex,
> >
> > first congrats to reach to this point. After many months is great to
> > finally can release :)
> >
> > I forked the thread to avoid mixing topics and let the discuss thread to
> > just discuss the RC2
> >
> > I'll try RC2 soon, but first I want to talk about the inherent problem. I
> > know we are all here making a huge effort to make Royale work and shine,
> > and be release manager is to spend many hours working in that task, so
> > first I want to express as well a huge recognition to all RMs that tried
> to
> > make this happen before you. I still didn't try to make myself a release,
> > so I'm talking without the knowledge you all guys have, so sorry if I say
> > something inconvenient now, but just want to talk about the elephant in
> the
> > room, so we can improve the process from now own.
> >
> > My perception, from a person that is still outside the release process,
> > still does not have all the knowledge and never was a RM is that the
> > process is not reliable. Again hope nobody feels that talk about this is
> > any kind of attack, just that if we agree on that, we could try to
> improve
> > for the better. Right now seems that only Alex can make a release happen
> > due to his machine configuration. I assume all RMs execute the RM
> > instructions, so the problem is not related to the instructions, but
> seems
> > more to the nature of how we build.
> >
> > So, my question is, what we could change to ensure scripts and process
> are
> > reliable in all machines and doable by any of us?
> > Is the process a mix of maven and ant what is making this so hard to do?
> > Just a comment, could be the nature of ant (more single separated
> scripting
> > based on computer environment config vs structured building based on
> > building framework and servers) a problem?
> >
> > I want to be a RM soon (hope to be available for this task around Feb-Mar
> > 2019), so its clear I still can say a word about the process just start
> > this thread and hoping no one feels this as an attack (since I recognize
> > the huge effort done to reach this point), but just a way to start trying
> > to think with open mind and see that we have at least a thing to solve so
> > any of us can make the same as Alex do
> >
> > Thanks in advance for your thoughts :)
> >
> > Carlos
> >
> >
> >
> >
> >
> > El mié., 14 nov. 2018 a las 19:46, Alex Harui ()
> > escribió:
> >
> > > This is the discussion thread.   RC1 was never put up for vote because
> > > there
> > > were issues with the notice files and build scripts when running from
> the
> > > packages and not the repo.
> > >
> > > Interestingly, the scripts ran just fine for me on my home Windows
> > > computer.
> > > I did not have the problems Om, Piotr, and Yishay had when uploading or
> > > downloading Maven artifacts.  Except when I tried watching videos while
> > > waiting for the scripts to run (the "maven" target takes 2 hours in
> > > Powershell, the "main" target took over an hour).   Then I would see
> > > uploads
> > > "hang".   So I would recommend to any future RMs to try to make sure
> the
> > > network is not otherwise too busy when running these scripts.
> > >
> > > Changes in this RC include:
> > >
> > >
> > >
> > > Thanks,
> > > Alex Harui
> > >
> > >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>


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

Re: Lets talk a bit about the release process (was Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2)

[OmPrakash Muppirala]

Personally, I am not sure why we are uploading stuff to maven central as
part of the RC process.  Can we simply bundle the source files and create a
release candidate?  Folks who want to test maven can run the maven scripts
locally which would copy stuff to the local .m2 repo instead.
That way we dont force maven on folks who dont need it.

Thoughts?

Thanks,
Om



On Wed, Nov 14, 2018 at 12:54 PM Carlos Rovira 
wrote:

> Hi Alex,
>
> first congrats to reach to this point. After many months is great to
> finally can release :)
>
> I forked the thread to avoid mixing topics and let the discuss thread to
> just discuss the RC2
>
> I'll try RC2 soon, but first I want to talk about the inherent problem. I
> know we are all here making a huge effort to make Royale work and shine,
> and be release manager is to spend many hours working in that task, so
> first I want to express as well a huge recognition to all RMs that tried to
> make this happen before you. I still didn't try to make myself a release,
> so I'm talking without the knowledge you all guys have, so sorry if I say
> something inconvenient now, but just want to talk about the elephant in the
> room, so we can improve the process from now own.
>
> My perception, from a person that is still outside the release process,
> still does not have all the knowledge and never was a RM is that the
> process is not reliable. Again hope nobody feels that talk about this is
> any kind of attack, just that if we agree on that, we could try to improve
> for the better. Right now seems that only Alex can make a release happen
> due to his machine configuration. I assume all RMs execute the RM
> instructions, so the problem is not related to the instructions, but seems
> more to the nature of how we build.
>
> So, my question is, what we could change to ensure scripts and process are
> reliable in all machines and doable by any of us?
> Is the process a mix of maven and ant what is making this so hard to do?
> Just a comment, could be the nature of ant (more single separated scripting
> based on computer environment config vs structured building based on
> building framework and servers) a problem?
>
> I want to be a RM soon (hope to be available for this task around Feb-Mar
> 2019), so its clear I still can say a word about the process just start
> this thread and hoping no one feels this as an attack (since I recognize
> the huge effort done to reach this point), but just a way to start trying
> to think with open mind and see that we have at least a thing to solve so
> any of us can make the same as Alex do
>
> Thanks in advance for your thoughts :)
>
> Carlos
>
>
>
>
>
> El mié., 14 nov. 2018 a las 19:46, Alex Harui ()
> escribió:
>
> > This is the discussion thread.   RC1 was never put up for vote because
> > there
> > were issues with the notice files and build scripts when running from the
> > packages and not the repo.
> >
> > Interestingly, the scripts ran just fine for me on my home Windows
> > computer.
> > I did not have the problems Om, Piotr, and Yishay had when uploading or
> > downloading Maven artifacts.  Except when I tried watching videos while
> > waiting for the scripts to run (the "maven" target takes 2 hours in
> > Powershell, the "main" target took over an hour).   Then I would see
> > uploads
> > "hang".   So I would recommend to any future RMs to try to make sure the
> > network is not otherwise too busy when running these scripts.
> >
> > Changes in this RC include:
> >
> >
> >
> > Thanks,
> > Alex Harui
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>

Lets talk a bit about the release process (was Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2)

[Carlos Rovira]

Hi Alex,

first congrats to reach to this point. After many months is great to
finally can release :)

I forked the thread to avoid mixing topics and let the discuss thread to
just discuss the RC2

I'll try RC2 soon, but first I want to talk about the inherent problem. I
know we are all here making a huge effort to make Royale work and shine,
and be release manager is to spend many hours working in that task, so
first I want to express as well a huge recognition to all RMs that tried to
make this happen before you. I still didn't try to make myself a release,
so I'm talking without the knowledge you all guys have, so sorry if I say
something inconvenient now, but just want to talk about the elephant in the
room, so we can improve the process from now own.

My perception, from a person that is still outside the release process,
still does not have all the knowledge and never was a RM is that the
process is not reliable. Again hope nobody feels that talk about this is
any kind of attack, just that if we agree on that, we could try to improve
for the better. Right now seems that only Alex can make a release happen
due to his machine configuration. I assume all RMs execute the RM
instructions, so the problem is not related to the instructions, but seems
more to the nature of how we build.

So, my question is, what we could change to ensure scripts and process are
reliable in all machines and doable by any of us?
Is the process a mix of maven and ant what is making this so hard to do?
Just a comment, could be the nature of ant (more single separated scripting
based on computer environment config vs structured building based on
building framework and servers) a problem?

I want to be a RM soon (hope to be available for this task around Feb-Mar
2019), so its clear I still can say a word about the process just start
this thread and hoping no one feels this as an attack (since I recognize
the huge effort done to reach this point), but just a way to start trying
to think with open mind and see that we have at least a thing to solve so
any of us can make the same as Alex do

Thanks in advance for your thoughts :)

Carlos





El mié., 14 nov. 2018 a las 19:46, Alex Harui ()
escribió:

> This is the discussion thread.   RC1 was never put up for vote because
> there
> were issues with the notice files and build scripts when running from the
> packages and not the repo.
>
> Interestingly, the scripts ran just fine for me on my home Windows
> computer.
> I did not have the problems Om, Piotr, and Yishay had when uploading or
> downloading Maven artifacts.  Except when I tried watching videos while
> waiting for the scripts to run (the "maven" target takes 2 hours in
> Powershell, the "main" target took over an hour).   Then I would see
> uploads
> "hang".   So I would recommend to any future RMs to try to make sure the
> network is not otherwise too busy when running these scripts.
>
> Changes in this RC include:
>
>
>
> Thanks,
> Alex Harui
>
>

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