Nightly Build Server going offline

2019-10-10 Thread Piotr Zarzycki
Ok I will, but first they need to be accessible outside ;) Not only for
commiters.

On Thu, Oct 10, 2019, 2:35 PM Carlos Rovira  wrote:

> Hi,
>
> I don't know if finally is better to change links on website. If so,
> please, let me know what links I must substitute and the new links to avoid
> confusion.
> Thanks
>
>
> El jue., 10 oct. 2019 a las 10:12, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > How can we expose Nightly build from new server outside ? Now if I would
> > like to send links it requires from me login.
> >
> > śr., 9 paź 2019 o 20:08 Alex Harui 
> napisał(a):
> >
> > > OK, I will switch the service to use the ApacheRoyaleCI account and see
> > > what happens.
> > >
> > > -ALex
> > >
> > > On 10/9/19, 9:12 AM, "Josh Tynjala" 
> wrote:
> > >
> > > Well, the build made it a bit further after I set the default app
> for
> > > .swf
> > > files. However, it seems that Flash Player is not picking up the
> > trust
> > > file
> > > that the RoyaleUnit Ant Task is creating. Based on the console log,
> > the
> > > Jenkins job seems to be creating it here:
> > >
> > >
> > >
> C:\windows\system32\config\systemprofile\AppData\Roaming\Macromedia\Flash
> > > Player\#Security\FlashPlayerTrust\royaleUnit.cfg
> > >
> > > Looking at Jenkins emails from the old server, it used to be in the
> > > user
> > > folder instead
> > >
> > > C:\Users\apacheroyale\AppData\Roaming\Macromedia\Flash
> > > Player\#Security\FlashPlayerTrust\royaleUnit.cfg
> > >
> > > I guess that would be C:\Users\ApacheRoyaleCI\ on the new server.
> It
> > > looks
> > > like royaleUnit.cfg exists in the user folder too, but I'm guessing
> > > that's
> > > from when I ran the tests manually. So maybe that's an interesting
> > > clue? Is
> > > the Jenkins job running as the ApacheRoyaleCI user, or could it be
> a
> > > different user account that can't access C:\Users\ApacheRoyaleCI\?
> I
> > > don't
> > > really know Jenkins, so I'm just throwing out ideas here.
> > >
> > > --
> > > Josh Tynjala
> > > Bowler Hat LLC <
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7Ca0a8b694fff24a69908b08d74cd380a7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637062343589197901sdata=CiqWmbjN8zckdXSyDfY8GlI9dA7dr6YuGwxgxGVzRzo%3Dreserved=0
> > > >
> > >
> > >
> > > On Wed, Oct 9, 2019 at 8:21 AM Josh Tynjala <
> > joshtynj...@bowlerhat.dev
> > > >
> > > wrote:
> > >
> > > > I logged into the server and discovered that js-swf build was
> > failing
> > > > because there was no default program for .swf files. I set the
> > > > flashplayerdebugger.exe that you downloaded as the default, and I
> > > was able
> > > > to successfully run the tests in a PowerShell window. I started a
> > > new build
> > > > in Jenkins, so we should hopefully see how it goes in a few
> > minutes.
> > > >
> > > > --
> > > > Josh Tynjala
> > > > Bowler Hat LLC <
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7Ca0a8b694fff24a69908b08d74cd380a7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637062343589197901sdata=CiqWmbjN8zckdXSyDfY8GlI9dA7dr6YuGwxgxGVzRzo%3Dreserved=0
> > > >
> > > >
> > > >
> > > > On Wed, Oct 9, 2019 at 8:08 AM Alex Harui
>  > >
> > > > wrote:
> > > >
> > > >> I sent an email to private@ with the new credentials and URL.
> I
> > > don't
> > > >> know how to get the old URL back at this point in time.  The
> > JSOnly
> > > build
> > > >> succeeded.  I'm trying to get the JS-SWF build to succeed.
> > > >>
> > > >>
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080data=02%7C01%7Caharui%40adobe.com%7Ca0a8b694fff24a69908b08d74cd380a7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637062343589207904sdata=Syw8dIiAfta0WLwjYLZNc0VAuTlx%2BQQTunbzq7fNko4%3Dreserved=0
>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-10-10 Thread Piotr Zarzycki
Hi Carlos,

Did you make an update API doc ? ->
https://royale.apache.org/asdoc/index.html

Thanks,
Piotr

pon., 7 paź 2019 o 19:38 Carlos Rovira  napisał(a):

> Hi Piotr,
> yes, I'll do in next few hours.
> thanks.
>
> El lun., 7 oct. 2019 a las 9:54, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>)
> escribió:
>
> > Hi Carlos,
> >
> > Will you be able update website with links for 0.9.6 release ?
> >
> > Thanks,
> > Piotr
> >
> > niedz., 6 paź 2019 o 10:52 Piotr Zarzycki 
> > napisał(a):
> >
> > > Hi Alex,
> > >
> > > Thank you for the fix. Everything worked fine this time.
> > >
> > > Piotr
> > >
> > > sob., 5 paź 2019 o 01:51 Alex Harui 
> > napisał(a):
> > >
> > >> I found some time to try the releasecandidate.xml and found the
> problem.
> > >> I pushed the fix to release/0.9.6.  So try that and see what happens.
> > >> It seemed to do the right thing for me on my Windows computer.
> > >>
> > >> You will next likely run into several merge conflicts.  I have not
> > looked
> > >> into the conflicts, but there is a good chance that some of that is
> due
> > to
> > >> the cherry-picking.  I am going to start a separate thread about
> branch
> > >> management.
> > >>
> > >> -Alex
> > >>
> > >> On 10/4/19, 10:55 AM, "Alex Harui"  wrote:
> > >>
> > >> If we don't fix the release scripts, then the next RM is probably
> > >> going to run into the same problem.  The time we spend now helps save
> > time
> > >> in the future.  It is wise to improve the process now in case I get
> run
> > >> over by a bus tomorrow.  If you do it manually and make a mistake, we
> > might
> > >> not catch it until later or cause more problems.
> > >>
> > >> IIRC, the Poms should not require changing.  Maven should have
> done
> > >> that already.
> > >>
> > >> All the places I know of changing are in the script.
> > >>
> > >> -Alex
> > >>
> > >> On 10/4/19, 10:46 AM, "Piotr Zarzycki"  >
> > >> wrote:
> > >>
> > >> Alex,
> > >>
> > >> Can I just do that changes manually on release branch and
> merge
> > >> stuff to
> > >> develop?
> > >>
> > >> I just don't won't to spend any more minute on release process
> > >> anymore.
> > >>
> > >> 1) I should change build properties
> > >> 2) I should change all poms
> > >>
> > >> Is there anymore place which I should know to change?
> > >>
> > >> Thanks,
> > >> Piotr
> > >>
> > >> On Fri, Oct 4, 2019, 7:41 PM Alex Harui
> > 
> > >> wrote:
> > >>
> > >> > Piotr,
> > >> >
> > >> > Again, I am asking you to get in the mindset of a developer
> > and
> > >> not just a
> > >> > user.  You can see that the Ant script is making some
> updates.
> > >> You can
> > >> > verify that the release branch does not have 0.9.7 for the
> > >> release.version
> > >> > in build.properties.  You can see there is 1 commit pending
> in
> > >> > royale-asjs.  You can see that the build.properties did get
> > >> changed to have
> > >> > release.version=0.9.7.
> > >> >
> > >> > So, you will have to investigate further.  What is in that
> > >> commit?  Is
> > >> > this output from a fresh start of cloning the repo or could
> > >> that commit be
> > >> > from a previous run?  How could Git change a file but not
> > >> report it?  Maybe
> > >> > add some  tags or use -verbose to get more output.
> But
> > >> just giving
> > >> > me minimal information and waiting for me to guess as to
> what
> > >> to do next is
> > >> > not very efficient, IMO.
> > >> >
> > >> > Thanks,
> > >> > -Alex
> > >> >
> > >> > On 1

Re: Nightly Build Server going offline

2019-10-10 Thread Piotr Zarzycki
How can we expose Nightly build from new server outside ? Now if I would
like to send links it requires from me login.

śr., 9 paź 2019 o 20:08 Alex Harui  napisał(a):

> OK, I will switch the service to use the ApacheRoyaleCI account and see
> what happens.
>
> -ALex
>
> On 10/9/19, 9:12 AM, "Josh Tynjala"  wrote:
>
> Well, the build made it a bit further after I set the default app for
> .swf
> files. However, it seems that Flash Player is not picking up the trust
> file
> that the RoyaleUnit Ant Task is creating. Based on the console log, the
> Jenkins job seems to be creating it here:
>
>
> C:\windows\system32\config\systemprofile\AppData\Roaming\Macromedia\Flash
> Player\#Security\FlashPlayerTrust\royaleUnit.cfg
>
> Looking at Jenkins emails from the old server, it used to be in the
> user
> folder instead
>
> C:\Users\apacheroyale\AppData\Roaming\Macromedia\Flash
> Player\#Security\FlashPlayerTrust\royaleUnit.cfg
>
> I guess that would be C:\Users\ApacheRoyaleCI\ on the new server. It
> looks
> like royaleUnit.cfg exists in the user folder too, but I'm guessing
> that's
> from when I ran the tests manually. So maybe that's an interesting
> clue? Is
> the Jenkins job running as the ApacheRoyaleCI user, or could it be a
> different user account that can't access C:\Users\ApacheRoyaleCI\? I
> don't
> really know Jenkins, so I'm just throwing out ideas here.
>
> --
> Josh Tynjala
> Bowler Hat LLC <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7Ca0a8b694fff24a69908b08d74cd380a7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637062343589197901sdata=CiqWmbjN8zckdXSyDfY8GlI9dA7dr6YuGwxgxGVzRzo%3Dreserved=0
> >
>
>
> On Wed, Oct 9, 2019 at 8:21 AM Josh Tynjala  >
> wrote:
>
> > I logged into the server and discovered that js-swf build was failing
> > because there was no default program for .swf files. I set the
> > flashplayerdebugger.exe that you downloaded as the default, and I
> was able
> > to successfully run the tests in a PowerShell window. I started a
> new build
> > in Jenkins, so we should hopefully see how it goes in a few minutes.
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7Ca0a8b694fff24a69908b08d74cd380a7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637062343589197901sdata=CiqWmbjN8zckdXSyDfY8GlI9dA7dr6YuGwxgxGVzRzo%3Dreserved=0
> >
> >
> >
> > On Wed, Oct 9, 2019 at 8:08 AM Alex Harui 
> > wrote:
> >
> >> I sent an email to private@ with the new credentials and URL.  I
> don't
> >> know how to get the old URL back at this point in time.  The JSOnly
> build
> >> succeeded.  I'm trying to get the JS-SWF build to succeed.
> >>
> >>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080data=02%7C01%7Caharui%40adobe.com%7Ca0a8b694fff24a69908b08d74cd380a7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637062343589207904sdata=Syw8dIiAfta0WLwjYLZNc0VAuTlx%2BQQTunbzq7fNko4%3Dreserved=0
> >>
> >> We should update all links to use the new URL.  Having someone else
> do
> >> what would be appreciated.
> >>
> >>
> >> -Alex
> >>
> >> On 10/9/19, 6:23 AM, "Carlos Rovira" 
> wrote:
> >>
> >> Hope Alex can let us know what he thinks about timing
> >> We can do a quick change directly in production if needed and
> then
> >> revert
> >> when needed to not mesh with pre for something punctual...
> >>
> >> El mié., 9 oct. 2019 a las 9:50, Piotr Zarzycki (<
> >> piotrzarzyck...@gmail.com>)
> >> escribió:
> >>
> >> > Hi,
> >> >
> >> > If we are going to stay for a longer time with nightly build
> >> offline we
> >> > should also update link to nightly build on our website. If
> it's
> >> only for
> >> > couple of days no problem.
> >> >
> >> > Thanks,
> >> > Piotr
> >> >
> >> > wt., 8 paź 2019 o 20:04 Carlos Rovira <
> carlosrov...@apache.org>
> >> > napisał(a):
> >>   

Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

2019-10-09 Thread Piotr Zarzycki
l here". When I look in the package for the JS-only
> > version,
> > >> > playerglobal is there. I do not see it in the JS_SWF version.
> > >> >
> > >> > <
> > >> >
> > >>
> >
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
>
> > >> > >
> > >> > Virus-free.
> > >> > www.avast.com
> > >> > <
> > >> >
> > >>
> >
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
>
> > >> > >
> > >> > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> > >> >
> > >> > On Wed, Oct 9, 2019 at 3:07 PM Alex Harui 
>
> > >> > wrote:
> > >> >
> > >> > > When you build with AIR_HOME (which is required to create
> release
> > >> > > artifacts, since we want to produce both jsonly and js-swf in
> one
> > >> run), a
> > >> > > different target called "jsonly-package" run and tries to muck
> with
> > >> some
> > >> > > files before packaging the js-only artifacts. It could be that
> the
> > >> > > jsonly-package needs updating now that SWF SWCs are listed in
> > >> > > royale-config.xml. That means we've had this bug for months and
> > >> nobody
> > >> > > noticed until now.
> > >> > >
> > >> > > -Alex
> > >> > >
> > >> > > On 10/9/19, 9:38 AM, "Josh Tynjala" 
>
> > >> wrote:
> > >> > >
> > >> > > It looks like the Ant target that updates the library-path for
> > the
> > >> > > JS-only
> > >> > > build is called tweak-for-jsonly. Copied here for convenience:
> > >> > >
> > >> > >
> > >> > >
> > >> >
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fasn0idata=02%7C01%7Caharui%40adobe.com%7C972794372a8a4037148008d74cd72cc9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637062359364655836sdata=7h3ZHxgGsfZqP8kE22amKQYDr7%2BNyQa7EpoG86147uU%3Dreserved=0
>
> > >> > >
> > >> > > I see that it has unless="env.AIR_HOME", which means that this
> > >> target
> > >> > > is
> > >> > > skipped if the AIR_HOME environment variable is set. With that
> > in
> > >> > > mind, I'm
> > >> > > guessing that AIR_HOME needs to be set for the js-swf build, but
> > >> > > cleared
> > >> > > for the js-only build.
> > >> > >
> > >> > > --
> > >> > > Josh Tynjala
> > >> > > Bowler Hat LLC <
> > >> > >
> > >> >
> > >>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7C972794372a8a4037148008d74cd72cc9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637062359364655836sdata=Ih2P7zf2c%2BLPn5ktks02EE7k6s24RKcabVem7VqjWeg%3Dreserved=0
>
> > >> > > >
> > >> > >
> > >> > >
> > >> > > On Wed, Oct 9, 2019 at 6:52 AM Piotr Zarzycki <
> > >> > > piotrzarzyck...@gmail.com>
> > >> > > wrote:
> > >> > >
> > >> > > > Hi Guys,
> > >> > > >
> > >> > > > It looks like we have broken royale-config in released SDK.
> > >> Andrew
> > >> > > raised
> > >> > > > in Moonshine GitHub issue that he couldn't build Hello World
> > >> > > project. I
> > >> > > > tried Moonshine and downloaded JS-only version of SDK. I get
> > >> > > following
> > >> > > > error [1].
> > >> > > > I downloaded JS-SWF version and tried compile project again -
> > >> this
> > >> > > time it
> > >> > > > went fine.
> > >> > > >
> > >> > > > JS-only version of released 0.9.6 contains in section
> > >> > >  -
> > >> > > > list of swc. - Those swc doesn't exists in JS-only.
> > >> > > >
> > >> > > > Fragment of config
> > >> > > >
> >

Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

2019-10-09 Thread Piotr Zarzycki
t;> >> > I wiped out the previous project and tried again with the Royale
> >> JS-SWF
> >> >> > version. When I try to compile the project in Moonshine for either
> >> JS or
> >> >> > Flash, I see this error message: "This SDK does not contains
> >> >> > playerglobal.swc in frameworks\libs\player\11.7\playerglobal.swc.
> >> >> Download
> >> >> > playerglobal here". When I look in the package for the JS-only
> >> version,
> >> >> > playerglobal is there. I do not see it in the JS_SWF version.
> >> >> >
> >> >> > <
> >> >> >
> >> >>
> >>
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> >> >> > >
> >> >> > Virus-free.
> >> >> > www.avast.com
> >> >> > <
> >> >> >
> >> >>
> >>
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> >> >> > >
> >> >> > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> >> >> >
> >> >> > On Wed, Oct 9, 2019 at 3:07 PM Alex Harui  >
> >> >> > wrote:
> >> >> >
> >> >> > > When you build with AIR_HOME (which is required to create release
> >> >> > > artifacts, since we want to produce both jsonly and js-swf in one
> >> >> run), a
> >> >> > > different target called "jsonly-package" run and tries to muck
> with
> >> >> some
> >> >> > > files before packaging the js-only artifacts.  It could be that
> the
> >> >> > > jsonly-package needs updating now that SWF SWCs are listed in
> >> >> > > royale-config.xml.  That means we've had this bug for months and
> >> >> nobody
> >> >> > > noticed until now.
> >> >> > >
> >> >> > > -Alex
> >> >> > >
> >> >> > > On 10/9/19, 9:38 AM, "Josh Tynjala" 
> >> >> wrote:
> >> >> > >
> >> >> > > It looks like the Ant target that updates the library-path
> for
> >> the
> >> >> > > JS-only
> >> >> > > build is called tweak-for-jsonly. Copied here for
> convenience:
> >> >> > >
> >> >> > >
> >> >> > >
> >> >> >
> >> >>
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fasn0idata=02%7C01%7Caharui%40adobe.com%7C972794372a8a4037148008d74cd72cc9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637062359364655836sdata=7h3ZHxgGsfZqP8kE22amKQYDr7%2BNyQa7EpoG86147uU%3Dreserved=0
> >> >> > >
> >> >> > > I see that it has unless="env.AIR_HOME", which means that
> this
> >> >> target
> >> >> > > is
> >> >> > > skipped if the AIR_HOME environment variable is set. With
> that
> >> in
> >> >> > > mind, I'm
> >> >> > > guessing that AIR_HOME needs to be set for the js-swf build,
> >> but
> >> >> > > cleared
> >> >> > > for the js-only build.
> >> >> > >
> >> >> > > --
> >> >> > > Josh Tynjala
> >> >> > > Bowler Hat LLC <
> >> >> > >
> >> >> >
> >> >>
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7C972794372a8a4037148008d74cd72cc9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637062359364655836sdata=Ih2P7zf2c%2BLPn5ktks02EE7k6s24RKcabVem7VqjWeg%3Dreserved=0
> >> >> > > >
> >> >> > >
> >> >> > >
> >> >> > > On Wed, Oct 9, 2019 at 6:52 AM Piotr Zarzycki <
> >> >> > > piotrzarzyck...@gmail.com>
> >> >> > > wrote:
> >> >> > >
> >> >> > > > Hi Guys,
> >> >> > > >
> >> >> > > > It looks like we have broken royale-config in released SDK.
> >> >> Andrew
> >> >> > > raised
> >> >> > > > in Moonshine Git

Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

2019-10-09 Thread Piotr Zarzycki
Hi Guys,

It looks like we have broken royale-config in released SDK. Andrew raised
in Moonshine GitHub issue that he couldn't build Hello World project. I
tried Moonshine and downloaded JS-only version of SDK. I get following
error [1].
I downloaded JS-SWF version and tried compile project again - this time it
went fine.

JS-only version of released 0.9.6 contains in section   -
list of swc. - Those swc doesn't exists in JS-only.

Fragment of config

> 
>  libs/Basic.swc
>  libs/Binding.swc
>  libs/Charts.swc
>  libs/Collections.swc
>  libs/Core.swc
> 


JS-only nightly build of 0.9.7 - doesn't contains in that section anything

>   
>   


[1] https://paste.apache.org/2lgvk

Thanks,
-- 

Piotr Zarzycki

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


Re: Nightly Build Server going offline

2019-10-09 Thread Piotr Zarzycki
Hi,

If we are going to stay for a longer time with nightly build offline we
should also update link to nightly build on our website. If it's only for
couple of days no problem.

Thanks,
Piotr

wt., 8 paź 2019 o 20:04 Carlos Rovira  napisał(a):

> 爛
>
> :)
>
> El mar., 8 oct. 2019 a las 18:12, Alex Harui ()
> escribió:
>
> > I am definitely planning to start rebuilding the server today.  Keep your
> > fingers crossed.
> >
> > -Alex
> >
> > On 10/7/19, 8:47 AM, "Alex Harui"  wrote:
> >
> > I think the merge happened, so I am going to try to do the rebuild
> > this week, probably on my Tuesday if I can finish up some fixes to
> > releasecandidate.xml needed for Windows today.
> >
> > -Alex
> >
> > On 10/7/19, 12:39 AM, "Carlos Rovira" 
> wrote:
> >
> > Hi,
> >
> > don't think a day be a problem. When can better warn in social
> > networks
> > about that 24h unavailability.
> > Other option is to store in pre web server (
> Royale.codeoscopic.com).
> > You
> > have credentials and can upload to Wordpress and then we can
> share
> > that
> > link.
> > Whatever option could be fine, but for a day, I don't think we
> > should
> > invest much time.
> >
> > thanks!
> >
> >
> >
> > El dom., 6 oct. 2019 a las 9:28, Harbs ()
> > escribió:
> >
> > > Seems fine to me.
> > >
> > > > On Oct 6, 2019, at 1:33 AM, Alex Harui
> >  wrote:
> > > >
> > > > I was only thinking about temporary distribution of the
> > nightly build
> > > while the CI server is offline.  I'm not sure it makes sense to
> > always copy
> > > the nightly build somewhere else.  I think the bandwidth would
> > add up.
> > > >
> > > > I'm mainly asking if anyone thinks it would be a problem if
> > the nightly
> > > builds were unavailable for a day (hopefully only a day).
> > > >
> > > > -Alex
> > > >
> > > > On 10/5/19, 6:41 AM, "Carlos Rovira" <
> carlosrov...@apache.org
> >  > > carlosrov...@apache.org>> wrote:
> > > >
> > > >Hi Alex,
> > > >
> > > >you're talking about just storing nightly builds? what
> > about using
> > > some
> > > >free storage out there, like a google drive, dropbox, or
> > other
> > > service like
> > > >this. We can create an "apacheroyale" account and share
> > credentials in
> > > >private.
> > > >
> > > >El sáb., 5 oct. 2019 a las 2:18, Alex Harui
> > ( > > >)
> > > >escribió:
> > > >
> > > >> Hi,
> > > >>
> > > >> To prove that we can rebuild our nightly build server (so
> > that someone
> > > >> else can host a build server someday and to prove we know
> > what our
> > > >> dependencies are), I'm going to try to rebuild it once the
> > release
> > > branch
> > > >> is merged into develop.  Could just take a day if I've saved
> > a record of
> > > >> everything we need.  Or not...
> > > >>
> > > >> There will be other emails when I finally shut it down to
> try
> > it.  If
> > > >> someone wants to host the last nightly somewhere and update
> > our links to
> > > >> it, great, otherwise we'll just cross our fingers...
> > > >>
> > > >> Thanks,
> > > >> -Alex
> > > >>
> > > >>
> > > >
> > > >--
> > > >Carlos Rovira
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C6f4957799c04453d1ef308d74b3da007%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637060600359555721sdata=AB%2BoIdhv4B5EMHSvpOwX9XEZTPgZVdW5Rs7mOEI0fHw%3Dreserved=0
> > > <
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C6f4957799c04453d1ef308d74b3da007%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637060600359565716sdata=O6hyvC%2FH%2BuPOuD8K%2FHBC4YYM71aEPEcvMs8ufKZkXqU%3Dreserved=0
> > > >
> > >
> >
> >
> > --
> > Carlos Rovira
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C6f4957799c04453d1ef308d74b3da007%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637060600359565716sdata=O6hyvC%2FH%2BuPOuD8K%2FHBC4YYM71aEPEcvMs8ufKZkXqU%3Dreserved=0
> >
> >
> >
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 

Piotr Zarzycki

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


[ANNOUNCE] Apache Royale 0.9.6 released!

2019-10-09 Thread Piotr Zarzycki
The Apache Royale community is pleased to announce the release of Apache
Royale 0.9.6.

The Apache Royale project is the next generation of the Apache Flex SDK. It
lets developers use MXML and ActionScript 3 to generate HTML/JS/CSS
applications which can run natively in browsers. The cross-compiled code
can also run on platforms like Electron or Apache Cordova (Adobe PhoneGap)
to build mobile applications.

This release should be considered ‘beta’ quality, although we’re very close
to a 1.0 release and we have many applications in production at this point.
The purpose of this release is to continue to gather feedback about
Royale’s features and the project’s implementation strategies, and to
recruit new contributors. We hope to grow the code base into an SDK and
tool chain that delivers the highest productivity when developing
applications that can run on many platforms. Beta releases, however, may
not handle all production needs.

Changes in 0.9.6:

Apache Royale Framework 0.9.6:
https://github.com/apache/royale-asjs/blob/apache-royale-0.9.6/RELEASE_NOTES.md
Apache Royale Compiler 0.9.6:
https://github.com/apache/royale-compiler/blob/apache-royale-0.9.6/RELEASE_NOTES.md

Please file bugs at:

https://github.com/apache/royale-asjs/issues

If you happen to know it is a compiler issue, please use:

https://github.com/apache/royale-compiler/issues

For questions about how to use Royale, send email to us...@royale.apache.org.
For questions and feedback on the development of the source code in the
release, send email to dev@royale.apache.org.

Apache Royale is available in source and binary form from the Apache
mirrors:

Source:
http://www.apache.org/dyn/closer.lua/royale/0.9.6/apache-royale-0.9.6-src.tar.gz

http://www.apache.org/dyn/closer.lua/royale/0.9.6/apache-royale-0.9.6-src.zip

Binary:
http://www.apache.org/dyn/closer.lua/royale/0.9.6/binaries/apache-royale-0.9.6-bin-js.tar.gz
http://www.apache.org/dyn/closer.lua/royale/0.9.6/binaries/apache-royale-0.9.6-bin-js.zip

Binary with SWF support:
http://www.apache.org/dyn/closer.lua/royale/0.9.6/binaries/apache-royale-0.9.6-bin-js-swf.tar.gz
http://www.apache.org/dyn/closer.lua/royale/0.9.6/binaries/apache-royale-0.9.6-bin-js-swf.zip

When downloading from a mirror site, please remember to verify the
downloads using signatures or MD5 hashes.

The binary packages can also be installed via NPM.

Mac:
  sudo npm install @apache-royale/royale-js -g

Or for SWF Support:
  sudo npm install @apache-royale/royale-js-swf -g

Windows:
  npm install @apache-royale/royale-js -g

Or for SWF Support:
  npm install @apache-royale/royale-js-swf -g

See the README for more information. The language reference (ASDoc) is
here: http://royale.apache.org/asdoc/

Additional documentation is here: https://apache.github.io/royale-docs/

The documentation is still a work in progress. Volunteers are welcome to
help improve it. Visit http://royale.apache.org/ for links to other
resources.

Please try Royale and become involved in shaping the future of application
development.

The Apache Royale Community
-- 

Piotr Zarzycki

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


Re: Release 0.9.6 Announce for web post?

2019-10-09 Thread Piotr Zarzycki
Hi Carlos,

I will send announce in couple of minutes. In the meantime I have found
that one thing seems to be wrong in blog post. Sentence:

"Updates to the RELEASE_NOTES made after this file was packaged into the
release artifacts can be found at this link
<https://github.com/apache/royale-asjs/wiki/Release-Notes-0.9.6>. You can
see more here
<https://github.com/apache/royale-asjs/blob/develop/RELEASE_NOTES.md>."
First link seems to redirect to blank page.

wt., 8 paź 2019 o 21:48 Piotr Zarzycki 
napisał(a):

> Let me make announce. I will do that tomorrow morning. :)
>
> You can next post social media.
>
> On Tue, Oct 8, 2019, 8:24 PM Carlos Rovira 
> wrote:
>
>> Hi
>>
>> website is updated.
>> @Piotr Zarzycki   do you want to share 0.9.6
>> in social media? or wait for announcement?
>>
>> thanks
>>
>>
>> El mar., 8 oct. 2019 a las 20:03, Carlos Rovira ()
>> escribió:
>>
>>> Hi Andrew,
>>>
>>> if you don't mind I take into account for next release, since I'm this
>>> days a bit out of time.
>>> Thanks for taking the review. I'll try to publish now
>>>
>>> Carlos
>>>
>>>
>>>
>>> El mar., 8 oct. 2019 a las 18:57, Andrew Wetmore ()
>>> escribió:
>>>
>>>> I have edited the release. The only thing I would improve, if I could,
>>>> is
>>>> the graphic at the top. The release number appears as "v0.9.6". I am
>>>> pretty
>>>> sure it would be better as "v. 0.9.6", but this is obviously not
>>>> something
>>>> to delay the release for.
>>>>
>>>> Andrew
>>>>
>>>> On Tue, Oct 8, 2019 at 11:56 AM Andrew Wetmore 
>>>> wrote:
>>>>
>>>> > Got it! Thanks!
>>>> >
>>>> > On Tue, Oct 8, 2019 at 10:49 AM Carlos Rovira <
>>>> carlosrov...@apache.org>
>>>> > wrote:
>>>> >
>>>> >> Yes! that's it :)
>>>> >>
>>>> >>
>>>> >> El mar., 8 oct. 2019 a las 16:31, Piotr Zarzycki (<
>>>> >> piotrzarzyck...@gmail.com>)
>>>> >> escribió:
>>>> >>
>>>> >> > I think that would be the link:
>>>> >> > https://royale.codeoscopic.com/apache-royale-v0-9-6-released/
>>>> >> >
>>>> >> > wt., 8 paź 2019 o 16:29 Andrew Wetmore 
>>>> >> napisał(a):
>>>> >> >
>>>> >> > > @Carlos Rovira  where is the draft
>>>> post? I
>>>> >> had
>>>> >> > a
>>>> >> > > hard disk failure this past weekend and am slowly rebuilding my
>>>> >> system.
>>>> >> > > Have to find all my links again.
>>>> >> > >
>>>> >> > > a
>>>> >> > >
>>>> >> > > On Tue, Oct 8, 2019 at 9:48 AM Andrew Wetmore <
>>>> cottag...@gmail.com>
>>>> >> > wrote:
>>>> >> > >
>>>> >> > > > I can do this in a couple of hours
>>>> >> > > >
>>>> >> > > > On Tue, Oct 8, 2019, 9:24 AM Carlos Rovira, <
>>>> >> carlosrov...@apache.org>
>>>> >> > > > wrote:
>>>> >> > > >
>>>> >> > > >> Hi Piotr,
>>>> >> > > >>
>>>> >> > > >> I'll wait Andrew's review and then will publish it. If Andrew
>>>> make
>>>> >> his
>>>> >> > > >> changes this afternoon, I can follow up and publish it.
>>>> >> > > >> Then we can post on social networks next or wait to tomorrow
>>>> >> > > >>
>>>> >> > > >>
>>>> >> > > >>
>>>> >> > > >> El mar., 8 oct. 2019 a las 11:21, Piotr Zarzycki (<
>>>> >> > > >> piotrzarzyck...@gmail.com>)
>>>> >> > > >> escribió:
>>>> >> > > >>
>>>> >> > > >> > Just to make sure that you understand why I asked you to
>>>> post
>>>> >> > download
>>>> >> > > >> > links on website along with source code.
>>>> >> &g

Release 0.9.6 Announce for web post?

2019-10-08 Thread Piotr Zarzycki
Let me make announce. I will do that tomorrow morning. :)

You can next post social media.

On Tue, Oct 8, 2019, 8:24 PM Carlos Rovira  wrote:

> Hi
>
> website is updated.
> @Piotr Zarzycki   do you want to share 0.9.6
> in social media? or wait for announcement?
>
> thanks
>
>
> El mar., 8 oct. 2019 a las 20:03, Carlos Rovira ()
> escribió:
>
>> Hi Andrew,
>>
>> if you don't mind I take into account for next release, since I'm this
>> days a bit out of time.
>> Thanks for taking the review. I'll try to publish now
>>
>> Carlos
>>
>>
>>
>> El mar., 8 oct. 2019 a las 18:57, Andrew Wetmore ()
>> escribió:
>>
>>> I have edited the release. The only thing I would improve, if I could, is
>>> the graphic at the top. The release number appears as "v0.9.6". I am
>>> pretty
>>> sure it would be better as "v. 0.9.6", but this is obviously not
>>> something
>>> to delay the release for.
>>>
>>> Andrew
>>>
>>> On Tue, Oct 8, 2019 at 11:56 AM Andrew Wetmore 
>>> wrote:
>>>
>>> > Got it! Thanks!
>>> >
>>> > On Tue, Oct 8, 2019 at 10:49 AM Carlos Rovira >> >
>>> > wrote:
>>> >
>>> >> Yes! that's it :)
>>> >>
>>> >>
>>> >> El mar., 8 oct. 2019 a las 16:31, Piotr Zarzycki (<
>>> >> piotrzarzyck...@gmail.com>)
>>> >> escribió:
>>> >>
>>> >> > I think that would be the link:
>>> >> > https://royale.codeoscopic.com/apache-royale-v0-9-6-released/
>>> >> >
>>> >> > wt., 8 paź 2019 o 16:29 Andrew Wetmore 
>>> >> napisał(a):
>>> >> >
>>> >> > > @Carlos Rovira  where is the draft
>>> post? I
>>> >> had
>>> >> > a
>>> >> > > hard disk failure this past weekend and am slowly rebuilding my
>>> >> system.
>>> >> > > Have to find all my links again.
>>> >> > >
>>> >> > > a
>>> >> > >
>>> >> > > On Tue, Oct 8, 2019 at 9:48 AM Andrew Wetmore <
>>> cottag...@gmail.com>
>>> >> > wrote:
>>> >> > >
>>> >> > > > I can do this in a couple of hours
>>> >> > > >
>>> >> > > > On Tue, Oct 8, 2019, 9:24 AM Carlos Rovira, <
>>> >> carlosrov...@apache.org>
>>> >> > > > wrote:
>>> >> > > >
>>> >> > > >> Hi Piotr,
>>> >> > > >>
>>> >> > > >> I'll wait Andrew's review and then will publish it. If Andrew
>>> make
>>> >> his
>>> >> > > >> changes this afternoon, I can follow up and publish it.
>>> >> > > >> Then we can post on social networks next or wait to tomorrow
>>> >> > > >>
>>> >> > > >>
>>> >> > > >>
>>> >> > > >> El mar., 8 oct. 2019 a las 11:21, Piotr Zarzycki (<
>>> >> > > >> piotrzarzyck...@gmail.com>)
>>> >> > > >> escribió:
>>> >> > > >>
>>> >> > > >> > Just to make sure that you understand why I asked you to post
>>> >> > download
>>> >> > > >> > links on website along with source code.
>>> >> > > >> >
>>> >> > > >> > I will announce on dev, users and announce list - someone who
>>> >> read
>>> >> > > >> email -
>>> >> > > >> > will have two options:
>>> >> > > >> > 1) Can click in that email on royale.apache.org
>>> >> > > >> > 2) Can download directly binaries or source code from
>>> provided
>>> >> links
>>> >> > > in
>>> >> > > >> the
>>> >> > > >> > email
>>> >> > > >> >
>>> >> > > >> > If user do #1 he will see old links on website which will be
>>> >> > > >> misleading. -
>>> >> > > >> > Do you understand now why I asked you to publish stuff first
>>> ?
>>> >> > 

Re: Release 0.9.6 Announce for web post?

2019-10-08 Thread Piotr Zarzycki
I think that would be the link:
https://royale.codeoscopic.com/apache-royale-v0-9-6-released/

wt., 8 paź 2019 o 16:29 Andrew Wetmore  napisał(a):

> @Carlos Rovira  where is the draft post? I had a
> hard disk failure this past weekend and am slowly rebuilding my system.
> Have to find all my links again.
>
> a
>
> On Tue, Oct 8, 2019 at 9:48 AM Andrew Wetmore  wrote:
>
> > I can do this in a couple of hours
> >
> > On Tue, Oct 8, 2019, 9:24 AM Carlos Rovira, 
> > wrote:
> >
> >> Hi Piotr,
> >>
> >> I'll wait Andrew's review and then will publish it. If Andrew make his
> >> changes this afternoon, I can follow up and publish it.
> >> Then we can post on social networks next or wait to tomorrow
> >>
> >>
> >>
> >> El mar., 8 oct. 2019 a las 11:21, Piotr Zarzycki (<
> >> piotrzarzyck...@gmail.com>)
> >> escribió:
> >>
> >> > Just to make sure that you understand why I asked you to post download
> >> > links on website along with source code.
> >> >
> >> > I will announce on dev, users and announce list - someone who read
> >> email -
> >> > will have two options:
> >> > 1) Can click in that email on royale.apache.org
> >> > 2) Can download directly binaries or source code from provided links
> in
> >> the
> >> > email
> >> >
> >> > If user do #1 he will see old links on website which will be
> >> misleading. -
> >> > Do you understand now why I asked you to publish stuff first ?
> >> >
> >> > However as I said if you prefer do this in a opposite way that's fine
> >> with
> >> > me. :)
> >> >
> >> >
> >> > wt., 8 paź 2019 o 11:17 Piotr Zarzycki 
> >> > napisał(a):
> >> >
> >> > > This is the goal of syncing everything tomorrow. I asked you to
> >> publish
> >> > > first link and source code on website, cause my announce probably go
> >> > first
> >> > > one and I didn't want to mislead with what will be on website.
> >> However if
> >> > > you wanted to do that differently I'm fine - Couple of hours of
> >> > misleading
> >> > > doesn't hurts anyone maybe. - We will see tomorrow.
> >> > >
> >> > > wt., 8 paź 2019 o 11:05 Carlos Rovira 
> >> > > napisał(a):
> >> > >
> >> > >> Hi,
> >> > >> ok, is normal,
> >> > >> as people following our dev, are as well using links to 0.9.6
> >> releases.
> >> > >> The update of links in website is more about to announce to the
> rest
> >> of
> >> > >> the
> >> > >> world that is not as close to us as the rest of community.
> >> > >> So it's important to communicate in the most organized way we can.
> >> > >>
> >> > >> thanks!
> >> > >>
> >> > >> El mar., 8 oct. 2019 a las 10:51, Piotr Zarzycki (<
> >> > >> piotrzarzyck...@gmail.com>)
> >> > >> escribió:
> >> > >>
> >> > >> > Just FYI: npm stuff and Maven artifacts are being published for
> >> couple
> >> > >> of
> >> > >> > days already, so people are using released 0.9.6 trough npm. -
> It's
> >> > >> happen
> >> > >> > automatically in case of npm.
> >> > >> >
> >> > >> > wt., 8 paź 2019 o 10:48 Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> >> > >> > napisał(a):
> >> > >> >
> >> > >> > > Fine with me. I make announce tomorrow morning and review what
> >> was
> >> > >> your
> >> > >> > > change and update Draft.
> >> > >> > >
> >> > >> > > wt., 8 paź 2019 o 10:46 Carlos Rovira  >
> >> > >> > > napisał(a):
> >> > >> > >
> >> > >> > >> Hi, Piotr,
> >> > >> > >>
> >> > >> > >> I think we should update all at the same time, since we want
> to
> >> > post
> >> > >> in
> >> > >> > >> twitter, Facebook and linkedin.
> >> > >> > >> Doesn't have sense to me upload just a few links since

