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: [VOTE] Release Apache Royale 0.9.4 RC2

[Olaf Krueger]

Sorry for accidentally polluting the vote thread :-(
Moved the post to the discussion thread [1]

[1] 
http://apache-royale-development.20373.n8.nabble.com/DISCUSS-Discuss-Release-Apache-Royale-0-9-4-RC2-tp7390p7488.html




--
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: [VOTE] 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: [VOTE] Release Apache Royale 0.9.4 RC2

[OmPrakash Muppirala]

+1 (binding)

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: y

On Fri, Nov 16, 2018 at 12:45 AM Harbs  wrote:

> +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.12.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: y
>
> 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: y
>
> Harbs

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.gz&data=02%7C01%7Caharui%40adobe.com%7C8c3cb407a16444958a6608d64bf9caa6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779933553764185&sdata=Tthv90BnjMScTq%2BhUibnA6jkwG4lixaZMcljf1XFFRA%3D&reserved=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.gz&data=02%7C01%7Caharui%40adobe.com%7C8c3cb407a16444958a6608d64bf9caa6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779933553764185&sdata=tFHKiRf0Q9O1pljLLcak7fweZmV1C%2BZ3n0eEgmtd9R4%3D&reserved=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.html&data=02%7C01%7Caharui%40adobe.com%7C8c3cb407a16444958a6608d64bf9caa6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779933553764185&sdata=Xu12pHIo1Wk%2B5EolVMSK%2BOgTlkueYL68XbVqBKH0lx4%3D&reserved=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
> wo

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.gz&data=02%7C01%7Caharui%40adobe.com%7C8c3cb407a16444958a6608d64bf9caa6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779933553764185&sdata=Tthv90BnjMScTq%2BhUibnA6jkwG4lixaZMcljf1XFFRA%3D&reserved=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.gz&data=02%7C01%7Caharui%40adobe.com%7C8c3cb407a16444958a6608d64bf9caa6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779933553764185&sdata=tFHKiRf0Q9O1pljLLcak7fweZmV1C%2BZ3n0eEgmtd9R4%3D&reserved=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.html&data=02%7C01%7Caharui%40adobe.com%7C8c3cb407a16444958a6608d64bf9caa6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779933553764185&sdata=Xu12pHIo1Wk%2B5EolVMSK%2BOgTlkueYL68XbVqBKH0lx4%3D&reserved=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 b

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.html&data=02%7C01%7Caharui%40adobe.com%7Cc8e6e5458886453f685608d64bfa7006%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779936326108233&sdata=eky3JTT4tMT%2FQ4QHL2XdoyFBDyyvcG%2BL1biq0%2FF79iI%3D&reserved=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]
> >
> 
http

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.4&data=02%7C01%7Caharui%40adobe.com%7Ca479a284bbfc45f11c9008d64bf13cc8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636779896835985170&sdata=V3Uy1JRZoZT%2FNEQXhuz%2Bfb%2B9YebyrLd77GzEhwRfwpE%3D&reserved=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%2FMUAD&data=02%7C01%7Caharui%40adobe.com%7C5f6a285c3f6a4147f88f08d64bf4da54%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779912346752062&sdata=dhwVb5SBKH55hRXcfoA8kGM0XGBG3Tn3O3UojQZ0msc%3D&reserved=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
> > folde

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 t

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%2FMUAD&data=02%7C01%7Caharui%40adobe.com%7C5f6a285c3f6a4147f88f08d64bf4da54%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779912346752062&sdata=dhwVb5SBKH55hRXcfoA8kGM0XGBG3Tn3O3UojQZ0msc%3D&reserved=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.4&data=02%7C01%7Caharui%40adobe.com%7Ca479a284bbfc45f11c9008d64bf13cc8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636779896835985170&sdata=V3Uy1JRZoZT%2FNEQXhuz%2Bfb%2B9YebyrLd77GzEhwRfwpE%3D&reserved=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,
 -A

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%2FMUAD&data=02%7C01%7Caharui%40adobe.com%7C39975fb0dc1e44d8dc9408d64bc1ad21%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779692539144991&sdata=Q0BIfl5E4ClKrqbptLo56Chmmf6Olno7r7Kapjx8XZ4%3D&reserved=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%2F6UPt&data=02%7C01%7Caharui%40adobe.com%7C39975fb0dc1e44d8dc9408d64bc1ad21%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779692539144991&sdata=zsEViovGTCj519MQTZjTWC5HUL7O9TxGuNbtFzemdUA%3D&reserved=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 actionsc

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.4&data=02%7C01%7Caharui%40adobe.com%7Ca479a284bbfc45f11c9008d64bf13cc8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636779896835985170&sdata=V3Uy1JRZoZT%2FNEQXhuz%2Bfb%2B9YebyrLd77GzEhwRfwpE%3D&reserved=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
>>> dow

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 6:21

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%2FMUAD&data=02%7C01%7Caharui%40adobe.com%7C39975fb0dc1e44d8dc9408d64bc1ad21%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779692539144991&sdata=Q0BIfl5E4ClKrqbptLo56Chmmf6Olno7r7Kapjx8XZ4%3D&reserved=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%2F6UPt&data=02%7C01%7Caharui%40adobe.com%7C39975fb0dc1e44d8dc9408d64bc1ad21%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779692539144991&sdata=zsEViovGTCj519MQTZjTWC5HUL7O9TxGuNbtFzemdUA%3D&reserved=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 

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

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%2FyBNf&data=02%7C01%7Caharui%40adobe.com%7C7931243fa0004c78011308d64b8e89f6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779472910908290&sdata=EzNAtqfkryWkRDjATNbf6rxN1TfudGCWR6qW5uOeIlQ%3D&reserved=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 output

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:
> 
> 
> >>>
> >>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2FyBNf&data=02%7C

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%2FyBNf&data=02%7C01%7Caharui%40adobe.com%7C7931243fa0004c78011308d64b8e89f6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779472910908290&sdata=EzNAtqfkryWkRDjATNbf6rxN1TfudGCWR6qW5uOeIlQ%3D&reserved=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 de

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%2F6UPt&data=02%7C01%7Caharui%40adobe.com%7Cd8b9ff82ff9c481a23ff08d64b9e0feb%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779539571723668&sdata=KOqUjui3kMSnFwGPfP8VDqgd2SF%2FrJSEXANq%2BFGaCE0%3D&reserved=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/

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%2F6UPt&data=02%7C01%7Caharui%40adobe.com%7Cd8b9ff82ff9c481a23ff08d64b9e0feb%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779539571723668&sdata=KOqUjui3kMSnFwGPfP8VDqgd2SF%2FrJSEXANq%2BFGaCE0%3D&reserved=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 

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%2F6UPt&data=02%7C01%7Caharui%40adobe.com%7Cd8b9ff82ff9c481a23ff08d64b9e0feb%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779539571723668&sdata=KOqUjui3kMSnFwGPfP8VDqgd2SF%2FrJSEXANq%2BFGaCE0%3D&reserved=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.
> > > >
> > > > T

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%2F6UPt&data=02%7C01%7Caharui%40adobe.com%7Cd8b9ff82ff9c481a23ff08d64b9e0feb%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779539571723668&sdata=KOqUjui3kMSnFwGPfP8VDqgd2SF%2FrJSEXANq%2BFGaCE0%3D&reserved=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:
> > >
> > >
> >
> 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2FyBNf&data=02%7C01%7Caharui%40adobe.com%7C

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%2FyBNf&data=02%7C01%7Caharui%40adobe.com%7C7931243fa0004c78011308d64b8e89f6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779472910908290&sdata=EzNAtqfkryWkRDjATNbf6rxN1TfudGCWR6qW5uOeIlQ%3D&reserved=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: [VOTE] Release Apache Royale 0.9.4 RC2