Re: Release 0.9.6 Announce for web post?

2019-10-08 Thread Piotr Zarzycki
Just to make sure that you understand why I asked you to post download
links on website along with source code.

I will announce on dev, users and announce list - someone who read email -
will have two options:
1) Can click in that email on royale.apache.org
2) Can download directly binaries or source code from provided links in the
email

If user do #1 he will see old links on website which will be misleading. -
Do you understand now why I asked you to publish stuff first ?

However as I said if you prefer do this in a opposite way that's fine with
me. :)


wt., 8 paź 2019 o 11:17 Piotr Zarzycki 
napisał(a):

> This is the goal of syncing everything tomorrow. I asked you to publish
> first link and source code on website, cause my announce probably go first
> one and I didn't want to mislead with what will be on website. However if
> you wanted to do that differently I'm fine - Couple of hours of misleading
> doesn't hurts anyone maybe. - We will see tomorrow.
>
> wt., 8 paź 2019 o 11:05 Carlos Rovira 
> napisał(a):
>
>> Hi,
>> ok, is normal,
>> as people following our dev, are as well using links to 0.9.6 releases.
>> The update of links in website is more about to announce to the rest of
>> the
>> world that is not as close to us as the rest of community.
>> So it's important to communicate in the most organized way we can.
>>
>> thanks!
>>
>> El mar., 8 oct. 2019 a las 10:51, Piotr Zarzycki (<
>> piotrzarzyck...@gmail.com>)
>> escribió:
>>
>> > Just FYI: npm stuff and Maven artifacts are being published for couple
>> of
>> > days already, so people are using released 0.9.6 trough npm. - It's
>> happen
>> > automatically in case of npm.
>> >
>> > wt., 8 paź 2019 o 10:48 Piotr Zarzycki 
>> > napisał(a):
>> >
>> > > Fine with me. I make announce tomorrow morning and review what was
>> your
>> > > change and update Draft.
>> > >
>> > > wt., 8 paź 2019 o 10:46 Carlos Rovira 
>> > > napisał(a):
>> > >
>> > >> Hi, Piotr,
>> > >>
>> > >> I think we should update all at the same time, since we want to post
>> in
>> > >> twitter, Facebook and linkedin.
>> > >> Doesn't have sense to me upload just a few links since almost nobody
>> > will
>> > >> notice it (and are already in GitHub releases). If we need to wait a
>> day
>> > >> to
>> > >> send the official announcement it's ok for me. We can finish to
>> improve
>> > >> the
>> > >> blog post in the meanwhile to do it better.
>> > >>
>> > >> For example, I changed a bit the wording, since we are not as
>> "early" or
>> > >> "alpha" and I mention as well that we have Apps in production, what
>> is
>> > now
>> > >> important.
>> > >> And finally talk about the improved Royale Docs that will be of help
>> for
>> > >> newcomers.
>> > >>
>> > >> I think Andrew can review the blog post and improve it and then be
>> ready
>> > >> to
>> > >> publish all tomorrow.
>> > >>
>> > >> As well if someone notice something that needs to be updated can
>> notify
>> > >> us.
>> > >>
>> > >> Thanks
>> > >>
>> > >>
>> > >> El mar., 8 oct. 2019 a las 10:37, Piotr Zarzycki (<
>> > >> piotrzarzyck...@gmail.com>)
>> > >> escribió:
>> > >>
>> > >> > Download and source code websites looks good to me. In blog post
>> you
>> > >> have
>> > >> > broken github links - review them and fix.
>> > >> >
>> > >> > Apart of that publish only Download and Source code. Blog post
>> should
>> > be
>> > >> > publish after I think official announce on dev, users and announce
>> > >> mailing
>> > >> > list. I'm going to do that tomorrow, cause there is still time for
>> > >> review
>> > >> > Draft of announcement.
>> > >> >
>> > >> > Thanks,
>> > >> > Piotr
>> > >> >
>> > >> > wt., 8 paź 2019 o 10:32 Carlos Rovira 
>> > >> > napisał(a):
>> > >> >
>> > >> > > Hi,
>> > >> > >
>> > >> > > Thanks Piotr, for the link

Re: Release 0.9.6 Announce for web post?

2019-10-08 Thread Piotr Zarzycki
This is the goal of syncing everything tomorrow. I asked you to publish
first link and source code on website, cause my announce probably go first
one and I didn't want to mislead with what will be on website. However if
you wanted to do that differently I'm fine - Couple of hours of misleading
doesn't hurts anyone maybe. - We will see tomorrow.

wt., 8 paź 2019 o 11:05 Carlos Rovira  napisał(a):

> Hi,
> ok, is normal,
> as people following our dev, are as well using links to 0.9.6 releases.
> The update of links in website is more about to announce to the rest of the
> world that is not as close to us as the rest of community.
> So it's important to communicate in the most organized way we can.
>
> thanks!
>
> El mar., 8 oct. 2019 a las 10:51, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>)
> escribió:
>
> > Just FYI: npm stuff and Maven artifacts are being published for couple of
> > days already, so people are using released 0.9.6 trough npm. - It's
> happen
> > automatically in case of npm.
> >
> > wt., 8 paź 2019 o 10:48 Piotr Zarzycki 
> > napisał(a):
> >
> > > Fine with me. I make announce tomorrow morning and review what was your
> > > change and update Draft.
> > >
> > > wt., 8 paź 2019 o 10:46 Carlos Rovira 
> > > napisał(a):
> > >
> > >> Hi, Piotr,
> > >>
> > >> I think we should update all at the same time, since we want to post
> in
> > >> twitter, Facebook and linkedin.
> > >> Doesn't have sense to me upload just a few links since almost nobody
> > will
> > >> notice it (and are already in GitHub releases). If we need to wait a
> day
> > >> to
> > >> send the official announcement it's ok for me. We can finish to
> improve
> > >> the
> > >> blog post in the meanwhile to do it better.
> > >>
> > >> For example, I changed a bit the wording, since we are not as "early"
> or
> > >> "alpha" and I mention as well that we have Apps in production, what is
> > now
> > >> important.
> > >> And finally talk about the improved Royale Docs that will be of help
> for
> > >> newcomers.
> > >>
> > >> I think Andrew can review the blog post and improve it and then be
> ready
> > >> to
> > >> publish all tomorrow.
> > >>
> > >> As well if someone notice something that needs to be updated can
> notify
> > >> us.
> > >>
> > >> Thanks
> > >>
> > >>
> > >> El mar., 8 oct. 2019 a las 10:37, Piotr Zarzycki (<
> > >> piotrzarzyck...@gmail.com>)
> > >> escribió:
> > >>
> > >> > Download and source code websites looks good to me. In blog post you
> > >> have
> > >> > broken github links - review them and fix.
> > >> >
> > >> > Apart of that publish only Download and Source code. Blog post
> should
> > be
> > >> > publish after I think official announce on dev, users and announce
> > >> mailing
> > >> > list. I'm going to do that tomorrow, cause there is still time for
> > >> review
> > >> > Draft of announcement.
> > >> >
> > >> > Thanks,
> > >> > Piotr
> > >> >
> > >> > wt., 8 paź 2019 o 10:32 Carlos Rovira 
> > >> > napisał(a):
> > >> >
> > >> > > Hi,
> > >> > >
> > >> > > Thanks Piotr, for the link :)
> > >> > >
> > >> > > I just updated website on pre site please take a quick look and
> I'll
> > >> > > publish it:
> > >> > >
> > >> > > https://royale.codeoscopic.com/apache-royale-v0-9-6-released/
> > >> > > https://royale.codeoscopic.com/download/
> > >> > > https://royale.codeoscopic.com/source-code/
> > >> > >
> > >> > > thanks
> > >> > >
> > >> > >
> > >> > >
> > >> > > El mar., 8 oct. 2019 a las 10:06, Carlos Rovira (<
> > >> > carlosrov...@apache.org
> > >> > > >)
> > >> > > escribió:
> > >> > >
> > >> > > > Hi,
> > >> > > >
> > >> > > > I'm updating all website in pre. I changed download and source
> > code
> > >> > > pages.
> > >> 

Re: Release 0.9.6 Announce for web post?

2019-10-08 Thread Piotr Zarzycki
Just FYI: npm stuff and Maven artifacts are being published for couple of
days already, so people are using released 0.9.6 trough npm. - It's happen
automatically in case of npm.

wt., 8 paź 2019 o 10:48 Piotr Zarzycki 
napisał(a):

> Fine with me. I make announce tomorrow morning and review what was your
> change and update Draft.
>
> wt., 8 paź 2019 o 10:46 Carlos Rovira 
> napisał(a):
>
>> Hi, Piotr,
>>
>> I think we should update all at the same time, since we want to post in
>> twitter, Facebook and linkedin.
>> Doesn't have sense to me upload just a few links since almost nobody will
>> notice it (and are already in GitHub releases). If we need to wait a day
>> to
>> send the official announcement it's ok for me. We can finish to improve
>> the
>> blog post in the meanwhile to do it better.
>>
>> For example, I changed a bit the wording, since we are not as "early" or
>> "alpha" and I mention as well that we have Apps in production, what is now
>> important.
>> And finally talk about the improved Royale Docs that will be of help for
>> newcomers.
>>
>> I think Andrew can review the blog post and improve it and then be ready
>> to
>> publish all tomorrow.
>>
>> As well if someone notice something that needs to be updated can notify
>> us.
>>
>> Thanks
>>
>>
>> El mar., 8 oct. 2019 a las 10:37, Piotr Zarzycki (<
>> piotrzarzyck...@gmail.com>)
>> escribió:
>>
>> > Download and source code websites looks good to me. In blog post you
>> have
>> > broken github links - review them and fix.
>> >
>> > Apart of that publish only Download and Source code. Blog post should be
>> > publish after I think official announce on dev, users and announce
>> mailing
>> > list. I'm going to do that tomorrow, cause there is still time for
>> review
>> > Draft of announcement.
>> >
>> > Thanks,
>> > Piotr
>> >
>> > wt., 8 paź 2019 o 10:32 Carlos Rovira 
>> > napisał(a):
>> >
>> > > Hi,
>> > >
>> > > Thanks Piotr, for the link :)
>> > >
>> > > I just updated website on pre site please take a quick look and I'll
>> > > publish it:
>> > >
>> > > https://royale.codeoscopic.com/apache-royale-v0-9-6-released/
>> > > https://royale.codeoscopic.com/download/
>> > > https://royale.codeoscopic.com/source-code/
>> > >
>> > > thanks
>> > >
>> > >
>> > >
>> > > El mar., 8 oct. 2019 a las 10:06, Carlos Rovira (<
>> > carlosrov...@apache.org
>> > > >)
>> > > escribió:
>> > >
>> > > > Hi,
>> > > >
>> > > > I'm updating all website in pre. I changed download and source code
>> > > pages.
>> > > > I'm going to do the blog post, for this I need the Annoucment, but I
>> > > can't
>> > > > see it in my mail client.
>> > > > @Piotr Zarzycki  can you send me that
>> email
>> > > > off list? I'm going to start from the 0.9.4 one in the meanwhile
>> > > >
>> > > > thanks
>> > > >
>> > > > Carlos
>> > > >
>> > > >
>> > > >
>> > > >
>> > > > El mar., 8 oct. 2019 a las 9:54, Piotr Zarzycki (<
>> > > > piotrzarzyck...@gmail.com>) escribió:
>> > > >
>> > > >> Carlos,
>> > > >>
>> > > >> Let me know if you have problems with updating links on website. If
>> > yes
>> > > I
>> > > >> will try to figure out how to do that.
>> > > >>
>> > > >> Thanks,
>> > > >> Piotr
>> > > >>
>> > > >> wt., 8 paź 2019 o 06:54 Piotr Zarzycki 
>> > > >> napisał(a):
>> > > >>
>> > > >> > Hey Andrew,
>> > > >> >
>> > > >> > Thank you!
>> > > >> >
>> > > >> > On Mon, Oct 7, 2019, 11:17 PM Andrew Wetmore <
>> cottag...@gmail.com>
>> > > >> wrote:
>> > > >> >
>> > > >> >> I looked over the draft announcement, Piotr, and it seems fine
>> as
>> > to
>> > > >> the
>> > > >> >> English. I cannot speak to the technical detai

Re: Release 0.9.6 Announce for web post?

2019-10-08 Thread Piotr Zarzycki
Fine with me. I make announce tomorrow morning and review what was your
change and update Draft.

wt., 8 paź 2019 o 10:46 Carlos Rovira  napisał(a):

> Hi, Piotr,
>
> I think we should update all at the same time, since we want to post in
> twitter, Facebook and linkedin.
> Doesn't have sense to me upload just a few links since almost nobody will
> notice it (and are already in GitHub releases). If we need to wait a day to
> send the official announcement it's ok for me. We can finish to improve the
> blog post in the meanwhile to do it better.
>
> For example, I changed a bit the wording, since we are not as "early" or
> "alpha" and I mention as well that we have Apps in production, what is now
> important.
> And finally talk about the improved Royale Docs that will be of help for
> newcomers.
>
> I think Andrew can review the blog post and improve it and then be ready to
> publish all tomorrow.
>
> As well if someone notice something that needs to be updated can notify us.
>
> Thanks
>
>
> El mar., 8 oct. 2019 a las 10:37, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>)
> escribió:
>
> > Download and source code websites looks good to me. In blog post you have
> > broken github links - review them and fix.
> >
> > Apart of that publish only Download and Source code. Blog post should be
> > publish after I think official announce on dev, users and announce
> mailing
> > list. I'm going to do that tomorrow, cause there is still time for review
> > Draft of announcement.
> >
> > Thanks,
> > Piotr
> >
> > wt., 8 paź 2019 o 10:32 Carlos Rovira 
> > napisał(a):
> >
> > > Hi,
> > >
> > > Thanks Piotr, for the link :)
> > >
> > > I just updated website on pre site please take a quick look and I'll
> > > publish it:
> > >
> > > https://royale.codeoscopic.com/apache-royale-v0-9-6-released/
> > > https://royale.codeoscopic.com/download/
> > > https://royale.codeoscopic.com/source-code/
> > >
> > > thanks
> > >
> > >
> > >
> > > El mar., 8 oct. 2019 a las 10:06, Carlos Rovira (<
> > carlosrov...@apache.org
> > > >)
> > > escribió:
> > >
> > > > Hi,
> > > >
> > > > I'm updating all website in pre. I changed download and source code
> > > pages.
> > > > I'm going to do the blog post, for this I need the Annoucment, but I
> > > can't
> > > > see it in my mail client.
> > > > @Piotr Zarzycki  can you send me that
> email
> > > > off list? I'm going to start from the 0.9.4 one in the meanwhile
> > > >
> > > > thanks
> > > >
> > > > Carlos
> > > >
> > > >
> > > >
> > > >
> > > > El mar., 8 oct. 2019 a las 9:54, Piotr Zarzycki (<
> > > > piotrzarzyck...@gmail.com>) escribió:
> > > >
> > > >> Carlos,
> > > >>
> > > >> Let me know if you have problems with updating links on website. If
> > yes
> > > I
> > > >> will try to figure out how to do that.
> > > >>
> > > >> Thanks,
> > > >> Piotr
> > > >>
> > > >> wt., 8 paź 2019 o 06:54 Piotr Zarzycki 
> > > >> napisał(a):
> > > >>
> > > >> > Hey Andrew,
> > > >> >
> > > >> > Thank you!
> > > >> >
> > > >> > On Mon, Oct 7, 2019, 11:17 PM Andrew Wetmore  >
> > > >> wrote:
> > > >> >
> > > >> >> I looked over the draft announcement, Piotr, and it seems fine as
> > to
> > > >> the
> > > >> >> English. I cannot speak to the technical details as well as other
> > > >> >> committers can.
> > > >> >>
> > > >> >> Andrew
> > > >> >>
> > > >> >> On Mon, Oct 7, 2019 at 5:01 PM Piotr Zarzycki <
> > > >> piotrzarzyck...@gmail.com>
> > > >> >> wrote:
> > > >> >>
> > > >> >> > Currently I'm waiting for review of Draft of announcement. Till
> > > >> maximum
> > > >> >> > Wednesday. Than I will send announce to dev, users and announce
> > > >> mailing
> > > >> >> > list.
> > > >> >> >
> > > >> >> > I think you sh

Re: Release 0.9.6 Announce for web post?

2019-10-08 Thread Piotr Zarzycki
Download and source code websites looks good to me. In blog post you have
broken github links - review them and fix.

Apart of that publish only Download and Source code. Blog post should be
publish after I think official announce on dev, users and announce mailing
list. I'm going to do that tomorrow, cause there is still time for review
Draft of announcement.

Thanks,
Piotr

wt., 8 paź 2019 o 10:32 Carlos Rovira  napisał(a):

> Hi,
>
> Thanks Piotr, for the link :)
>
> I just updated website on pre site please take a quick look and I'll
> publish it:
>
> https://royale.codeoscopic.com/apache-royale-v0-9-6-released/
> https://royale.codeoscopic.com/download/
> https://royale.codeoscopic.com/source-code/
>
> thanks
>
>
>
> El mar., 8 oct. 2019 a las 10:06, Carlos Rovira ( >)
> escribió:
>
> > Hi,
> >
> > I'm updating all website in pre. I changed download and source code
> pages.
> > I'm going to do the blog post, for this I need the Annoucment, but I
> can't
> > see it in my mail client.
> > @Piotr Zarzycki  can you send me that email
> > off list? I'm going to start from the 0.9.4 one in the meanwhile
> >
> > thanks
> >
> > Carlos
> >
> >
> >
> >
> > El mar., 8 oct. 2019 a las 9:54, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>) escribió:
> >
> >> Carlos,
> >>
> >> Let me know if you have problems with updating links on website. If yes
> I
> >> will try to figure out how to do that.
> >>
> >> Thanks,
> >> Piotr
> >>
> >> wt., 8 paź 2019 o 06:54 Piotr Zarzycki 
> >> napisał(a):
> >>
> >> > Hey Andrew,
> >> >
> >> > Thank you!
> >> >
> >> > On Mon, Oct 7, 2019, 11:17 PM Andrew Wetmore 
> >> wrote:
> >> >
> >> >> I looked over the draft announcement, Piotr, and it seems fine as to
> >> the
> >> >> English. I cannot speak to the technical details as well as other
> >> >> committers can.
> >> >>
> >> >> Andrew
> >> >>
> >> >> On Mon, Oct 7, 2019 at 5:01 PM Piotr Zarzycki <
> >> piotrzarzyck...@gmail.com>
> >> >> wrote:
> >> >>
> >> >> > Currently I'm waiting for review of Draft of announcement. Till
> >> maximum
> >> >> > Wednesday. Than I will send announce to dev, users and announce
> >> mailing
> >> >> > list.
> >> >> >
> >> >> > I think you should create draft and post it once announce will be
> >> sent.
> >> >> >
> >> >> > Apart of that I should add our release somewhere in the whimsy but
> I
> >> >> don't
> >> >> > remember where - I need to find that.
> >> >> >
> >> >> > Piotr
> >> >> >
> >> >> > On Mon, Oct 7, 2019, 9:33 PM Andrew Wetmore 
> >> >> wrote:
> >> >> >
> >> >> > > That would be good
> >> >> > >
> >> >> > > On Mon, Oct 7, 2019, 4:10 PM Carlos Rovira, <
> >> carlosrov...@apache.org>
> >> >> > > wrote:
> >> >> > >
> >> >> > > > Hi,
> >> >> > > > I'll be updating website in next few hours, but I was thinking
> we
> >> >> don't
> >> >> > > > have the habitual blog post for 0.9.6 release.
> >> >> > > > Should I create one from scratch based on 0.9.4?
> >> >> > > >
> >> >> > > > thanks
> >> >> > > >
> >> >> > > > --
> >> >> > > > Carlos Rovira
> >> >> > > > http://about.me/carlosrovira
> >> >> > > >
> >> >> > >
> >> >> >
> >> >>
> >> >>
> >> >> --
> >> >> Andrew Wetmore
> >> >>
> >> >> http://cottage14.blogspot.com/
> >> >>
> >> >
> >>
> >> --
> >>
> >> Piotr Zarzycki
> >>
> >> Patreon: *https://www.patreon.com/piotrzarzycki
> >> <https://www.patreon.com/piotrzarzycki>*
> >>
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 

Piotr Zarzycki

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


Re: Release 0.9.6 Announce for web post?

2019-10-08 Thread Piotr Zarzycki
Sorry it meant to be on dev.

wt., 8 paź 2019 o 10:11 Piotr Zarzycki 
napisał(a):

> Carlos,
>
> Here you have link to pony archive [1] and if you prefer nabble [2]
>
> [1]
> https://lists.apache.org/thread.html/3eb43d9ad3796179965ce7e91bee1e6cf864bf17044db3c6201adcbd@%3Cdev.royale.apache.org%3E
> [2]
> http://apache-royale-development.20373.n8.nabble.com/DRAFT-ANNOUNCE-Apache-Royale-0-9-6-released-td12408.html
>
> Thanks,
> Piotr
>
> wt., 8 paź 2019 o 10:06 Carlos Rovira 
> napisał(a):
>
>> Hi,
>>
>> I'm updating all website in pre. I changed download and source code pages.
>> I'm going to do the blog post, for this I need the Annoucment, but I
>> can't see it in my mail client.
>> @Piotr Zarzycki  can you send me that email
>> off list? I'm going to start from the 0.9.4 one in the meanwhile
>>
>> thanks
>>
>> Carlos
>>
>>
>>
>>
>> El mar., 8 oct. 2019 a las 9:54, Piotr Zarzycki (<
>> piotrzarzyck...@gmail.com>) escribió:
>>
>>> Carlos,
>>>
>>> Let me know if you have problems with updating links on website. If yes I
>>> will try to figure out how to do that.
>>>
>>> Thanks,
>>> Piotr
>>>
>>> wt., 8 paź 2019 o 06:54 Piotr Zarzycki 
>>> napisał(a):
>>>
>>> > Hey Andrew,
>>> >
>>> > Thank you!
>>> >
>>> > On Mon, Oct 7, 2019, 11:17 PM Andrew Wetmore 
>>> wrote:
>>> >
>>> >> I looked over the draft announcement, Piotr, and it seems fine as to
>>> the
>>> >> English. I cannot speak to the technical details as well as other
>>> >> committers can.
>>> >>
>>> >> Andrew
>>> >>
>>> >> On Mon, Oct 7, 2019 at 5:01 PM Piotr Zarzycki <
>>> piotrzarzyck...@gmail.com>
>>> >> wrote:
>>> >>
>>> >> > Currently I'm waiting for review of Draft of announcement. Till
>>> maximum
>>> >> > Wednesday. Than I will send announce to dev, users and announce
>>> mailing
>>> >> > list.
>>> >> >
>>> >> > I think you should create draft and post it once announce will be
>>> sent.
>>> >> >
>>> >> > Apart of that I should add our release somewhere in the whimsy but I
>>> >> don't
>>> >> > remember where - I need to find that.
>>> >> >
>>> >> > Piotr
>>> >> >
>>> >> > On Mon, Oct 7, 2019, 9:33 PM Andrew Wetmore 
>>> >> wrote:
>>> >> >
>>> >> > > That would be good
>>> >> > >
>>> >> > > On Mon, Oct 7, 2019, 4:10 PM Carlos Rovira, <
>>> carlosrov...@apache.org>
>>> >> > > wrote:
>>> >> > >
>>> >> > > > Hi,
>>> >> > > > I'll be updating website in next few hours, but I was thinking
>>> we
>>> >> don't
>>> >> > > > have the habitual blog post for 0.9.6 release.
>>> >> > > > Should I create one from scratch based on 0.9.4?
>>> >> > > >
>>> >> > > > thanks
>>> >> > > >
>>> >> > > > --
>>> >> > > > Carlos Rovira
>>> >> > > > http://about.me/carlosrovira
>>> >> > > >
>>> >> > >
>>> >> >
>>> >>
>>> >>
>>> >> --
>>> >> Andrew Wetmore
>>> >>
>>> >> http://cottage14.blogspot.com/
>>> >>
>>> >
>>>
>>> --
>>>
>>> Piotr Zarzycki
>>>
>>> Patreon: *https://www.patreon.com/piotrzarzycki
>>> <https://www.patreon.com/piotrzarzycki>*
>>>
>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


-- 

Piotr Zarzycki

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


Re: Release 0.9.6 Announce for web post?

2019-10-08 Thread Piotr Zarzycki
Carlos,

Let me know if you have problems with updating links on website. If yes I
will try to figure out how to do that.

Thanks,
Piotr

wt., 8 paź 2019 o 06:54 Piotr Zarzycki 
napisał(a):

> Hey Andrew,
>
> Thank you!
>
> On Mon, Oct 7, 2019, 11:17 PM Andrew Wetmore  wrote:
>
>> I looked over the draft announcement, Piotr, and it seems fine as to the
>> English. I cannot speak to the technical details as well as other
>> committers can.
>>
>> Andrew
>>
>> On Mon, Oct 7, 2019 at 5:01 PM Piotr Zarzycki 
>> wrote:
>>
>> > Currently I'm waiting for review of Draft of announcement. Till maximum
>> > Wednesday. Than I will send announce to dev, users and announce mailing
>> > list.
>> >
>> > I think you should create draft and post it once announce will be sent.
>> >
>> > Apart of that I should add our release somewhere in the whimsy but I
>> don't
>> > remember where - I need to find that.
>> >
>> > Piotr
>> >
>> > On Mon, Oct 7, 2019, 9:33 PM Andrew Wetmore 
>> wrote:
>> >
>> > > That would be good
>> > >
>> > > On Mon, Oct 7, 2019, 4:10 PM Carlos Rovira, 
>> > > wrote:
>> > >
>> > > > Hi,
>> > > > I'll be updating website in next few hours, but I was thinking we
>> don't
>> > > > have the habitual blog post for 0.9.6 release.
>> > > > Should I create one from scratch based on 0.9.4?
>> > > >
>> > > > thanks
>> > > >
>> > > > --
>> > > > Carlos Rovira
>> > > > http://about.me/carlosrovira
>> > > >
>> > >
>> >
>>
>>
>> --
>> Andrew Wetmore
>>
>> http://cottage14.blogspot.com/
>>
>

-- 

Piotr Zarzycki

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


Re: Heads up on XML

2019-10-08 Thread Piotr Zarzycki
Hi Greg,

Questions inline.

pon., 7 paź 2019 o 01:49 Greg Dove  napisał(a):

> Hi Piotr, just a quick follow-up to let you know that was all good, I had
> already tested the merge and conflict resolution myself and was ready to
> step in and help with that if that was necessary, but you already did it
> before I got a chance to send my email about that. :)
>
> I have to say: well done for getting through the release process. I could
> sense your frustration at times, and I know it must have seemed like it
> took far too long, but I am sure you have made a huge difference for the
> future in terms of that process.
>
>
> also fyi, I had to use -Dgenerate.swf.swcs=true in my local maven build
> today, and I was vaguely aware of discussions about this during release
> prep.
> But I wonder if this is necessary. Can't we just use the top level profiles
> at the lower levels instead of creating new profiles? There's probably a
> gap in my understanding of why this was necessary, but I would have
> expected that we could simply use something like:
>
> 
> generate-swcs-for-swf
> 
> 
> org.apache.royale.framework
> Core
> 0.9.7-SNAPSHOT
> swc
> swf
> 
> 
> 
>
>
How this activates  generate.swf.swcs ? What should I do if I wanted to
build only one module ? Doing that in above way how will change main
command which launches maven build ?


> in the framework modules, instead of:
>
>   
>   swf-dependencies
>   
>   
>   generate.swf.swcs
>   
>   
>   
>   
>   org.apache.royale.framework
>   Core
>   0.9.7-SNAPSHOT
>   swc
>   swf
>   
>   
>   
>
> (the above approach works locally for me just using the maven profile
> itself, if I make the changes to all framework modules, but as I said I
> could be missing something in relation to the issue that is being
> addressed)
>
>
> On Sun, Oct 6, 2019 at 11:20 PM Greg Dove  wrote:
>
> > Hi Piotr, I will check that in the morning local time... in about 8
> hours.
> >
> > On Sun, 6 Oct 2019, 21:54 Piotr Zarzycki, 
> > wrote:
> >
> >> Hi Greg,
> >>
> >> I run into merge conflict during merge release branch to develop into
> file
> >> which you have changed lately. Could you please verify on develop if I
> >> didn't remove anything, if I resolve conflict correctly. [1]
> >>
> >> [1]
> >>
> >>
> https://github.com/apache/royale-compiler/blob/develop/compiler-jx/src/main/java/org/apache/royale/compiler/internal/codegen/js/jx/MemberAccessEmitter.java
> >>
> >> Thanks,
> >> Piotr
> >>
> >> śr., 2 paź 2019 o 11:06 Harbs  napisał(a):
> >>
> >> > OK.
> >> >
> >> > I’ll test memory with and without your changes and let you know the
> >> > differences. :-)
> >> >
> >> > Harbs
> >> >
> >> > > On Oct 2, 2019, at 11:29 AM, Greg Dove  wrote:
> >> > >
> >> > > @harbs
> >> > >
> >> > > FYI in addition to some other stuff, I am close to pushing my
> updates
> >> to
> >> > > XML. This should be in the next hour or so.
> >> > >
> >> > > I kept the QName caching pretty close to how you had it, with only
> >> some
> >> > > minor changes.
> >> > > I tried to do some extra memory optimization, and in theory it
> should
> >> > > provide better results, but to be honest I don't have a good way to
> >> > measure
> >> > > this in the browser. I tried the Chrome performance.memory
> extensions
> >> > but I
> >> > > don't have much confidence in that given how much it varies between
> >> > reloads
> >> > > without changing anything else. The extra code changes I made were
> to
> >> > make
> >> > > the '_nodeKind' strings into String object references, so they only
> >> refer
> >> > > to a single reference to a string instead of multiple copies of
> >> > primitives.
> >> > > That change is isolated to a single commit so can easily be reversed
> >> if
> >> > > there is something not good about it... but all my local tests
> >> continue
> >> > to
&g

issues with Sourcetree in Mac

2019-10-07 Thread Piotr Zarzycki
Hi Carlos,

It means that you cannot update links on the website?

I'm using GitHub Desktop and yesterday everything was working fine.

Thanks,
Piotr

On Mon, Oct 7, 2019, 11:34 PM Carlos Rovira  wrote:

> Hi,
>
> I'm having issues with source tree on Mac
> this Saturday I tried to commit some changes and I was not able to do it. I
> can commit to local but not push to remote
> I thought that was some punctual problem, and since I had not much time, I
> decided to wait to next day.
> I'm trying today and still the problem remains.
> I could determine that I can git push from command line and what is failing
> is GitHub
>
> Tomorrow I'll try to solve it, but in the meantime I want to ask if it's
> only me. I didn't do anything in my Mac to have this kind of changes so
> don't know why it's this happening.
> Maybe something has changed in GitHub or something that is what is causing
> this issue?
>
> thanks
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


Release 0.9.6 Announce for web post?

2019-10-07 Thread Piotr Zarzycki
Hey Andrew,

Thank you!

On Mon, Oct 7, 2019, 11:17 PM Andrew Wetmore  wrote:

> I looked over the draft announcement, Piotr, and it seems fine as to the
> English. I cannot speak to the technical details as well as other
> committers can.
>
> Andrew
>
> On Mon, Oct 7, 2019 at 5:01 PM Piotr Zarzycki 
> wrote:
>
> > Currently I'm waiting for review of Draft of announcement. Till maximum
> > Wednesday. Than I will send announce to dev, users and announce mailing
> > list.
> >
> > I think you should create draft and post it once announce will be sent.
> >
> > Apart of that I should add our release somewhere in the whimsy but I
> don't
> > remember where - I need to find that.
> >
> > Piotr
> >
> > On Mon, Oct 7, 2019, 9:33 PM Andrew Wetmore  wrote:
> >
> > > That would be good
> > >
> > > On Mon, Oct 7, 2019, 4:10 PM Carlos Rovira, 
> > > wrote:
> > >
> > > > Hi,
> > > > I'll be updating website in next few hours, but I was thinking we
> don't
> > > > have the habitual blog post for 0.9.6 release.
> > > > Should I create one from scratch based on 0.9.4?
> > > >
> > > > thanks
> > > >
> > > > --
> > > > Carlos Rovira
> > > > http://about.me/carlosrovira
> > > >
> > >
> >
>
>
> --
> Andrew Wetmore
>
> http://cottage14.blogspot.com/
>


Release 0.9.6 Announce for web post?

2019-10-07 Thread Piotr Zarzycki
Currently I'm waiting for review of Draft of announcement. Till maximum
Wednesday. Than I will send announce to dev, users and announce mailing
list.

I think you should create draft and post it once announce will be sent.

Apart of that I should add our release somewhere in the whimsy but I don't
remember where - I need to find that.

Piotr

On Mon, Oct 7, 2019, 9:33 PM Andrew Wetmore  wrote:

> That would be good
>
> On Mon, Oct 7, 2019, 4:10 PM Carlos Rovira, 
> wrote:
>
> > Hi,
> > I'll be updating website in next few hours, but I was thinking we don't
> > have the habitual blog post for 0.9.6 release.
> > Should I create one from scratch based on 0.9.4?
> >
> > thanks
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>


Re: Build failed in Jenkins: royale-asjs #2777

2019-10-07 Thread Piotr Zarzycki
ed: 0.861 sec
> [royaleunit] Suite: flexUnitTests.xml.XMLQNameTest
> [royaleunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time
> elapsed: 0.738 sec
> [royaleunit]
> [royaleunit] Results :
> [royaleunit]
> [royaleunit] Tests run: 63, Failures: 1, Errors: 0, Skipped: 0, Time
> elapsed: 7.749 sec
> [royaleunit]
>
> BUILD FAILED
> <
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/build.xml>:653:
> The following error occurred while executing this line:
> <
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/build.xml>:134:
> The following error occurred while executing this line:
> <
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/build.xml>:369:
> The following error occurred while executing this line:
> <
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/projects/XML/build.xml>:67:
> The following error occurred while executing this line:
> <
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/projects/XML/src/test/royale/build.xml>:104:
> RoyaleUnit tests failed during the test run.
>
> Total time: 15 minutes 49 seconds
> Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g
> Build step 'Invoke Ant' marked build as failure
> Skipped archiving because build is not successful
>


-- 

Piotr Zarzycki

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


Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-10-07 Thread Piotr Zarzycki
Hi Carlos,

Will you be able update website with links for 0.9.6 release ?

Thanks,
Piotr

niedz., 6 paź 2019 o 10:52 Piotr Zarzycki 
napisał(a):

> Hi Alex,
>
> Thank you for the fix. Everything worked fine this time.
>
> Piotr
>
> sob., 5 paź 2019 o 01:51 Alex Harui  napisał(a):
>
>> I found some time to try the releasecandidate.xml and found the problem.
>> I pushed the fix to release/0.9.6.  So try that and see what happens.
>> It seemed to do the right thing for me on my Windows computer.
>>
>> You will next likely run into several merge conflicts.  I have not looked
>> into the conflicts, but there is a good chance that some of that is due to
>> the cherry-picking.  I am going to start a separate thread about branch
>> management.
>>
>> -Alex
>>
>> On 10/4/19, 10:55 AM, "Alex Harui"  wrote:
>>
>> If we don't fix the release scripts, then the next RM is probably
>> going to run into the same problem.  The time we spend now helps save time
>> in the future.  It is wise to improve the process now in case I get run
>> over by a bus tomorrow.  If you do it manually and make a mistake, we might
>> not catch it until later or cause more problems.
>>
>> IIRC, the Poms should not require changing.  Maven should have done
>> that already.
>>
>> All the places I know of changing are in the script.
>>
>> -Alex
>>
>> On 10/4/19, 10:46 AM, "Piotr Zarzycki" 
>> wrote:
>>
>> Alex,
>>
>> Can I just do that changes manually on release branch and merge
>> stuff to
>> develop?
>>
>> I just don't won't to spend any more minute on release process
>> anymore.
>>
>> 1) I should change build properties
>> 2) I should change all poms
>>
>> Is there anymore place which I should know to change?
>>
>> Thanks,
>> Piotr
>>
>> On Fri, Oct 4, 2019, 7:41 PM Alex Harui 
>> wrote:
>>
>> > Piotr,
>> >
>> > Again, I am asking you to get in the mindset of a developer and
>> not just a
>> > user.  You can see that the Ant script is making some updates.
>> You can
>> > verify that the release branch does not have 0.9.7 for the
>> release.version
>> > in build.properties.  You can see there is 1 commit pending in
>> > royale-asjs.  You can see that the build.properties did get
>> changed to have
>> > release.version=0.9.7.
>> >
>> > So, you will have to investigate further.  What is in that
>> commit?  Is
>> > this output from a fresh start of cloning the repo or could
>> that commit be
>> > from a previous run?  How could Git change a file but not
>> report it?  Maybe
>> > add some  tags or use -verbose to get more output.  But
>> just giving
>> > me minimal information and waiting for me to guess as to what
>> to do next is
>> > not very efficient, IMO.
>> >
>> > Thanks,
>> > -Alex
>> >
>> > On 10/4/19, 4:01 AM, "Piotr Zarzycki" <
>> piotrzarzyck...@gmail.com> wrote:
>> >
>> > Hi Alex,
>> >
>> > Git status after failing for all 3 repos [1].
>> >
>> > Here is how build.properties look like after performing
>> update.versions
>> > target [2].
>> >
>> > I will skip some part to move forward but update.versions
>> is important.
>> >
>> > [1]
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fl3zs9data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010sdata=nvSDESjmBw5j%2FlBoaIPGTUiBKrkoXcAVGIyUV371eE8%3Dreserved=0
>> > [2]
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F0zvoudata=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010sdata=ljQmwiJbtqsTIj3tx9%2FtKyy%2Bns5Sz7P%2BCQE3Knb%2F1fA%3Dreserved=0
>> >
>> > Thanks,
>> > Piotr
>> >
>> > czw., 3 paź 2019 o 17:49 Alex Haru

[DRAFT][ANNOUNCE] Apache Royale 0.9.6 released!

2019-10-06 Thread Piotr Zarzycki
Hi Guys,

Below draft of our announcement. I made also draft of the release on
GitHub. [1] I will wait 48h before I send it to announce. I think there is
one more place where I need to update in whimsy - can someone remember me
where it was ?

---
The Apache Royale community is pleased to announce the release of Apache
Royale 0.9.6.

The Apache Royale project is developing a next-generation of the Apache
Flex SDK. Royale has the goal of allowing applications developed in MXML
and ActionScript to not only run in the Flash/AIR runtimes, but also to run
natively in the browser without Flash, on mobile devices as a
PhoneGap/Cordova application, and in embedded JS environments such as
Chromium Embedded Framework. Royale has the potential to allow your MXML
and ActionScript code to run in even more places than Flash currently does.

This release should be considered ‘beta' quality. The purpose of this
release is to gather feedback about the features and implementation
strategies, and to recruit new contributors. We hope to grow the code base
into an SDK and tool chain that delivers the highest productivity when
developing applications that can run on many platforms. Beta releases may
not handle production needs.

Please file bugs at:

https://github.com/apache/royale-asjs/issues

If you happen to know it is a compiler issue, please use:

https://github.com/apache/royale-compiler/issues

For questions about how to use Royale, send email to us...@royale.apache.org.
For questions and feedback on the development of the source code in the
release, send email to dev@royale.apache.org.

Apache Royale is available in source and binary form from the Apache
mirrors:

Source:
http://www.apache.org/dyn/closer.lua/royale/0.9.6/apache-royale-0.9.6-src.tar.gz

http://www.apache.org/dyn/closer.lua/royale/0.9.6/apache-royale-0.9.6-src.zip

Binary:
http://www.apache.org/dyn/closer.lua/royale/0.9.6/binaries/apache-royale-0.9.6-bin-js.tar.gz
http://www.apache.org/dyn/closer.lua/royale/0.9.6/binaries/apache-royale-0.9.6-bin-js.zip

Binary with SWF support:
http://www.apache.org/dyn/closer.lua/royale/0.9.6/binaries/apache-royale-0.9.6-bin-js-swf.tar.gz
http://www.apache.org/dyn/closer.lua/royale/0.9.6/binaries/apache-royale-0.9.6-bin-js-swf.zip

When downloading from a mirror site, please remember to verify the
downloads using signatures or MD5 hashes.

The binary packages can also be installed via NPM.

Mac:

  sudo npm install @apache-royale/royale-js -g

Or for SWF Support:

  sudo npm install @apache-royale/royale-js-swf -g

Windows:

  npm install @apache-royale/royale-js -g

Or for SWF Support:

  npm install @apache-royale/royale-js-swf -g


See the README for more information. The language reference (ASDoc) is here:

  http://royale.apache.org/asdoc/

Additional documentation is here:

  https://apache.github.io/royale-docs/

The documentation is still a work in progress.  Volunteers are welcome to
help improve it. Visit http://royale.apache.org/ for links to other
resources.

Please try Royale and become involved in shaping the future of application
development.

The Apache Royale Community
---

[1]
https://github.com/apache/royale-asjs/releases/tag/untagged-279226b72126eeb56c78

Thanks,
-- 

Piotr Zarzycki

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


Re: Heads up on XML

2019-10-06 Thread Piotr Zarzycki
ill) now handle XML e4x references in nested function calls
> inside
> >>>> the filter, e.g. things like:
> >>>> e.g.
> >>>> var people:XML = 
> >>>>   
> >>>>   Bob
> >>>>   32
> >>>>   
> >>>>   
> >>>>   Joe
> >>>>   46
> >>>>   
> >>>>   ;
> >>>> var findJoeByAge:Function = function (i:int):Boolean {
> >>>>   return i > 40;
> >>>>   };
> >>>> people.person.(findJoeByAge(parseInt(age))).name
> >>>>
> >>>>
> >>>> I have lots more granular tests in QName, Namespace, and XML with
> >>> tuning to
> >>>> improve reliability.
> >>>> toXMLString XML node output also matches flash more correctly in what
> I
> >>>> have coming.
> >>>>
> >>>> One thing that I am trying to figure out, which I would appreciate
> >>> input on
> >>>> if someone has an answer:
> >>>> For the example:
> >>>>
> >>>> var feed:XML = new XML(
> >>>>   'http://www.w3.org/2005/Atom;
> >>>> xmlns:m="nothing">\n' +
> >>>>   '   >>>> href="blah/12321/domain/"/>\n' +
> >>>>   '\n');
> >>>> var atomSpace:Namespace = new Namespace('http://www.w3.org/2005/Atom'
> );
> >>>>
> >>>> Can anyone explain why this (in SWF, as a reference implementation):
> >>>> trace(feed.atomSpace::link.length())
> >>>> trace(feed.atomSpace::link.toXMLString())
> >>>> //output:
> >>>> 0
> >>>> {empty string}
> >>>> is different to:
> >>>> trace(feed.child(new QName(atomSpace,'link')).length())
> >>>> trace(feed.child(new QName(atomSpace,'link')).toXMLString())
> >>>> //output:
> >>>> 1
> >>>> http://www.w3.org/2005/Atom; xmlns:m="nothing"/>
> >>>>
> >>>> I had assumed the above cases would be the same, but the second one is
> >>>> behaving as if it has the default namespace included with the
> specified
> >>>> namespace in the QName matching (it does correctly match the namespace
> >>>> specifically as well -with e.g.  >>> is
> >>>> bound to the uri, but also seems to include link nodes with the
> default
> >>>> namespace, whether or not it is declared). I can accommodate this
> >>>> difference to make them behave the same, I just would like to
> understand
> >>>> the basis for the actual rules if anyone knows
> >>>>
> >>>> I should be in a position to push the updates this coming weekend I
> >>> think.
> >>>
> >>>
>
>

-- 

Piotr Zarzycki

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


Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-10-06 Thread Piotr Zarzycki
Hi Alex,

Thank you for the fix. Everything worked fine this time.

Piotr

sob., 5 paź 2019 o 01:51 Alex Harui  napisał(a):

> I found some time to try the releasecandidate.xml and found the problem.
> I pushed the fix to release/0.9.6.  So try that and see what happens.  It
> seemed to do the right thing for me on my Windows computer.
>
> You will next likely run into several merge conflicts.  I have not looked
> into the conflicts, but there is a good chance that some of that is due to
> the cherry-picking.  I am going to start a separate thread about branch
> management.
>
> -Alex
>
> On 10/4/19, 10:55 AM, "Alex Harui"  wrote:
>
> If we don't fix the release scripts, then the next RM is probably
> going to run into the same problem.  The time we spend now helps save time
> in the future.  It is wise to improve the process now in case I get run
> over by a bus tomorrow.  If you do it manually and make a mistake, we might
> not catch it until later or cause more problems.
>
> IIRC, the Poms should not require changing.  Maven should have done
> that already.
>
> All the places I know of changing are in the script.
>
> -Alex
>
> On 10/4/19, 10:46 AM, "Piotr Zarzycki" 
> wrote:
>
> Alex,
>
> Can I just do that changes manually on release branch and merge
> stuff to
> develop?
>
> I just don't won't to spend any more minute on release process
> anymore.
>
> 1) I should change build properties
> 2) I should change all poms
>
> Is there anymore place which I should know to change?
>
> Thanks,
> Piotr
>
> On Fri, Oct 4, 2019, 7:41 PM Alex Harui 
> wrote:
>
> > Piotr,
> >
> > Again, I am asking you to get in the mindset of a developer and
> not just a
> > user.  You can see that the Ant script is making some updates.
> You can
> > verify that the release branch does not have 0.9.7 for the
> release.version
> > in build.properties.  You can see there is 1 commit pending in
> > royale-asjs.  You can see that the build.properties did get
> changed to have
> > release.version=0.9.7.
> >
> > So, you will have to investigate further.  What is in that
> commit?  Is
> > this output from a fresh start of cloning the repo or could that
> commit be
> > from a previous run?  How could Git change a file but not report
> it?  Maybe
> > add some  tags or use -verbose to get more output.  But
> just giving
> > me minimal information and waiting for me to guess as to what to
> do next is
> > not very efficient, IMO.
> >
> > Thanks,
> > -Alex
> >
> > On 10/4/19, 4:01 AM, "Piotr Zarzycki" 
> wrote:
> >
> > Hi Alex,
> >
> > Git status after failing for all 3 repos [1].
> >
> > Here is how build.properties look like after performing
> update.versions
> > target [2].
> >
> > I will skip some part to move forward but update.versions is
> important.
> >
> > [1]
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fl3zs9data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010sdata=nvSDESjmBw5j%2FlBoaIPGTUiBKrkoXcAVGIyUV371eE8%3Dreserved=0
> > [2]
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F0zvoudata=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010sdata=ljQmwiJbtqsTIj3tx9%2FtKyy%2Bns5Sz7P%2BCQE3Knb%2F1fA%3Dreserved=0
> >
> > Thanks,
> > Piotr
> >
> > czw., 3 paź 2019 o 17:49 Alex Harui  >
> > napisał(a):
> >
> > > What does "git status" show in the 3 repos?
> > >
> > > The update.versions should have at least changed the
> > build.properties file
> > > in the repo.
> > >
> > > You can try skipping over steps by listing the steps on
> the command
> > line.
> > > You might need to list some pre-requisite steps before or
> add them
> > to the
> > > "depends

[DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-10-04 Thread Piotr Zarzycki
Alex,

Can I just do that changes manually on release branch and merge stuff to
develop?

I just don't won't to spend any more minute on release process anymore.

1) I should change build properties
2) I should change all poms

Is there anymore place which I should know to change?

Thanks,
Piotr

On Fri, Oct 4, 2019, 7:41 PM Alex Harui  wrote:

> Piotr,
>
> Again, I am asking you to get in the mindset of a developer and not just a
> user.  You can see that the Ant script is making some updates.  You can
> verify that the release branch does not have 0.9.7 for the release.version
> in build.properties.  You can see there is 1 commit pending in
> royale-asjs.  You can see that the build.properties did get changed to have
> release.version=0.9.7.
>
> So, you will have to investigate further.  What is in that commit?  Is
> this output from a fresh start of cloning the repo or could that commit be
> from a previous run?  How could Git change a file but not report it?  Maybe
> add some  tags or use -verbose to get more output.  But just giving
> me minimal information and waiting for me to guess as to what to do next is
> not very efficient, IMO.
>
> Thanks,
> -Alex
>
> On 10/4/19, 4:01 AM, "Piotr Zarzycki"  wrote:
>
> Hi Alex,
>
> Git status after failing for all 3 repos [1].
>
> Here is how build.properties look like after performing update.versions
> target [2].
>
> I will skip some part to move forward but update.versions is important.
>
> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fl3zs9data=02%7C01%7Caharui%40adobe.com%7Ce698bee1f6c14909189a08d748ba43bf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637057837153205594sdata=xBLjNOwyVKVNWQyKw%2F2%2F2pJD5KKl5ZgzxbCxoaVPrSI%3Dreserved=0
> [2]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F0zvoudata=02%7C01%7Caharui%40adobe.com%7Ce698bee1f6c14909189a08d748ba43bf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637057837153205594sdata=nmPTpAqG5dWUT%2BglHfM%2BQwpUEzvL%2F59P9GQ%2BqYQUvEs%3Dreserved=0
>
> Thanks,
> Piotr
>
> czw., 3 paź 2019 o 17:49 Alex Harui 
> napisał(a):
>
> > What does "git status" show in the 3 repos?
> >
> > The update.versions should have at least changed the
> build.properties file
> > in the repo.
> >
> > You can try skipping over steps by listing the steps on the command
> line.
> > You might need to list some pre-requisite steps before or add them
> to the
> > "depends" of the step that needs it.
> >
> > ant -e -f releasecandidate.xml -Drelease.version=0.9.6 -Drc=3
> > update.versions merge_rc_to_develop release.maven.staging.repo
> >
> > -Alex
> >
> > On 10/3/19, 1:49 AM, "Piotr Zarzycki" 
> wrote:
> >
> > Those are the steps from the script which need to be done still:
> >
> > 1)  
> > 2) 
> > 3) 
> >
> > Number #1 is failing.
> >
> >
> > czw., 3 paź 2019 o 10:41 Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> > napisał(a):
> >
> > > It looks like we already have:
> > > 1) Successfully published npm:
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.npmjs.com%2Fpackage%2F%40apache-royale%2Froyale-jsdata=02%7C01%7Caharui%40adobe.com%7Ce698bee1f6c14909189a08d748ba43bf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637057837153205594sdata=m35lsvR0DTt5MVy0Y5pgDbcIaUexq72ZnmMNjaeakJI%3Dreserved=0
> > > 2) Successfully published which can be updated on the website:
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Froyale%2F0.9.6%2Fbinaries%2Fapache-royale-0.9.6-bin-js.tar.gzdata=02%7C01%7Caharui%40adobe.com%7Ce698bee1f6c14909189a08d748ba43bf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637057837153205594sdata=bHENqecd10JZ0BvQvyDsgYXNm%2FHSAIZYM%2F5aKmifyr8%3Dreserved=0
> > >
> > > Thanks,
> > > Piotr
> > >
> > > czw., 3 paź 2019 o 10:33 Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> > > napisał(a):
> > >
> > >> I have used npm password from private and went trough
> publishing
> > npm and
> > >> it's failed on next step update.version with the same error.
> Here
> > you go
> > >> full log [1].
> > >>

Re: Welcome Andrew Wetmore to Apache Royale's PMC

2019-10-04 Thread Piotr Zarzycki
  Hi Andrew! Good luck! :)

pt., 4 paź 2019 o 11:16 Harbs  napisał(a):

> Welcome! I'm thrilled with all you’ve done for Royale! :-)
>
> Harbs
>
> > On Oct 3, 2019, at 8:55 PM, OmPrakash Muppirala 
> wrote:
> >
> > It is with great pleasure that I announce that the Apache Royale PMC
> members have voted in Andrew Wetmore to the PMC.  Please join us in
> welcoming him.  This is a recognition of Andrew's great work in helping out
> with Apache Royale's documentation among other things.
> >
> > Regards,
> > Om
> > (On behalf of Apache Royale PMC)
>
>

-- 

Piotr Zarzycki

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


Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-10-04 Thread Piotr Zarzycki
Hi Alex,

Git status after failing for all 3 repos [1].

Here is how build.properties look like after performing update.versions
target [2].

I will skip some part to move forward but update.versions is important.

[1] https://paste.apache.org/l3zs9
[2] https://paste.apache.org/0zvou

Thanks,
Piotr

czw., 3 paź 2019 o 17:49 Alex Harui  napisał(a):

> What does "git status" show in the 3 repos?
>
> The update.versions should have at least changed the build.properties file
> in the repo.
>
> You can try skipping over steps by listing the steps on the command line.
> You might need to list some pre-requisite steps before or add them to the
> "depends" of the step that needs it.
>
> ant -e -f releasecandidate.xml -Drelease.version=0.9.6 -Drc=3
> update.versions merge_rc_to_develop release.maven.staging.repo
>
> -Alex
>
> On 10/3/19, 1:49 AM, "Piotr Zarzycki"  wrote:
>
> Those are the steps from the script which need to be done still:
>
> 1)  
> 2) 
> 3) 
>
> Number #1 is failing.
>
>
> czw., 3 paź 2019 o 10:41 Piotr Zarzycki 
> napisał(a):
>
> > It looks like we already have:
> > 1) Successfully published npm:
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.npmjs.com%2Fpackage%2F%40apache-royale%2Froyale-jsdata=02%7C01%7Caharui%40adobe.com%7Cc21097df22b0426c28a808d747dea04e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637056893810206817sdata=4idQHiSsqaCC57d%2FMoZYx%2Bze3xZRLwrahAJhYykR2WI%3Dreserved=0
> > 2) Successfully published which can be updated on the website:
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Froyale%2F0.9.6%2Fbinaries%2Fapache-royale-0.9.6-bin-js.tar.gzdata=02%7C01%7Caharui%40adobe.com%7Cc21097df22b0426c28a808d747dea04e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637056893810206817sdata=piwVUdIWhFhDZTIjKG9CCTkJBuzx5QKitI%2F%2BYSYyv0A%3Dreserved=0
> >
> > Thanks,
> > Piotr
> >
> > czw., 3 paź 2019 o 10:33 Piotr Zarzycki 
> > napisał(a):
> >
> >> I have used npm password from private and went trough publishing
> npm and
> >> it's failed on next step update.version with the same error. Here
> you go
> >> full log [1].
> >>
> >> What will happen if I run publish npm stuff again ? I can omit that
> part
> >> in the next attempt.
> >>
> >> Om can you check whether my npm publish stuff went ok ?
> >>
> >> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fyl06ddata=02%7C01%7Caharui%40adobe.com%7Cc21097df22b0426c28a808d747dea04e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637056893810206817sdata=K3Jqc8tjhRGyCjE2vHIzVyDQ070L3HYxLzjBNFzrtdI%3Dreserved=0
> >>
> >> Thanks,
> >> Piotr
> >>
> >> Thanks,
> >> Piotr
> >>
> >> śr., 2 paź 2019 o 18:40 Alex Harui 
> napisał(a):
> >>
> >>> Responses inline...
> >>>
> >>> On 10/2/19, 1:37 AM, "Piotr Zarzycki" 
> >>> wrote:
> >>>
> >>> Just to understand something. releasecandidate script is using
> tag
> >>> instead
> >>> release branch to whole operation of increase version ?
> >>>
> >>> No, the  "get_head_of_rc_branches" target should get you the head.
> >>>
> >>> > Hi,
> >>> >
> >>> > I just tried releasecandidate script. It contains following
> steps.
> >>> >
> >>> > 
> >>> > 
> >>> > 
> >>> > 
> >>> > 
> >>> > 
> >>> > 
> >>> > 
> >>> >
> >>> > One step previous was move in svn binaries from dev folder to
> >>> release - I
> >>> > omit that cause I did it already manually. Launching
> following
> >>> steps I
> >>> > reached release.npm - Which requires login and password to
> npm - I
> >>> > omitted that as well. Next was update.versions and it failed
> with
> >>> following
> >>> > stack trace [1]
> >>> >
> >>>
> >>> Th

Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-10-03 Thread Piotr Zarzycki
Those are the steps from the script which need to be done still:

1)  
2) 
3) 

Number #1 is failing.


czw., 3 paź 2019 o 10:41 Piotr Zarzycki 
napisał(a):

> It looks like we already have:
> 1) Successfully published npm:
> https://www.npmjs.com/package/@apache-royale/royale-js
> 2) Successfully published which can be updated on the website:
> https://www.apache.org/dyn/closer.lua/royale/0.9.6/binaries/apache-royale-0.9.6-bin-js.tar.gz
>
> Thanks,
> Piotr
>
> czw., 3 paź 2019 o 10:33 Piotr Zarzycki 
> napisał(a):
>
>> I have used npm password from private and went trough publishing npm and
>> it's failed on next step update.version with the same error. Here you go
>> full log [1].
>>
>> What will happen if I run publish npm stuff again ? I can omit that part
>> in the next attempt.
>>
>> Om can you check whether my npm publish stuff went ok ?
>>
>> [1] https://paste.apache.org/yl06d
>>
>> Thanks,
>> Piotr
>>
>> Thanks,
>> Piotr
>>
>> śr., 2 paź 2019 o 18:40 Alex Harui  napisał(a):
>>
>>> Responses inline...
>>>
>>> On 10/2/19, 1:37 AM, "Piotr Zarzycki" 
>>> wrote:
>>>
>>> Just to understand something. releasecandidate script is using tag
>>> instead
>>> release branch to whole operation of increase version ?
>>>
>>> No, the  "get_head_of_rc_branches" target should get you the head.
>>>
>>> > Hi,
>>> >
>>> > I just tried releasecandidate script. It contains following steps.
>>> >
>>> > 
>>> > 
>>> > 
>>> > 
>>> > 
>>> > 
>>> > 
>>> > 
>>> >
>>> > One step previous was move in svn binaries from dev folder to
>>> release - I
>>> > omit that cause I did it already manually. Launching following
>>> steps I
>>> > reached release.npm - Which requires login and password to npm - I
>>> > omitted that as well. Next was update.versions and it failed with
>>> following
>>> > stack trace [1]
>>> >
>>>
>>> The login and password is available in the private@ archives.
>>>
>>>
>>> > In mentioned lines in the stacktrace I have:
>>> >
>>> > Line 1088:
>>> > 
>>> >
>>> > Line 1216:
>>> > 
>>> > 
>>> > 
>>> > >> />
>>> > 
>>> >
>>> > [1]
>>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F15biudata=02%7C01%7Caharui%40adobe.com%7Ca6fd586ab1f044a4b2c408d74713bf65%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637056022453516542sdata=usDOkcnLx4HhZJSYsMde5pnvgQMDyKLSIKeOccmCJkc%3Dreserved=0
>>>
>>> You did not post the whole log, so it is possible you missed a step.
>>> There is almost no way there shouldn't be changes and the head should not
>>> be detached.
>>>
>>> -Alex
>>>
>>>
>>
>> --
>>
>> Piotr Zarzycki
>>
>> Patreon: *https://www.patreon.com/piotrzarzycki
>> <https://www.patreon.com/piotrzarzycki>*
>>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


-- 

Piotr Zarzycki

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


Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-10-03 Thread Piotr Zarzycki
It looks like we already have:
1) Successfully published npm:
https://www.npmjs.com/package/@apache-royale/royale-js
2) Successfully published which can be updated on the website:
https://www.apache.org/dyn/closer.lua/royale/0.9.6/binaries/apache-royale-0.9.6-bin-js.tar.gz

Thanks,
Piotr

czw., 3 paź 2019 o 10:33 Piotr Zarzycki 
napisał(a):

> I have used npm password from private and went trough publishing npm and
> it's failed on next step update.version with the same error. Here you go
> full log [1].
>
> What will happen if I run publish npm stuff again ? I can omit that part
> in the next attempt.
>
> Om can you check whether my npm publish stuff went ok ?
>
> [1] https://paste.apache.org/yl06d
>
> Thanks,
> Piotr
>
> Thanks,
> Piotr
>
> śr., 2 paź 2019 o 18:40 Alex Harui  napisał(a):
>
>> Responses inline...
>>
>> On 10/2/19, 1:37 AM, "Piotr Zarzycki"  wrote:
>>
>> Just to understand something. releasecandidate script is using tag
>> instead
>> release branch to whole operation of increase version ?
>>
>> No, the  "get_head_of_rc_branches" target should get you the head.
>>
>> > Hi,
>> >
>> > I just tried releasecandidate script. It contains following steps.
>> >
>> > 
>> > 
>> > 
>> > 
>> > 
>> > 
>> > 
>> > 
>> >
>> > One step previous was move in svn binaries from dev folder to
>> release - I
>> > omit that cause I did it already manually. Launching following
>> steps I
>> > reached release.npm - Which requires login and password to npm - I
>> > omitted that as well. Next was update.versions and it failed with
>> following
>> > stack trace [1]
>> >
>>
>> The login and password is available in the private@ archives.
>>
>>
>> > In mentioned lines in the stacktrace I have:
>> >
>> > Line 1088:
>> > 
>> >
>> > Line 1216:
>> > 
>> > 
>> > 
>> > 
>> > 
>> >
>> > [1]
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F15biudata=02%7C01%7Caharui%40adobe.com%7Ca6fd586ab1f044a4b2c408d74713bf65%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637056022453516542sdata=usDOkcnLx4HhZJSYsMde5pnvgQMDyKLSIKeOccmCJkc%3Dreserved=0
>>
>> You did not post the whole log, so it is possible you missed a step.
>> There is almost no way there shouldn't be changes and the head should not
>> be detached.
>>
>> -Alex
>>
>>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


-- 

Piotr Zarzycki

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


Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-10-03 Thread Piotr Zarzycki
I have used npm password from private and went trough publishing npm and
it's failed on next step update.version with the same error. Here you go
full log [1].

What will happen if I run publish npm stuff again ? I can omit that part in
the next attempt.

Om can you check whether my npm publish stuff went ok ?

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

Thanks,
Piotr

Thanks,
Piotr

śr., 2 paź 2019 o 18:40 Alex Harui  napisał(a):

> Responses inline...
>
> On 10/2/19, 1:37 AM, "Piotr Zarzycki"  wrote:
>
> Just to understand something. releasecandidate script is using tag
> instead
> release branch to whole operation of increase version ?
>
> No, the  "get_head_of_rc_branches" target should get you the head.
>
> > Hi,
> >
> > I just tried releasecandidate script. It contains following steps.
> >
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> >
> > One step previous was move in svn binaries from dev folder to
> release - I
> > omit that cause I did it already manually. Launching following steps
> I
> > reached release.npm - Which requires login and password to npm - I
> > omitted that as well. Next was update.versions and it failed with
> following
> > stack trace [1]
> >
>
> The login and password is available in the private@ archives.
>
>
> > In mentioned lines in the stacktrace I have:
> >
> > Line 1088:
> > 
> >
> > Line 1216:
> > 
> > 
> > 
> > 
> > 
> >
> > [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F15biudata=02%7C01%7Caharui%40adobe.com%7Ca6fd586ab1f044a4b2c408d74713bf65%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637056022453516542sdata=usDOkcnLx4HhZJSYsMde5pnvgQMDyKLSIKeOccmCJkc%3Dreserved=0
>
> You did not post the whole log, so it is possible you missed a step.
> There is almost no way there shouldn't be changes and the head should not
> be detached.
>
> -Alex
>
>

-- 

Piotr Zarzycki

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


Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-10-02 Thread Piotr Zarzycki
Just to understand something. releasecandidate script is using tag instead
release branch to whole operation of increase version ?
Cause on release branch I have already version increased, so what's the
point of doing anything using tag ?

śr., 2 paź 2019 o 10:27 Piotr Zarzycki 
napisał(a):

> Hi,
>
> I just tried releasecandidate script. It contains following steps.
>
> 
> 
> 
> 
> 
> 
> 
> 
>
> One step previous was move in svn binaries from dev folder to release - I
> omit that cause I did it already manually. Launching following steps I
> reached release.npm - Which requires login and password to npm - I
> omitted that as well. Next was update.versions and it failed with following
> stack trace [1]
>
> In mentioned lines in the stacktrace I have:
>
> Line 1088:
> 
>
> Line 1216:
> 
> 
> 
> 
> 
>
> [1] https://paste.apache.org/15biu
>
> Thanks,
> Piotr
>
>
>
> śr., 2 paź 2019 o 02:54 OmPrakash Muppirala 
> napisał(a):
>
>> On Tue, Oct 1, 2019 at 8:32 AM Alex Harui 
>> wrote:
>>
>> > The releasecandidate.xml script will tell you what to do on
>> > repository.apache.org to release the Maven stuff, and release the npm
>> > stuff as well.  The whole point of these scripts is so you don't have to
>> > ask for help.  If you do end up needing help, then the scripts need
>> > improving.  We want to capture knowledge in these scripts and on the
>> wiki.
>> >
>> >
>> Alex, did you merge your fixes to the npm related stuff into the release
>> branch?  If yes, I think we should be good to go.
>>
>> Thanks,
>> Om
>>
>>
>> > -Alex
>> >
>> > On 10/1/19, 12:30 AM, "Piotr Zarzycki" 
>> wrote:
>> >
>> > Hi Om,
>> >
>> > What I need to do in order to release stuff on npm. Can you do this
>> > for me
>> > once I push release to svn ?
>> >
>> > Thanks,
>> > Piotr
>> >
>> > wt., 1 paź 2019 o 09:25 Piotr Zarzycki 
>> > napisał(a):
>> >
>> > > Hi Harbs,
>> > >
>> > > I think we have enough votes. I still have to gather info how
>> > actually
>> > > release Maven artifacts. However I'm going to push binaries today
>> in
>> > svn.
>> > >
>> > > Thanks,
>> > > Piotr
>> > >
>> > > sob., 28 wrz 2019 o 20:02 Harbs 
>> napisał(a):
>> > >
>> > >> FYI, I will not be able to test the release until Wednesday.
>> > >>
>> > >> If the vote is still open, I plan on testing then.
>> > >>
>> > >> Thanks,
>> > >> Harbs
>> > >>
>> > >> > On Sep 25, 2019, at 5:24 PM, Piotr Zarzycki <
>> > piotrzarzyck...@gmail.com>
>> > >> wrote:
>> > >> >
>> > >> > Ok, new and hopefully the last one RC3. I didn't run
>> ApproveScript
>> > >> myself
>> > >> > yet, but will do that tomorrow or next week.
>> > >> >
>> > >> > śr., 25 wrz 2019 o 16:23 Apache Royale CI Server <
>> > >> apacheroyal...@gmail.com>
>> > >> > napisał(a):
>> > >> >
>> > >> >> This is the discussion thread.
>> > >> >>
>> > >> >> Thanks,
>> > >> >> Piotr
>> > >> >
>> > >> >
>> > >> >
>> > >> > --
>> > >> >
>> > >> > Piotr Zarzycki
>> > >> >
>> > >> > Patreon: *
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3Dreserved=0
>> > >> > <
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39

Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-10-02 Thread Piotr Zarzycki
Hi,

I just tried releasecandidate script. It contains following steps.










One step previous was move in svn binaries from dev folder to release - I
omit that cause I did it already manually. Launching following steps I
reached release.npm - Which requires login and password to npm - I
omitted that as well. Next was update.versions and it failed with following
stack trace [1]

In mentioned lines in the stacktrace I have:

Line 1088:


Line 1216:






[1] https://paste.apache.org/15biu

Thanks,
Piotr



śr., 2 paź 2019 o 02:54 OmPrakash Muppirala 
napisał(a):

> On Tue, Oct 1, 2019 at 8:32 AM Alex Harui 
> wrote:
>
> > The releasecandidate.xml script will tell you what to do on
> > repository.apache.org to release the Maven stuff, and release the npm
> > stuff as well.  The whole point of these scripts is so you don't have to
> > ask for help.  If you do end up needing help, then the scripts need
> > improving.  We want to capture knowledge in these scripts and on the
> wiki.
> >
> >
> Alex, did you merge your fixes to the npm related stuff into the release
> branch?  If yes, I think we should be good to go.
>
> Thanks,
> Om
>
>
> > -Alex
> >
> > On 10/1/19, 12:30 AM, "Piotr Zarzycki" 
> wrote:
> >
> > Hi Om,
> >
> > What I need to do in order to release stuff on npm. Can you do this
> > for me
> > once I push release to svn ?
> >
> > Thanks,
> > Piotr
> >
> > wt., 1 paź 2019 o 09:25 Piotr Zarzycki 
> > napisał(a):
> >
> > > Hi Harbs,
> > >
> > > I think we have enough votes. I still have to gather info how
> > actually
> > > release Maven artifacts. However I'm going to push binaries today
> in
> > svn.
> > >
> > > Thanks,
> > > Piotr
> > >
> > > sob., 28 wrz 2019 o 20:02 Harbs 
> napisał(a):
> > >
> > >> FYI, I will not be able to test the release until Wednesday.
> > >>
> > >> If the vote is still open, I plan on testing then.
> > >>
> > >> Thanks,
> > >> Harbs
> > >>
> > >> > On Sep 25, 2019, at 5:24 PM, Piotr Zarzycki <
> > piotrzarzyck...@gmail.com>
> > >> wrote:
> > >> >
> > >> > Ok, new and hopefully the last one RC3. I didn't run
> ApproveScript
> > >> myself
> > >> > yet, but will do that tomorrow or next week.
> > >> >
> > >> > śr., 25 wrz 2019 o 16:23 Apache Royale CI Server <
> > >> apacheroyal...@gmail.com>
> > >> > napisał(a):
> > >> >
> > >> >> This is the discussion thread.
> > >> >>
> > >> >> Thanks,
> > >> >> Piotr
> > >> >
> > >> >
> > >> >
> > >> > --
> > >> >
> > >> > Piotr Zarzycki
> > >> >
> > >> > Patreon: *
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3Dreserved=0
> > >> > <
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3Dreserved=0
> > >*
> > >>
> > >>
> > >
> > > --
> > >
> > > Piotr Zarzycki
> > >
> > > Patreon: *
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3Dreserved=0
> > > <
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3Dreserved=0
> > >*
> > >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3Dreserved=0
> > <
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3Dreserved=0
> > >*
> >
> >
> >
>


-- 

Piotr Zarzycki

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


Re: ASDoc fails to compile with ANT

2019-10-01 Thread Piotr Zarzycki
I will run tomorrow releasecandidate script and see what will happen, so
expect some merge tomorrow ;)

wt., 1 paź 2019 o 17:41 Alex Harui  napisał(a):

> That was fixed in the release branch.  I think Piotr will merge soon to
> develop.  For now, define the Adobe environment variables (AIR_HOME,
> PLAYERGLOBAL_HOME, FLASHPLAYER_DEBUGGER).
>
> -Alex
>
> On 10/1/19, 3:39 AM, "Carlos Rovira"  wrote:
>
> Hi,
>
> I tried to run ASDoc to update site with latest reference. I remember
> that
> ASDoc can only be compiled right with ANT.
> This is what I get after run "ant" in ASDoc folder:
>
> build_example.check-air:
>
>
> build_example.copy-app-xml:
>
>
> main:
>
>
> json:
>
>  [echo] ROYALE_COMPILER_HOME:
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/js
>
>  [java] 0.673472226 seconds
>
>  [java]
>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml(145):
> col: 0 unable to open
>
> '/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/ASDoc/src/main/config//11.1'.
>
>  [java]
>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml
> (line: 145)
>
>  [java]
>
>  [java]   
>
>  [java]
>
>  [java]
>
>  [java] Java Result: 5
>
>
> BUILD FAILED
>
>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/ASDoc/build.xml:48:
> The following error occurred while executing this line:
>
>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/ASDoc/build.xml:107:
> condition satisfied
>
>
> Total time: 14 seconds
>
>
>
> I suppose that some of the latest changes in building must be
> propagated to
> ASDoc as well.
>
>
> Can someone take a look to see what could be the problem?
>
>
> thanks
>
> --
> Carlos Rovira
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C3c194c67a3ff4cbbc02508d7465baa7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637055231831849685sdata=wUmzvVFO%2By9l8G45rJkOKqu3%2FFeid%2FYrvU0f%2Bcfhb80%3Dreserved=0
>
>
>

-- 

Piotr Zarzycki

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


Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-10-01 Thread Piotr Zarzycki
I see that releasecandidate.xml script can help me with last steps. Does it
doing Maven releases as well ?
That steps includes also push to svn - I just did it manually, so I will
probably comment out commit part and run script. - I think tomorrow.

wt., 1 paź 2019 o 09:29 Piotr Zarzycki 
napisał(a):

> Hi Om,
>
> What I need to do in order to release stuff on npm. Can you do this for me
> once I push release to svn ?
>
> Thanks,
> Piotr
>
> wt., 1 paź 2019 o 09:25 Piotr Zarzycki 
> napisał(a):
>
>> Hi Harbs,
>>
>> I think we have enough votes. I still have to gather info how actually
>> release Maven artifacts. However I'm going to push binaries today in svn.
>>
>> Thanks,
>> Piotr
>>
>> sob., 28 wrz 2019 o 20:02 Harbs  napisał(a):
>>
>>> FYI, I will not be able to test the release until Wednesday.
>>>
>>> If the vote is still open, I plan on testing then.
>>>
>>> Thanks,
>>> Harbs
>>>
>>> > On Sep 25, 2019, at 5:24 PM, Piotr Zarzycki 
>>> wrote:
>>> >
>>> > Ok, new and hopefully the last one RC3. I didn't run ApproveScript
>>> myself
>>> > yet, but will do that tomorrow or next week.
>>> >
>>> > śr., 25 wrz 2019 o 16:23 Apache Royale CI Server <
>>> apacheroyal...@gmail.com>
>>> > napisał(a):
>>> >
>>> >> This is the discussion thread.
>>> >>
>>> >> Thanks,
>>> >> Piotr
>>> >
>>> >
>>> >
>>> > --
>>> >
>>> > Piotr Zarzycki
>>> >
>>> > Patreon: *https://www.patreon.com/piotrzarzycki
>>> > <https://www.patreon.com/piotrzarzycki>*
>>>
>>>
>>
>> --
>>
>> Piotr Zarzycki
>>
>> Patreon: *https://www.patreon.com/piotrzarzycki
>> <https://www.patreon.com/piotrzarzycki>*
>>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


-- 

Piotr Zarzycki

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


[RESULT][VOTE] Release Apache Royale 0.9.6 RC3

2019-10-01 Thread Piotr Zarzycki
Vote passes with 4 +1 votes.

Thank you for voting! We are finally having release.
Piotr

pon., 30 wrz 2019 o 16:23 Piotr Zarzycki 
napisał(a):