[Harbs]

+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.12.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: y

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: y

Harbs

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%2FyBNf&data=02%7C01%7Caharui%40adobe.com%7C7931243fa0004c78011308d64b8e89f6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779472910908290&sdata=EzNAtqfkryWkRDjATNbf6rxN1TfudGCWR6qW5uOeIlQ%3D&reserved=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 dependen

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%2FyBNf&data=02%7C01%7Caharui%40adobe.com%7C7931243fa0004c78011308d64b8e89f6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779472910908290&sdata=EzNAtqfkryWkRDjATNbf6rxN1TfudGCWR6qW5uOeIlQ%3D&reserved=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]
> >>   [INF

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 th

Build failed in Jenkins: TourDeFlexMigration #161

[apacheroyaleci]

See 


Changes:

[aharui] fail build if swf compc fails

[aharui] instead of just , use more decoration so it is clear what you are 
trying

[aharui] fail if swf comic fails

[aharui] more cleanup of

[aharui] mustella must also handle

[aharui] fix localToGlobal

[aharui] more cleanup now that calls to super are checked for whether the member

[aharui] get more of MXTests working again

[aharui] need this file for fresh Maven builds

[aharui] tweak numeric stepper size so mxtests pass

--
[...truncated 32.33 KB...]
[mxmlc] scanning for overrides: ITableRowElement
[mxmlc] scanning for overrides: InlineGraphicElement
[mxmlc] scanning for overrides: SubParagraphGroupElementBase
[mxmlc] scanning for overrides: LinkElement
[mxmlc] scanning for overrides: ListElement
[mxmlc] scanning for overrides: ListItemElement
[mxmlc] scanning for overrides: TCYElement
[mxmlc] scanning for overrides: TabElement
[mxmlc] scanning for overrides: TableBlockContainer
[mxmlc] scanning for overrides: TableFormattedElement
[mxmlc] scanning for overrides: TableCellElement
[mxmlc] scanning for overrides: TableColElement
[mxmlc] scanning for overrides: TableRowElement
[mxmlc] scanning for overrides: TruncationOptions
[mxmlc] scanning for overrides: BackgroundColor
[mxmlc] scanning for overrides: BaselineOffset
[mxmlc] scanning for overrides: BaselineShift
[mxmlc] scanning for overrides: BorderColor
[mxmlc] scanning for overrides: BreakStyle
[mxmlc] scanning for overrides: Category
[mxmlc] scanning for overrides: ClearFloats
[mxmlc] scanning for overrides: ColorName
[mxmlc] scanning for overrides: Float
[mxmlc] scanning for overrides: IListMarkerFormat
[mxmlc] scanning for overrides: ListStylePosition
[mxmlc] scanning for overrides: ListStyleType
[mxmlc] scanning for overrides: TLFTypographicCase
[mxmlc] scanning for overrides: TableFrame
[mxmlc] scanning for overrides: TableRules
[mxmlc] scanning for overrides: TextDecoration
[mxmlc] scanning for overrides: VerticalAlign
[mxmlc] scanning for overrides: WhiteSpaceCollapse
[mxmlc] scanning for overrides: Property
[mxmlc] scanning for overrides: ArrayProperty
[mxmlc] scanning for overrides: PropertyFactory
[mxmlc] scanning for overrides: FactoryUtil
[mxmlc] scanning for overrides: BreakOpportunity
[mxmlc] scanning for overrides: CFFHinting
[mxmlc] scanning for overrides: DigitCase
[mxmlc] scanning for overrides: DigitWidth
[mxmlc] scanning for overrides: ElementFormat
[mxmlc] scanning for overrides: FontDescription
[mxmlc] scanning for overrides: FontLookup
[mxmlc] scanning for overrides: FontMetrics
[mxmlc] scanning for overrides: FontWeight
[mxmlc] scanning for overrides: ITextFactory
[mxmlc] scanning for overrides: JustificationStyle
[mxmlc] scanning for overrides: Kerning
[mxmlc] scanning for overrides: LigatureLevel
[mxmlc] scanning for overrides: RenderingMode
[mxmlc] scanning for overrides: TextBaseline
[mxmlc] scanning for overrides: TextElement
[mxmlc] scanning for overrides: HTMLTextFactory
[mxmlc] scanning for overrides: IBrowserEvent
[mxmlc] scanning for overrides: KeyboardEvent
[mxmlc] scanning for overrides: PathHelper
[mxmlc] scanning for overrides: PathSegmentsCollection
[mxmlc] scanning for overrides: PathSegment
[mxmlc] scanning for overrides: LineSegment
[mxmlc] scanning for overrides: MoveSegment
[mxmlc] scanning for overrides: CubicBezierSegment
[mxmlc] scanning for overrides: QuadraticPoints
[mxmlc] scanning for overrides: QuadraticBezierSegment
[mxmlc] scanning for overrides: EllipticalArcSegment
[mxmlc] scanning for overrides: PathBuilder
[mxmlc] scanning for overrides: SolidColor
[mxmlc] scanning for overrides: LogEvent
[mxmlc] scanning for overrides: AcknowledgeMessageExt
[mxmlc] scanning for overrides: CommandMessageExt
[mxmlc] scanning for overrides: MessagePerformanceInfo
[mxmlc] scanning for overrides: AbstractConsumer
[mxmlc] scanning for overrides: Consumer
[mxmlc] scanning for overrides: ConsumerMessageDispatcher
[mxmlc] scanning for overrides: ByteArray
[mxmlc] scanning for overrides: AMFBinaryData
[mxmlc] scanning for overrides: Traits
[mxmlc] scanning for overrides: NumberlineUtil
[mxmlc] scanning for overrides: StandardHelper
[mxmlc] scanning for overrides: TextLineUtil
[mxmlc] scanning for overrides: IFactoryComposer
[mxmlc] scanning for overrides: FlowComposerBase
[mxmlc] scanning for overrides: StandardFlowComposer
[mxmlc] scanning for overrides: FactoryComposer
[mxmlc] scanning for overrides: Parcel
[mxmlc] scanning for overrides: Span
[mxmlc] scanning for ove