> +1 (Binding)
>
> Package
> https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc3/apache-royale-0.9.6-src.zip
> Java 1.8
> OS: Windows 10 amd64 10.0
> 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.6/rc3/binaries/apache-royale-0.9.6-bin-js-swf.zip
> 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
>
> Additionally I was able build and run big Apache Royale application
> I was able build PureMVC source code to swc.
>
> sob., 28 wrz 2019 o 02:40 Carlos Rovira 
> napisał(a):
>
>> +1
>>
>> approve:
>>
>>
>> +1
>>
>> Package
>>
>> https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc3/apache-royale-0.9.6-src.tar.gz
>>
>> Java 1.8
>>
>> OS: Mac OS X x86_64 10.14.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.6/rc3/binaries/apache-royale-0.9.6-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
>>
>>
>>
>>
>> El jue., 26 sept. 2019 a las 21:05, Alex Harui (> >)
>> escribió:
>>
>> > +1
>> > Package
>> >
>> https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc3/apache-royale-0.9.6-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.6/rc3/binaries/apache-royale-0.9.6-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
>> >
>> > I tested with both a clean js-only and clean js-swf configuration.
>> >
>> > -Alex
>> >
>> > On 9/25/19, 7:23 AM, "Apache Royale CI Server" <
>> apacheroyal...@gmail.com>
>> > wrote:
>> >
>> > Hi,
>> >
>> > This is the vote for the 0.9.6 release of Apache Royale.
>> >
>> > The release candidate can be found here;
>> >
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.6%2Frc3%2Fdata=02%7C01%7Caharui%40adobe.com%7Cb8881952698c4de9211a08d741c3e343%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637050181900826730sdata=7mgOGrzL7RpQR%2FmCwIrw1EZzmUN2UpfkqvuuXPcVTDo%3Dreserved=0
>> >
>> > Before voting please review the section,'What are the ASF
>> requirements
>> > on
>> > approving a release?', at:
>> >
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache.org%2Fdev%2Frelease.html%23approving-a-releasedata=02%7C01%7Caharui%40adobe.com%7Cb8881952698c4de9211a08d741c3e343%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637050181900826730sdata=svKLd3TVFay9L5Yupvom3se2fcfyEG3ak8sw9vrUn7I%3Dreserved=0
>> >
>> > At a minimum you would be expected to check that:
>> > - SHA and signed packages are correct
>> > - README, RELEASE_NOTES, NOTICE and LICENSE files are all fine
>> > - That the build script completes successfully
>> > - That you can compile and cross-compile a simple example using the
>> > SDK.
>> >
>> > The KEYS file is at
>> >
>> https://nam04.safelinks.protection.outlook.com/?url

Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-10-01 Thread Piotr Zarzycki
Hi Om,

What I need to do in order to release stuff on npm. Can you do this for me
once I push release to svn ?

Thanks,
Piotr

wt., 1 paź 2019 o 09:25 Piotr Zarzycki 
napisał(a):

> Hi Harbs,
>
> I think we have enough votes. I still have to gather info how actually
> release Maven artifacts. However I'm going to push binaries today in svn.
>
> Thanks,
> Piotr
>
> sob., 28 wrz 2019 o 20:02 Harbs  napisał(a):
>
>> FYI, I will not be able to test the release until Wednesday.
>>
>> If the vote is still open, I plan on testing then.
>>
>> Thanks,
>> Harbs
>>
>> > On Sep 25, 2019, at 5:24 PM, Piotr Zarzycki 
>> wrote:
>> >
>> > Ok, new and hopefully the last one RC3. I didn't run ApproveScript
>> myself
>> > yet, but will do that tomorrow or next week.
>> >
>> > śr., 25 wrz 2019 o 16:23 Apache Royale CI Server <
>> apacheroyal...@gmail.com>
>> > napisał(a):
>> >
>> >> This is the discussion thread.
>> >>
>> >> Thanks,
>> >> Piotr
>> >
>> >
>> >
>> > --
>> >
>> > Piotr Zarzycki
>> >
>> > Patreon: *https://www.patreon.com/piotrzarzycki
>> > <https://www.patreon.com/piotrzarzycki>*
>>
>>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


-- 

Piotr Zarzycki

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


Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-10-01 Thread Piotr Zarzycki
Hi Harbs,

I think we have enough votes. I still have to gather info how actually
release Maven artifacts. However I'm going to push binaries today in svn.

Thanks,
Piotr

sob., 28 wrz 2019 o 20:02 Harbs  napisał(a):

> FYI, I will not be able to test the release until Wednesday.
>
> If the vote is still open, I plan on testing then.
>
> Thanks,
> Harbs
>
> > On Sep 25, 2019, at 5:24 PM, Piotr Zarzycki 
> wrote:
> >
> > Ok, new and hopefully the last one RC3. I didn't run ApproveScript myself
> > yet, but will do that tomorrow or next week.
> >
> > śr., 25 wrz 2019 o 16:23 Apache Royale CI Server <
> apacheroyal...@gmail.com>
> > napisał(a):
> >
> >> This is the discussion thread.
> >>
> >> Thanks,
> >> Piotr
> >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > <https://www.patreon.com/piotrzarzycki>*
>
>

-- 

Piotr Zarzycki

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


[VOTE] Release Apache Royale 0.9.6 RC3

2019-09-30 Thread Piotr Zarzycki
lso get the binary packages via NPM.  The -js package can be
> > installed via:
> >
> > npm install
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.6%2Frc3%2Fbinaries%2Fapache-royale-0.9.6-bin-js.tar.gzdata=02%7C01%7Caharui%40adobe.com%7Cb8881952698c4de9211a08d741c3e343%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637050181900826730sdata=atcvZ5SEucw7k0BJFHxbD%2BMpTnykL7HFPujYuhxaoI0%3Dreserved=0
> > -g
> >
> > The full package with SWF support can be installed via:
> >
> > npm install
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.6%2Frc3%2Fbinaries%2Fapache-royale-0.9.6-bin-js-swf.tar.gzdata=02%7C01%7Caharui%40adobe.com%7Cb8881952698c4de9211a08d741c3e343%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637050181900826730sdata=ZyPz%2FexylsWD0KIlV1cJLPdQqSu1ov%2FM0u0tirP3iBM%3Dreserved=0
> > -g
> >
> > Maven artifacts are staged here:
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapacheroyale-1058data=02%7C01%7Caharui%40adobe.com%7Cb8881952698c4de9211a08d741c3e343%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637050181900826730sdata=vZmV5F1faQGUelsQIziJOVoYRMtRqp1FaSfkoAjJjEE%3Dreserved=0
> >
> > Please vote to approve this release:
> > +1 Approve the release
> > -1 Disapprove the release (please provide specific comments to why)
> >
> > This vote will be open for 72 hours or until a result can be called.
> >
> > The vote passes if there is:
> > - At least 3 +1 votes from the PMC
> > - More positive votes than negative votes
> >
> > Remember that this is a 'beta-quality' release so expect there
> > will be many bugs found.  IMO the goal is not to try to find and fix
> > bugs
> > in the RC, but to make sure we have the packaging right, and enough
> > functionality that folks will have some success trying to use it.
> >
> > People who are not in PMC are also encouraged to test out the release
> > and
> > vote, although their votes will not be binding, they can influence
> how
> > the
> > PMC votes.
> >
> > When voting please indicate what OS, IDE, Flash Player version and
> AIR
> > version you tested with.
> >
> > For your convenience, there is an ant script that automates the
> common
> > steps to validate a release.  Instead of individually downloading the
> > package and signature files, unzipping, etc, you can instead:
> > 1) create an empty folder,
> > 2) download into that folder this file:
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.6%2Frc3%2FApproveRoyale.xmldata=02%7C01%7Caharui%40adobe.com%7Cb8881952698c4de9211a08d741c3e343%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637050181900826730sdata=mYm%2BktB70vGktO0tSGi4caVWKkswNHtR8wuCil3p5HI%3Dreserved=0
> > 3) run the script:
> >ant -e -f ApproveRoyale.xml -Drelease.version=0.9.6 -Drc=3
> >If you want to test SWF support during the approval, use:
> >ant -e -f ApproveRoyale.xml -Drelease.version=0.9.6 -Drc=3
> > -Duse-flash=true
> >
> > You are not required to use this script, and more testing of the
> > packages and build results are always encouraged.
> >
> > Please put all discussion about this release in the DISCUSSION thread
> > not this VOTE thread.
> >
> > Thanks,
> > Piotr
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 

Piotr Zarzycki

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


[DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-09-25 Thread Piotr Zarzycki
Carlos,

I can only propose copy player global in appropriate place and try again. I
have no idea how to resolve your problem.

Thanks,
Piotr


On Wed, Sep 25, 2019, 10:37 PM Carlos Rovira 
wrote:

> Hi, yes, I copied in the RC2 thread what was appearing
>
> btw, I tried again adding the proposed commands with no luck. The fail is
> the same as before:
>
> Downloading from central:
>
> https://repo.maven.apache.org/maven2/com/adobe/flash/framework/playerglobal/20.0/playerglobal-20.0.swc
>
> [INFO]
> 
>
> [INFO] Reactor Summary for Apache Royale: Compiler: Parent 0.9.6:
>
> [INFO]
>
> [INFO] Apache Royale: Compiler: Parent  FAILURE [
> 0.953 s]
>
> [INFO] Apache Royale: Compiler: Compiler-Common ... SKIPPED
>
> [INFO] Apache Royale: Compiler: Test Utils  SKIPPED
>
> [INFO] Apache Royale: Compiler: Externc ... SKIPPED
>
> [INFO] Apache Royale: Compiler: Compiler .. SKIPPED
>
> [INFO] Apache Royale: Compiler: Compiler-JX ... SKIPPED
>
> [INFO] Apache Royale: Compiler: SWFUtils .. SKIPPED
>
> [INFO] Apache Royale: Compiler: Debugger .. SKIPPED
>
> [INFO] Apache Royale: Compiler: OEM Layer . SKIPPED
>
> [INFO] Apache Royale: Royale Ant Tasks  SKIPPED
>
> [INFO] Apache Royale: RoyaleUnit Ant Tasks  SKIPPED
>
> [INFO] Apache Royale: Royale Maven Plugin . SKIPPED
>
> [INFO]
> 
>
> [INFO] BUILD FAILURE
>
> [INFO]
> 
>
> [INFO] Total time:  8.704 s
>
> [INFO] Finished at: 2019-09-25T21:00:22+02:00
>
> [INFO]
> 
>
> [ERROR] Failed to execute goal on project royale-compiler-parent: Could not
> resolve dependencies for project
> org.apache.royale.compiler:royale-compiler-parent:pom:0.9.6: Could not find
> artifact com.adobe.flash.framework:playerglobal:swc:20.0 in apache-release
> (
> https://repository.apache.org/content/repositories/releases) -> [Help 1]
>
> [ERROR]
>
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
>
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>
> [ERROR]
>
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
>
> [ERROR] [Help 1]
>
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
>
>
> BUILD FAILED
>
> /Users/carlosrovira/Downloads/testrc3/ApproveRoyale.xml:778: The following
> error occurred while executing this line:
>
> /Users/carlosrovira/Downloads/testrc3/ApproveRoyale.xml:801: exec returned:
> 1
>
>
> Total time: 28 minutes 57 seconds
>
>
>
>
>
> El mié., 25 sept. 2019 a las 21:27, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > By endless loop you mean that script cannot download playerglobal -
> Asking
> > for the license?
> >
> > On Wed, Sep 25, 2019, 8:25 PM Carlos Rovira 
> > wrote:
> >
> > > Hi
> > > I tried in the meanwhile with your settings and enter in the endless
> loop
> > > as in RC2
> > >
> > > I'll try to run now adding that to the command and report back
> > >
> > >
> > > El mié., 25 sept. 2019 a las 18:59, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>) escribió:
> > >
> > > > The same issue as it was previously. You are missing playerglobal - I
> > > don't
> > > > know why at all. You can try to switch to my settings - don't forget
> > > update
> > > > link to maven artifacts in it.
> > > >
> > > > I'm not sure also but maybe you should try to run approve script with
> > > this
> > > > one: -Dgenerate.swf.swcs=true and -DskipTests=true.
> > > >
> > > > śr., 25 wrz 2019 o 18:41 Carlos Rovira 
> > > > napisał(a):
> > > >
> > > > > Hi,
> > > > >
> > > > > sorry to report that my try failed. I tried with clean .m2 and my
> own
> > > > > settings.xml. Maybe I need to switch to the settings Piotr send to
> > me?
> > > > >
> > > > > as well I used the instruction provided in email: ant -e -f
> > > > > ApproveRoyale.xml -Drelease.version=0.9.6 -Drc

[DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-09-25 Thread Piotr Zarzycki
By endless loop you mean that script cannot download playerglobal - Asking
for the license?

On Wed, Sep 25, 2019, 8:25 PM Carlos Rovira  wrote:

> Hi
> I tried in the meanwhile with your settings and enter in the endless loop
> as in RC2
>
> I'll try to run now adding that to the command and report back
>
>
> El mié., 25 sept. 2019 a las 18:59, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > The same issue as it was previously. You are missing playerglobal - I
> don't
> > know why at all. You can try to switch to my settings - don't forget
> update
> > link to maven artifacts in it.
> >
> > I'm not sure also but maybe you should try to run approve script with
> this
> > one: -Dgenerate.swf.swcs=true and -DskipTests=true.
> >
> > śr., 25 wrz 2019 o 18:41 Carlos Rovira 
> > napisał(a):
> >
> > > Hi,
> > >
> > > sorry to report that my try failed. I tried with clean .m2 and my own
> > > settings.xml. Maybe I need to switch to the settings Piotr send to me?
> > >
> > > as well I used the instruction provided in email: ant -e -f
> > > ApproveRoyale.xml -Drelease.version=0.9.6 -Drc=3
> > >
> > >
> > > ache.org/maven2/org/antlr/antlr/3.4/antlr-3.4.jar (1.1 MB at 2.7
> > > MB/s)[INFO]
> > >
> 
> > >
> > > [INFO] Reactor Build Order:
> > >
> > > [INFO]
> > >
> > > [INFO] Apache Royale: Compiler: Parent
> > > [pom]
> > >
> > > [INFO] Apache Royale: Compiler: Compiler-Common
> > > [jar]
> > >
> > > [INFO] Apache Royale: Compiler: Test Utils
> > > [jar]
> > >
> > > [INFO] Apache Royale: Compiler: Externc
> > > [jar]
> > >
> > > [INFO] Apache Royale: Compiler: Compiler
> > > [jar]
> > >
> > > [INFO] Apache Royale: Compiler: Compiler-JX
> > > [jar]
> > >
> > > [INFO] Apache Royale: Compiler: SWFUtils
> > > [jar]
> > >
> > > [INFO] Apache Royale: Compiler: Debugger
> > > [jar]
> > >
> > > [INFO] Apache Royale: Compiler: OEM Layer
> > > [jar]
> > >
> > > [INFO] Apache Royale: Royale Ant Tasks
> > > [jar]
> > >
> > > [INFO] Apache Royale: RoyaleUnit Ant Tasks
> > > [jar]
> > >
> > > [INFO] Apache Royale: Royale Maven Plugin
> > > [maven-plugin]
> > >
> > > [INFO]
> > >
> > > [INFO] -< org.apache.royale.compiler:royale-compiler-parent
> > > >--
> > >
> > > [INFO] Building Apache Royale: Compiler: Parent 0.9.6
> > > [1/12]
> > >
> > > [INFO] [ pom
> > > ]-
> > >
> > > Downloading from apache-release:
> > >
> > >
> >
> https://repository.apache.org/content/repositories/releases/com/adobe/flash/framework/playerglobal/20.0/playerglobal-20.0.pom
> > >
> > > Downloading from central:
> > >
> > >
> >
> https://repo.maven.apache.org/maven2/com/adobe/flash/framework/playerglobal/20.0/playerglobal-20.0.pom
> > >
> > > [WARNING] The POM for com.adobe.flash.framework:playerglobal:swc:20.0
> is
> > > missing, no dependency information available
> > >
> > > Downloading from apache-release:
> > >
> > >
> >
> https://repository.apache.org/content/repositories/releases/com/adobe/flash/framework/playerglobal/20.0/playerglobal-20.0.swc
> > >
> > > Downloading from central:
> > >
> > >
> >
> https://repo.maven.apache.org/maven2/com/adobe/flash/framework/playerglobal/20.0/playerglobal-20.0.swc
> > >
> > > [INFO]
> > >
> 
> > >
> > > [INFO] Reactor Summary for Apache Royale: Compiler: Parent 0.9.6:
> > >
> > > [INFO]
> > >
> > > [INFO] Apache Royale: Compiler: Parent  FAILURE [
> > > 0.982 s]
> > >
> > > [INFO] Apache Royale: Compiler: Compiler-Common ... SKIPPED
> > >
> > > [INFO] Apache Royale: Compiler: Test Utils  SKIPPED
> > >
> > > [INFO] Apache Royale: Compiler: Externc ... SKIPPED
> > >
> > > [INFO] Apache Royale: Compiler: Compiler .. SKIPPED
> > >
> > > [INFO] Apa

Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-09-25 Thread Piotr Zarzycki
The same issue as it was previously. You are missing playerglobal - I don't
know why at all. You can try to switch to my settings - don't forget update
link to maven artifacts in it.

I'm not sure also but maybe you should try to run approve script with this
one: -Dgenerate.swf.swcs=true and -DskipTests=true.

śr., 25 wrz 2019 o 18:41 Carlos Rovira  napisał(a):

> Hi,
>
> sorry to report that my try failed. I tried with clean .m2 and my own
> settings.xml. Maybe I need to switch to the settings Piotr send to me?
>
> as well I used the instruction provided in email: ant -e -f
> ApproveRoyale.xml -Drelease.version=0.9.6 -Drc=3
>
>
> ache.org/maven2/org/antlr/antlr/3.4/antlr-3.4.jar (1.1 MB at 2.7
> MB/s)[INFO]
> 
>
> [INFO] Reactor Build Order:
>
> [INFO]
>
> [INFO] Apache Royale: Compiler: Parent
> [pom]
>
> [INFO] Apache Royale: Compiler: Compiler-Common
> [jar]
>
> [INFO] Apache Royale: Compiler: Test Utils
> [jar]
>
> [INFO] Apache Royale: Compiler: Externc
> [jar]
>
> [INFO] Apache Royale: Compiler: Compiler
> [jar]
>
> [INFO] Apache Royale: Compiler: Compiler-JX
> [jar]
>
> [INFO] Apache Royale: Compiler: SWFUtils
> [jar]
>
> [INFO] Apache Royale: Compiler: Debugger
> [jar]
>
> [INFO] Apache Royale: Compiler: OEM Layer
> [jar]
>
> [INFO] Apache Royale: Royale Ant Tasks
> [jar]
>
> [INFO] Apache Royale: RoyaleUnit Ant Tasks
> [jar]
>
> [INFO] Apache Royale: Royale Maven Plugin
> [maven-plugin]
>
> [INFO]
>
> [INFO] -< org.apache.royale.compiler:royale-compiler-parent
> >--
>
> [INFO] Building Apache Royale: Compiler: Parent 0.9.6
> [1/12]
>
> [INFO] [ pom
> ]-
>
> Downloading from apache-release:
>
> https://repository.apache.org/content/repositories/releases/com/adobe/flash/framework/playerglobal/20.0/playerglobal-20.0.pom
>
> Downloading from central:
>
> https://repo.maven.apache.org/maven2/com/adobe/flash/framework/playerglobal/20.0/playerglobal-20.0.pom
>
> [WARNING] The POM for com.adobe.flash.framework:playerglobal:swc:20.0 is
> missing, no dependency information available
>
> Downloading from apache-release:
>
> https://repository.apache.org/content/repositories/releases/com/adobe/flash/framework/playerglobal/20.0/playerglobal-20.0.swc
>
> Downloading from central:
>
> https://repo.maven.apache.org/maven2/com/adobe/flash/framework/playerglobal/20.0/playerglobal-20.0.swc
>
> [INFO]
> 
>
> [INFO] Reactor Summary for Apache Royale: Compiler: Parent 0.9.6:
>
> [INFO]
>
> [INFO] Apache Royale: Compiler: Parent  FAILURE [
> 0.982 s]
>
> [INFO] Apache Royale: Compiler: Compiler-Common ... SKIPPED
>
> [INFO] Apache Royale: Compiler: Test Utils  SKIPPED
>
> [INFO] Apache Royale: Compiler: Externc ... SKIPPED
>
> [INFO] Apache Royale: Compiler: Compiler .. SKIPPED
>
> [INFO] Apache Royale: Compiler: Compiler-JX ... SKIPPED
>
> [INFO] Apache Royale: Compiler: SWFUtils .. SKIPPED
>
> [INFO] Apache Royale: Compiler: Debugger .. SKIPPED
>
> [INFO] Apache Royale: Compiler: OEM Layer . SKIPPED
>
> [INFO] Apache Royale: Royale Ant Tasks  SKIPPED
>
> [INFO] Apache Royale: RoyaleUnit Ant Tasks  SKIPPED
>
> [INFO] Apache Royale: Royale Maven Plugin . SKIPPED
>
> [INFO]
> 
>
> [INFO] BUILD FAILURE
>
> [INFO]
> 
>
> [INFO] Total time:  8.438 s
>
> [INFO] Finished at: 2019-09-25T18:35:49+02:00
>
> [INFO]
> 
>
> [ERROR] Failed to execute goal on project royale-compiler-parent: Could not
> resolve dependencies for project
> org.apache.royale.compiler:royale-compiler-parent:pom:0.9.6: Could not find
> artifact com.adobe.flash.framework:playerglobal:swc:20.0 in apache-release
> (
> https://repository.apache.org/content/repositories/releases) -> [Help 1]
>
> [ERROR]
>
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
>
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>
> [ERROR]
>
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
>
> 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-09-25 Thread Piotr Zarzycki
I'm not sure how it happened this time, but yeah we finally have. ;)

śr., 25 wrz 2019 o 17:54 Carlos Rovira  napisał(a):

> Hi Piotr,
> great to see we have different threads in gmail :)
>
> El mié., 25 sept. 2019 a las 16:24, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > Ok, new and hopefully the last one RC3. I didn't run ApproveScript myself
> > yet, but will do that tomorrow or next week.
> >
> > śr., 25 wrz 2019 o 16:23 Apache Royale CI Server <
> apacheroyal...@gmail.com
> > >
> > napisał(a):
> >
> > > This is the discussion thread.
> > >
> > > Thanks,
> > > Piotr
> >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > <https://www.patreon.com/piotrzarzycki>*
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 

Piotr Zarzycki

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


Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-09-25 Thread Piotr Zarzycki
Ok, new and hopefully the last one RC3. I didn't run ApproveScript myself
yet, but will do that tomorrow or next week.

śr., 25 wrz 2019 o 16:23 Apache Royale CI Server 
napisał(a):

> This is the discussion thread.
>
> Thanks,
> Piotr



-- 

Piotr Zarzycki

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


Re: Royale_Release_Step_011 - Build # 22 - Still Failing!

2019-09-24 Thread Piotr Zarzycki
It looks like this step is running build with that, but it still failing.
Locally adding  generate.swf.swcs=true helps me pass by problems.

C:\apache\apache-maven-3.6.0\bin\mvn.cmd --batch-mode release:perform
-DpushChanges=false -Dusername=piotrzarzycki21
-Darguments=-DaltReleaseDeploymentRepository=release-repo::default::file:./release-dir
-P "generate-swcs-for-swf,release-swcs,main" -Dgenerate.swf.swcs=true
&& exit %%ERRORLEVEL%%


śr., 25 wrz 2019 o 07:32 Apache Royale CI Server 
napisał(a):

> Royale_Release_Step_011 - Build # 22 - Still Failing:
>
> Check console output at
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_011/22/
> to view the results.



-- 

Piotr Zarzycki

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


Re: Royale_Release_Step_011 - Build # 21 - Failure!

2019-09-24 Thread Piotr Zarzycki
Ok I got it! I need to add param:  -Dgenerate.swf.swcs=true

śr., 25 wrz 2019 o 07:22 Piotr Zarzycki 
napisał(a):

> Anyone know why Binding module completely doesn't see Core ? I did build
> even locally and have same issue :(
>
> śr., 25 wrz 2019 o 06:43 Apache Royale CI Server 
> napisał(a):
>
>> Royale_Release_Step_011 - Build # 21 - Failure:
>>
>> Check console output at
>> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_011/21/
>> to view the results.
>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


-- 

Piotr Zarzycki

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


Re: Royale_Release_Step_011 - Build # 21 - Failure!

2019-09-24 Thread Piotr Zarzycki
Anyone know why Binding module completely doesn't see Core ? I did build
even locally and have same issue :(

śr., 25 wrz 2019 o 06:43 Apache Royale CI Server 
napisał(a):

> Royale_Release_Step_011 - Build # 21 - Failure:
>
> Check console output at
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_011/21/
> to view the results.



-- 

Piotr Zarzycki

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


Re: Royale_Release_Step_010 - Build # 23 - Failure!

2019-09-24 Thread Piotr Zarzycki
This step is failing. Anyone understand what is going on ?

wt., 24 wrz 2019 o 16:27 Apache Royale CI Server 
napisał(a):

> Royale_Release_Step_010 - Build # 23 - Failure:
>
> Check console output at
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_010/23/
> to view the results.



-- 

Piotr Zarzycki

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


Re: Jenkins down

2019-09-24 Thread Piotr Zarzycki
I got it working! In jenkins folder jenkins.xml file has -Xrs -Xmx256m - I
increased value to -Xrs -Xmx1024m.

wt., 24 wrz 2019 o 12:38 Piotr Zarzycki 
napisał(a):

> Hi Carlos,
>
> I just took a risk and restart PC. It didn't help and Jenkins is still
> down :(
>
> wt., 24 wrz 2019 o 10:44 Carlos Rovira 
> napisał(a):
>
>> Hi Piotr,
>>
>> don't know too much about that machine (almost I never touched it). But I
>> think a restart should not be a problem. I understand that processes in
>> use
>> are Maven, ANT, and things like that that should be present on restart.
>> Also, don't know if we have some document for restart process somewhere,
>> but if doesn't exit, I assume there should be no much problem. Also
>> restoring machines is something needed sometimes...
>>
>> El mar., 24 sept. 2019 a las 10:35, Piotr Zarzycki (<
>> piotrzarzyck...@gmail.com>) escribió:
>>
>> > Hi Guys,
>> >
>> > It looks like I broke something on our remote machine. Machine was
>> pretty
>> > slow today, so I have tried restart Jenkins and close some java
>> processes.
>> > It helped, but I cannot currently run jenkins at all. Maybe restarting
>> > machine could help, but I'm not sure what would be repercussions after
>> > that.
>> >
>> > Anyone know ?
>> >
>> > I'm sorry for troubles.
>> >
>> > Thanks,
>> > --
>> >
>> > Piotr Zarzycki
>> >
>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


-- 

Piotr Zarzycki

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


Re: Jenkins down

2019-09-24 Thread Piotr Zarzycki
Hi Carlos,

I just took a risk and restart PC. It didn't help and Jenkins is still down
:(

wt., 24 wrz 2019 o 10:44 Carlos Rovira  napisał(a):

> Hi Piotr,
>
> don't know too much about that machine (almost I never touched it). But I
> think a restart should not be a problem. I understand that processes in use
> are Maven, ANT, and things like that that should be present on restart.
> Also, don't know if we have some document for restart process somewhere,
> but if doesn't exit, I assume there should be no much problem. Also
> restoring machines is something needed sometimes...
>
> El mar., 24 sept. 2019 a las 10:35, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > Hi Guys,
> >
> > It looks like I broke something on our remote machine. Machine was pretty
> > slow today, so I have tried restart Jenkins and close some java
> processes.
> > It helped, but I cannot currently run jenkins at all. Maybe restarting
> > machine could help, but I'm not sure what would be repercussions after
> > that.
> >
> > Anyone know ?
> >
> > I'm sorry for troubles.
> >
> > Thanks,
> > --
> >
> > Piotr Zarzycki
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 

Piotr Zarzycki

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


Jenkins down

2019-09-24 Thread Piotr Zarzycki
Hi Guys,

It looks like I broke something on our remote machine. Machine was pretty
slow today, so I have tried restart Jenkins and close some java processes.
It helped, but I cannot currently run jenkins at all. Maybe restarting
machine could help, but I'm not sure what would be repercussions after
that.

Anyone know ?

I'm sorry for troubles.

Thanks,
-- 

Piotr Zarzycki


[CANCEL][VOTE] Release Apache Royale 0.9.6 RC2

2019-09-24 Thread Piotr Zarzycki
It turns out that build for SDK developers are equal important as binaries
for the user. I'm canceling that vote in order to prepare RC3 with fixes
related to that.

czw., 19 wrz 2019 o 10:08 Apache Royale CI Server 
napisał(a):

> Hi,
>
> This is the vote for the 0.9.6 release of Apache Royale.
>
> The release candidate can be found here;
> https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc2/
>
> Before voting please review the section,'What are the ASF requirements on
> approving a release?', at:
> http://www.apache.org/dev/release.html#approving-a-release
>
> At a minimum you would be expected to check that:
> - SHA and signed packages are correct
> - README, RELEASE_NOTES, NOTICE and LICENSE files are all fine
> - That the build script completes successfully
> - That you can compile and cross-compile a simple example using the SDK.
>
> The KEYS file is at https://dist.apache.org/repos/dist/release/royale/KEYS
>
> The source package is a combination of the 3 main Royale repos.
>
> To use the binary package, unzip it into a folder.  The -js package is
> ready-to-use in an IDE or command-line.  If you need SWF output, use the
> -js-swf package and use Apache Ant to run the InstallAdobeSDKs script via:
>   ant -f InstallAdobeSDKs.xml
>
> You may also get the binary packages via NPM.  The -js package can be
> installed via:
>
> npm install
> https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc2/binaries/apache-royale-0.9.6-bin-js.tar.gz
> -g
>
> The full package with SWF support can be installed via:
>
> npm install
> https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc2/binaries/apache-royale-0.9.6-bin-js-swf.tar.gz
> -g
>
> Maven artifacts are staged here:
> https://repository.apache.org/content/repositories/orgapacheroyale-1057
>
> Please vote to approve this release:
> +1 Approve the release
> -1 Disapprove the release (please provide specific comments to why)
>
> This vote will be open for 72 hours or until a result can be called.
>
> The vote passes if there is:
> - At least 3 +1 votes from the PMC
> - More positive votes than negative votes
>
> Remember that this is a 'beta-quality' release so expect there
> will be many bugs found.  IMO the goal is not to try to find and fix bugs
> in the RC, but to make sure we have the packaging right, and enough
> functionality that folks will have some success trying to use it.
>
> People who are not in PMC are also encouraged to test out the release and
> vote, although their votes will not be binding, they can influence how the
> PMC votes.
>
> When voting please indicate what OS, IDE, Flash Player version and AIR
> version you tested with.
>
> For your convenience, there is an ant script that automates the common
> steps to validate a release.  Instead of individually downloading the
> package and signature files, unzipping, etc, you can instead:
> 1) create an empty folder,
> 2) download into that folder this file:
> https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc2/ApproveRoyale.xml
> 3) run the script:
>ant -e -f ApproveRoyale.xml -Drelease.version=0.9.6 -Drc=2
>If you want to test SWF support during the approval, use:
>ant -e -f ApproveRoyale.xml -Drelease.version=0.9.6 -Drc=2
> -Duse-flash=true
>
> You are not required to use this script, and more testing of the packages
> and build results are always encouraged.
>
> Please put all discussion about this release in the DISCUSSION thread not
> this VOTE thread.
>
> Thanks,
> Piotr



-- 

Piotr Zarzycki

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


[DISCUSS] Release Apache Royale 0.9.6 RC2

2019-09-23 Thread Piotr Zarzycki
Anyone know what should Carlos setup in that environment variable to pass
farther?

On Mon, Sep 23, 2019, 7:18 PM Carlos Rovira  wrote:

> Hi,
> process did the same endless loop.
>
> @Piotr Zarzycki  do you mean to add to may
> .bash_profile "export
> systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted= 6d2bc022" ?
>
>
>
> El lun., 23 sept. 2019 a las 18:40, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > Do you have this env. setup
> > systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted ? You need
> > to have with value I think  6d2bc022.
> >
> > pon., 23 wrz 2019 o 18:33 Carlos Rovira 
> > napisał(a):
> >
> > > Hi Piotr,
> > >
> > > For this hour my laptop was running the build again, and now the script
> > > seems to end in an endless loop repeating this in console all the time:
> > >
> > >
> > >
> >
> "Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=6d2bc022
> > > )
> > >
> > > Do you accept (Yes/No) ? Your System-Id: 6d2bc022
> > >
> > > The Adobe SDK license agreement applies to the Adobe AIR SDK. Do you
> want
> > > to install the Adobe AIR SDK? Adobe AIR SDK License:
> > > http://www.adobe.com/products/air/sdk-eula.html
> > >
> > > (In a non-interactive build such as a CI server build, alternatively to
> > > typing y or yes you can also set a system property containing your
> system
> > > which is interpreted as equivalent to accepting by typing y or yes: -"
> > >
> > > I can launch it again to see what happens...
> > >
> > >
> > >
> > >
> > > El lun., 23 sept. 2019 a las 17:16, Carlos Rovira (<
> > > carlosrov...@apache.org>)
> > > escribió:
> > >
> > > > Hi Piotr,
> > > >
> > > > sorry, ignore my latest emails. Since I forgot to switch .m2
> > > repositories.
> > > > In the real one there's no such layout
> > > > Going to rerun again.
> > > >
> > > >
> > > >
> > > >
> > > > El lun., 23 sept. 2019 a las 17:13, Piotr Zarzycki (<
> > > > piotrzarzyck...@gmail.com>) escribió:
> > > >
> > > >> Ok so what is the output of your build now ?
> > > >>
> > > >> pon., 23 wrz 2019 o 17:11 Carlos Rovira 
> > > >> napisał(a):
> > > >>
> > > >> > Hi Piotr,
> > > >> > since finally layouts are the same, I think is not worth it to do
> > the
> > > >> > sending.
> > > >> > The only difference is the file exposed in my last email
> > > >> >
> > > >> > El lun., 23 sept. 2019 a las 16:47, Piotr Zarzycki (<
> > > >> > piotrzarzyck...@gmail.com>) escribió:
> > > >> >
> > > >> > > Carlos,
> > > >> > >
> > > >> > > Mailing list won't allow post screenshot. Upload them somewhere
> > and
> > > >> post
> > > >> > > links.
> > > >> > >
> > > >> > > pon., 23 wrz 2019 o 16:27 Carlos Rovira <
> carlosrov...@apache.org>
> > > >> > > napisał(a):
> > > >> > >
> > > >> > > > Hi all,
> > > >> > > >
> > > >> > > > Piotr and I discover off list the following:
> > > >> > > >
> > > >> > > > this is what I have in my .m2
> > > >> > > > [image: Captura de pantalla 2019-09-23 a las 16.11.04.png]
> > > >> > > >
> > > >> > > >
> > > >> > > > and this the Pitro's package layout that sent me off list:
> > > >> > > >
> > > >> > > > [image: Captura de pantalla 2019-09-23 a las 16.12.19.png]
> > > >> > > >
> > > >> > > > how is possible Piotr and I get different layouts?
> > > >> > > >
> > > >> > > > I'll try to build now with his layout
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > > >> > > > El lun., 23 sept. 2019 

[Discuss] Discuss Release Apache Royale 0.9.6 RC2

2019-09-23 Thread Piotr Zarzycki
Carlos,

Well I don't see importance from user perspective to that changes at all.
It means that you are not going to vote?

Thanks,
Piotr

On Mon, Sep 23, 2019, 7:22 PM Carlos Rovira  wrote:

> Hi,
>
> I will stop for today, want to work a bit on royale-docs mobile layout that
> I have near finish, so I'll wait for Alex changes and try tomorrow. IMHO
> this stuff is important, so it's worth the waiting time of a day or two.
>
> Thanks
>
>
>
>
>
> El lun., 23 sept. 201. 9 a las 17:59, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > My point is that all those fixes are for SDK Developers, not for Users. I
> > would like to satisfy users not SDK developers, the first one are waiting
> > too long for release.
> >
> > pon., 23 wrz 2019 o 17:53 Alex Harui 
> > napisał(a):
> >
> > > Depends on your definition of small.  The .mvn/extensions.xml is
> missing
> > > from royale-compiler.  That's why it won't auto-download the Adobe
> stuff.
> > >
> > > Then almost every pom.xml needs to be changed to support js-only.
> > >
> > > -Alex
> > >
> > > On 9/23/19, 8:50 AM, "Piotr Zarzycki" 
> > wrote:
> > >
> > > Alex,
> > >
> > > Carlos is able to build framework by ANT so to me it's enough to go
> > > with
> > > release. I have pushed him to try cause I thought that with some
> > small
> > > workarounds he will be able to build that as well.
> > >
> > > Thanks,
> > > Piotr
> > >
> > > pon., 23 wrz 2019 o 17:46 Alex Harui 
> > > napisał(a):
> > >
> > > > Update:  There is definitely a problem with the source package
> that
> > > > prevents building the source with Maven from a truly clean
> machine.
> > > I have
> > > > some changes pending.  This is going to be a pretty large commit
> as
> > > if
> > > > affects a lot of files.   I'm not sure why Piotr is have Carlos
> > > continue to
> > > > try things.  That seems like duplication of effort to me.  I will
> > > hopefully
> > > > have this working by end of my day today.
> > > >
> > > > -Alex
> > > >
> > > > On 9/21/19, 4:51 PM, "Alex Harui" 
> > wrote:
> > > >
> > > > I changed the subject to try to keep the threads separated.
> > > >
> > > > Please remember that the scripts and instructions are biased
> > > towards
> > > > js-only.  If you have PLAYERGLOBAL_HOME, AIR_HOME, and
> > > FLASHPLAYER_DEBUGGER
> > > > set then you will need different profiles.
> > > >
> > > > Looks like this failure is caused by change 228f4fbd1.  There
> > > should
> > > > not be hard dependencies on Adobe stuff in order to support
> > js-only.
> > > >
> > > > In testing a fix, I found out how to reproduce Josh's first
> > > issue with
> > > > the Maven build from a clean machine (remove all adobe and royale
> > > artifacts
> > > > from local repo) for js-only.  More changes to the poms are
> > > necessary.  I
> > > > will try to figure it out.
> > > >
> > > > And so, this means that a few more folks are likely to have
> > > trouble
> > > > building from source.  Again, most folks are going to just use
> the
> > > > binaries, but I'm worried about first impressions for those who
> do
> > > use the
> > > > source.
> > > >
> > > > -Alex
> > > >
> > > > On 9/21/19, 2:32 PM, "Carlos Rovira" <
> carlosrov...@apache.org>
> > > wrote:
> > > >
> > > > HI Piotr,
> > > >
> > > > since I have work to do on docs, I prefer to try with
> some
> > > > concrete info,
> > > > or I'll end going like chicken without head :)
> > > > I can test with and without vars on my .bash_profile too.
> > > >
> > > > Even we can release 0.9.6 and left this issues for 0.9.7
> > > >
> > > > thanks
> > > >
> > > > Carlos
> > > >
> > > &

Re: [DISCUSS] Release Apache Royale 0.9.6 RC2

2019-09-23 Thread Piotr Zarzycki
Do you have this env. setup
systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted ? You need
to have with value I think  6d2bc022.

pon., 23 wrz 2019 o 18:33 Carlos Rovira 
napisał(a):

> Hi Piotr,
>
> For this hour my laptop was running the build again, and now the script
> seems to end in an endless loop repeating this in console all the time:
>
>
> "Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=6d2bc022
> )
>
> Do you accept (Yes/No) ? Your System-Id: 6d2bc022
>
> The Adobe SDK license agreement applies to the Adobe AIR SDK. Do you want
> to install the Adobe AIR SDK? Adobe AIR SDK License:
> http://www.adobe.com/products/air/sdk-eula.html
>
> (In a non-interactive build such as a CI server build, alternatively to
> typing y or yes you can also set a system property containing your system
> which is interpreted as equivalent to accepting by typing y or yes: -"
>
> I can launch it again to see what happens...
>
>
>
>
> El lun., 23 sept. 2019 a las 17:16, Carlos Rovira (<
> carlosrov...@apache.org>)
> escribió:
>
> > Hi Piotr,
> >
> > sorry, ignore my latest emails. Since I forgot to switch .m2
> repositories.
> > In the real one there's no such layout
> > Going to rerun again.
> >
> >
> >
> >
> > El lun., 23 sept. 2019 a las 17:13, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>) escribió:
> >
> >> Ok so what is the output of your build now ?
> >>
> >> pon., 23 wrz 2019 o 17:11 Carlos Rovira 
> >> napisał(a):
> >>
> >> > Hi Piotr,
> >> > since finally layouts are the same, I think is not worth it to do the
> >> > sending.
> >> > The only difference is the file exposed in my last email
> >> >
> >> > El lun., 23 sept. 2019 a las 16:47, Piotr Zarzycki (<
> >> > piotrzarzyck...@gmail.com>) escribió:
> >> >
> >> > > Carlos,
> >> > >
> >> > > Mailing list won't allow post screenshot. Upload them somewhere and
> >> post
> >> > > links.
> >> > >
> >> > > pon., 23 wrz 2019 o 16:27 Carlos Rovira 
> >> > > napisał(a):
> >> > >
> >> > > > Hi all,
> >> > > >
> >> > > > Piotr and I discover off list the following:
> >> > > >
> >> > > > this is what I have in my .m2
> >> > > > [image: Captura de pantalla 2019-09-23 a las 16.11.04.png]
> >> > > >
> >> > > >
> >> > > > and this the Pitro's package layout that sent me off list:
> >> > > >
> >> > > > [image: Captura de pantalla 2019-09-23 a las 16.12.19.png]
> >> > > >
> >> > > > how is possible Piotr and I get different layouts?
> >> > > >
> >> > > > I'll try to build now with his layout
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > > El lun., 23 sept. 2019 a las 16:04, Piotr Zarzycki (<
> >> > > > piotrzarzyck...@gmail.com>) escribió:
> >> > > >
> >> > > >> Carlos,
> >> > > >>
> >> > > >> It's not exactly the same, cause my settings eliminate one issue
> >> from
> >> > > your
> >> > > >> log. I have send you player global off list - just put it
> manually
> >> > into
> >> > > >> Maven folder and try again.
> >> > > >>
> >> > > >> Thanks,
> >> > > >> Piotr
> >> > > >>
> >> > > >> pon., 23 wrz 2019 o 13:50 Carlos Rovira  >
> >> > > >> napisał(a):
> >> > > >>
> >> > > >> > Hi,
> >> > > >> >
> >> > > >> > sorry to say that build failed. Here's the final log. Mostly
> the
> >> > same
> >> > > >> > problem with flash player as always:
> >> > > >> >
> >> > > >> > 0 MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress
> (1):
> >> > > >> 1.0/1.0
> >> > > >> > MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1):
> >> > > 1.0/1.0
> >> > > >> > MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1):
> >&

Re: [Discuss] Discuss Release Apache Royale 0.9.6 RC2

2019-09-23 Thread Piotr Zarzycki
My point is that all those fixes are for SDK Developers, not for Users. I
would like to satisfy users not SDK developers, the first one are waiting
too long for release.

pon., 23 wrz 2019 o 17:53 Alex Harui  napisał(a):

> Depends on your definition of small.  The .mvn/extensions.xml is missing
> from royale-compiler.  That's why it won't auto-download the Adobe stuff.
>
> Then almost every pom.xml needs to be changed to support js-only.
>
> -Alex
>
> On 9/23/19, 8:50 AM, "Piotr Zarzycki"  wrote:
>
> Alex,
>
> Carlos is able to build framework by ANT so to me it's enough to go
> with
> release. I have pushed him to try cause I thought that with some small
> workarounds he will be able to build that as well.
>
> Thanks,
> Piotr
>
> pon., 23 wrz 2019 o 17:46 Alex Harui 
> napisał(a):
>
> > Update:  There is definitely a problem with the source package that
> > prevents building the source with Maven from a truly clean machine.
> I have
> > some changes pending.  This is going to be a pretty large commit as
> if
> > affects a lot of files.   I'm not sure why Piotr is have Carlos
> continue to
> > try things.  That seems like duplication of effort to me.  I will
> hopefully
> > have this working by end of my day today.
> >
> > -Alex
> >
> > On 9/21/19, 4:51 PM, "Alex Harui"  wrote:
> >
> > I changed the subject to try to keep the threads separated.
> >
> > Please remember that the scripts and instructions are biased
> towards
> > js-only.  If you have PLAYERGLOBAL_HOME, AIR_HOME, and
> FLASHPLAYER_DEBUGGER
> > set then you will need different profiles.
> >
> > Looks like this failure is caused by change 228f4fbd1.  There
> should
> > not be hard dependencies on Adobe stuff in order to support js-only.
> >
> > In testing a fix, I found out how to reproduce Josh's first
> issue with
> > the Maven build from a clean machine (remove all adobe and royale
> artifacts
> > from local repo) for js-only.  More changes to the poms are
> necessary.  I
> > will try to figure it out.
> >
> > And so, this means that a few more folks are likely to have
> trouble
> > building from source.  Again, most folks are going to just use the
> > binaries, but I'm worried about first impressions for those who do
> use the
> > source.
> >
> > -Alex
> >
> > On 9/21/19, 2:32 PM, "Carlos Rovira" 
> wrote:
> >
> > HI Piotr,
> >
> > since I have work to do on docs, I prefer to try with some
> > concrete info,
>     >     or I'll end going like chicken without head :)
> > I can test with and without vars on my .bash_profile too.
> >
> > Even we can release 0.9.6 and left this issues for 0.9.7
> >
> > thanks
> >
> > Carlos
> >
> >
> >
> >
> > El sáb., 21 sept. 2019 a las 22:44, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>) escribió:
> >
> > > You have example of such file in repository. Just based on
> that
> > setup
> > > staging link repository. Currently in that file you have
> > Snapshot links and
> > > release. Based on this you can setup staging.
> > >
> > > Apart of that I have shared such file some time ago in the
> > previous
> > > releases.
> > >
> > > I'm not sure even if that is needed it's just I wanted to
> > confirm that is
> > > really not needed.
> > >
> > > Do you have player global setup env variable?
> > >
> > > If you won't figure out stuff I will share it on Monday.
> > >
> > > Thanks,
> > > Piotr
> > >
> > > On Sat, Sep 21, 2019, 8:06 PM Carlos Rovira <
> > carlosrov...@apache.org>
> > > wrote:
> > >
> > > > Hi Piort,
> > > >
> > > > can you share here the set of links to add to my
> > .m2/settings.xml?
> > > >
> > > > thanks
> >   

Re: [Discuss] Discuss Release Apache Royale 0.9.6 RC2

2019-09-23 Thread Piotr Zarzycki
Alex,

Carlos is able to build framework by ANT so to me it's enough to go with
release. I have pushed him to try cause I thought that with some small
workarounds he will be able to build that as well.

Thanks,
Piotr

pon., 23 wrz 2019 o 17:46 Alex Harui  napisał(a):

> Update:  There is definitely a problem with the source package that
> prevents building the source with Maven from a truly clean machine.  I have
> some changes pending.  This is going to be a pretty large commit as if
> affects a lot of files.   I'm not sure why Piotr is have Carlos continue to
> try things.  That seems like duplication of effort to me.  I will hopefully
> have this working by end of my day today.
>
> -Alex
>
> On 9/21/19, 4:51 PM, "Alex Harui"  wrote:
>
> I changed the subject to try to keep the threads separated.
>
> Please remember that the scripts and instructions are biased towards
> js-only.  If you have PLAYERGLOBAL_HOME, AIR_HOME, and FLASHPLAYER_DEBUGGER
> set then you will need different profiles.
>
> Looks like this failure is caused by change 228f4fbd1.  There should
> not be hard dependencies on Adobe stuff in order to support js-only.
>
> In testing a fix, I found out how to reproduce Josh's first issue with
> the Maven build from a clean machine (remove all adobe and royale artifacts
> from local repo) for js-only.  More changes to the poms are necessary.  I
> will try to figure it out.
>
> And so, this means that a few more folks are likely to have trouble
> building from source.  Again, most folks are going to just use the
> binaries, but I'm worried about first impressions for those who do use the
> source.
>
> -Alex
>
> On 9/21/19, 2:32 PM, "Carlos Rovira"  wrote:
>
> HI Piotr,
>
> since I have work to do on docs, I prefer to try with some
> concrete info,
> or I'll end going like chicken without head :)
> I can test with and without vars on my .bash_profile too.
>
> Even we can release 0.9.6 and left this issues for 0.9.7
>
> thanks
>
> Carlos
>
>
>
>
> El sáb., 21 sept. 2019 a las 22:44, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > You have example of such file in repository. Just based on that
> setup
> > staging link repository. Currently in that file you have
> Snapshot links and
> > release. Based on this you can setup staging.
> >
> > Apart of that I have shared such file some time ago in the
> previous
> > releases.
> >
> > I'm not sure even if that is needed it's just I wanted to
> confirm that is
> > really not needed.
> >
> > Do you have player global setup env variable?
> >
> > If you won't figure out stuff I will share it on Monday.
> >
> > Thanks,
> > Piotr
> >
> > On Sat, Sep 21, 2019, 8:06 PM Carlos Rovira <
> carlosrov...@apache.org>
> > wrote:
> >
> > > Hi Piort,
> > >
> > > can you share here the set of links to add to my
> .m2/settings.xml?
> > >
> > > thanks
> > >
> > >
> > >
> > >
> > > El sáb., 21 sept. 2019 a las 19:02, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>) escribió:
> > >
> > > > Switching subject to discuss.
> > > >
> > > > Carlos can you put in your settings link toavem staging
> artifacts? And
> > > run
> > > > approve script again.
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > On Sat, Sep 21, 2019, 6:49 PM Carlos Rovira <
> carlosrov...@apache.org>
> > > > wrote:
> > > >
> > > > > Curious thing is:
> > > > >
> > > > > if I run in my source tree royale-compiler folder this:
> > > > >
> > > > > mvn -s settings-template.xml -DskipTests clean install
> > > > >
> > > > >
> > > > > with clean .m2 all ends properly.
> > > > >
> > > > >
> > > > > if I run it in the downloaded RC2 folder it fails:
> > > > >
> > > > >
>

Re: [DISCUSS] Release Apache Royale 0.9.6 RC2

2019-09-23 Thread Piotr Zarzycki
Ok so what is the output of your build now ?

pon., 23 wrz 2019 o 17:11 Carlos Rovira 
napisał(a):

> Hi Piotr,
> since finally layouts are the same, I think is not worth it to do the
> sending.
> The only difference is the file exposed in my last email
>
> El lun., 23 sept. 2019 a las 16:47, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > Carlos,
> >
> > Mailing list won't allow post screenshot. Upload them somewhere and post
> > links.
> >
> > pon., 23 wrz 2019 o 16:27 Carlos Rovira 
> > napisał(a):
> >
> > > Hi all,
> > >
> > > Piotr and I discover off list the following:
> > >
> > > this is what I have in my .m2
> > > [image: Captura de pantalla 2019-09-23 a las 16.11.04.png]
> > >
> > >
> > > and this the Pitro's package layout that sent me off list:
> > >
> > > [image: Captura de pantalla 2019-09-23 a las 16.12.19.png]
> > >
> > > how is possible Piotr and I get different layouts?
> > >
> > > I'll try to build now with his layout
> > >
> > >
> > >
> > >
> > >
> > > El lun., 23 sept. 2019 a las 16:04, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>) escribió:
> > >
> > >> Carlos,
> > >>
> > >> It's not exactly the same, cause my settings eliminate one issue from
> > your
> > >> log. I have send you player global off list - just put it manually
> into
> > >> Maven folder and try again.
> > >>
> > >> Thanks,
> > >> Piotr
> > >>
> > >> pon., 23 wrz 2019 o 13:50 Carlos Rovira 
> > >> napisał(a):
> > >>
> > >> > Hi,
> > >> >
> > >> > sorry to say that build failed. Here's the final log. Mostly the
> same
> > >> > problem with flash player as always:
> > >> >
> > >> > 0 MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1):
> > >> 1.0/1.0
> > >> > MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1):
> > 1.0/1.0
> > >> > MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1):
> > 1.0/1.0
> > >> > MBProgress (1): 1.0 MBDownloaded from
> central:
> > >> >
> > >>
> >
> https://repo.maven.apache.org/maven2/de/jflex/jflex/1.6.0/jflex-1.6.0.jar
> > >> > (1.0 MB at 3.7 MB/s)[INFO]
> > >> >
> > 
> > >> >
> > >> > [INFO] Reactor Summary for Apache Royale: Compiler: Parent 0.9.6:
> > >> >
> > >> > [INFO]
> > >> >
> > >> > [INFO] Apache Royale: Compiler: Parent  SUCCESS
> [
> > >> > 6.206 s]
> > >> >
> > >> > [INFO] Apache Royale: Compiler: Compiler-Common ... SUCCESS
> > >> [01:24
> > >> > min]
> > >> >
> > >> > [INFO] Apache Royale: Compiler: Test Utils  SUCCESS
> [
> > >> > 3.174 s]
> > >> >
> > >> > [INFO] Apache Royale: Compiler: Externc ... SUCCESS
> [
> > >> > 58.423 s]
> > >> >
> > >> > [INFO] Apache Royale: Compiler: Compiler .. FAILURE
> [
> > >> > 8.802 s]
> > >> >
> > >> > [INFO] Apache Royale: Compiler: Compiler-JX ... SKIPPED
> > >> >
> > >> > [INFO] Apache Royale: Compiler: SWFUtils .. SKIPPED
> > >> >
> > >> > [INFO] Apache Royale: Compiler: Debugger .. SKIPPED
> > >> >
> > >> > [INFO] Apache Royale: Compiler: OEM Layer . SKIPPED
> > >> >
> > >> > [INFO] Apache Royale: Royale Ant Tasks  SKIPPED
> > >> >
> > >> > [INFO] Apache Royale: RoyaleUnit Ant Tasks  SKIPPED
> > >> >
> > >> > [INFO] Apache Royale: Royale Maven Plugin . SKIPPED
> > >> >
> > >> > [INFO]
> > >> >
> > 
> > >> >
> > >> > [INFO] BUILD FAILURE
> > >> >
> > >> > [INFO]
> > >> >
> > --

Re: [DISCUSS] Release Apache Royale 0.9.6 RC2

2019-09-23 Thread Piotr Zarzycki
Carlos,

Mailing list won't allow post screenshot. Upload them somewhere and post
links.

pon., 23 wrz 2019 o 16:27 Carlos Rovira 
napisał(a):

> Hi all,
>
> Piotr and I discover off list the following:
>
> this is what I have in my .m2
> [image: Captura de pantalla 2019-09-23 a las 16.11.04.png]
>
>
> and this the Pitro's package layout that sent me off list:
>
> [image: Captura de pantalla 2019-09-23 a las 16.12.19.png]
>
> how is possible Piotr and I get different layouts?
>
> I'll try to build now with his layout
>
>
>
>
>
> El lun., 23 sept. 2019 a las 16:04, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
>> Carlos,
>>
>> It's not exactly the same, cause my settings eliminate one issue from your
>> log. I have send you player global off list - just put it manually into
>> Maven folder and try again.
>>
>> Thanks,
>> Piotr
>>
>> pon., 23 wrz 2019 o 13:50 Carlos Rovira 
>> napisał(a):
>>
>> > Hi,
>> >
>> > sorry to say that build failed. Here's the final log. Mostly the same
>> > problem with flash player as always:
>> >
>> > 0 MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1):
>> 1.0/1.0
>> > MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0
>> > MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0
>> > MBProgress (1): 1.0 MBDownloaded from central:
>> >
>> https://repo.maven.apache.org/maven2/de/jflex/jflex/1.6.0/jflex-1.6.0.jar
>> > (1.0 MB at 3.7 MB/s)[INFO]
>> > 
>> >
>> > [INFO] Reactor Summary for Apache Royale: Compiler: Parent 0.9.6:
>> >
>> > [INFO]
>> >
>> > [INFO] Apache Royale: Compiler: Parent  SUCCESS [
>> > 6.206 s]
>> >
>> > [INFO] Apache Royale: Compiler: Compiler-Common ... SUCCESS
>> [01:24
>> > min]
>> >
>> > [INFO] Apache Royale: Compiler: Test Utils  SUCCESS [
>> > 3.174 s]
>> >
>> > [INFO] Apache Royale: Compiler: Externc ... SUCCESS [
>> > 58.423 s]
>> >
>> > [INFO] Apache Royale: Compiler: Compiler .. FAILURE [
>> > 8.802 s]
>> >
>> > [INFO] Apache Royale: Compiler: Compiler-JX ... SKIPPED
>> >
>> > [INFO] Apache Royale: Compiler: SWFUtils .. SKIPPED
>> >
>> > [INFO] Apache Royale: Compiler: Debugger .. SKIPPED
>> >
>> > [INFO] Apache Royale: Compiler: OEM Layer . SKIPPED
>> >
>> > [INFO] Apache Royale: Royale Ant Tasks  SKIPPED
>> >
>> > [INFO] Apache Royale: RoyaleUnit Ant Tasks  SKIPPED
>> >
>> > [INFO] Apache Royale: Royale Maven Plugin . SKIPPED
>> >
>> > [INFO]
>> > 
>> >
>> > [INFO] BUILD FAILURE
>> >
>> > [INFO]
>> > 
>> >
>> > [INFO] Total time:  02:51 min
>> >
>> > [INFO] Finished at: 2019-09-23T13:40:46+02:00
>> >
>> > [INFO]
>> > 
>> >
>> > [ERROR] Failed to execute goal on project compiler: Could not resolve
>> > dependencies for project org.apache.royale.compiler:compiler:jar:0.9.6:
>> > Could not find artifact com.adobe.flash.framework:playerglobal:swc:20.0
>> in
>> > apache-release (
>> > https://repository.apache.org/content/repositories/releases)
>> > -> [Help 1]
>> >
>> > [ERROR]
>> >
>> > [ERROR] To see the full stack trace of the errors, re-run Maven with
>> the -e
>> > switch.
>> >
>> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> >
>> > [ERROR]
>> >
>> > [ERROR] For more information about the errors and possible solutions,
>> > please read the following articles:
>> >
>> > [ERROR] [Help 1]
>> >
>> >
>> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
>> >
>> > [ERROR]
>> >
>> > [ERROR] After correcting the problems, you can resume the build with the
>> > command
>

Re: [DISCUSS] Release Apache Royale 0.9.6 RC2

2019-09-23 Thread Piotr Zarzycki
Carlos,

It's not exactly the same, cause my settings eliminate one issue from your
log. I have send you player global off list - just put it manually into
Maven folder and try again.

Thanks,
Piotr

pon., 23 wrz 2019 o 13:50 Carlos Rovira 
napisał(a):

> Hi,
>
> sorry to say that build failed. Here's the final log. Mostly the same
> problem with flash player as always:
>
> 0 MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0
> MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0
> MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0
> MBProgress (1): 1.0 MBDownloaded from central:
> https://repo.maven.apache.org/maven2/de/jflex/jflex/1.6.0/jflex-1.6.0.jar
> (1.0 MB at 3.7 MB/s)[INFO]
> 
>
> [INFO] Reactor Summary for Apache Royale: Compiler: Parent 0.9.6:
>
> [INFO]
>
> [INFO] Apache Royale: Compiler: Parent  SUCCESS [
> 6.206 s]
>
> [INFO] Apache Royale: Compiler: Compiler-Common ... SUCCESS [01:24
> min]
>
> [INFO] Apache Royale: Compiler: Test Utils  SUCCESS [
> 3.174 s]
>
> [INFO] Apache Royale: Compiler: Externc ... SUCCESS [
> 58.423 s]
>
> [INFO] Apache Royale: Compiler: Compiler .. FAILURE [
> 8.802 s]
>
> [INFO] Apache Royale: Compiler: Compiler-JX ... SKIPPED
>
> [INFO] Apache Royale: Compiler: SWFUtils .. SKIPPED
>
> [INFO] Apache Royale: Compiler: Debugger .. SKIPPED
>
> [INFO] Apache Royale: Compiler: OEM Layer . SKIPPED
>
> [INFO] Apache Royale: Royale Ant Tasks  SKIPPED
>
> [INFO] Apache Royale: RoyaleUnit Ant Tasks  SKIPPED
>
> [INFO] Apache Royale: Royale Maven Plugin . SKIPPED
>
> [INFO]
> 
>
> [INFO] BUILD FAILURE
>
> [INFO]
> 
>
> [INFO] Total time:  02:51 min
>
> [INFO] Finished at: 2019-09-23T13:40:46+02:00
>
> [INFO]
> 
>
> [ERROR] Failed to execute goal on project compiler: Could not resolve
> dependencies for project org.apache.royale.compiler:compiler:jar:0.9.6:
> Could not find artifact com.adobe.flash.framework:playerglobal:swc:20.0 in
> apache-release (
> https://repository.apache.org/content/repositories/releases)
> -> [Help 1]
>
> [ERROR]
>
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
>
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>
> [ERROR]
>
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
>
> [ERROR] [Help 1]
>
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
>
> [ERROR]
>
> [ERROR] After correcting the problems, you can resume the build with the
> command
>
> [ERROR]   mvn  -rf :compiler
>
>
> BUILD FAILED
>
> /Users/carlosrovira/Downloads/testrc2/ApproveRoyale.xml:778: The following
> error occurred while executing this line:
>
> /Users/carlosrovira/Downloads/testrc2/ApproveRoyale.xml:789: exec returned:
> 1
>
>
> Total time: 40 minutes 58 seconds
>
> macbookpro:testrc2 carlosrovira$
>
>
>
>
> El lun., 23 sept. 2019 a las 12:39, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > Hey Carlos,
> >
> > Answers inline.
> >
> > pon., 23 wrz 2019 o 12:34 Carlos Rovira 
> > napisał(a):
> >
> > > Hi Piotr,
> > >
> > > I want to try now. To try this xml with Approve xml workflow:
> > >
> > > 1.- should I put it in my .m2 folder (and remove mine)? or there's
> > another
> > > way?
> > >
> > Yes. You can also try to modify maven target and add to each exec run -s
> > "path to your settings"
> >
> >
> > > 2.- should I remove all my env vars in my .bash_profile?
> > >
> > Don't touch it.
> >
> >
> > > 3.- I assume I must run the command: "ant -e -f ApproveRoyale.xml
> > > -Drelease.version=0.9.6 -Drc=2" inside the folder I created with the
> > > Approve xml file in it.
> > >
> >
> > Yes. I'm running it with -DskipTests=true
> >
> >
> > >
> > > thanks
> > >
> > >
> > > El lun., 23 sept. 2019 a las 10:20, Piotr Zarzycki (<
&

Re: [DISCUSS] Release Apache Royale 0.9.6 RC2

2019-09-23 Thread Piotr Zarzycki
Hey Carlos,

Answers inline.

pon., 23 wrz 2019 o 12:34 Carlos Rovira 
napisał(a):

> Hi Piotr,
>
> I want to try now. To try this xml with Approve xml workflow:
>
> 1.- should I put it in my .m2 folder (and remove mine)? or there's another
> way?
>
Yes. You can also try to modify maven target and add to each exec run -s
"path to your settings"


> 2.- should I remove all my env vars in my .bash_profile?
>
Don't touch it.


> 3.- I assume I must run the command: "ant -e -f ApproveRoyale.xml
> -Drelease.version=0.9.6 -Drc=2" inside the folder I created with the
> Approve xml file in it.
>

Yes. I'm running it with -DskipTests=true


>
> thanks
>
>
> El lun., 23 sept. 2019 a las 10:20, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > Hi Carlos,
> >
> > Here you have settings.xml which I'm using. Please try this one with
> > Approve script [1]. Pay attention in it that I have put there staging
> > artifacts link, so you know what I'm talking about in the next release.
> > According to what Josh is saying this settings with staging artifacts
> > shouldn't be required, but still I would like to try that idea.
> >
> > Don't forget in approve script modify target build_maven and change exec
> > which is starting royale-asjs build to:
> >
> >  > dir="${basedir}/${maven.package.url.name}/royale-asjs"
> > failonerror="true" >
> > 
> > 
> > 
> > 
> > 
> >
> > Let me know if it helps.
> >
> > [1] https://paste.apache.org/gfift
> >
> > Thanks,
> > Piotr
> >
> > niedz., 22 wrz 2019 o 19:24 Carlos Rovira 
> > napisał(a):
> >
> > > Hi,
> > >
> > > yes, I was not able to build even using -s settings-template.xml.
> > > I tried adding it in the Approve xml workflow code and trying to build
> > > directly with maven with a clean .m2
> > > In exchange, If I try to build in my usual royale repo folder as usual
> > from
> > > clean, it works all ok
> > > As well I tried commenting/uncommenting environment vars in my
> > > .bash_profile
> > >
> > > thanks
> > >
> > >
> > >
> > >
> > > El dom., 22 sept. 2019 a las 16:10, Josh Tynjala (<
> > > joshtynj...@bowlerhat.dev>)
> > > escribió:
> > >
> > > > That was my original assumption, but it sounds like Carlos had issues
> > > > trying that.
> > > >
> > > > - Josh
> > > >
> > > > On Sunday, September 22, 2019, Piotr Zarzycki <
> > piotrzarzyck...@gmail.com
> > > >
> > > > wrote:
> > > > > Josh,
> > > > >
> > > > > Are you saying that settings-template from repository should be
> > enough
> > > to
> > > > > get stuff working for Carlos? I'm confused right now.
> > > > >
> > > > > Thanks,
> > > > > Piotr
> > > > >
> > > > > On Sun, Sep 22, 2019, 1:43 AM Josh Tynjala <
> > joshtynj...@bowlerhat.dev>
> > > > > wrote:
> > > > >
> > > > >> I'm guessing that the settings template isn't supposed to be
> > required
> > > > for
> > > > >> JS-only builds, similar to the other things discussed in this
> thread
> > > (or
> > > > >> the previous RC thread).
> > > > >>
> > > > >> I know that this file is needed to download the proprietary Adobe
> > bits
> > > > >> (since Maven doesn't know where to find them by default), and that
> > > > seemed
> > > > >> to be where your build failed.
> > > > >>
> > > > >> - Josh
> > > > >>
> > > > >> On Saturday, September 21, 2019, Carlos Rovira <
> > > carlosrov...@apache.org
> > > > >
> > > > >> wrote:
> > > > >> > Thanks Josh,
> > > > >> >
> > > > >> > I just tried with Approve xml and get similar results (I copy
> > here)
> > > > >> > I'll try using the setting, I forgot completely about it.. But
> > this
> > > > means
> > > > >> > the instructions to build are wrong right?
> > > > >> >
> > > > >> >
> > > > >> > Here's my console output after try with the Approve xml script
> > &g

Re: [DISCUSS] Release Apache Royale 0.9.6 RC2

2019-09-23 Thread Piotr Zarzycki
Hi Carlos,

Here you have settings.xml which I'm using. Please try this one with
Approve script [1]. Pay attention in it that I have put there staging
artifacts link, so you know what I'm talking about in the next release.
According to what Josh is saying this settings with staging artifacts
shouldn't be required, but still I would like to try that idea.

Don't forget in approve script modify target build_maven and change exec
which is starting royale-asjs build to:








Let me know if it helps.

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

Thanks,
Piotr

niedz., 22 wrz 2019 o 19:24 Carlos Rovira 
napisał(a):

> Hi,
>
> yes, I was not able to build even using -s settings-template.xml.
> I tried adding it in the Approve xml workflow code and trying to build
> directly with maven with a clean .m2
> In exchange, If I try to build in my usual royale repo folder as usual from
> clean, it works all ok
> As well I tried commenting/uncommenting environment vars in my
> .bash_profile
>
> thanks
>
>
>
>
> El dom., 22 sept. 2019 a las 16:10, Josh Tynjala (<
> joshtynj...@bowlerhat.dev>)
> escribió:
>
> > That was my original assumption, but it sounds like Carlos had issues
> > trying that.
> >
> > - Josh
> >
> > On Sunday, September 22, 2019, Piotr Zarzycki  >
> > wrote:
> > > Josh,
> > >
> > > Are you saying that settings-template from repository should be enough
> to
> > > get stuff working for Carlos? I'm confused right now.
> > >
> > > Thanks,
> > > Piotr
> > >
> > > On Sun, Sep 22, 2019, 1:43 AM Josh Tynjala 
> > > wrote:
> > >
> > >> I'm guessing that the settings template isn't supposed to be required
> > for
> > >> JS-only builds, similar to the other things discussed in this thread
> (or
> > >> the previous RC thread).
> > >>
> > >> I know that this file is needed to download the proprietary Adobe bits
> > >> (since Maven doesn't know where to find them by default), and that
> > seemed
> > >> to be where your build failed.
> > >>
> > >> - Josh
> > >>
> > >> On Saturday, September 21, 2019, Carlos Rovira <
> carlosrov...@apache.org
> > >
> > >> wrote:
> > >> > Thanks Josh,
> > >> >
> > >> > I just tried with Approve xml and get similar results (I copy here)
> > >> > I'll try using the setting, I forgot completely about it.. But this
> > means
> > >> > the instructions to build are wrong right?
> > >> >
> > >> >
> > >> > Here's my console output after try with the Approve xml script
> (mostly
> > >> the
> > >> > same as trying to build with maven):
> > >> >
> > >> > [INFO] --- maven-install-plugin:2.5.2:install (default-install) @
> > >> > compiler-externc ---
> > >> >
> > >> > [INFO] Installing
> > >> >
> > >>
> > >>
> >
> >
> /Users/carlosrovira/Downloads/testrc2/apache-royale-0.9.6-maven-src/royale-compiler/compiler-externc/target/compiler-externc-0.9.6.jar
> > >> > to
> > >> >
> > >>
> > >>
> >
> >
> /Users/carlosrovira/.m2/repository/org/apache/royale/compiler/compiler-externc/0.9.6/compiler-externc-0.9.6.jar
> > >> >
> > >> > [INFO] Installing
> > >> >
> > >>
> > >>
> >
> >
> /Users/carlosrovira/Downloads/testrc2/apache-royale-0.9.6-maven-src/royale-compiler/compiler-externc/pom.xml
> > >> > to
> > >> >
> > >>
> > >>
> >
> >
> /Users/carlosrovira/.m2/repository/org/apache/royale/compiler/compiler-externc/0.9.6/compiler-externc-0.9.6.pom
> > >> >
> > >> > [INFO] Installing
> > >> >
> > >>
> > >>
> >
> >
> /Users/carlosrovira/Downloads/testrc2/apache-royale-0.9.6-maven-src/royale-compiler/compiler-externc/target/compiler-externc-0.9.6-tests.jar
> > >> > to
> > >> >
> > >>
> > >>
> >
> >
> /Users/carlosrovira/.m2/repository/org/apache/royale/compiler/compiler-externc/0.9.6/compiler-externc-0.9.6-tests.jar
> > >> >
> > >> > [INFO]
> > >> >
> > >> > [INFO] < org.apache.royale.compiler:compiler
> > >> >>-
> > >> >
> > >> &

[DISCUSS] Release Apache Royale 0.9.6 RC2

2019-09-22 Thread Piotr Zarzycki
Josh,

Are you saying that settings-template from repository should be enough to
get stuff working for Carlos? I'm confused right now.

Thanks,
Piotr

On Sun, Sep 22, 2019, 1:43 AM Josh Tynjala 
wrote:

> I'm guessing that the settings template isn't supposed to be required for
> JS-only builds, similar to the other things discussed in this thread (or
> the previous RC thread).
>
> I know that this file is needed to download the proprietary Adobe bits
> (since Maven doesn't know where to find them by default), and that seemed
> to be where your build failed.
>
> - Josh
>
> On Saturday, September 21, 2019, Carlos Rovira 
> wrote:
> > Thanks Josh,
> >
> > I just tried with Approve xml and get similar results (I copy here)
> > I'll try using the setting, I forgot completely about it.. But this means
> > the instructions to build are wrong right?
> >
> >
> > Here's my console output after try with the Approve xml script (mostly
> the
> > same as trying to build with maven):
> >
> > [INFO] --- maven-install-plugin:2.5.2:install (default-install) @
> > compiler-externc ---
> >
> > [INFO] Installing
> >
>
> /Users/carlosrovira/Downloads/testrc2/apache-royale-0.9.6-maven-src/royale-compiler/compiler-externc/target/compiler-externc-0.9.6.jar
> > to
> >
>
> /Users/carlosrovira/.m2/repository/org/apache/royale/compiler/compiler-externc/0.9.6/compiler-externc-0.9.6.jar
> >
> > [INFO] Installing
> >
>
> /Users/carlosrovira/Downloads/testrc2/apache-royale-0.9.6-maven-src/royale-compiler/compiler-externc/pom.xml
> > to
> >
>
> /Users/carlosrovira/.m2/repository/org/apache/royale/compiler/compiler-externc/0.9.6/compiler-externc-0.9.6.pom
> >
> > [INFO] Installing
> >
>
> /Users/carlosrovira/Downloads/testrc2/apache-royale-0.9.6-maven-src/royale-compiler/compiler-externc/target/compiler-externc-0.9.6-tests.jar
> > to
> >
>
> /Users/carlosrovira/.m2/repository/org/apache/royale/compiler/compiler-externc/0.9.6/compiler-externc-0.9.6-tests.jar
> >
> > [INFO]
> >
> > [INFO] < org.apache.royale.compiler:compiler
> >>-
> >
> > [INFO] Building Apache Royale: Compiler: Compiler 0.9.6
> > [5/12]
> >
> > [INFO] [ jar
> > ]-
> >
> > [WARNING] The POM for com.adobe.flash.framework:playerglobal:swc:20.0 is
> > missing, no dependency information available
> >
> > [INFO]
> > 
> >
> > [INFO] Reactor Summary for Apache Royale: Compiler: Parent 0.9.6:
> >
> > [INFO]
> >
> > [INFO] Apache Royale: Compiler: Parent  SUCCESS [
> > 2.102 s]
> >
> > [INFO] Apache Royale: Compiler: Compiler-Common ... SUCCESS [
> > 4.555 s]
> >
> > [INFO] Apache Royale: Compiler: Test Utils  SUCCESS [
> > 0.431 s]
> >
> > [INFO] Apache Royale: Compiler: Externc ... SUCCESS [
> > 9.225 s]
> >
> > [INFO] Apache Royale: Compiler: Compiler .. FAILURE [
> > 0.052 s]
> >
> > [INFO] Apache Royale: Compiler: Compiler-JX ... SKIPPED
> >
> > [INFO] Apache Royale: Compiler: SWFUtils .. SKIPPED
> >
> > [INFO] Apache Royale: Compiler: Debugger .. SKIPPED
> >
> > [INFO] Apache Royale: Compiler: OEM Layer . SKIPPED
> >
> > [INFO] Apache Royale: Royale Ant Tasks  SKIPPED
> >
> > [INFO] Apache Royale: RoyaleUnit Ant Tasks  SKIPPED
> >
> > [INFO] Apache Royale: Royale Maven Plugin . SKIPPED
> >
> > [INFO]
> > 
> >
> > [INFO] BUILD FAILURE
> >
> > [INFO]
> > 
> >
> > [INFO] Total time:  16.690 s
> >
> > [INFO] Finished at: 2019-09-21T15:33:35+02:00
> >
> > [INFO]
> > 
> >
> > [ERROR] Failed to execute goal on project compiler: Could not resolve
> > dependencies for project org.apache.royale.compiler:compiler:jar:0.9.6:
> > Failure to find com.adobe.flash.framework:playerglobal:swc:20.0 in
> > https://repository.apache.org/content/repositories/releases was cached
> in
> > the local repository, resolution will not be reattempted until the update
> > interval of apache-release has elapsed or updates are forced -> [Help 1]
> >
> > [ERROR]
> >
> > [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e
> > switch.
> >
> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> >
> > [ERROR]
> >
> > [ERROR] For more information about the errors and possible solutions,
> > please read the following articles:
> >
> > [ERROR] [Help 1]
> >
>
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
> >
> > [ERROR]
> >
> > [ERROR] After correcting the problems, you can resume the build with the
> > command
> >
> > [ERROR]   mvn  -rf :compiler
> >
> >
> > BUILD FAILED
> >

[Discuss] Release Apache Royale 0.9.6 RC2

2019-09-21 Thread Piotr Zarzycki
I provided you concrete info what to do, but You expected a solution -
that's a whole different story. :)

No problem I hope we will get vote from some one else.

Thanks,
Piotr

On Sat, Sep 21, 2019, 11:32 PM Carlos Rovira 
wrote:

> HI Piotr,
>
> since I have work to do on docs, I prefer to try with some concrete info,
> or I'll end going like chicken without head :)
> I can test with and without vars on my .bash_profile too.
>
> Even we can release 0.9.6 and left this issues for 0.9.7
>
> thanks
>
> Carlos
>
>
>
>
> El sáb., 21 sept. 2019 a las 22:44, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > You have example of such file in repository. Just based on that setup
> > staging link repository. Currently in that file you have Snapshot links
> and
> > release. Based on this you can setup staging.
> >
> > Apart of that I have shared such file some time ago in the previous
> > releases.
> >
> > I'm not sure even if that is needed it's just I wanted to confirm that is
> > really not needed.
> >
> > Do you have player global setup env variable?
> >
> > If you won't figure out stuff I will share it on Monday.
> >
> > Thanks,
> > Piotr
> >
> > On Sat, Sep 21, 2019, 8:06 PM Carlos Rovira 
> > wrote:
> >
> > > Hi Piort,
> > >
> > > can you share here the set of links to add to my .m2/settings.xml?
> > >
> > > thanks
> > >
> > >
> > >
> > >
> > > El sáb., 21 sept. 2019 a las 19:02, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>) escribió:
> > >
> > > > Switching subject to discuss.
> > > >
> > > > Carlos can you put in your settings link toavem staging artifacts?
> And
> > > run
> > > > approve script again.
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > On Sat, Sep 21, 2019, 6:49 PM Carlos Rovira  >
> > > > wrote:
> > > >
> > > > > Curious thing is:
> > > > >
> > > > > if I run in my source tree royale-compiler folder this:
> > > > >
> > > > > mvn -s settings-template.xml -DskipTests clean install
> > > > >
> > > > >
> > > > > with clean .m2 all ends properly.
> > > > >
> > > > >
> > > > > if I run it in the downloaded RC2 folder it fails:
> > > > >
> > > > >
> > > > > Downloaded from central:
> > > > >
> > > > >
> > > >
> > >
> >
> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-container-default/1.0-alpha-9-stable-1/plexus-container-default-1.0-alpha-9-stable-1.jar
> > > > > (194 kB at 290 kB/s)
> > > > >
> > > > > Downloaded from central:
> > > > >
> > https://repo.maven.apache.org/maven2/org/antlr/ST4/4.0.4/ST4-4.0.4.jar
> > > > > (237
> > > > > kB at 345 kB/s)
> > > > >
> > > > > [*ERROR*] [ERROR] Some problems were encountered while processing
> the
> > > > POMs:
> > > > >
> > > > > [ERROR] Unresolveable build extension: Plugin
> > > > > net.sourceforge.jburg:jburg-maven-plugin:1.10.4 or one of its
> > > > dependencies
> > > > > could not be resolved: Could not find artifact
> > > > > org.apache.royale.compiler:compiler-jburg-types:jar:1.1.0 in
> > > > > apache-plugins-release (
> > > > > https://repository.apache.org/content/repositories/releases) @
> > > > >
> > > > > [ERROR] Unresolveable build extension: Plugin
> > > > > net.sourceforge.jburg:jburg-maven-plugin:1.10.4 or one of its
> > > > dependencies
> > > > > could not be resolved: Could not find artifact
> > > > > org.apache.royale.compiler:compiler-jburg-types:jar:1.1.0 in
> > > > > apache-plugins-release (
> > > > > https://repository.apache.org/content/repositories/releases) @
> > > > >
> > > > >  @
> > > > >
> > > > > [*ERROR*] The build could not read 2 projects -> *[Help 1]*
> > > > >
> > > > > [*ERROR*]
> > > > >
> > > > > [*ERROR*]   The project org.apache.royale.compiler:compiler:0.9.6
> > > > >
> > > > >
> > > >
> > >
> >
> (/Users/carlosrovira/D

[Discuss] Release Apache Royale 0.9.6 RC2

2019-09-21 Thread Piotr Zarzycki
You have example of such file in repository. Just based on that setup
staging link repository. Currently in that file you have Snapshot links and
release. Based on this you can setup staging.

Apart of that I have shared such file some time ago in the previous
releases.

I'm not sure even if that is needed it's just I wanted to confirm that is
really not needed.

Do you have player global setup env variable?

If you won't figure out stuff I will share it on Monday.

Thanks,
Piotr

On Sat, Sep 21, 2019, 8:06 PM Carlos Rovira  wrote:

> Hi Piort,
>
> can you share here the set of links to add to my .m2/settings.xml?
>
> thanks
>
>
>
>
> El sáb., 21 sept. 2019 a las 19:02, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > Switching subject to discuss.
> >
> > Carlos can you put in your settings link toavem staging artifacts? And
> run
> > approve script again.
> >
> > Thanks,
> > Piotr
> >
> > On Sat, Sep 21, 2019, 6:49 PM Carlos Rovira 
> > wrote:
> >
> > > Curious thing is:
> > >
> > > if I run in my source tree royale-compiler folder this:
> > >
> > > mvn -s settings-template.xml -DskipTests clean install
> > >
> > >
> > > with clean .m2 all ends properly.
> > >
> > >
> > > if I run it in the downloaded RC2 folder it fails:
> > >
> > >
> > > Downloaded from central:
> > >
> > >
> >
> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-container-default/1.0-alpha-9-stable-1/plexus-container-default-1.0-alpha-9-stable-1.jar
> > > (194 kB at 290 kB/s)
> > >
> > > Downloaded from central:
> > > https://repo.maven.apache.org/maven2/org/antlr/ST4/4.0.4/ST4-4.0.4.jar
> > > (237
> > > kB at 345 kB/s)
> > >
> > > [*ERROR*] [ERROR] Some problems were encountered while processing the
> > POMs:
> > >
> > > [ERROR] Unresolveable build extension: Plugin
> > > net.sourceforge.jburg:jburg-maven-plugin:1.10.4 or one of its
> > dependencies
> > > could not be resolved: Could not find artifact
> > > org.apache.royale.compiler:compiler-jburg-types:jar:1.1.0 in
> > > apache-plugins-release (
> > > https://repository.apache.org/content/repositories/releases) @
> > >
> > > [ERROR] Unresolveable build extension: Plugin
> > > net.sourceforge.jburg:jburg-maven-plugin:1.10.4 or one of its
> > dependencies
> > > could not be resolved: Could not find artifact
> > > org.apache.royale.compiler:compiler-jburg-types:jar:1.1.0 in
> > > apache-plugins-release (
> > > https://repository.apache.org/content/repositories/releases) @
> > >
> > >  @
> > >
> > > [*ERROR*] The build could not read 2 projects -> *[Help 1]*
> > >
> > > [*ERROR*]
> > >
> > > [*ERROR*]   The project org.apache.royale.compiler:compiler:0.9.6
> > >
> > >
> >
> (/Users/carlosrovira/Downloads/apache-royale-0.9.6-src/royale-compiler/compiler/pom.xml)
> > > has 1 error
> > >
> > > [*ERROR*] Unresolveable build extension: Plugin
> > > net.sourceforge.jburg:jburg-maven-plugin:1.10.4 or one of its
> > dependencies
> > > could not be resolved: Could not find artifact
> > > org.apache.royale.compiler:compiler-jburg-types:jar:1.1.0 in
> > > apache-plugins-release (
> > > https://repository.apache.org/content/repositories/releases) -> *[Help
> > 2]*
> > >
> > > [*ERROR*]
> > >
> > > [*ERROR*]   The project org.apache.royale.compiler:debugger:0.9.6
> > >
> > >
> >
> (/Users/carlosrovira/Downloads/apache-royale-0.9.6-src/royale-compiler/debugger/pom.xml)
> > > has 1 error
> > >
> > > [*ERROR*] Unresolveable build extension: Plugin
> > > net.sourceforge.jburg:jburg-maven-plugin:1.10.4 or one of its
> > dependencies
> > > could not be resolved: Could not find artifact
> > > org.apache.royale.compiler:compiler-jburg-types:jar:1.1.0 in
> > > apache-plugins-release (
> > > https://repository.apache.org/content/repositories/releases) -> *[Help
> > 2]*
> > >
> > > [*ERROR*]
> > >
> > > [*ERROR*] To see the full stack trace of the errors, re-run Maven with
> > the
> > > *-e* switch.
> > >
> > > [*ERROR*] Re-run Maven using the *-X* switch to enable full debug
> > logging.
> > >
> > > [*ERROR*]
> > >
> > > [*ERROR*] For more information a

[Discuss] Release Apache Royale 0.9.6 RC2

2019-09-21 Thread Piotr Zarzycki
Carlos,

Whenever you reply you need to edit subject to make sure that you
responding to the right thread. Gmail issue.

Thanks,
Piotr

On Sat, Sep 21, 2019, 5:40 PM Carlos Rovira  wrote:

> Josh,
>
> with a clean .m2, just tried in "royale-compiler" folder to run (after mvn
> clean install -P -main,utils):
>
> mvn -s settings-template.xml clean install
>
>
> And still fail trying to get flash player 20.0
>
>
> [*INFO*] Apache Royale: Compiler: Compiler .. *FAILURE* [
> 9.009 s]
>
> [*INFO*] Apache Royale: Compiler: Compiler-JX ... *SKIPPED*
>
> [*INFO*] Apache Royale: Compiler: SWFUtils .. *SKIPPED*
>
> [*INFO*] Apache Royale: Compiler: Debugger .. *SKIPPED*
>
> [*INFO*] Apache Royale: Compiler: OEM Layer . *SKIPPED*
>
> [*INFO*] Apache Royale: Royale Ant Tasks  *SKIPPED*
>
> [*INFO*] Apache Royale: RoyaleUnit Ant Tasks  *SKIPPED*
>
> [*INFO*] Apache Royale: Royale Maven Plugin . *SKIPPED*
>
> [*INFO*]
> **
>
> [*INFO*] *BUILD FAILURE*
>
> [*INFO*]
> **
>
> [*INFO*] Total time:  02:17 min
>
> [*INFO*] Finished at: 2019-09-21T17:35:48+02:00
>
> [*INFO*]
> **
>
> [*ERROR*] Failed to execute goal on project compiler: *Could not resolve
> dependencies for project org.apache.royale.compiler:compiler:jar:0.9.6:
> Could not find artifact com.adobe.flash.framework:playerglobal:swc:20.0 in
> apache-release (
> https://repository.apache.org/content/repositories/releases
> )* -> *[Help
> 1]*
>
>
>
>
>
> El sáb., 21 sept. 2019 a las 17:25, Carlos Rovira (<
> carlosrov...@apache.org>)
> escribió:
>
> > Thanks Josh,
> >
> > I just tried with Approve xml and get similar results (I copy here)
> > I'll try using the setting, I forgot completely about it.. But this means
> > the instructions to build are wrong right?
> >
> >
> > Here's my console output after try with the Approve xml script (mostly
> the
> > same as trying to build with maven):
> >
> > [INFO] --- maven-install-plugin:2.5.2:install (default-install) @
> > compiler-externc ---
> >
> > [INFO] Installing
> >
> /Users/carlosrovira/Downloads/testrc2/apache-royale-0.9.6-maven-src/royale-compiler/compiler-externc/target/compiler-externc-0.9.6.jar
> > to
> >
> /Users/carlosrovira/.m2/repository/org/apache/royale/compiler/compiler-externc/0.9.6/compiler-externc-0.9.6.jar
> >
> > [INFO] Installing
> >
> /Users/carlosrovira/Downloads/testrc2/apache-royale-0.9.6-maven-src/royale-compiler/compiler-externc/pom.xml
> > to
> >
> /Users/carlosrovira/.m2/repository/org/apache/royale/compiler/compiler-externc/0.9.6/compiler-externc-0.9.6.pom
> >
> > [INFO] Installing
> >
> /Users/carlosrovira/Downloads/testrc2/apache-royale-0.9.6-maven-src/royale-compiler/compiler-externc/target/compiler-externc-0.9.6-tests.jar
> > to
> >
> /Users/carlosrovira/.m2/repository/org/apache/royale/compiler/compiler-externc/0.9.6/compiler-externc-0.9.6-tests.jar
> >
> > [INFO]
> >
> > [INFO] < org.apache.royale.compiler:compiler
> > >-
> >
> > [INFO] Building Apache Royale: Compiler: Compiler 0.9.6
> > [5/12]
> >
> > [INFO] [ jar
> > ]-
> >
> > [WARNING] The POM for com.adobe.flash.framework:playerglobal:swc:20.0 is
> > missing, no dependency information available
> >
> > [INFO]
> > 
> >
> > [INFO] Reactor Summary for Apache Royale: Compiler: Parent 0.9.6:
> >
> > [INFO]
> >
> > [INFO] Apache Royale: Compiler: Parent  SUCCESS [
> > 2.102 s]
> >
> > [INFO] Apache Royale: Compiler: Compiler-Common ... SUCCESS [
> > 4.555 s]
> >
> > [INFO] Apache Royale: Compiler: Test Utils  SUCCESS [
> > 0.431 s]
> >
> > [INFO] Apache Royale: Compiler: Externc ... SUCCESS [
> > 9.225 s]
> >
> > [INFO] Apache Royale: Compiler: Compiler .. FAILURE [
> > 0.052 s]
> >
> > [INFO] Apache Royale: Compiler: Compiler-JX ... SKIPPED
> >
> > [INFO] Apache Royale: Compiler: SWFUtils .. SKIPPED
> >
> > [INFO] Apache Royale: Compiler: Debugger .. SKIPPED
> >
> > [INFO] Apache Royale: Compiler: OEM Layer . SKIPPED
> >
> > [INFO] Apache Royale: Royale Ant Tasks  SKIPPED
> >
> > [INFO] Apache Royale: RoyaleUnit Ant Tasks  SKIPPED
> >
> > [INFO] Apache Royale: Royale Maven Plugin . SKIPPED
> >
> > [INFO]
> > 
> >
> > [INFO] BUILD FAILURE
> >
> > [INFO]
> > 

[Discuss] Release Apache Royale 0.9.6 RC2

2019-09-21 Thread Piotr Zarzycki
Switching subject to discuss.

Carlos can you put in your settings link toavem staging artifacts? And run
approve script again.

Thanks,
Piotr

On Sat, Sep 21, 2019, 6:49 PM Carlos Rovira  wrote:

> Curious thing is:
>
> if I run in my source tree royale-compiler folder this:
>
> mvn -s settings-template.xml -DskipTests clean install
>
>
> with clean .m2 all ends properly.
>
>
> if I run it in the downloaded RC2 folder it fails:
>
>
> Downloaded from central:
>
> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-container-default/1.0-alpha-9-stable-1/plexus-container-default-1.0-alpha-9-stable-1.jar
> (194 kB at 290 kB/s)
>
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/antlr/ST4/4.0.4/ST4-4.0.4.jar
> (237
> kB at 345 kB/s)
>
> [*ERROR*] [ERROR] Some problems were encountered while processing the POMs:
>
> [ERROR] Unresolveable build extension: Plugin
> net.sourceforge.jburg:jburg-maven-plugin:1.10.4 or one of its dependencies
> could not be resolved: Could not find artifact
> org.apache.royale.compiler:compiler-jburg-types:jar:1.1.0 in
> apache-plugins-release (
> https://repository.apache.org/content/repositories/releases) @
>
> [ERROR] Unresolveable build extension: Plugin
> net.sourceforge.jburg:jburg-maven-plugin:1.10.4 or one of its dependencies
> could not be resolved: Could not find artifact
> org.apache.royale.compiler:compiler-jburg-types:jar:1.1.0 in
> apache-plugins-release (
> https://repository.apache.org/content/repositories/releases) @
>
>  @
>
> [*ERROR*] The build could not read 2 projects -> *[Help 1]*
>
> [*ERROR*]
>
> [*ERROR*]   The project org.apache.royale.compiler:compiler:0.9.6
>
> (/Users/carlosrovira/Downloads/apache-royale-0.9.6-src/royale-compiler/compiler/pom.xml)
> has 1 error
>
> [*ERROR*] Unresolveable build extension: Plugin
> net.sourceforge.jburg:jburg-maven-plugin:1.10.4 or one of its dependencies
> could not be resolved: Could not find artifact
> org.apache.royale.compiler:compiler-jburg-types:jar:1.1.0 in
> apache-plugins-release (
> https://repository.apache.org/content/repositories/releases) -> *[Help 2]*
>
> [*ERROR*]
>
> [*ERROR*]   The project org.apache.royale.compiler:debugger:0.9.6
>
> (/Users/carlosrovira/Downloads/apache-royale-0.9.6-src/royale-compiler/debugger/pom.xml)
> has 1 error
>
> [*ERROR*] Unresolveable build extension: Plugin
> net.sourceforge.jburg:jburg-maven-plugin:1.10.4 or one of its dependencies
> could not be resolved: Could not find artifact
> org.apache.royale.compiler:compiler-jburg-types:jar:1.1.0 in
> apache-plugins-release (
> https://repository.apache.org/content/repositories/releases) -> *[Help 2]*
>
> [*ERROR*]
>
> [*ERROR*] To see the full stack trace of the errors, re-run Maven with the
> *-e* switch.
>
> [*ERROR*] Re-run Maven using the *-X* switch to enable full debug logging.
>
> [*ERROR*]
>
> [*ERROR*] For more information about the errors and possible solutions,
> please read the following articles:
>
> [*ERROR*] *[Help 1]*
> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
>
> [*ERROR*] *[Help 2]*
> http://cwiki.apache.org/confluence/display/MAVEN/PluginManagerException
>
> macbookpro:royale-compiler carlosrovira$
>
>
>
> this time because I run without profiles main,utils
>
>
>
>
>
>
> El sáb., 21 sept. 2019 a las 17:40, Carlos Rovira (<
> carlosrov...@apache.org>)
> escribió:
>
> > Josh,
> >
> > with a clean .m2, just tried in "royale-compiler" folder to run (after
> mvn
> > clean install -P -main,utils):
> >
> > mvn -s settings-template.xml clean install
> >
> >
> > And still fail trying to get flash player 20.0
> >
> >
> > [*INFO*] Apache Royale: Compiler: Compiler .. *FAILURE*
> > [  9.009 s]
> >
> > [*INFO*] Apache Royale: Compiler: Compiler-JX ... *SKIPPED*
> >
> > [*INFO*] Apache Royale: Compiler: SWFUtils .. *SKIPPED*
> >
> > [*INFO*] Apache Royale: Compiler: Debugger .. *SKIPPED*
> >
> > [*INFO*] Apache Royale: Compiler: OEM Layer . *SKIPPED*
> >
> > [*INFO*] Apache Royale: Royale Ant Tasks  *SKIPPED*
> >
> > [*INFO*] Apache Royale: RoyaleUnit Ant Tasks  *SKIPPED*
> >
> > [*INFO*] Apache Royale: Royale Maven Plugin . *SKIPPED*
> >
> > [*INFO*]
> >
> **
> >
> > [*INFO*] *BUILD FAILURE*
> >
> > [*INFO*]
> >
> **
> >
> > [*INFO*] Total time:  02:17 min
> >
> > [*INFO*] Finished at: 2019-09-21T17:35:48+02:00
> >
> > [*INFO*]
> >
> **
> >
> > [*ERROR*] Failed to execute goal on project compiler: *Could not resolve
> > dependencies for project org.apache.royale.compiler:compiler:jar:0.9.6:
> > Could not find artifact com.adobe.flash.framework:playerglobal:swc:20.0
> in
> > apache-release (
> 

[DISCUSS] Release Apache Royale 0.9.6 RC2

2019-09-21 Thread Piotr Zarzycki
If I'm correct approval scripts do both. Try and report if you have any
problems. Remember about Josh's modifications.

On Sat, Sep 21, 2019, 2:41 PM Carlos Rovira  wrote:

> Hi Piotr, I'm not using the Approval script xml, I'm building with Maven as
> instructions report.
> I can use Approval script too but I think that will be another way to do
> things (and another will be ANT build too).
>
>
> El sáb., 21 sept. 2019 a las 13:48, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > Hmm...Approval script is building stuff for you by Maven. Modify it as
> Josh
> > suggested and run according to instruction in Voting thread.
> >
> > On Sat, Sep 21, 2019, 1:06 PM Carlos Rovira 
> > wrote:
> >
> > > Hi,
> > >
> > > having the time to try RC2. I'm having the following issues. In RC1 I
> > tried
> > > ANT and all went ok. Know as Piotr suggest I'm trying to build with
> Maven
> > > with a clean(empty) .m2.
> > >
> > > packaged to test in RC2 is: apache-royale-0.9.6-src.tar.gz
> > >
> > > Instructions in src are the following:
> > >
> > > Building Royale With Apache Maven
> > >
> > > =
> > >
> > >
> > > Royale requires Maven 3.3.9 or greater to be installed on your
> computer.
> > >
> > >
> > > To build Royale with Apache Maven, run Maven in the 3 folders as
> follows:
> > >
> > >
> > > royale-compiler:  mvn clean install -P -main,utils
> > >
> > > royale-compiler:  mvn clean install
> > >
> > > royale-typedefs:  mvn clean install
> > >
> > > royale-asjs:  mvn clean install
> > >
> > >
> > > When complete, you should be able to use the Maven archetypes in
> > > royale-asjs/archetypes
> > >
> > > to build Royale applications.
> > >
> > >
> > >
> > >  from downloaded src/royale-compiler folder I run first:
> > >
> > > mvn clean install -P -main,utils
> > >
> > > This was ok
> > >
> > > Then in the same compiler folder run:
> > >
> > > mvn clean install
> > >
> > > This time I get this error:
> > >
> > >
> > > [*INFO*]
> > >
> >
> **
> > >
> > > [*INFO*] *Reactor Summary for Apache Royale: Compiler: Parent 0.9.6:*
> > >
> > > [*INFO*]
> > >
> > > [*INFO*] Apache Royale: Compiler: Parent 
> *SUCCESS* [
> > > 1.763 s]
> > >
> > > [*INFO*] Apache Royale: Compiler: Compiler-Common ... *SUCCESS*
> > > [01:07 min]
> > >
> > > [*INFO*] Apache Royale: Compiler: Test Utils 
> *SUCCESS* [
> > > 2.307 s]
> > >
> > > [*INFO*] Apache Royale: Compiler: Externc ...
> *SUCCESS* [
> > > 49.839 s]
> > >
> > > [*INFO*] Apache Royale: Compiler: Compiler ..
> *FAILURE* [
> > > 8.878 s]
> > >
> > > [*INFO*] Apache Royale: Compiler: Compiler-JX ... *SKIPPED*
> > >
> > > [*INFO*] Apache Royale: Compiler: SWFUtils .. *SKIPPED*
> > >
> > > [*INFO*] Apache Royale: Compiler: Debugger .. *SKIPPED*
> > >
> > > [*INFO*] Apache Royale: Compiler: OEM Layer . *SKIPPED*
> > >
> > > [*INFO*] Apache Royale: Royale Ant Tasks  *SKIPPED*
> > >
> > > [*INFO*] Apache Royale: RoyaleUnit Ant Tasks  *SKIPPED*
> > >
> > > [*INFO*] Apache Royale: Royale Maven Plugin . *SKIPPED*
> > >
> > > [*INFO*]
> > >
> >
> **
> > >
> > > [*INFO*] *BUILD FAILURE*
> > >
> > > [*INFO*]
> > >
> >
> *----*
> > >
> > > [*INFO*] Total time:  02:18 min
> > >
> > > [*INFO*] Finished at: 2019-09-21T12:51:06+02:00
> > >
> > > [*INFO*]
> > >
> >
> **
> > >
> > > [*ERROR*] Failed to execute goal on project compiler: *Could not
> resolve
> > > dependencies for project org.apache.royale.compiler:compiler:jar:0.9.6:
> > > Co

[DISCUSS] Release Apache Royale 0.9.6 RC2

2019-09-21 Thread Piotr Zarzycki
Hmm...Approval script is building stuff for you by Maven. Modify it as Josh
suggested and run according to instruction in Voting thread.

On Sat, Sep 21, 2019, 1:06 PM Carlos Rovira  wrote:

> Hi,
>
> having the time to try RC2. I'm having the following issues. In RC1 I tried
> ANT and all went ok. Know as Piotr suggest I'm trying to build with Maven
> with a clean(empty) .m2.
>
> packaged to test in RC2 is: apache-royale-0.9.6-src.tar.gz
>
> Instructions in src are the following:
>
> Building Royale With Apache Maven
>
> =
>
>
> Royale requires Maven 3.3.9 or greater to be installed on your computer.
>
>
> To build Royale with Apache Maven, run Maven in the 3 folders as follows:
>
>
> royale-compiler:  mvn clean install -P -main,utils
>
> royale-compiler:  mvn clean install
>
> royale-typedefs:  mvn clean install
>
> royale-asjs:  mvn clean install
>
>
> When complete, you should be able to use the Maven archetypes in
> royale-asjs/archetypes
>
> to build Royale applications.
>
>
>
>  from downloaded src/royale-compiler folder I run first:
>
> mvn clean install -P -main,utils
>
> This was ok
>
> Then in the same compiler folder run:
>
> mvn clean install
>
> This time I get this error:
>
>
> [*INFO*]
> **
>
> [*INFO*] *Reactor Summary for Apache Royale: Compiler: Parent 0.9.6:*
>
> [*INFO*]
>
> [*INFO*] Apache Royale: Compiler: Parent  *SUCCESS* [
> 1.763 s]
>
> [*INFO*] Apache Royale: Compiler: Compiler-Common ... *SUCCESS*
> [01:07 min]
>
> [*INFO*] Apache Royale: Compiler: Test Utils  *SUCCESS* [
> 2.307 s]
>
> [*INFO*] Apache Royale: Compiler: Externc ... *SUCCESS* [
> 49.839 s]
>
> [*INFO*] Apache Royale: Compiler: Compiler .. *FAILURE* [
> 8.878 s]
>
> [*INFO*] Apache Royale: Compiler: Compiler-JX ... *SKIPPED*
>
> [*INFO*] Apache Royale: Compiler: SWFUtils .. *SKIPPED*
>
> [*INFO*] Apache Royale: Compiler: Debugger .. *SKIPPED*
>
> [*INFO*] Apache Royale: Compiler: OEM Layer . *SKIPPED*
>
> [*INFO*] Apache Royale: Royale Ant Tasks  *SKIPPED*
>
> [*INFO*] Apache Royale: RoyaleUnit Ant Tasks  *SKIPPED*
>
> [*INFO*] Apache Royale: Royale Maven Plugin . *SKIPPED*
>
> [*INFO*]
> **
>
> [*INFO*] *BUILD FAILURE*
>
> [*INFO*]
> **
>
> [*INFO*] Total time:  02:18 min
>
> [*INFO*] Finished at: 2019-09-21T12:51:06+02:00
>
> [*INFO*]
> **
>
> [*ERROR*] Failed to execute goal on project compiler: *Could not resolve
> dependencies for project org.apache.royale.compiler:compiler:jar:0.9.6:
> Could not find artifact com.adobe.flash.framework:playerglobal:swc:20.0 in
> apache-release (
> https://repository.apache.org/content/repositories/releases
> <https://repository.apache.org/content/repositories/releases>)* -> *[Help
> 1]*
>
> [*ERROR*]
>
> [*ERROR*] To see the full stack trace of the errors, re-run Maven with the
> *-e* switch.
>
> [*ERROR*] Re-run Maven using the *-X* switch to enable full debug logging.
>
>
>
>
>
>
> El vie., 20 sept. 2019 a las 18:24, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > Yes sure. I would like to hear from others what they think.
> >
> > Personally much worst to me is the fact that we didn't release SDK in
> > several months. I would rather spend 5 minutes on writing email to
> instruct
> > user who has problem with building SDK than spend another 4 hours on
> > preparing and testing another RC - even if someone is paying me for that.
> >
> > Let's hear from others.
> >
> > Thanks,
> > Piotr
> >
> > pt., 20 wrz 2019 o 18:18 Alex Harui 
> napisał(a):
> >
> > > I don't know.  Would be nice to get other's opinions.  We make these
> > > attempts to lower the effort to get the source and work with it, so
> when
> > > that workflow isn't working it doesn't make us look good.  FWIW, if you
> > > clone the repo and try to build without the Adobe stuff, that should
> > > probably fail the same way.
> > >
> > > -Alex
> > >
> > > On 9/19/19, 11:21 PM, "Piotr Zarzycki" 
> > wrote:
> > >

[DISCUSS] Release Apache Royale 0.9.6 RC2

2019-09-20 Thread Piotr Zarzycki
Yes sure. I would like to hear from others what they think.

Personally much worst to me is the fact that we didn't release SDK in
several months. I would rather spend 5 minutes on writing email to instruct
user who has problem with building SDK than spend another 4 hours on
preparing and testing another RC - even if someone is paying me for that.

Let's hear from others.

Thanks,
Piotr

pt., 20 wrz 2019 o 18:18 Alex Harui  napisał(a):

> I don't know.  Would be nice to get other's opinions.  We make these
> attempts to lower the effort to get the source and work with it, so when
> that workflow isn't working it doesn't make us look good.  FWIW, if you
> clone the repo and try to build without the Adobe stuff, that should
> probably fail the same way.
>
> -Alex
>
> On 9/19/19, 11:21 PM, "Piotr Zarzycki"  wrote:
>
> Hi Alex,
>
> I'm moving with topic here cause it's related. Maybe solution for not
> working build without some env. variables is just have section Known
> issues
> in our announcement?
>
> Thanks,
> Piotr
>
> pt., 20 wrz 2019 o 08:19 Piotr Zarzycki 
> napisał(a):
>
> > Hi Josh,
> >
> > Maybe you could commit that to develop?
> >
> > Thanks,
> > Piotr
> >
> > czw., 19 wrz 2019 o 18:19 Josh Tynjala 
> > napisał(a):
> >
> >> If anyone else has problems with the Maven build when running the
> >> ApproveRoyale.xml script, I was able to fix it by modifying this
> section
> >> where the framework is built:
> >>
> >>  >> dir="${basedir}/${maven.package.url.name}/royale-asjs"
> >> failonerror="true">
> >> 
> >> 
> >> 
> >> 
> >> 
> >>
> >> --
> >> Josh Tynjala
> >> Bowler Hat LLC <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7Cd794c4ef78a3433bc95e08d73d92bfc0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637045572800498366sdata=seKWdtHYwJnr10AgVph8%2BOgYgk5746cRnEBpGNnKgwM%3Dreserved=0
> >
> >>
> >>
> >> On Thu, Sep 19, 2019 at 1:08 AM Apache Royale CI Server <
> >> apacheroyal...@gmail.com> wrote:
> >>
> >> > This is the discussion thread.
> >> >
> >> > Thanks,
> >> > Piotr
> >>
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Cd794c4ef78a3433bc95e08d73d92bfc0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637045572800498366sdata=J%2BSrhIzulD7eR%2FUUruVIgxma%2FXS4%2FdvmBF4r48qhSEQ%3Dreserved=0
> > <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Cd794c4ef78a3433bc95e08d73d92bfc0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637045572800498366sdata=J%2BSrhIzulD7eR%2FUUruVIgxma%2FXS4%2FdvmBF4r48qhSEQ%3Dreserved=0
> >*
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Cd794c4ef78a3433bc95e08d73d92bfc0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637045572800498366sdata=J%2BSrhIzulD7eR%2FUUruVIgxma%2FXS4%2FdvmBF4r48qhSEQ%3Dreserved=0
> <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Cd794c4ef78a3433bc95e08d73d92bfc0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637045572800498366sdata=J%2BSrhIzulD7eR%2FUUruVIgxma%2FXS4%2FdvmBF4r48qhSEQ%3Dreserved=0
> >*
>
>
>

-- 

Piotr Zarzycki

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


[DISCUSS] Release Apache Royale 0.9.6 RC2

2019-09-20 Thread Piotr Zarzycki
Alex,

Second issue is a blocker only for someone who wanted to developing Royale
SDK, from my perspective it is not a blocker for a release.

Thanks,
Piotr

pt., 20 wrz 2019 o 18:13 Alex Harui  napisał(a):

> Specifically, requiring the profile generate-swcs-for-swf will fail when
> running ApproveRoyale.xml in a js-only configuration.
>
> My commit last night detects env.AIR_HOME and selects the set of profiles
> to use.  I saw it work for both js-only and js-swf configurations.
>
> -Alex
>
> On 9/20/19, 9:02 AM, "Piotr Zarzycki"  wrote:
>
> What won't work exactly ? Build ? Or Royale for user IDE ?
>
> pt., 20 wrz 2019 o 17:57 Alex Harui 
> napisał(a):
>
> > Please don't commit that.  It won't work for js-only.
> >
> > I pushed a solution for both last night.
> >
> > Thanks,
> > -Alex
> >
> > On 9/19/19, 11:20 PM, "Piotr Zarzycki" 
> wrote:
> >
> > Hi Josh,
> >
> > Maybe you could commit that to develop?
> >
> > Thanks,
> > Piotr
> >
> > czw., 19 wrz 2019 o 18:19 Josh Tynjala <
> joshtynj...@bowlerhat.dev>
> > napisał(a):
> >
> > > If anyone else has problems with the Maven build when running
> the
> > > ApproveRoyale.xml script, I was able to fix it by modifying
> this
> > section
> > > where the framework is built:
> > >
> > >  > > dir="${basedir}/${maven.package.url.name}/royale-asjs"
> > > failonerror="true">
> > > 
> > > 
> > > 
> > > 
> > > 
> > >
> > > --
> > > Josh Tynjala
> > > Bowler Hat LLC <
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7C8a3cf242c0024b14fe6008d73de3ebee%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637045921437938079sdata=n8xZarFdKuH32hNz2yLeDEVJnGmeQd5zExYQ2gC36Z8%3Dreserved=0
> > >
> > >
> > >
> > > On Thu, Sep 19, 2019 at 1:08 AM Apache Royale CI Server <
> > > apacheroyal...@gmail.com> wrote:
> > >
> > > > This is the discussion thread.
> > > >
> > > > Thanks,
> > > > Piotr
> > >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7C8a3cf242c0024b14fe6008d73de3ebee%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637045921437938079sdata=QeebXriRWQgKc05kJiui7YCon6Lee0vSc%2BosijEfwuU%3Dreserved=0
> > <
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7C8a3cf242c0024b14fe6008d73de3ebee%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637045921437938079sdata=QeebXriRWQgKc05kJiui7YCon6Lee0vSc%2BosijEfwuU%3Dreserved=0
> > >*
> >
> >
> >
>
> --
>
> Piotr Zarzycki
>
> Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7C8a3cf242c0024b14fe6008d73de3ebee%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637045921437938079sdata=QeebXriRWQgKc05kJiui7YCon6Lee0vSc%2BosijEfwuU%3Dreserved=0
> <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7C8a3cf242c0024b14fe6008d73de3ebee%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637045921437938079sdata=QeebXriRWQgKc05kJiui7YCon6Lee0vSc%2BosijEfwuU%3Dreserved=0
> >*
>
>
>

-- 

Piotr Zarzycki

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


[DISCUSS] Release Apache Royale 0.9.6 RC2

2019-09-20 Thread Piotr Zarzycki
What won't work exactly ? Build ? Or Royale for user IDE ?

pt., 20 wrz 2019 o 17:57 Alex Harui  napisał(a):

> Please don't commit that.  It won't work for js-only.
>
> I pushed a solution for both last night.
>
> Thanks,
> -Alex
>
> On 9/19/19, 11:20 PM, "Piotr Zarzycki"  wrote:
>
> Hi Josh,
>
> Maybe you could commit that to develop?
>
> Thanks,
> Piotr
>
> czw., 19 wrz 2019 o 18:19 Josh Tynjala 
> napisał(a):
>
> > If anyone else has problems with the Maven build when running the
> > ApproveRoyale.xml script, I was able to fix it by modifying this
> section
> > where the framework is built:
> >
> >  > dir="${basedir}/${maven.package.url.name}/royale-asjs"
> > failonerror="true">
> > 
> > 
> > 
> > 
> > 
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7Ce4ea4c5bfc0f479a8bfd08d73d92997c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637045572159032939sdata=BDj9pGPEd7LYnGt4k0uBrLS5gjGCv7CubuAD9NJN5wQ%3Dreserved=0
> >
> >
> >
> > On Thu, Sep 19, 2019 at 1:08 AM Apache Royale CI Server <
> > apacheroyal...@gmail.com> wrote:
> >
> > > This is the discussion thread.
> > >
> > > Thanks,
> > > Piotr
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Ce4ea4c5bfc0f479a8bfd08d73d92997c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637045572159032939sdata=Zw24uGCHtcSPLPDHwstsYWscS3AxqHmbhgmfIyPoRq0%3Dreserved=0
> <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Ce4ea4c5bfc0f479a8bfd08d73d92997c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637045572159032939sdata=Zw24uGCHtcSPLPDHwstsYWscS3AxqHmbhgmfIyPoRq0%3Dreserved=0
> >*
>
>
>

-- 

Piotr Zarzycki

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


[VOTE] Release Apache Royale 0.9.6 RC2

2019-09-20 Thread Piotr Zarzycki
+1 (Binding)

Package
https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc2/apache-royale-0.9.6-src.zip
Java 1.8
OS: Windows 10 amd64 10.0
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.6/rc2/binaries/apache-royale-0.9.6-bin-js-swf.zip
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

Additionally:
- I was able to build large Royale application using Maven staging
artifacts and deployed it to development server
- I was able to build and use PureMVC sources to library project using
Maven staging artifacts
- Binaries were correctly recognized by Moonshine IDE

Thanks,
Piotr

czw., 19 wrz 2019 o 10:08 Apache Royale CI Server 
napisał(a):

> Hi,
>
> This is the vote for the 0.9.6 release of Apache Royale.
>
> The release candidate can be found here;
> https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc2/
>
> Before voting please review the section,'What are the ASF requirements on
> approving a release?', at:
> http://www.apache.org/dev/release.html#approving-a-release
>
> At a minimum you would be expected to check that:
> - SHA and signed packages are correct
> - README, RELEASE_NOTES, NOTICE and LICENSE files are all fine
> - That the build script completes successfully
> - That you can compile and cross-compile a simple example using the SDK.
>
> The KEYS file is at https://dist.apache.org/repos/dist/release/royale/KEYS
>
> The source package is a combination of the 3 main Royale repos.
>
> To use the binary package, unzip it into a folder.  The -js package is
> ready-to-use in an IDE or command-line.  If you need SWF output, use the
> -js-swf package and use Apache Ant to run the InstallAdobeSDKs script via:
>   ant -f InstallAdobeSDKs.xml
>
> You may also get the binary packages via NPM.  The -js package can be
> installed via:
>
> npm install
> https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc2/binaries/apache-royale-0.9.6-bin-js.tar.gz
> -g
>
> The full package with SWF support can be installed via:
>
> npm install
> https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc2/binaries/apache-royale-0.9.6-bin-js-swf.tar.gz
> -g
>
> Maven artifacts are staged here:
> https://repository.apache.org/content/repositories/orgapacheroyale-1057
>
> Please vote to approve this release:
> +1 Approve the release
> -1 Disapprove the release (please provide specific comments to why)
>
> This vote will be open for 72 hours or until a result can be called.
>
> The vote passes if there is:
> - At least 3 +1 votes from the PMC
> - More positive votes than negative votes
>
> Remember that this is a 'beta-quality' release so expect there
> will be many bugs found.  IMO the goal is not to try to find and fix bugs
> in the RC, but to make sure we have the packaging right, and enough
> functionality that folks will have some success trying to use it.
>
> People who are not in PMC are also encouraged to test out the release and
> vote, although their votes will not be binding, they can influence how the
> PMC votes.
>
> When voting please indicate what OS, IDE, Flash Player version and AIR
> version you tested with.
>
> For your convenience, there is an ant script that automates the common
> steps to validate a release.  Instead of individually downloading the
> package and signature files, unzipping, etc, you can instead:
> 1) create an empty folder,
> 2) download into that folder this file:
> https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc2/ApproveRoyale.xml
> 3) run the script:
>ant -e -f ApproveRoyale.xml -Drelease.version=0.9.6 -Drc=2
>If you want to test SWF support during the approval, use:
>ant -e -f ApproveRoyale.xml -Drelease.version=0.9.6 -Drc=2
> -Duse-flash=true
>
> You are not required to use this script, and more testing of the packages
> and build results are always encouraged.
>
> Please put all discussion about this release in the DISCUSSION thread not
> this VOTE thread.
>
> Thanks,
> Piotr



-- 

Piotr Zarzycki

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


[DISCUSS] Release Apache Royale 0.9.6 RC2

2019-09-20 Thread Piotr Zarzycki
Hi Alex,

I'm moving with topic here cause it's related. Maybe solution for not
working build without some env. variables is just have section Known issues
in our announcement?

Thanks,
Piotr

pt., 20 wrz 2019 o 08:19 Piotr Zarzycki 
napisał(a):

> Hi Josh,
>
> Maybe you could commit that to develop?
>
> Thanks,
> Piotr
>
> czw., 19 wrz 2019 o 18:19 Josh Tynjala 
> napisał(a):
>
>> If anyone else has problems with the Maven build when running the
>> ApproveRoyale.xml script, I was able to fix it by modifying this section
>> where the framework is built:
>>
>> > dir="${basedir}/${maven.package.url.name}/royale-asjs"
>> failonerror="true">
>> 
>> 
>> 
>> 
>> 
>>
>> --
>> Josh Tynjala
>> Bowler Hat LLC <https://bowlerhat.dev>
>>
>>
>> On Thu, Sep 19, 2019 at 1:08 AM Apache Royale CI Server <
>> apacheroyal...@gmail.com> wrote:
>>
>> > This is the discussion thread.
>> >
>> > Thanks,
>> > Piotr
>>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


-- 

Piotr Zarzycki

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


[DISCUSS] Release Apache Royale 0.9.6 RC2

2019-09-20 Thread Piotr Zarzycki
Hi Josh,

Maybe you could commit that to develop?

Thanks,
Piotr

czw., 19 wrz 2019 o 18:19 Josh Tynjala 
napisał(a):

> If anyone else has problems with the Maven build when running the
> ApproveRoyale.xml script, I was able to fix it by modifying this section
> where the framework is built:
>
>  dir="${basedir}/${maven.package.url.name}/royale-asjs"
> failonerror="true">
> 
> 
> 
> 
> 
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Thu, Sep 19, 2019 at 1:08 AM Apache Royale CI Server <
> apacheroyal...@gmail.com> wrote:
>
> > This is the discussion thread.
> >
> > Thanks,
> > Piotr
>


-- 

Piotr Zarzycki

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


Re: [royale-asjs] branch release/0.9.6 updated: fix ASDoc js-only

2019-09-19 Thread Piotr Zarzycki
I'm in favor of moving forward. I would like to finally release stuff.

I can live with setting up env. Variables. I'm concern by the user
experience than mine.

Thanks,
Piotr

On Thu, Sep 19, 2019, 10:36 PM Alex Harui  wrote:

> Don't know.  Judgement call.
>
> We've done a bunch of work since 0.9.4 to allow folks to be able to
> compile without the Adobe Flash and AIR SDKs.  I've run into a couple of
> problems.  ASDoc's JSON generator was failing if you didn't have Flash
> SDK.  I mentioned it in the RC1 discuss thread.  I think because it is only
> this one example it is probably ok.
>
> What is less ok is another commit I have pending which is that the main
> SWC build fails if you don't have Flash and AIR SDKs.  In theory, none of
> you should have been able to get the build to work without environment
> variables for the Adobe stuff.  So it depends a bit on how important we
> think building from sources without the Adobe stuff is for this release.
> If you did get the build to work without the Adobe stuff, check your
> environment and post the console output.  I was fooled by having a
> PLAYERGLOBAL_HOME still set.  When I took it away, more things broke.
>
> I'm testing building with Flash/AIR now to try to make sure my js-only
> changes didn't affect js-swf.
>
> -Alex
>
> On 9/19/19, 1:19 PM, "Piotr Zarzycki"  wrote:
>
> Hi Alex,
>
> We need to have it in 0.9.6?
>
> Thanks,
> Piotr
>
> On Thu, Sep 19, 2019, 9:49 PM  wrote:
>
> > This is an automated email from the ASF dual-hosted git repository.
> >
> > aharui pushed a commit to branch release/0.9.6
> > in repository
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitbox.apache.org%2Frepos%2Fasf%2Froyale-asjs.gitdata=02%7C01%7Caharui%40adobe.com%7Ce89e6b8c27de4c9708df08d73d3ea535%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637045211631183873sdata=6RUG3ci0p%2F%2BQT3vYHOMFRqqW0QtukJPg8sydnisbSEc%3Dreserved=0
> >
> >
> > The following commit(s) were added to refs/heads/release/0.9.6 by
> this
> > push:
> >  new 55f3786  fix ASDoc js-only
> > 55f3786 is described below
> >
> > commit 55f37864c2a1b58b00eb41bad9ae2a9c121a6c6e
> > Author: Alex Harui 
> > AuthorDate: Thu Sep 19 11:19:28 2019 -0700
> >
> > fix ASDoc js-only
> > ---
> >  .../ASDoc/src/main/config/asdoc-js-config.xml  | 41
> > +-
> >  1 file changed, 40 insertions(+), 1 deletion(-)
> >
> > diff --git
> a/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml
> > b/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml
> > index a720ac6..8fd00e5 100644
> > --- a/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml
> > +++ b/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml
> > @@ -141,7 +141,7 @@
> >
> >
> >
> > -
> >
> {playerglobalHome}/{targetPlayerMajorVersion}.{targetPlayerMinorVersion}
> > +
> ${frameworks_dir}/js/libs/XMLJS.swc
> >
> >
> >  
> > @@ -537,6 +537,8 @@
> >
> >
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/ITextFieldView.as
> >
> >
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/ImageAndTextButtonView.as
> >
> >
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/CheckBoxView.as
> > +
> >
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/CloseButtonView.as
> > +
> >
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/ControlBarMeasurementBead.as
> >
> >
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/CSSButtonView.as
> >
> >
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/CSSTextButtonView.as
> >
> >
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/CSSToggleButtonView.as
> > @@ -558,6 +560,8 @@
> >
> >
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/HScrollBarTrackView.as
> >
> >
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/VRuleView.as
> >
> >
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/HRuleView.as
> > +
> >
> ${frameworks_dir}/projects/B

Re: [royale-asjs] branch release/0.9.6 updated: fix ASDoc js-only

2019-09-19 Thread Piotr Zarzycki
Hi Alex,

We need to have it in 0.9.6?

Thanks,
Piotr

On Thu, Sep 19, 2019, 9:49 PM  wrote:

> This is an automated email from the ASF dual-hosted git repository.
>
> aharui pushed a commit to branch release/0.9.6
> in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
>
>
> The following commit(s) were added to refs/heads/release/0.9.6 by this
> push:
>  new 55f3786  fix ASDoc js-only
> 55f3786 is described below
>
> commit 55f37864c2a1b58b00eb41bad9ae2a9c121a6c6e
> Author: Alex Harui 
> AuthorDate: Thu Sep 19 11:19:28 2019 -0700
>
> fix ASDoc js-only
> ---
>  .../ASDoc/src/main/config/asdoc-js-config.xml  | 41
> +-
>  1 file changed, 40 insertions(+), 1 deletion(-)
>
> diff --git a/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml
> b/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml
> index a720ac6..8fd00e5 100644
> --- a/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml
> +++ b/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml
> @@ -141,7 +141,7 @@
>
>
>
> -
>  
> {playerglobalHome}/{targetPlayerMajorVersion}.{targetPlayerMinorVersion}
> +  ${frameworks_dir}/js/libs/XMLJS.swc
>
>
>  
> @@ -537,6 +537,8 @@
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/ITextFieldView.as
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/ImageAndTextButtonView.as
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/CheckBoxView.as
> +
>  
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/CloseButtonView.as
> +
>  
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/ControlBarMeasurementBead.as
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/CSSButtonView.as
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/CSSTextButtonView.as
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/CSSToggleButtonView.as
> @@ -558,6 +560,8 @@
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/HScrollBarTrackView.as
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/VRuleView.as
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/HRuleView.as
> +
>  
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/SolidBackgroundBead.as
> +
>  
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/SolidBackgroundWithChangeListenerBead.as
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/TextInputView.as
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/TextInputWithBorderView.as
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/TextAreaView.as
> @@ -572,6 +576,41 @@
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/supportClasses/VScrollBar.as
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/supportClasses/HScrollBar.as
>
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/supportClasses/ScrollBar.as
> +
>  
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/controllers/ButtonAutoRepeatController.as
> +
>  
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/beads/controllers/DropDownListController.as
> +
>  
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/supportClasses/TextFieldItemRenderer.as
> +
>  
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/supportClasses/VScrollBar.as
> +
>  
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/supportClasses/HScrollBar.as
> +
>  
> ${frameworks_dir}/projects/Basic/src/main/royale/org/apache/royale/html/supportClasses/ScrollBar.as
> +
>  
> ${frameworks_dir}/projects/Core/src/main/royale/org/apache/royale/core/CSSShape.as
> +
>  
> ${frameworks_dir}/projects/Core/src/main/royale/org/apache/royale/core/CSSSprite.as
> +
>  
> ${frameworks_dir}/projects/Core/src/main/royale/org/apache/royale/core/IBorderModel.as
> +
>  
> ${frameworks_dir}/projects/Core/src/main/royale/org/apache/royale/core/StageProxy.as
> +
>  
> ${frameworks_dir}/projects/Core/src/main/royale/org/apache/royale/core/StyleableCSSTextField.as
> +
>  
> ${frameworks_dir}/projects/Core/src/main/royale/org/apache/royale/core/WrappedMovieClip.as
> +
>  
> ${frameworks_dir}/projects/Core/src/main/royale/org/apache/royale/core/WrappedShape.as
> +
>  
> ${frameworks_dir}/projects/Core/src/main/royale/org/apache/royale/core/WrappedSprite.as
> +
>  
> ${frameworks_dir}/projects/Core/src/main/royale/org/apache/royale/core/WrappedTextField.as
> +
>  
> ${frameworks_dir}/projects/Core/src/main/royale/org/apache/royale/core/UIButtonBase.as
> +
>  
> 

Re: [royale-asjs] branch release/0.9.6 updated: Fix releasessteps script

2019-09-19 Thread Piotr Zarzycki
The only explanation which I have is that script failed with error saying
that  releaseversion is not present. I don't have anything more to add
unfortunately.

czw., 19 wrz 2019 o 18:19 Alex Harui  napisał(a):

> IMO, any change that can't be supported by a technical explanation
> probably shouldn't be committed.  Can you explain why this change is
> necessary?
>
> -Alex
>
> On 9/19/19, 1:03 AM, "Piotr Zarzycki"  wrote:
>
> I just went trough whole the process and didn't have any kind of
> problems.
> I'm pushing RC2. If you think I should revert that I can. I don't have
> anymore console log with it.
>
> śr., 18 wrz 2019 o 16:18 Alex Harui 
> napisał(a):
>
> > Changing releaseversion to release.version should not be necessary
> and
> > might break something else.  Can you reproduce the failure?  What is
> the
> > console log?  How did it not pick up the releaseversion from
> > build.properties?
> >
> > -Alex
> >
> > On 9/17/19, 10:53 PM, "pio...@apache.org"  wrote:
> >
> > This is an automated email from the ASF dual-hosted git
> repository.
> >
> > piotrz pushed a commit to branch release/0.9.6
> > in repository
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitbox.apache.org%2Frepos%2Fasf%2Froyale-asjs.gitdata=02%7C01%7Caharui%40adobe.com%7Cd1486c9d132a491e274108d73cd7cff9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637044769931764780sdata=ETBx881FDXp%2FwR9qLHW95kJl5uNPTBGDOqsjPvoIBlI%3Dreserved=0
> >
> >
> > The following commit(s) were added to refs/heads/release/0.9.6
> by this
> > push:
> >  new 84c2e85  Fix releasessteps script
> > 84c2e85 is described below
> >
> > commit 84c2e855c5a316ad21ff3a8ac6ac0cde826eecf0
> > Author: Piotr Zarzycki 
> > AuthorDate: Wed Sep 18 07:47:03 2019 +0200
> >
> > Fix releasessteps script
> >
> > - Add RoyaleUnit to swcs list and sign target
> > - Fix property release.version
> > ---
> >  releasesteps.xml | 43
> +++
> >  1 file changed, 23 insertions(+), 20 deletions(-)
> >
> > diff --git a/releasesteps.xml b/releasesteps.xml
> > index 01d0061..5c3edf1 100644
> > --- a/releasesteps.xml
> > +++ b/releasesteps.xml
> > @@ -219,7 +219,7 @@
> >  
> >  
> > - >
> value="Basic,Binding,Charts,Collections,Core,CreateJS,DragDrop,Effects,Express,Flat,FontAwesome,Formatters,GoogleMaps,Graphics,HTML,HTML5,Icons,JQuery,Jewel,Crux,Language,MXRoyale,MaterialDesignLite,Mobile,Network,Reflection,RoyaleSite,SparkRoyale,Storage,TLF,Text,XML,BasicTheme,JewelTheme"/>
> > + >
> value="Basic,Binding,Charts,Collections,Core,CreateJS,DragDrop,Effects,Express,Flat,FontAwesome,Formatters,GoogleMaps,Graphics,HTML,HTML5,Icons,JQuery,Jewel,Crux,Language,MXRoyale,MaterialDesignLite,Mobile,Network,Reflection,RoyaleUnit,RoyaleSite,SparkRoyale,Storage,TLF,Text,XML,BasicTheme,JewelTheme"/>
> >   > message="${swcs-list}"/>
> >  
> >
> > @@ -501,6 +501,9 @@
> >  
> >  
> >  
> > +   
> > +
> > +
> >  
> >  
> >  
> > @@ -880,7 +883,7 @@
> >
> >   > depends="check-air-home,check-playerglobal-home,check-runtime-env" >
> >  
> > - >
> src="${artifactfolder}/artifacts/apache-royale-${releaseversion}-src.zip"
> > dest="${artifactfolder}/sources" >
> > + >
> src="${artifactfolder}/artifacts/apache-royale-${release.version}-src.zip"
> > dest="${artifactfolder}/sources" >
> >  
> >
> >   target="all"
> > />
> > @@ -891,21 +894,21 @@
> >   > failonerror="true" >
> >  
> >  
> > - > value="org.apache.royale.compiler-${releaseversion}-rc${rc}" />
> > + > value="org.apache.royale.compiler-

[DISCUSS] Release Apache Royale 0.9.6 RC2

2019-09-19 Thread Piotr Zarzycki
Btw. When you answering trough Gmail make sure by Editing Title to which
thread are responding in. Delete "RE", cause it probably will end up with
creating new thread.

czw., 19 wrz 2019 o 10:14 Piotr Zarzycki 
napisał(a):

> Hi Guys,
>
> RC2 ready to test. Josh provides in discuss thread how to get my keys to
> check signature.
>
> gpg --keyserver keys.gnupg.net --recv-keys D5C80F47
>
> Thanks,
> Piotr
>
>
> czw., 19 wrz 2019 o 10:08 Apache Royale CI Server <
> apacheroyal...@gmail.com> napisał(a):
>
>> This is the discussion thread.
>>
>> Thanks,
>> Piotr
>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


-- 

Piotr Zarzycki

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


[DISCUSS] Release Apache Royale 0.9.6 RC2

2019-09-19 Thread Piotr Zarzycki
Hi Guys,

RC2 ready to test. Josh provides in discuss thread how to get my keys to
check signature.

gpg --keyserver keys.gnupg.net --recv-keys D5C80F47

Thanks,
Piotr


czw., 19 wrz 2019 o 10:08 Apache Royale CI Server 
napisał(a):

> This is the discussion thread.
>
> Thanks,
> Piotr



-- 

Piotr Zarzycki

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


[CANCEL][VOTE] Release Apache Royale 0.9.6 RC1

2019-09-19 Thread Piotr Zarzycki
Cancelling the vote due to some issues.

wt., 17 wrz 2019 o 15:43 Apache Royale CI Server 
napisał(a):

> Hi,
>
> This is the vote for the 0.9.6 release of Apache Royale.
>
> The release candidate can be found here;
> https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc1/
>
> Before voting please review the section,'What are the ASF requirements on
> approving a release?', at:
> http://www.apache.org/dev/release.html#approving-a-release
>
> At a minimum you would be expected to check that:
> - SHA and signed packages are correct
> - README, RELEASE_NOTES, NOTICE and LICENSE files are all fine
> - That the build script completes successfully
> - That you can compile and cross-compile a simple example using the SDK.
>
> The KEYS file is at https://dist.apache.org/repos/dist/release/royale/KEYS
>
> The source package is a combination of the 3 main Royale repos.
>
> To use the binary package, unzip it into a folder.  The -js package is
> ready-to-use in an IDE or command-line.  If you need SWF output, use the
> -js-swf package and use Apache Ant to run the InstallAdobeSDKs script via:
>   ant -f InstallAdobeSDKs.xml
>
> You may also get the binary packages via NPM.  The -js package can be
> installed via:
>
> npm install
> https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc1/binaries/apache-royale-0.9.6-bin-js.tar.gz
> -g
>
> The full package with SWF support can be installed via:
>
> npm install
> https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc1/binaries/apache-royale-0.9.6-bin-js-swf.tar.gz
> -g
>
> Maven artifacts are staged here:
> https://repository.apache.org/content/repositories/orgapacheroyale-1056
>
> Please vote to approve this release:
> +1 Approve the release
> -1 Disapprove the release (please provide specific comments to why)
>
> This vote will be open for 72 hours or until a result can be called.
>
> The vote passes if there is:
> - At least 3 +1 votes from the PMC
> - More positive votes than negative votes
>
> Remember that this is a 'beta-quality' release so expect there
> will be many bugs found.  IMO the goal is not to try to find and fix bugs
> in the RC, but to make sure we have the packaging right, and enough
> functionality that folks will have some success trying to use it.
>
> People who are not in PMC are also encouraged to test out the release and
> vote, although their votes will not be binding, they can influence how the
> PMC votes.
>
> When voting please indicate what OS, IDE, Flash Player version and AIR
> version you tested with.
>
> For your convenience, there is an ant script that automates the common
> steps to validate a release.  Instead of individually downloading the
> package and signature files, unzipping, etc, you can instead:
> 1) create an empty folder,
> 2) download into that folder this file:
> https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc1/ApproveRoyale.xml
> 3) run the script:
>ant -e -f ApproveRoyale.xml -Drelease.version=0.9.6 -Drc=1
>If you want to test SWF support during the approval, use:
>ant -e -f ApproveRoyale.xml -Drelease.version=0.9.6 -Drc=1
> -Duse-flash=true
>
> You are not required to use this script, and more testing of the packages
> and build results are always encouraged.
>
> Please put all discussion about this release in the DISCUSSION thread not
> this VOTE thread.
>
> Thanks,
> Piotr



-- 

Piotr Zarzycki

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


Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-19 Thread Piotr Zarzycki
Thanks Josh. Unfortunately I still do not see form where Maven taking up
artifacts. When you will be testing RC2, please consider clean up maven
cache and again collect the logs.

śr., 18 wrz 2019 o 18:18 Josh Tynjala 
napisał(a):

> Maven with -X:
>
> https://paste.apache.org/ffq08
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Wed, Sep 18, 2019 at 8:44 AM Piotr Zarzycki 
> wrote:
>
> > Thanks Josh. In logs there isn't any url from which you are downloading
> > artifacts. It means probably you are using cached one. One option is to
> > remove cached artifacts and run build, the second is run build with -X.
> > It doesn't have to be full build - it's the matter of see what actually
> > maven do.
> >
> > śr., 18 wrz 2019 o 16:40 Josh Tynjala 
> > napisał(a):
> >
> > > Here's the console output from the Maven section of the build:
> > >
> > > https://paste.apache.org/cczye
> > >
> > > --
> > > Josh Tynjala
> > > Bowler Hat LLC <https://bowlerhat.dev>
> > >
> > >
> > > On Tue, Sep 17, 2019 at 10:20 PM Alex Harui 
> > > wrote:
> > >
> > > > I assume that wasn't the whole log.  I think we want to see the part
> > > where
> > > > it builds Core, we only see the last bit of Core.  Core looks like it
> > > > thought it was in js-only config and didn't build a swf swc and/or
> > > Binding
> > > > thinks it is building swf swcs and is looking for Core's swf swc.
> > > >
> > > > FWIW, I am having a bunch of other build issues related to js-only
> for
> > > Ant
> > > > for the ASDoc example.  It worked in the past because I still had
> > > > PLAYERGLOBAL_HOME set in the environment, but when I took that away a
> > > bunch
> > > > of new things cropped up.  Could be a  day or two of work.  We could
> > > still
> > > > approve the release and folks who want js-only will have to not build
> > > ASDoc.
> > > >
> > > > -Alex
> > > >
> > > > On 9/17/19, 8:59 PM, "Piotr Zarzycki" 
> > > wrote:
> > > >
> > > > Hi Josh,
> > > >
> > > > Do you have in your Maven config setup link to Maven artifacts?
> > Cause
> > > > error
> > > > is saying that it was attempt of downloading them from Snapshot.
> > > > However
> > > > Core build successfully, so I'm a bit confused.
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > On Tue, Sep 17, 2019, 11:47 PM Josh Tynjala <
> > > joshtynj...@bowlerhat.dev
> > > > >
> > > > wrote:
> > > >
> > > > > Unfortunately, I'm seeing that the Maven part of ApproveRoyale
> is
> > > > failing
> > > > > too. Here's the end of my console output:
> > > > >
> > > > >
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F83mivdata=02%7C01%7Caharui%40adobe.com%7C5418ae5d4cb94b454ab208d73beca2c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637043759850631985sdata=j%2FYDlKQ7Tx54p2PJfg2tEoGg2I5Mi19BMB5fFcZcKy4%3Dreserved=0
> > > > >
> > > > > --
> > > > > Josh Tynjala
> > > > > Bowler Hat LLC <
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7C5418ae5d4cb94b454ab208d73beca2c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637043759850631985sdata=%2BTdmGXZr5uiQaJ36dU8QeOQLGIpR8adX5ktk8%2FRo8ME%3Dreserved=0
> > > > >
> > > > >
> > > > >
> > > > > On Tue, Sep 17, 2019 at 2:22 PM Josh Tynjala <
> > > > joshtynj...@bowlerhat.dev>
> > > > > wrote:
> > > > >
> > > > > > Getting the following error when running the ApproveRoyale
> ant
> > > > script...
> > > > > >
> > > > > > Error: unable to open
> > > > > >
> > > > >
> > > >
> > >
> >
> '/Users/joshtynjala/Desktop/royale/apache-royale-0.9.6-src/royale-asjs/examples/royale/CreditCardValidatorExample/src/main/royale/App.mxml'.
> > > > > >
> > > > > > Seems to be caused by this lin

Re: [royale-asjs] branch release/0.9.6 updated: Fix releasessteps script

2019-09-19 Thread Piotr Zarzycki
I just went trough whole the process and didn't have any kind of problems.
I'm pushing RC2. If you think I should revert that I can. I don't have
anymore console log with it.

śr., 18 wrz 2019 o 16:18 Alex Harui  napisał(a):

> Changing releaseversion to release.version should not be necessary and
> might break something else.  Can you reproduce the failure?  What is the
> console log?  How did it not pick up the releaseversion from
> build.properties?
>
> -Alex
>
> On 9/17/19, 10:53 PM, "pio...@apache.org"  wrote:
>
> This is an automated email from the ASF dual-hosted git repository.
>
> piotrz pushed a commit to branch release/0.9.6
> in repository
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitbox.apache.org%2Frepos%2Fasf%2Froyale-asjs.gitdata=02%7C01%7Caharui%40adobe.com%7C780e787968ef41434f6708d73bfc78e8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637043827860542212sdata=qQC5eeDfhB2Rz%2BdGfyJohLsFJuz%2BdkFCb8WPcrwW5PI%3Dreserved=0
>
>
> The following commit(s) were added to refs/heads/release/0.9.6 by this
> push:
>  new 84c2e85  Fix releasessteps script
> 84c2e85 is described below
>
> commit 84c2e855c5a316ad21ff3a8ac6ac0cde826eecf0
> Author: Piotr Zarzycki 
> AuthorDate: Wed Sep 18 07:47:03 2019 +0200
>
> Fix releasessteps script
>
> - Add RoyaleUnit to swcs list and sign target
> - Fix property release.version
> ---
>  releasesteps.xml | 43 +++
>  1 file changed, 23 insertions(+), 20 deletions(-)
>
> diff --git a/releasesteps.xml b/releasesteps.xml
> index 01d0061..5c3edf1 100644
> --- a/releasesteps.xml
> +++ b/releasesteps.xml
> @@ -219,7 +219,7 @@
>  
>  
> - value="Basic,Binding,Charts,Collections,Core,CreateJS,DragDrop,Effects,Express,Flat,FontAwesome,Formatters,GoogleMaps,Graphics,HTML,HTML5,Icons,JQuery,Jewel,Crux,Language,MXRoyale,MaterialDesignLite,Mobile,Network,Reflection,RoyaleSite,SparkRoyale,Storage,TLF,Text,XML,BasicTheme,JewelTheme"/>
> + value="Basic,Binding,Charts,Collections,Core,CreateJS,DragDrop,Effects,Express,Flat,FontAwesome,Formatters,GoogleMaps,Graphics,HTML,HTML5,Icons,JQuery,Jewel,Crux,Language,MXRoyale,MaterialDesignLite,Mobile,Network,Reflection,RoyaleUnit,RoyaleSite,SparkRoyale,Storage,TLF,Text,XML,BasicTheme,JewelTheme"/>
>   message="${swcs-list}"/>
>  
>
> @@ -501,6 +501,9 @@
>  
>  
>  
> +   
> +
> +
>  
>  
>  
> @@ -880,7 +883,7 @@
>
>   depends="check-air-home,check-playerglobal-home,check-runtime-env" >
>  
> - src="${artifactfolder}/artifacts/apache-royale-${releaseversion}-src.zip"
> dest="${artifactfolder}/sources" >
> + src="${artifactfolder}/artifacts/apache-royale-${release.version}-src.zip"
> dest="${artifactfolder}/sources" >
>  
>
>   />
> @@ -891,21 +894,21 @@
>   failonerror="true" >
>  
>  
> - value="org.apache.royale.compiler-${releaseversion}-rc${rc}" />
> + value="org.apache.royale.compiler-${release.version}-rc${rc}" />
>  https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-compiler.gitdata=02%7C01%7Caharui%40adobe.com%7C780e787968ef41434f6708d73bfc78e8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637043827860542212sdata=Qvy8HglyeoGWo6fV45tu7%2FBURYBHpRgWnx%2F4Mk33ZCo%3Dreserved=0;
> />
>  
>  
>   failonerror="true" >
>  
>  
> - value="org.apache.royale.typedefs-${releaseversion}-rc${rc}" />
> + value="org.apache.royale.typedefs-${release.version}-rc${rc}" />
>  https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-typedefs.gitdata=02%7C01%7Caharui%40adobe.com%7C780e787968ef41434f6708d73bfc78e8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637043827860542212sdata=8jWPOp%2FH%2FKQr9u4ynBRMnXklSST2yaqUCTazqrc7vlA%3Dreserved=0;
> />
>  
>  
>   failonerror="true" >
>  
>  
> - value="org.apache.royale.framework-${releaseversion}-r

Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-18 Thread Piotr Zarzycki
Thanks Josh. In logs there isn't any url from which you are downloading
artifacts. It means probably you are using cached one. One option is to
remove cached artifacts and run build, the second is run build with -X.
It doesn't have to be full build - it's the matter of see what actually
maven do.

śr., 18 wrz 2019 o 16:40 Josh Tynjala 
napisał(a):

> Here's the console output from the Maven section of the build:
>
> https://paste.apache.org/cczye
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Tue, Sep 17, 2019 at 10:20 PM Alex Harui 
> wrote:
>
> > I assume that wasn't the whole log.  I think we want to see the part
> where
> > it builds Core, we only see the last bit of Core.  Core looks like it
> > thought it was in js-only config and didn't build a swf swc and/or
> Binding
> > thinks it is building swf swcs and is looking for Core's swf swc.
> >
> > FWIW, I am having a bunch of other build issues related to js-only for
> Ant
> > for the ASDoc example.  It worked in the past because I still had
> > PLAYERGLOBAL_HOME set in the environment, but when I took that away a
> bunch
> > of new things cropped up.  Could be a  day or two of work.  We could
> still
> > approve the release and folks who want js-only will have to not build
> ASDoc.
> >
> > -Alex
> >
> > On 9/17/19, 8:59 PM, "Piotr Zarzycki" 
> wrote:
> >
> > Hi Josh,
> >
> > Do you have in your Maven config setup link to Maven artifacts? Cause
> > error
> > is saying that it was attempt of downloading them from Snapshot.
> > However
> > Core build successfully, so I'm a bit confused.
> >
> > Thanks,
> > Piotr
> >
> > On Tue, Sep 17, 2019, 11:47 PM Josh Tynjala <
> joshtynj...@bowlerhat.dev
> > >
> > wrote:
> >
> > > Unfortunately, I'm seeing that the Maven part of ApproveRoyale is
> > failing
> > > too. Here's the end of my console output:
> > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F83mivdata=02%7C01%7Caharui%40adobe.com%7C5418ae5d4cb94b454ab208d73beca2c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637043759850631985sdata=j%2FYDlKQ7Tx54p2PJfg2tEoGg2I5Mi19BMB5fFcZcKy4%3Dreserved=0
> > >
> > > --
> > > Josh Tynjala
> > > Bowler Hat LLC <
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7C5418ae5d4cb94b454ab208d73beca2c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637043759850631985sdata=%2BTdmGXZr5uiQaJ36dU8QeOQLGIpR8adX5ktk8%2FRo8ME%3Dreserved=0
> > >
> > >
> > >
> > > On Tue, Sep 17, 2019 at 2:22 PM Josh Tynjala <
> > joshtynj...@bowlerhat.dev>
> > > wrote:
> > >
> > > > Getting the following error when running the ApproveRoyale ant
> > script...
> > > >
> > > > Error: unable to open
> > > >
> > >
> >
> '/Users/joshtynjala/Desktop/royale/apache-royale-0.9.6-src/royale-asjs/examples/royale/CreditCardValidatorExample/src/main/royale/App.mxml'.
> > > >
> > > > Seems to be caused by this line in build.xml from
> > > > CreditCardValidatorExample:
> > > >
> > > > 
> > > >
> > > > There is no App.mxml, but there is a
> > CreditCardValidatorExample.mxml, so
> > > I
> > > > think that the value is supposed to be
> "CreditCardValidatorExample"
> > > instead:
> > > >
> > > > 
> > > >
> > > > I just pushed a commit to develop to fix that for the next
> release.
> > > >
> > > > I will locally adjust ApproveRoyale to skip the examples and
> > finish the
> > > > rest of the approval process. Assuming that everything else
> > completes
> > > > successfully, a broken example build script is not enough to
> > prevent me
> > > > from approving this release candidate.
> > > >
> > > > --
> > > > Josh Tynjala
> > > > Bowler Hat LLC <
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7C5418ae5d4cb94b454ab208d73beca2c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637043759850631985sdata=%2BTdmGXZr5uiQaJ36dU8QeOQLGIpR8adX5ktk8%2FRo8ME%3Dreserved=0
> > >
> > > >
> > > >
> > > > On Tue, Sep 17, 2019 at 6:43 AM Apache Royale CI Server <
> > > > apacheroyal...@gmail.com> wrote:
> > > >
> > > >> This is the discussion thread.
> > > >>
> > > >> Thanks,
> > > >> Piotr
> > > >
> > > >
> > >
> >
> >
> >
>


-- 

Piotr Zarzycki

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


Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-18 Thread Piotr Zarzycki
Hi Josh,

The question is how Maven know if won't setup in settings link to staging
to use proper version of compiler and sdk. How Maven taking from staging
artefacts if you won't tell to him?

I have tried build sources using in settings [1] - I didn't try without it.

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

Thanks,
Piotr

śr., 18 wrz 2019 o 16:14 Josh Tynjala 
napisał(a):

> I don't know enough about Maven to answer your question, Piotr. All I can
> say is that I have successfully run the ApproveRoyale script for previous
> releases, and I don't think that I have changed any kind of global Maven
> settings on this machine since then.
>
> I can run it again and share the entire log, if that will help anyone,
> though.
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Tue, Sep 17, 2019 at 8:59 PM Piotr Zarzycki 
> wrote:
>
> > Hi Josh,
> >
> > Do you have in your Maven config setup link to Maven artifacts? Cause
> error
> > is saying that it was attempt of downloading them from Snapshot. However
> > Core build successfully, so I'm a bit confused.
> >
> > Thanks,
> > Piotr
> >
> > On Tue, Sep 17, 2019, 11:47 PM Josh Tynjala 
> > wrote:
> >
> > > Unfortunately, I'm seeing that the Maven part of ApproveRoyale is
> failing
> > > too. Here's the end of my console output:
> > >
> > > https://paste.apache.org/83miv
> > >
> > > --
> > > Josh Tynjala
> > > Bowler Hat LLC <https://bowlerhat.dev>
> > >
> > >
> > > On Tue, Sep 17, 2019 at 2:22 PM Josh Tynjala <
> joshtynj...@bowlerhat.dev>
> > > wrote:
> > >
> > > > Getting the following error when running the ApproveRoyale ant
> > script...
> > > >
> > > > Error: unable to open
> > > >
> > >
> >
> '/Users/joshtynjala/Desktop/royale/apache-royale-0.9.6-src/royale-asjs/examples/royale/CreditCardValidatorExample/src/main/royale/App.mxml'.
> > > >
> > > > Seems to be caused by this line in build.xml from
> > > > CreditCardValidatorExample:
> > > >
> > > > 
> > > >
> > > > There is no App.mxml, but there is a CreditCardValidatorExample.mxml,
> > so
> > > I
> > > > think that the value is supposed to be "CreditCardValidatorExample"
> > > instead:
> > > >
> > > > 
> > > >
> > > > I just pushed a commit to develop to fix that for the next release.
> > > >
> > > > I will locally adjust ApproveRoyale to skip the examples and finish
> the
> > > > rest of the approval process. Assuming that everything else completes
> > > > successfully, a broken example build script is not enough to prevent
> me
> > > > from approving this release candidate.
> > > >
> > > > --
> > > > Josh Tynjala
> > > > Bowler Hat LLC <https://bowlerhat.dev>
> > > >
> > > >
> > > > On Tue, Sep 17, 2019 at 6:43 AM Apache Royale CI Server <
> > > > apacheroyal...@gmail.com> wrote:
> > > >
> > > >> This is the discussion thread.
> > > >>
> > > >> Thanks,
> > > >> Piotr
> > > >
> > > >
> > >
> >
>


-- 

Piotr Zarzycki

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


Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-17 Thread Piotr Zarzycki
I'm going to push fixes for release steps script today and make RC2. If I
figure out how to export gpg KEY in a proper format as it is in KEYS file I
will update them as well - if not people can use Josh's way of getting my
key for now.

śr., 18 wrz 2019 o 07:20 Alex Harui  napisał(a):

> I assume that wasn't the whole log.  I think we want to see the part where
> it builds Core, we only see the last bit of Core.  Core looks like it
> thought it was in js-only config and didn't build a swf swc and/or Binding
> thinks it is building swf swcs and is looking for Core's swf swc.
>
> FWIW, I am having a bunch of other build issues related to js-only for Ant
> for the ASDoc example.  It worked in the past because I still had
> PLAYERGLOBAL_HOME set in the environment, but when I took that away a bunch
> of new things cropped up.  Could be a  day or two of work.  We could still
> approve the release and folks who want js-only will have to not build ASDoc.
>
> -Alex
>
> On 9/17/19, 8:59 PM, "Piotr Zarzycki"  wrote:
>
> Hi Josh,
>
> Do you have in your Maven config setup link to Maven artifacts? Cause
> error
> is saying that it was attempt of downloading them from Snapshot.
> However
> Core build successfully, so I'm a bit confused.
>
> Thanks,
> Piotr
>
> On Tue, Sep 17, 2019, 11:47 PM Josh Tynjala  >
> wrote:
>
> > Unfortunately, I'm seeing that the Maven part of ApproveRoyale is
> failing
> > too. Here's the end of my console output:
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F83mivdata=02%7C01%7Caharui%40adobe.com%7C5418ae5d4cb94b454ab208d73beca2c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637043759850631985sdata=j%2FYDlKQ7Tx54p2PJfg2tEoGg2I5Mi19BMB5fFcZcKy4%3Dreserved=0
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7C5418ae5d4cb94b454ab208d73beca2c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637043759850631985sdata=%2BTdmGXZr5uiQaJ36dU8QeOQLGIpR8adX5ktk8%2FRo8ME%3Dreserved=0
> >
> >
> >
> > On Tue, Sep 17, 2019 at 2:22 PM Josh Tynjala <
> joshtynj...@bowlerhat.dev>
> > wrote:
> >
> > > Getting the following error when running the ApproveRoyale ant
> script...
> > >
> > > Error: unable to open
> > >
> >
> '/Users/joshtynjala/Desktop/royale/apache-royale-0.9.6-src/royale-asjs/examples/royale/CreditCardValidatorExample/src/main/royale/App.mxml'.
> > >
> > > Seems to be caused by this line in build.xml from
> > > CreditCardValidatorExample:
> > >
> > > 
> > >
> > > There is no App.mxml, but there is a
> CreditCardValidatorExample.mxml, so
> > I
> > > think that the value is supposed to be "CreditCardValidatorExample"
> > instead:
> > >
> > > 
> > >
> > > I just pushed a commit to develop to fix that for the next release.
> > >
> > > I will locally adjust ApproveRoyale to skip the examples and
> finish the
> > > rest of the approval process. Assuming that everything else
> completes
> > > successfully, a broken example build script is not enough to
> prevent me
> > > from approving this release candidate.
> > >
> > > --
> > > Josh Tynjala
> > > Bowler Hat LLC <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7C5418ae5d4cb94b454ab208d73beca2c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637043759850631985sdata=%2BTdmGXZr5uiQaJ36dU8QeOQLGIpR8adX5ktk8%2FRo8ME%3Dreserved=0
> >
> > >
> > >
> > > On Tue, Sep 17, 2019 at 6:43 AM Apache Royale CI Server <
> > > apacheroyal...@gmail.com> wrote:
> > >
> > >> This is the discussion thread.
> > >>
> > >> Thanks,
> > >> Piotr
> > >
> > >
> >
>
>
>

-- 

Piotr Zarzycki

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


[DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-17 Thread Piotr Zarzycki
Hi Josh,

Do you have in your Maven config setup link to Maven artifacts? Cause error
is saying that it was attempt of downloading them from Snapshot. However
Core build successfully, so I'm a bit confused.

Thanks,
Piotr

On Tue, Sep 17, 2019, 11:47 PM Josh Tynjala 
wrote:

> Unfortunately, I'm seeing that the Maven part of ApproveRoyale is failing
> too. Here's the end of my console output:
>
> https://paste.apache.org/83miv
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>
>
> On Tue, Sep 17, 2019 at 2:22 PM Josh Tynjala 
> wrote:
>
> > Getting the following error when running the ApproveRoyale ant script...
> >
> > Error: unable to open
> >
> '/Users/joshtynjala/Desktop/royale/apache-royale-0.9.6-src/royale-asjs/examples/royale/CreditCardValidatorExample/src/main/royale/App.mxml'.
> >
> > Seems to be caused by this line in build.xml from
> > CreditCardValidatorExample:
> >
> > 
> >
> > There is no App.mxml, but there is a CreditCardValidatorExample.mxml, so
> I
> > think that the value is supposed to be "CreditCardValidatorExample"
> instead:
> >
> > 
> >
> > I just pushed a commit to develop to fix that for the next release.
> >
> > I will locally adjust ApproveRoyale to skip the examples and finish the
> > rest of the approval process. Assuming that everything else completes
> > successfully, a broken example build script is not enough to prevent me
> > from approving this release candidate.
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC 
> >
> >
> > On Tue, Sep 17, 2019 at 6:43 AM Apache Royale CI Server <
> > apacheroyal...@gmail.com> wrote:
> >
> >> This is the discussion thread.
> >>
> >> Thanks,
> >> Piotr
> >
> >
>


Discuss of release steps preparation

2019-09-17 Thread Piotr Zarzycki
Alex,

I will fix those issues once we make current release. Both of them are not
a blockers in my opinion.

How issue in release steps script can influence sources ?

Thanks,
Piotr


On Tue, Sep 17, 2019, 7:29 PM Alex Harui  wrote:

> If you had to do that, how do you know the RC is still valid?  Sounds like
> there is a version number that isn't right in the source package.  One
> reason to have scripts is to detect things that are not right.  Yes there
> might be bugs in the scripts, but if you didn't have to do this before, it
> should imply that something changes in the source package.
>
> Please fix issues like the signing of RoyaleUnit.  Otherwise, who's job is
> it to fix it?  I could, but then we're back to the same problem of nobody
> else knowing how to fix the scripts.
>
> -Alex
>
> On 9/17/19, 3:58 AM, "Piotr Zarzycki"  wrote:
>
> Another small issue which I discovered is that I had to specify in Step
> 13 -Drelease.version=0.9.6 -Dreleaseversion=0.9.6 - With dot and
> without
> dot, cause script failed on compiler cloning.
>
>     Thanks,
> Piotr
>
> wt., 17 wrz 2019 o 10:47 Piotr Zarzycki 
> napisał(a):
>
> > Hi Guys,
> >
> > I'm in a process of uploading Maven artifacts and after upload I got
> > following problem [1]. I will sign those artifacts manually, but
> this is
> > something what should be fixed in the script for the next release.
> >
> > [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fibb.co%2Fzh0r5nndata=02%7C01%7Caharui%40adobe.com%7C1fc0eda016c142c6749208d73b5df97a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637043147117439927sdata=ooR8yrRymFsNi6fa%2BZ3%2BUdMqWSoq0cPow8wUfaOw2mI%3Dreserved=0
> >
> > Thanks,
> > Piotr
> >
> > niedz., 15 wrz 2019 o 08:18 Alex Harui 
> > napisał(a):
> >
> >> Glad you are getting back to normal.  Please review what is in the
> >> release branch before the RC so we can fix things before Piotr
> spends a lot
> >> of time creating the RC.
> >>
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fblob%2Frelease%2F0.9.6%2FRELEASE_NOTES.mddata=02%7C01%7Caharui%40adobe.com%7C1fc0eda016c142c6749208d73b5df97a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637043147117439927sdata=9F0OmcoS2IPo6XKwtw7RWCSX0R3U5NLe1XX%2Fk10r%2Fms%3Dreserved=0
> >>
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fblob%2Frelease%2F0.9.6%2Freleasemgr%2FRELEASE_NOTESdata=02%7C01%7Caharui%40adobe.com%7C1fc0eda016c142c6749208d73b5df97a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637043147117449928sdata=b1gmeUkWeRBI0nuEplLMutT8tcWobwtbsvSOSuxtYOQ%3Dreserved=0
> >>
> >> Because of the way we package, the releasemgr/RELEASE_NOTES is the
> >> top-level release notes in the source package because the package
> contains
> >> all 3 repos and the releasemgr files are copied to the top.  The
> .MD file
> >> is for GitHub visitors to the repo.
> >>
> >> Thanks,
> >> -Alex
> >>
> >> On 9/14/19, 11:06 AM, "Andrew Wetmore"  wrote:
> >>
> >> We have power and internet again, at last. I guess I should
> wait to
> >> review
> >> texts until the next version of the release candidate.
> >>
> >> On Sat, Sep 14, 2019 at 3:01 PM Piotr Zarzycki <
> >> piotrzarzyck...@gmail.com>
> >> wrote:
> >>
> >> > Hi Carlos,
> >> >
> >> > I see you did commit to 0.9.6 branch, so we are good unless
> there is
> >> > something left in develop which should I pick. I will review
> all of
> >> that on
> >> > Monday.
> >> >
> >> > Thanks,
> >> > Piotr
> >> >
> >> > On Sat, Sep 14, 2019, 5:26 PM Carlos Rovira <
> >> carlosrov...@apache.org>
> >> > wrote:
> >> >
> >> > > Hi Piotr,
> >> > >
> >> > > seems there was a little confusion here and Greg and I did
> the
> >> changes in
> >> > > the release version of RELEASE_NOTES.
> >> > > Hope you can merge both in your process. I followed my
> changes
> >> since
> >> > &

[DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-17 Thread Piotr Zarzycki
Carlos,

Could you also try to setup Maven artifacts and build your project - see if
all is ok?

It is the matter of setup links with artifacts in settings.xml. Set it as
active profile and maybe switch in pom to 0.9.6 non Snapshot.

If you will have time!

Thanks,
Piotr

On Tue, Sep 17, 2019, 6:34 PM Carlos Rovira  wrote:

> Hi Piotr, is ok is in royale-asjs README repo. All ok
>
> (about gmail mixing topics, good catch...although that's very strange gmail
> behavior :-? )
>
>
>
> El mar., 17 sept. 2019 a las 18:25, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > Are you checking README in sources? I think those information are in some
> > release notes file not readme.
> >
> > On Tue, Sep 17, 2019, 6:17 PM Carlos Rovira 
> > wrote:
> >
> > > Hi Piotr,
> > >
> > > I notice this thread is VOTE and not DISCUSS.
> > >
> > > About celebration, I think it deserves admiration, although we know we
> > > still could need a little final adjustment. But this process is about
> > 99%,
> > > so is good to celebrate all the hard work here by Alex, Om, you and
> > others
> > > involved :)
> > >
> > > Going to my checking of RC1: In README I think there are missing notes.
> > We
> > > provided a lot more. Don't know if is ok as is cause we couldn't add
> all
> > > latest notes (I though only Andrew's revision was left from this
> > release).
> > > I see just this (while final notes was about x3 more lines):
> > >
> > > Apache Royale 0.9.6
> > > ===
> > >
> > > - Compiles faster
> > > - Many additional components available.
> > > - Emulations of many other components available.
> > > - For applications targeting JavaScript, you can now incorporate the
> > >   vast resources available in existing, free JavaScript libraries.
> > > - Dozens of bugs reported, investigated, and squashed. For details of
> > >   closed bug reports see
> > > https://github.com/apache/royale-asjs/issues?q=is%3Aissue+is%3Aclosed
> > >
> > > Thanks!
> > >
> > >
> > >
> > > El mar., 17 sept. 2019 a las 17:14, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>) escribió:
> > >
> > > > Hi Carlos,
> > > >
> > > > Thanks but I won't start celebrate till someone build stuff on his PC
> > > using
> > > > approval script or whatever other method.
> > > >
> > > > I did try script. I reached the point where SDK need to be build - I
> > left
> > > > it for now to try tomorrow maybe.
> > > >
> > > > wt., 17 wrz 2019 o 17:02 Carlos Rovira 
> > > > napisał(a):
> > > >
> > > > > Hi,
> > > > > congrats to reach this step! many work involved here so far! :)
> > > > >
> > > > > El mar., 17 sept. 2019 a las 15:45, Piotr Zarzycki (<
> > > > > piotrzarzyck...@gmail.com>) escribió:
> > > > >
> > > > > > Hi Guys,
> > > > > >
> > > > > > I believe we can officially start testing, providing feedback and
> > > > > hopefully
> > > > > > voting.
> > > > > >
> > > > > > Thanks,
> > > > > > Piotr
> > > > > >
> > > > > > wt., 17 wrz 2019 o 15:43 Apache Royale CI Server <
> > > > > apacheroyal...@gmail.com
> > > > > > >
> > > > > > napisał(a):
> > > > > >
> > > > > > > This is the discussion thread.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Piotr
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > >
> > > > > > Piotr Zarzycki
> > > > > >
> > > > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > > <https://www.patreon.com/piotrzarzycki>*
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Carlos Rovira
> > > > > http://about.me/carlosrovira
> > > > >
> > > >
> > > >
> > > > --
> > > >
> > > > Piotr Zarzycki
> > > >
> > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > <https://www.patreon.com/piotrzarzycki>*
> > > >
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


[DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-17 Thread Piotr Zarzycki
Are you checking README in sources? I think those information are in some
release notes file not readme.

On Tue, Sep 17, 2019, 6:17 PM Carlos Rovira  wrote:

> Hi Piotr,
>
> I notice this thread is VOTE and not DISCUSS.
>
> About celebration, I think it deserves admiration, although we know we
> still could need a little final adjustment. But this process is about 99%,
> so is good to celebrate all the hard work here by Alex, Om, you and others
> involved :)
>
> Going to my checking of RC1: In README I think there are missing notes. We
> provided a lot more. Don't know if is ok as is cause we couldn't add all
> latest notes (I though only Andrew's revision was left from this release).
> I see just this (while final notes was about x3 more lines):
>
> Apache Royale 0.9.6
> ===
>
> - Compiles faster
> - Many additional components available.
> - Emulations of many other components available.
> - For applications targeting JavaScript, you can now incorporate the
>   vast resources available in existing, free JavaScript libraries.
> - Dozens of bugs reported, investigated, and squashed. For details of
>   closed bug reports see
> https://github.com/apache/royale-asjs/issues?q=is%3Aissue+is%3Aclosed
>
> Thanks!
>
>
>
> El mar., 17 sept. 2019 a las 17:14, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > Hi Carlos,
> >
> > Thanks but I won't start celebrate till someone build stuff on his PC
> using
> > approval script or whatever other method.
> >
> > I did try script. I reached the point where SDK need to be build - I left
> > it for now to try tomorrow maybe.
> >
> > wt., 17 wrz 2019 o 17:02 Carlos Rovira 
> > napisał(a):
> >
> > > Hi,
> > > congrats to reach this step! many work involved here so far! :)
> > >
> > > El mar., 17 sept. 2019 a las 15:45, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>) escribió:
> > >
> > > > Hi Guys,
> > > >
> > > > I believe we can officially start testing, providing feedback and
> > > hopefully
> > > > voting.
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > wt., 17 wrz 2019 o 15:43 Apache Royale CI Server <
> > > apacheroyal...@gmail.com
> > > > >
> > > > napisał(a):
> > > >
> > > > > This is the discussion thread.
> > > > >
> > > > > Thanks,
> > > > > Piotr
> > > >
> > > >
> > > >
> > > > --
> > > >
> > > > Piotr Zarzycki
> > > >
> > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > <https://www.patreon.com/piotrzarzycki>*
> > > >
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > <https://www.patreon.com/piotrzarzycki>*
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


[DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-17 Thread Piotr Zarzycki
Carlos,

Gmail merge both topics, but if you hit Reply All and check Edit Title you
can make sure that your replaying in a good subject. Check before reply.

Thanks,
Piotr

On Tue, Sep 17, 2019, 6:17 PM Carlos Rovira  wrote:

> Hi Piotr,
>
> I notice this thread is VOTE and not DISCUSS.
>
> About celebration, I think it deserves admiration, although we know we
> still could need a little final adjustment. But this process is about 99%,
> so is good to celebrate all the hard work here by Alex, Om, you and others
> involved :)
>
> Going to my checking of RC1: In README I think there are missing notes. We
> provided a lot more. Don't know if is ok as is cause we couldn't add all
> latest notes (I though only Andrew's revision was left from this release).
> I see just this (while final notes was about x3 more lines):
>
> Apache Royale 0.9.6
> ===
>
> - Compiles faster
> - Many additional components available.
> - Emulations of many other components available.
> - For applications targeting JavaScript, you can now incorporate the
>   vast resources available in existing, free JavaScript libraries.
> - Dozens of bugs reported, investigated, and squashed. For details of
>   closed bug reports see
> https://github.com/apache/royale-asjs/issues?q=is%3Aissue+is%3Aclosed
>
> Thanks!
>
>
>
> El mar., 17 sept. 2019 a las 17:14, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > Hi Carlos,
> >
> > Thanks but I won't start celebrate till someone build stuff on his PC
> using
> > approval script or whatever other method.
> >
> > I did try script. I reached the point where SDK need to be build - I left
> > it for now to try tomorrow maybe.
> >
> > wt., 17 wrz 2019 o 17:02 Carlos Rovira 
> > napisał(a):
> >
> > > Hi,
> > > congrats to reach this step! many work involved here so far! :)
> > >
> > > El mar., 17 sept. 2019 a las 15:45, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>) escribió:
> > >
> > > > Hi Guys,
> > > >
> > > > I believe we can officially start testing, providing feedback and
> > > hopefully
> > > > voting.
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > wt., 17 wrz 2019 o 15:43 Apache Royale CI Server <
> > > apacheroyal...@gmail.com
> > > > >
> > > > napisał(a):
> > > >
> > > > > This is the discussion thread.
> > > > >
> > > > > Thanks,
> > > > > Piotr
> > > >
> > > >
> > > >
> > > > --
> > > >
> > > > Piotr Zarzycki
> > > >
> > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > <https://www.patreon.com/piotrzarzycki>*
> > > >
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > <https://www.patreon.com/piotrzarzycki>*
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


[DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-17 Thread Piotr Zarzycki
Hi Carlos,

Thanks but I won't start celebrate till someone build stuff on his PC using
approval script or whatever other method.

I did try script. I reached the point where SDK need to be build - I left
it for now to try tomorrow maybe.

wt., 17 wrz 2019 o 17:02 Carlos Rovira  napisał(a):

> Hi,
> congrats to reach this step! many work involved here so far! :)
>
> El mar., 17 sept. 2019 a las 15:45, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > Hi Guys,
> >
> > I believe we can officially start testing, providing feedback and
> hopefully
> > voting.
> >
> > Thanks,
> > Piotr
> >
> > wt., 17 wrz 2019 o 15:43 Apache Royale CI Server <
> apacheroyal...@gmail.com
> > >
> > napisał(a):
> >
> > > This is the discussion thread.
> > >
> > > Thanks,
> > > Piotr
> >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > <https://www.patreon.com/piotrzarzycki>*
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 

Piotr Zarzycki

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


[DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-17 Thread Piotr Zarzycki
Hi Guys,

I believe we can officially start testing, providing feedback and hopefully
voting.

Thanks,
Piotr

wt., 17 wrz 2019 o 15:43 Apache Royale CI Server 
napisał(a):

> This is the discussion thread.
>
> Thanks,
> Piotr



-- 

Piotr Zarzycki

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


Re: Discuss of release steps preparation

2019-09-17 Thread Piotr Zarzycki
Another small issue which I discovered is that I had to specify in Step
13 -Drelease.version=0.9.6 -Dreleaseversion=0.9.6 - With dot and without
dot, cause script failed on compiler cloning.

Thanks,
Piotr

wt., 17 wrz 2019 o 10:47 Piotr Zarzycki 
napisał(a):

> Hi Guys,
>
> I'm in a process of uploading Maven artifacts and after upload I got
> following problem [1]. I will sign those artifacts manually, but this is
> something what should be fixed in the script for the next release.
>
> [1] https://ibb.co/zh0r5nn
>
> Thanks,
> Piotr
>
> niedz., 15 wrz 2019 o 08:18 Alex Harui 
> napisał(a):
>
>> Glad you are getting back to normal.  Please review what is in the
>> release branch before the RC so we can fix things before Piotr spends a lot
>> of time creating the RC.
>>
>> https://github.com/apache/royale-asjs/blob/release/0.9.6/RELEASE_NOTES.md
>>
>> https://github.com/apache/royale-asjs/blob/release/0.9.6/releasemgr/RELEASE_NOTES
>>
>> Because of the way we package, the releasemgr/RELEASE_NOTES is the
>> top-level release notes in the source package because the package contains
>> all 3 repos and the releasemgr files are copied to the top.  The .MD file
>> is for GitHub visitors to the repo.
>>
>> Thanks,
>> -Alex
>>
>> On 9/14/19, 11:06 AM, "Andrew Wetmore"  wrote:
>>
>> We have power and internet again, at last. I guess I should wait to
>> review
>> texts until the next version of the release candidate.
>>
>> On Sat, Sep 14, 2019 at 3:01 PM Piotr Zarzycki <
>> piotrzarzyck...@gmail.com>
>> wrote:
>>
>> > Hi Carlos,
>> >
>> > I see you did commit to 0.9.6 branch, so we are good unless there is
>> > something left in develop which should I pick. I will review all of
>> that on
>> > Monday.
>> >
>> > Thanks,
>> > Piotr
>> >
>> > On Sat, Sep 14, 2019, 5:26 PM Carlos Rovira <
>> carlosrov...@apache.org>
>> > wrote:
>> >
>> > > Hi Piotr,
>> > >
>> > > seems there was a little confusion here and Greg and I did the
>> changes in
>> > > the release version of RELEASE_NOTES.
>> > > Hope you can merge both in your process. I followed my changes
>> since
>> > > December to try to bring all relevant things done.
>> > > Thanks
>> > >
>> > > El sáb., 14 sept. 2019 a las 15:39, Piotr Zarzycki (<
>> > > piotrzarzyck...@gmail.com>) escribió:
>> > >
>> > > > Hi Greg,
>> > > >
>> > > > I'm sorry for a late response. I'm going to take what's develop
>> has in
>> > it
>> > > > on Monday by cherry picking - to do not break release branch,
>> so where
>> > > you
>> > > > commit it will be good and won't miss it.
>> > > >
>> > > > Thanks,
>> > > > Piotr
>> > > >
>> > > > pt., 13 wrz 2019 o 19:24 Greg Dove 
>> napisał(a):
>> > > >
>> > > > > Hi Piotr,
>> > > > >
>> > > > > I'm not so familiar with the release process. Do you want
>> additions
>> > to
>> > > go
>> > > > > directly into the release branch or should that be added to
>> develop
>> > > > > (assuming you would merge into release)?
>> > > > >
>> > > > > I see Josh added note about RoyalUnit in develop [1], which
>> is not
>> > yet
>> > > in
>> > > > > release.[2] . So perhaps you will merge from develop? I'm not
>> sure
>> > how
>> > > > this
>> > > > > all needs to work.
>> > > > >
>> > > > > I'm thinking to add the following to 0.9.6 release notes
>> (changes
>> > since
>> > > > > 0.9.4) for some of the things I worked on:
>> > > > >
>> > > > > -Improvements to AMF / RemoteObject Support
>> > > > > -AMFBinaryData api now matches flash.utils.ByteArray, (the
>> missing
>> > > > feature
>> > > > > is non-UTF String encoding support). It therefore now works
>> for deep
>> > > > > 

Re: Discuss of release steps preparation

2019-09-17 Thread Piotr Zarzycki
Hi Guys,

I'm in a process of uploading Maven artifacts and after upload I got
following problem [1]. I will sign those artifacts manually, but this is
something what should be fixed in the script for the next release.

[1] https://ibb.co/zh0r5nn

Thanks,
Piotr

niedz., 15 wrz 2019 o 08:18 Alex Harui 
napisał(a):

> Glad you are getting back to normal.  Please review what is in the release
> branch before the RC so we can fix things before Piotr spends a lot of time
> creating the RC.
>
> https://github.com/apache/royale-asjs/blob/release/0.9.6/RELEASE_NOTES.md
>
> https://github.com/apache/royale-asjs/blob/release/0.9.6/releasemgr/RELEASE_NOTES
>
> Because of the way we package, the releasemgr/RELEASE_NOTES is the
> top-level release notes in the source package because the package contains
> all 3 repos and the releasemgr files are copied to the top.  The .MD file
> is for GitHub visitors to the repo.
>
> Thanks,
> -Alex
>
> On 9/14/19, 11:06 AM, "Andrew Wetmore"  wrote:
>
> We have power and internet again, at last. I guess I should wait to
> review
> texts until the next version of the release candidate.
>
> On Sat, Sep 14, 2019 at 3:01 PM Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> wrote:
>
> > Hi Carlos,
> >
> > I see you did commit to 0.9.6 branch, so we are good unless there is
> > something left in develop which should I pick. I will review all of
> that on
> > Monday.
> >
> > Thanks,
> > Piotr
> >
> > On Sat, Sep 14, 2019, 5:26 PM Carlos Rovira  >
> > wrote:
> >
> > > Hi Piotr,
> > >
> > > seems there was a little confusion here and Greg and I did the
> changes in
> > > the release version of RELEASE_NOTES.
> > > Hope you can merge both in your process. I followed my changes
> since
> > > December to try to bring all relevant things done.
> > > Thanks
> > >
> > > El sáb., 14 sept. 2019 a las 15:39, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>) escribió:
> > >
> > > > Hi Greg,
> > > >
> > > > I'm sorry for a late response. I'm going to take what's develop
> has in
> > it
> > > > on Monday by cherry picking - to do not break release branch, so
> where
> > > you
> > > > commit it will be good and won't miss it.
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > pt., 13 wrz 2019 o 19:24 Greg Dove 
> napisał(a):
> > > >
> > > > > Hi Piotr,
> > > > >
> > > > > I'm not so familiar with the release process. Do you want
> additions
> > to
> > > go
> > > > > directly into the release branch or should that be added to
> develop
> > > > > (assuming you would merge into release)?
> > > > >
> > > > > I see Josh added note about RoyalUnit in develop [1], which is
> not
> > yet
> > > in
> > > > > release.[2] . So perhaps you will merge from develop? I'm not
> sure
> > how
> > > > this
> > > > > all needs to work.
> > > > >
> > > > > I'm thinking to add the following to 0.9.6 release notes
> (changes
> > since
> > > > > 0.9.4) for some of the things I worked on:
> > > > >
> > > > > -Improvements to AMF / RemoteObject Support
> > > > > -AMFBinaryData api now matches flash.utils.ByteArray, (the
> missing
> > > > feature
> > > > > is non-UTF String encoding support). It therefore now works
> for deep
> > > > > cloning via readObject/writeObject and registerClassAlias.
> > > > > -Updates to Royale collections library with support for
> sorting and
> > > > > filtering via ArrayListView. Simple example added to Tour de
> Jewel
> > > > > -A conforming runtime implementation of AS3 Vector (typed
> Arrays) was
> > > > added
> > > > > for javascript output, with options for avoiding certain
> runtime
> > > checks.
> > > > > -int, uint, Class are now represented as simple, distinct types
> > (Class
> > > is
> > > > > now not 'Object', int is now not 'Number' for example), and
> these
> > > s

Re: [royale-asjs] branch release/0.9.6 updated: Update RELEASE_NOTES.md

2019-09-16 Thread Piotr Zarzycki
I know Andrew. No problem ! :)

pon., 16 wrz 2019 o 12:39 Andrew Wetmore  napisał(a):

> The hurricane and is aftermath slowed me down. Anyhow all my edits were
> minor.
>
> On Mon, Sep 16, 2019, 7:01 AM Piotr Zarzycki, 
> wrote:
>
> > Hi Andrew,
> >
> > I'm sorry but I already started preparing artifacts, so this probably
> won't
> > go to 0.9.6.
> >
> > Thanks,
> > Piotr
> >
> > pon., 16 wrz 2019 o 11:55  napisał(a):
> >
> > > This is an automated email from the ASF dual-hosted git repository.
> > >
> > > andreww pushed a commit to branch release/0.9.6
> > > in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
> > >
> > >
> > > The following commit(s) were added to refs/heads/release/0.9.6 by this
> > > push:
> > >  new 4136e54  Update RELEASE_NOTES.md
> > > 4136e54 is described below
> > >
> > > commit 4136e543b3dba11bfadb08d9ce357cbb36d7b9a4
> > > Author: Andrew Wetmore 
> > > AuthorDate: Mon Sep 16 06:55:05 2019 -0300
> > >
> > > Update RELEASE_NOTES.md
> > >
> > > Many small text edits.
> > > ---
> > >  RELEASE_NOTES.md | 62
> > > 
> > >  1 file changed, 31 insertions(+), 31 deletions(-)
> > >
> > > diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md
> > > index a4a4bb0..9e8ec3c 100644
> > > --- a/RELEASE_NOTES.md
> > > +++ b/RELEASE_NOTES.md
> > > @@ -1,38 +1,38 @@
> > >  Apache Royale 0.9.6
> > >  ===
> > >
> > > -- Compiles faster
> > > -- For applications targeting JavaScript, you can now incorporate the
> > vast
> > > resources available in existing, free, JavaScript libraries.
> > > -- Many additional components available:
> > > -  - for Jewel: Wizard, PopUp, TabBar, Module, ModuleLoader, FooterBar,
> > > Badge, ScrollableSectionContent, HorizontalListScroll
> > > -- Emulations of many other components available
> > > -- Many improvements and fixes in Jewel UI Set:
> > > -  - DateField/DateChooser full implememtation.
> > > -  - Fixes to make components work right on IE11 and Android/iOS mobile
> > > devices.
> > > -  - Many improvements to all themes included (styles for new
> components,
> > > added more styles like disabled missing in some components,...)
> > > -  - Many beads included for Jewel set:
> > > -- Added search filter bead on Jewel ComboBox
> > > -- Added SearchFilterForList bead to use with Jewel List and
> > TextInput.
> > > +- Compiles faster.
> > > +- For applications targeting JavaScript, you can now incorporate the
> > vast
> > > resources available in existing, free JavaScript libraries.
> > > +- Many additional components are available:
> > > +  - for the Jewel component set, Wizard, PopUp, TabBar, Module,
> > > ModuleLoader, FooterBar, Badge, ScrollableSectionContent, and
> > > HorizontalListScroll are now available.
> > > +- Emulations of many other components are available.
> > > +- Many improvements and fixes in the Jewel component set:
> > > +  - Full implementation of DateField/DateChooser.
> > > +  - Components now work correctly on IE11 and on Android/iOS mobile
> > > devices.
> > > +  - Many improvements to all themes, such as styles for new components
> > > and a disabled style that was missing in some components.
> > > +  - Many beads have been added for Jewel components:
> > > +- Search filter bead on Jewel ComboBox
> > > +- SearchFilterForList bead to use with Jewel List and TextInput
> > >  - RequiredSelection for DropDownList
> > > -  - Improvements on focus handling
> > > -  - Button now extends from new BasicButton
> > > -- Many improvements on Tour De Jewel demo app to show all new
> components
> > > and beads developed in this version.
> > > -- Added BrowserOrientation bead
> > > -- Added loadCSS, to load external CSS dinamically.
> > > -- Added generation of source-maps to all Royale libs for better
> > debugging
> > > framework code.
> > > +  - Improvements to focus handling.
> > > +  - Button now extends from new BasicButton.
> > > +- Many improvements on Tour De Jewel demo app to show components and
> > > beads introduced in this version.
> > > +- Added BrowserOrientation bead.
> > > +- Added loadCSS, to load external CSS dyna

Re: [royale-asjs] branch release/0.9.6 updated: Update RELEASE_NOTES.md

2019-09-16 Thread Piotr Zarzycki
t; -- New Apache Royale Crux MVC/DI/IOC application architecture library
> (based on Swiz Framework) was added, with some simple examples
> -- Added many new or missing libs to [ASDocs reference](
> https://royale.apache.org/asdoc/)
> +- Updates to Royale collections library with support for sorting and
> filtering via ArrayListView. Simple example added to Tour de Jewel.
> +- A conforming runtime implementation of AS3 Vector (typed Arrays) was
> added for javaScript output, with options for avoiding certain runtime
> checks.
> +- int, uint, Class are now represented as simple, distinct types (Class
> is now not an 'Object', int is now not a 'Number', for example), and these
> support indirect 'as' or 'is' type checking and instantiation, matching swf
> behavior.
> +- General improvements and additions to the Reflection library.
> +- New Apache Royale Crux MVC/DI/IOC application architecture library
> (based on Swiz Framework) was added, with some simple examples.
> +- Added and updated documentation in many areaas of [ASDocs reference](
> https://royale.apache.org/asdoc/).
>  - Dozens of bugs reported, investigated, and squashed. For details of
> -  closed bug reports see [GitHub Issues list](
> https://github.com/apache/royale-asjs/issues?q=is%3Aissue+is%3Aclosed)
> +  closed bug reports see [GitHub Issues list](
> https://github.com/apache/royale-asjs/issues?q=is%3Aissue+is%3Aclosed).
>
> -Updates to the RELEASE_NOTES discovered after this file was packaged into
> the release artifacts can be found here:
> +Updates to the RELEASE_NOTES made after this file was packaged into the
> release artifacts can be found here:
>
>  https://github.com/apache/royale-asjs/wiki/Release-Notes-0.9.6
>
> @@ -54,7 +54,7 @@ Known Issues:
>  frameworks/libs/MXRoyale.swc, frameworks/libs/SparkRoyale.swc,
> frameworks/js/libs/MXRoyaleJS.swc,
>  and frameworks/js/libs/SparkRoyaleJS.swc from their library-paths (or
> from the file system).
>
> -Updates to the RELEASE_NOTES discovered after this file was packaged into
> the release artifacts can be found here:
> +Updates to the RELEASE_NOTES made after this file was packaged into the
> release artifacts can be found here:
>
>  https://github.com/apache/royale-asjs/wiki/Release-Notes-0.9.4
>
> @@ -79,7 +79,7 @@ Apache Royale 0.9.2
>  - Fixed Maven distribution so you can use in IDEs like VSCode, Moonshine
> and more.
>- https://github.com/apache/royale-asjs/issues/125
>
> -Updates to the RELEASE_NOTES discovered after this file was packaged into
> the release artifacts can be found here:
> +Updates to the RELEASE_NOTES made after this file was packaged into the
> release artifacts can be found here:
>
>  https://github.com/apache/royale-asjs/wiki/Release-Notes-0.9.2
>
> @@ -88,7 +88,7 @@ Apache Royale 0.9.1
>
>  - The ASDoc example was upgraded to look better, show events, and provide
> permalinks.
>
> -Updates to the RELEASE_NOTES discovered after this file was packaged into
> the release artifacts can be found here:
> +Updates to the RELEASE_NOTES made after this file was packaged into the
> release artifacts can be found here:
>
>  https://github.com/apache/royale-asjs/wiki/Release-Notes-0.9.1
>
> @@ -102,7 +102,7 @@ without Flash.
>  Apache Royale was previously released by the Apache Flex project.  You can
>  see RELEASE_NOTES for earlier releases in the Apache Flex releases.
>
> -Updates to the RELEASE_NOTES discovered after this file was packaged into
> the release artifacts can be found here:
> +Updates to the RELEASE_NOTES made after this file was packaged into the
> release artifacts can be found here:
>
>  https://github.com/apache/royale-asjs/wiki/Release-Notes-0.9.0
>
>
>

-- 

Piotr Zarzycki

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


Discuss of release steps preparation

2019-09-14 Thread Piotr Zarzycki
Hi Carlos,

I see you did commit to 0.9.6 branch, so we are good unless there is
something left in develop which should I pick. I will review all of that on
Monday.

Thanks,
Piotr

On Sat, Sep 14, 2019, 5:26 PM Carlos Rovira  wrote:

> Hi Piotr,
>
> seems there was a little confusion here and Greg and I did the changes in
> the release version of RELEASE_NOTES.
> Hope you can merge both in your process. I followed my changes since
> December to try to bring all relevant things done.
> Thanks
>
> El sáb., 14 sept. 2019 a las 15:39, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > Hi Greg,
> >
> > I'm sorry for a late response. I'm going to take what's develop has in it
> > on Monday by cherry picking - to do not break release branch, so where
> you
> > commit it will be good and won't miss it.
> >
> > Thanks,
> > Piotr
> >
> > pt., 13 wrz 2019 o 19:24 Greg Dove  napisał(a):
> >
> > > Hi Piotr,
> > >
> > > I'm not so familiar with the release process. Do you want additions to
> go
> > > directly into the release branch or should that be added to develop
> > > (assuming you would merge into release)?
> > >
> > > I see Josh added note about RoyalUnit in develop [1], which is not yet
> in
> > > release.[2] . So perhaps you will merge from develop? I'm not sure how
> > this
> > > all needs to work.
> > >
> > > I'm thinking to add the following to 0.9.6 release notes (changes since
> > > 0.9.4) for some of the things I worked on:
> > >
> > > -Improvements to AMF / RemoteObject Support
> > > -AMFBinaryData api now matches flash.utils.ByteArray, (the missing
> > feature
> > > is non-UTF String encoding support). It therefore now works for deep
> > > cloning via readObject/writeObject and registerClassAlias.
> > > -Updates to Royale collections library with support for sorting and
> > > filtering via ArrayListView. Simple example added to Tour de Jewel
> > > -A conforming runtime implementation of AS3 Vector (typed Arrays) was
> > added
> > > for javascript output, with options for avoiding certain runtime
> checks.
> > > -int, uint, Class are now represented as simple, distinct types (Class
> is
> > > now not 'Object', int is now not 'Number' for example), and these
> support
> > > indirect 'as' or 'is' type checking and instantiation, matching swf
> > > behavior.
> > > -General Improvements and additions in Reflection library
> > > -New Apache Royale Crux MVC/DI/IOC application architecture library
> > (based
> > > on Swiz Framework) was added, with some simple examples
> > >
> > > If it's too late to add those, no worries, I can add that to the
> 'Updates
> > > to the RELEASE_NOTES discovered after this file was packaged' wiki
> > >
> > > 1. https://github.com/apache/royale-asjs/blob/develop/RELEASE_NOTES.md
> > > 2.
> > >
> >
> https://github.com/apache/royale-asjs/blob/release/0.9.6/RELEASE_NOTES.md
> > >
> > >
> > > Thanks,
> > > Greg
> > >
> > > On Fri, Sep 13, 2019 at 8:49 PM Piotr Zarzycki <
> > piotrzarzyck...@gmail.com>
> > > wrote:
> > >
> > > > Hi Guys,
> > > >
> > > > I would like to cut RC1 again on Monday, so if anything should be
> > tested
> > > or
> > > > added please do so before Monday.
> > > >
> > > > Let me know if anything is against that.
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > On Fri, Sep 13, 2019, 12:32 AM Alex Harui 
> > > > wrote:
> > > >
> > > > > I pushed changes to update the config.xml files.  It seemed to work
> > for
> > > > > me.  Try beta10 if you want to test it.
> > > > >
> > > > > npm install  @apache-royale/royale-js-swf@0.9.6-beta10 -g
> > > > >
> > > > > Thanks,
> > > > > -Alex
> > > > >
> > > > > On 9/12/19, 10:56 AM, "Alex Harui" 
> > wrote:
> > > > >
> > > > > I guess that’s expected.  I didn’t realize I had a
> > > PLAYERGLOBAL_HOME
> > > > > environment variable that was overriding.
> > > > >
> > > > > The post install script would have to go replace the
> > target-player
> > > in
> > > > > every -config.xml file (like royale-config.xml).  If yo

  1   2   3   4   5   6   7   8   9   10   >