Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-10-10 Thread Carlos Rovira
Hi,

yes, I already did some days ago an uploaded to website
If you search for some new class (like jewel SimpleButton) it appears now.



El jue., 10 oct. 2019 a las 11:49, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> 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" <
> piotrzarzyck...@gmail.com
> > >
> > > >> 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]
> > > >> >
> > > >>
> > >
> >
> 

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

Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-10-07 Thread Carlos Rovira
Hi Piotr,
yes, I'll do in next few hours.
thanks.

El lun., 7 oct. 2019 a las 9:54, Piotr Zarzycki ()
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 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 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.
> >> > > 

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

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" 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" <
> piotrzarzyck...@gmail.com>
> > wrote:
> > >
> > > Those are the steps from the script which need to be
> done still:
> > >
> > > 1)  
> > > 2) 
> > > 3) 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-10-04 Thread Alex Harui
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" 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:
> 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-10-04 Thread Alex Harui
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%7Cb3dac62555b84b704da308d748f2d525%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058080114668654sdata=Eabe%2BihRxhaEOgJlRj3XwIL%2BlidBAd5FTFhVoHfXBoM%3Dreserved=0
> [2]
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F0zvoudata=02%7C01%7Caharui%40adobe.com%7Cb3dac62555b84b704da308d748f2d525%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058080114668654sdata=A16mYpPcwNwWhDp7UcWnEPBazsYxcUUvpfGVXJw3xrs%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%7Cb3dac62555b84b704da308d748f2d525%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058080114668654sdata=on7rGMQu6TJkkyOZlBNYViAEL9BoZvMzFs0W1VR64IU%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%7Cb3dac62555b84b704da308d748f2d525%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058080114678648sdata=rhUFPvh70ZPm3pi04pnf7HFxZNfTaNcOFe88JndpEmU%3Dreserved=0
> > >
> > > Thanks,
> > 

[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].
> > >>
> > >> 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%7Ce698bee1f6c14909189a08d748ba43bf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637057837153205594sdata=yusB%2Bj5z5%2BZZsOFkUS8X4FKK0OYJnRK0EvTf9aBK7Uo%3Dreserved=0
> 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-10-04 Thread Alex Harui
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 
> 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 
> > 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%7Ce698bee1f6c14909189a08d748ba43bf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637057837153205594sdata=yusB%2Bj5z5%2BZZsOFkUS8X4FKK0OYJnRK0EvTf9aBK7Uo%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  

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]
> >>> >
> >>>
> >>> The login and password is available in the private@ archives.
> >>>
> >>>
> >>> > In mentioned lines in the stacktrace I have:
> >>> >
> >>> > Line 1088:
> >>> > 
> >>> >
> >>> > Line 1216:
> >>> >  failonerror="true" >
> >>> > 
> >>> > 
> >>> >  >>> />
> >>> > 
> >>> >
> >>> > [1]
> >>>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F15biudata=02%7C01%7Caharui%40adobe.com%7Cc21097df22b0426c28a808d747dea04e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637056893810216809sdata=Rh%2BpFQBRbL6mWzbRaSdIWJV3zA1N0rjMbHDUTGGLzsA%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 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-10-03 Thread Alex Harui
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]
>>> >
>>>
>>> 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%7Cc21097df22b0426c28a808d747dea04e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637056893810216809sdata=Rh%2BpFQBRbL6mWzbRaSdIWJV3zA1N0rjMbHDUTGGLzsA%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://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Cc21097df22b0426c28a808d747dea04e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637056893810216809sdata=WdrjOKyp0zKKmGO6QoZlKhSv%2B2l5lJPwSd6jRl7Lyu4%3Dreserved=0
>> 

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
>> *
>>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>


-- 

Piotr Zarzycki

Patreon: *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
> *
>


-- 

Piotr Zarzycki

Patreon: *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
*


Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-10-02 Thread Alex Harui
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 



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

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
*


Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-10-01 Thread OmPrakash Muppirala
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
> >*
>
>
>


Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-10-01 Thread Alex Harui
Releasecandidate.xml can't do steps on repository.apache.org.  It will remind 
you to go there and release the staged artifacts.

-Alex

On 10/1/19, 6:55 AM, "Piotr Zarzycki"  wrote:

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://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7C6393850c281646e4a2fd08d74676fc91%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055349164603152sdata=2bHGyBtNo%2Fae9L07W688ICEXmgEMk9tHNY63WzHcv%2Bw%3Dreserved=0
>>> > 
*
>>>
>>>
>>
>> --
>>
>> Piotr Zarzycki
>>
>> Patreon: 
*https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7C6393850c281646e4a2fd08d74676fc91%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055349164603152sdata=2bHGyBtNo%2Fae9L07W688ICEXmgEMk9tHNY63WzHcv%2Bw%3Dreserved=0
>> 
*
>>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: 
*https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7C6393850c281646e4a2fd08d74676fc91%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055349164603152sdata=2bHGyBtNo%2Fae9L07W688ICEXmgEMk9tHNY63WzHcv%2Bw%3Dreserved=0
> 
*
>


-- 

Piotr Zarzycki

Patreon: 
*https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7C6393850c281646e4a2fd08d74676fc91%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055349164603152sdata=2bHGyBtNo%2Fae9L07W688ICEXmgEMk9tHNY63WzHcv%2Bw%3Dreserved=0

*




Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-10-01 Thread Alex Harui
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

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


-- 

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

*




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
>>> > *
>>>
>>>
>>
>> --
>>
>> Piotr Zarzycki
>>
>> Patreon: *https://www.patreon.com/piotrzarzycki
>> *
>>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>


-- 

Piotr Zarzycki

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


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
>> > *
>>
>>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>


-- 

Piotr Zarzycki

Patreon: *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
> > *
>
>

-- 

Piotr Zarzycki

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


Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-09-28 Thread Harbs
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 
> napisał(a):
> 
>> This is the discussion thread.
>> 
>> Thanks,
>> Piotr
> 
> 
> 
> -- 
> 
> Piotr Zarzycki
> 
> Patreon: *https://www.patreon.com/piotrzarzycki
> *



Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-09-28 Thread Carlos Rovira
Hi Alex,

About Vars: I have:

   -  ANT_HOME
   - MAVEN_OPTS
   - JAVA_HOME,
   - GOOG_HOME
   - ROYALE_HOME
   - ROYALE_COMPILER_HOME
   - ROYALE_TYPEDEFS_HOME
   - FLEX_HOME (I supposed this last one can be removed too, but didn't
   notice

I commented

   - PLAYERGLOBAL_HOME
   - PLAYERGLOBAL_VERSION
   - FLASHPLAYER_DEBUGGER
   - AIR_HOME


This is the entire log of my latest failed: https://paste.apache.org/23e88

The settings that Piotr is this: https://paste.apache.org/gfift

Thanks


Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-09-28 Thread Alex Harui
What environment variables are set?
What settings did Piotr recommend and what did you actually use?

If you can post a link to the entire log it might help.  For example, if you 
didn't see the ASCII art for "FLEX" then the extensions did not kick in.  By 
the time you get around to building a Theme, the playerglobal should have been 
brought down by some other SWC.

-Alex

On 9/27/19, 6:24 PM, "Carlos Rovira"  wrote:

Hi,

ok, seems the latest test didn't work. it failed here:

[INFO]


[INFO] BUILD FAILURE

[INFO]


[INFO] Total time:  01:38 min

[INFO] Finished at: 2019-09-28T03:13:17+02:00

[INFO]


*[ERROR] Failed to execute goal
org.apache.royale.compiler:royale-maven-plugin:0.9.6:compile-as
(default-compile-as) on project BasicTheme: Could not resolve dependencies
for project org.apache.royale.framework:BasicTheme:swc:0.9.6: Could not
find artifact com.adobe.air.framework:airglobal:swc:20.0 in apache-release *

(https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Freleasesdata=02%7C01%7Caharui%40adobe.com%7Cd2752bf4f655470293ec08d743b29795%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637052306637926610sdata=6IPEWelySZ23%2FNOSuURLUBBP7Y0OVnfBnwUzIYT6BwE%3Dreserved=0)
 -> [Help 1]

[ERROR]

[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.

[ERROR] Re-run Maven using the -X switch to enable full debug logging.

[ERROR]

[ERROR] For more information about the errors and possible solutions,
please read the following articles:

[ERROR] [Help 1]

https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FMAVEN%2FMojoExecutionExceptiondata=02%7C01%7Caharui%40adobe.com%7Cd2752bf4f655470293ec08d743b29795%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637052306637926610sdata=ACIxw1nGBWU1TZl5UYlS4gdBybLC9GHQy%2Fh9bCSxsR8%3Dreserved=0

[ERROR]

[ERROR] After correcting the problems, you can resume the build with the
command

[ERROR]   mvn  -rf :BasicTheme


BUILD FAILED

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

/Users/carlosrovira/Downloads/testrc3/ApproveRoyale.xml:811: exec returned:
1


Total time: 30 minutes 54 seconds


Maybe some more refinement should be done in BasicTheme?
Also the following Discuss threads could have more instructions about
removing env vars for beginners trying to use the process




El sáb., 28 sept. 2019 a las 3:05, Carlos Rovira ()
escribió:

> Hi,
>
> thanks Josh and Alex for your help on this. I finally get the approve xml
> method to work on my machine :)
>
> I need to :
> - Use the latest Aprove xml
> - remove my AIR_HOME and FLASH (player and debugger) env vars.
> - and use the settings provided by Piotr. Although I'm making a new try
> now with my own setting to see if that is not needed trying to understand
> finally what's really needed or not.
>
> Since the process is long (more than 50' in my machine, I'll probably
> report here tomorrow if this final experiement finally worked :).
>
>
> El jue., 26 sept. 2019 a las 23:47, Alex Harui 
()
> escribió:
>
>> Thanks for trying it.  I just updated the ApproveRoyale.xml linked to in
>> the vote thread to try to eliminate people getting the wrong one..
>>
>> -Alex
>>
>> On 9/26/19, 1:48 PM, "Josh Tynjala"  wrote:
>>
>> Thank you, Alex! I tried your changes with adobe/royale artifacts
>> deleted
>> from .m2, and I was able to get through both js and js-swf builds
>> successfully.
>>
>> Carlos, I think that these changes will allow you to get through the
>> process now too.
>>
>> For everyone's convenience, here's a link to the latest
>> ApproveRoyale.xml
>> script for 0.9.6:
>>
>>
>> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fblob%2Frelease%2F0.9.6%2FApproveRoyale.xmldata=02%7C01%7Caharui%40adobe.com%7Cd2752bf4f655470293ec08d743b29795%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637052306637926610sdata=Y9AXfwVZ%2FsOgvV71l%2FE5qj8qkNdcvLiOJpgIzxM%2FXK8%3Dreserved=0
>>
>> Use this one instead of the one linked from the [VOTE] thread. Just
>> to be
>> clear, since ApproveRoyale.xml is a convenience script for PMC
>> members to
>> aid with the 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-09-27 Thread Carlos Rovira
Hi,

ok, seems the latest test didn't work. it failed here:

[INFO]


[INFO] BUILD FAILURE

[INFO]


[INFO] Total time:  01:38 min

[INFO] Finished at: 2019-09-28T03:13:17+02:00

[INFO]


*[ERROR] Failed to execute goal
org.apache.royale.compiler:royale-maven-plugin:0.9.6:compile-as
(default-compile-as) on project BasicTheme: Could not resolve dependencies
for project org.apache.royale.framework:BasicTheme:swc:0.9.6: Could not
find artifact com.adobe.air.framework:airglobal: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/MojoExecutionException

[ERROR]

[ERROR] After correcting the problems, you can resume the build with the
command

[ERROR]   mvn  -rf :BasicTheme


BUILD FAILED

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

/Users/carlosrovira/Downloads/testrc3/ApproveRoyale.xml:811: exec returned:
1


Total time: 30 minutes 54 seconds


Maybe some more refinement should be done in BasicTheme?
Also the following Discuss threads could have more instructions about
removing env vars for beginners trying to use the process




El sáb., 28 sept. 2019 a las 3:05, Carlos Rovira ()
escribió:

> Hi,
>
> thanks Josh and Alex for your help on this. I finally get the approve xml
> method to work on my machine :)
>
> I need to :
> - Use the latest Aprove xml
> - remove my AIR_HOME and FLASH (player and debugger) env vars.
> - and use the settings provided by Piotr. Although I'm making a new try
> now with my own setting to see if that is not needed trying to understand
> finally what's really needed or not.
>
> Since the process is long (more than 50' in my machine, I'll probably
> report here tomorrow if this final experiement finally worked :).
>
>
> El jue., 26 sept. 2019 a las 23:47, Alex Harui ()
> escribió:
>
>> Thanks for trying it.  I just updated the ApproveRoyale.xml linked to in
>> the vote thread to try to eliminate people getting the wrong one..
>>
>> -Alex
>>
>> On 9/26/19, 1:48 PM, "Josh Tynjala"  wrote:
>>
>> Thank you, Alex! I tried your changes with adobe/royale artifacts
>> deleted
>> from .m2, and I was able to get through both js and js-swf builds
>> successfully.
>>
>> Carlos, I think that these changes will allow you to get through the
>> process now too.
>>
>> For everyone's convenience, here's a link to the latest
>> ApproveRoyale.xml
>> script for 0.9.6:
>>
>>
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fblob%2Frelease%2F0.9.6%2FApproveRoyale.xmldata=02%7C01%7Caharui%40adobe.com%7C42a3ce7a5d684b82c6c108d742c2ce68%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637051276838990699sdata=djQYfxCvBrh5dkSnZI7ocryl515uHvkLk7qkXOFy2WQ%3Dreserved=0
>>
>> Use this one instead of the one linked from the [VOTE] thread. Just
>> to be
>> clear, since ApproveRoyale.xml is a convenience script for PMC
>> members to
>> aid with the release voting process, and not something that end users
>> or
>> potential contributors need to use, these latest changes to
>> ApproveRoyale.xml don't require the creation of a new RC.
>>
>> --
>> Josh Tynjala
>> Bowler Hat LLC <
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7C42a3ce7a5d684b82c6c108d742c2ce68%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637051276838990699sdata=I4Hl9o57gg8F3Yk3TlzTYQE3eJTYFLdzj7xsfpgPfnw%3Dreserved=0
>> >
>>
>>
>> On Thu, Sep 26, 2019 at 11:34 AM Alex Harui > >
>> wrote:
>>
>> > Yeah, I just saw that myself.  That's because I didn't merge in my
>> changes
>> > correctly.  I just pushed one that seems to be working better.
>> >
>> > -Alex
>> >
>> > On 9/26/19, 10:27 AM, "Josh Tynjala" 
>> wrote:
>> >
>> > Thanks, Alex. The ApproveRoyale.mxml from the latest
>> release/0.9.6 is
>> > working for me if I delete all adobe/royale artifacts from my
>> .m2, and
>> > if I
>> > omit -Duse-flash=true. However, with -Duse-flash=true, I'm
>> seeing
>> > compiler
>> > errors when Maven tries to build the SWF version of Binding.swc.
>> >
>> > A couple of examples of the errors (there are many more):
>> >
>> >
>> >
>> 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-09-27 Thread Carlos Rovira
Hi,

thanks Josh and Alex for your help on this. I finally get the approve xml
method to work on my machine :)

I need to :
- Use the latest Aprove xml
- remove my AIR_HOME and FLASH (player and debugger) env vars.
- and use the settings provided by Piotr. Although I'm making a new try now
with my own setting to see if that is not needed trying to understand
finally what's really needed or not.

Since the process is long (more than 50' in my machine, I'll probably
report here tomorrow if this final experiement finally worked :).


El jue., 26 sept. 2019 a las 23:47, Alex Harui ()
escribió:

> Thanks for trying it.  I just updated the ApproveRoyale.xml linked to in
> the vote thread to try to eliminate people getting the wrong one..
>
> -Alex
>
> On 9/26/19, 1:48 PM, "Josh Tynjala"  wrote:
>
> Thank you, Alex! I tried your changes with adobe/royale artifacts
> deleted
> from .m2, and I was able to get through both js and js-swf builds
> successfully.
>
> Carlos, I think that these changes will allow you to get through the
> process now too.
>
> For everyone's convenience, here's a link to the latest
> ApproveRoyale.xml
> script for 0.9.6:
>
>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fblob%2Frelease%2F0.9.6%2FApproveRoyale.xmldata=02%7C01%7Caharui%40adobe.com%7C42a3ce7a5d684b82c6c108d742c2ce68%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637051276838990699sdata=djQYfxCvBrh5dkSnZI7ocryl515uHvkLk7qkXOFy2WQ%3Dreserved=0
>
> Use this one instead of the one linked from the [VOTE] thread. Just to
> be
> clear, since ApproveRoyale.xml is a convenience script for PMC members
> to
> aid with the release voting process, and not something that end users
> or
> potential contributors need to use, these latest changes to
> ApproveRoyale.xml don't require the creation of a new RC.
>
> --
> Josh Tynjala
> Bowler Hat LLC <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7C42a3ce7a5d684b82c6c108d742c2ce68%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637051276838990699sdata=I4Hl9o57gg8F3Yk3TlzTYQE3eJTYFLdzj7xsfpgPfnw%3Dreserved=0
> >
>
>
> On Thu, Sep 26, 2019 at 11:34 AM Alex Harui 
> wrote:
>
> > Yeah, I just saw that myself.  That's because I didn't merge in my
> changes
> > correctly.  I just pushed one that seems to be working better.
> >
> > -Alex
> >
> > On 9/26/19, 10:27 AM, "Josh Tynjala" 
> wrote:
> >
> > Thanks, Alex. The ApproveRoyale.mxml from the latest
> release/0.9.6 is
> > working for me if I delete all adobe/royale artifacts from my
> .m2, and
> > if I
> > omit -Duse-flash=true. However, with -Duse-flash=true, I'm seeing
> > compiler
> > errors when Maven tries to build the SWF version of Binding.swc.
> >
> > A couple of examples of the errors (there are many more):
> >
> >
> >
> /Users/joshtynjala/Desktop/royale/apache-royale-0.9.6-maven-src/royale-asjs/frameworks/projects/Binding/src/main/royale/org/apache/royale/binding/ApplicationDataBinding.as(23):
> > col: 12 Warning: Definition org.apache.royale.core.IBinding
> could not
> > be
> > found.
> >
> > import org.apache.royale.core.IBinding;
> >^
> >
> >
> >
> /Users/joshtynjala/Desktop/royale/apache-royale-0.9.6-maven-src/royale-asjs/frameworks/projects/Binding/src/main/royale/org/apache/royale/binding/ApplicationDataBinding.as(27):
> > col: 12 Warning: Definition org.apache.royale.core.IBead could
> not be
> > found.
> >
> > import org.apache.royale.core.IBead;
> >^
> >
> > Could it be because you removed the asjs_mvn_defines from
> > ApproveRoyale.xml
> > in your new commit that added inputstring="Yes"? I added that
> back in,
> > and
> > my change seemed to allow me to finish the script successfully
> with
> > -Duse-flash=true.
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC <
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7C42a3ce7a5d684b82c6c108d742c2ce68%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637051276838990699sdata=I4Hl9o57gg8F3Yk3TlzTYQE3eJTYFLdzj7xsfpgPfnw%3Dreserved=0
> > >
> >
> >
> > On Thu, Sep 26, 2019 at 12:47 AM Alex Harui
> 
> > wrote:
> >
> > > Looks like I missed a commit.  I just pushed the
> ApproveRoyale.xml I
> > was
> > > using to the release branch.
> > >
> > > Try that one and see if it works better.  It shouldn't require
> the
> > > workaround you used.
> > >
> > > Thanks,
> > > -Alex
> > >
> > > On 9/25/19, 4:16 PM, "Josh Tynjala"  >
> > wrote:
> > >
>   

Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-09-26 Thread Alex Harui
Thanks for trying it.  I just updated the ApproveRoyale.xml linked to in the 
vote thread to try to eliminate people getting the wrong one..

-Alex

On 9/26/19, 1:48 PM, "Josh Tynjala"  wrote:

Thank you, Alex! I tried your changes with adobe/royale artifacts deleted
from .m2, and I was able to get through both js and js-swf builds
successfully.

Carlos, I think that these changes will allow you to get through the
process now too.

For everyone's convenience, here's a link to the latest ApproveRoyale.xml
script for 0.9.6:


https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fblob%2Frelease%2F0.9.6%2FApproveRoyale.xmldata=02%7C01%7Caharui%40adobe.com%7C42a3ce7a5d684b82c6c108d742c2ce68%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637051276838990699sdata=djQYfxCvBrh5dkSnZI7ocryl515uHvkLk7qkXOFy2WQ%3Dreserved=0

Use this one instead of the one linked from the [VOTE] thread. Just to be
clear, since ApproveRoyale.xml is a convenience script for PMC members to
aid with the release voting process, and not something that end users or
potential contributors need to use, these latest changes to
ApproveRoyale.xml don't require the creation of a new RC.

--
Josh Tynjala
Bowler Hat LLC 



On Thu, Sep 26, 2019 at 11:34 AM Alex Harui 
wrote:

> Yeah, I just saw that myself.  That's because I didn't merge in my changes
> correctly.  I just pushed one that seems to be working better.
>
> -Alex
>
> On 9/26/19, 10:27 AM, "Josh Tynjala"  wrote:
>
> Thanks, Alex. The ApproveRoyale.mxml from the latest release/0.9.6 is
> working for me if I delete all adobe/royale artifacts from my .m2, and
> if I
> omit -Duse-flash=true. However, with -Duse-flash=true, I'm seeing
> compiler
> errors when Maven tries to build the SWF version of Binding.swc.
>
> A couple of examples of the errors (there are many more):
>
>
> 
/Users/joshtynjala/Desktop/royale/apache-royale-0.9.6-maven-src/royale-asjs/frameworks/projects/Binding/src/main/royale/org/apache/royale/binding/ApplicationDataBinding.as(23):
> col: 12 Warning: Definition org.apache.royale.core.IBinding could not
> be
> found.
>
> import org.apache.royale.core.IBinding;
>^
>
>
> 
/Users/joshtynjala/Desktop/royale/apache-royale-0.9.6-maven-src/royale-asjs/frameworks/projects/Binding/src/main/royale/org/apache/royale/binding/ApplicationDataBinding.as(27):
> col: 12 Warning: Definition org.apache.royale.core.IBead could not be
> found.
>
> import org.apache.royale.core.IBead;
>^
>
> Could it be because you removed the asjs_mvn_defines from
> ApproveRoyale.xml
> in your new commit that added inputstring="Yes"? I added that back in,
> and
> my change seemed to allow me to finish the script successfully with
> -Duse-flash=true.
>
> --
> Josh Tynjala
> Bowler Hat LLC <
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7C42a3ce7a5d684b82c6c108d742c2ce68%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637051276838990699sdata=I4Hl9o57gg8F3Yk3TlzTYQE3eJTYFLdzj7xsfpgPfnw%3Dreserved=0
> >
>
>
> On Thu, Sep 26, 2019 at 12:47 AM Alex Harui 
> wrote:
>
> > Looks like I missed a commit.  I just pushed the ApproveRoyale.xml I
> was
> > using to the release branch.
> >
> > Try that one and see if it works better.  It shouldn't require the
> > workaround you used.
> >
> > Thanks,
> > -Alex
> >
> > On 9/25/19, 4:16 PM, "Josh Tynjala" 
> wrote:
> >
> > To get the system property working with ApproveRoyale.xml, I
> added the
> > following line to each of the mvn commands in my local copy of
> > ApproveRoyale.xml:
> >
> >  >
> >
> 
value="-Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=499700b6"/>
> >
> > This should work for anyone using Bash's yes command to quickly
> > approve the
> > license headers (after you've already done it once manually, of
> > course).
> >
> > yes | ant -e -f ApproveRoyale.xml -Drelease.version=0.9.6 -Drc=3
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC <
> >
> 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-09-26 Thread Josh Tynjala
Thank you, Alex! I tried your changes with adobe/royale artifacts deleted
from .m2, and I was able to get through both js and js-swf builds
successfully.

Carlos, I think that these changes will allow you to get through the
process now too.

For everyone's convenience, here's a link to the latest ApproveRoyale.xml
script for 0.9.6:

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

Use this one instead of the one linked from the [VOTE] thread. Just to be
clear, since ApproveRoyale.xml is a convenience script for PMC members to
aid with the release voting process, and not something that end users or
potential contributors need to use, these latest changes to
ApproveRoyale.xml don't require the creation of a new RC.

--
Josh Tynjala
Bowler Hat LLC 


On Thu, Sep 26, 2019 at 11:34 AM Alex Harui 
wrote:

> Yeah, I just saw that myself.  That's because I didn't merge in my changes
> correctly.  I just pushed one that seems to be working better.
>
> -Alex
>
> On 9/26/19, 10:27 AM, "Josh Tynjala"  wrote:
>
> Thanks, Alex. The ApproveRoyale.mxml from the latest release/0.9.6 is
> working for me if I delete all adobe/royale artifacts from my .m2, and
> if I
> omit -Duse-flash=true. However, with -Duse-flash=true, I'm seeing
> compiler
> errors when Maven tries to build the SWF version of Binding.swc.
>
> A couple of examples of the errors (there are many more):
>
>
> /Users/joshtynjala/Desktop/royale/apache-royale-0.9.6-maven-src/royale-asjs/frameworks/projects/Binding/src/main/royale/org/apache/royale/binding/ApplicationDataBinding.as(23):
> col: 12 Warning: Definition org.apache.royale.core.IBinding could not
> be
> found.
>
> import org.apache.royale.core.IBinding;
>^
>
>
> /Users/joshtynjala/Desktop/royale/apache-royale-0.9.6-maven-src/royale-asjs/frameworks/projects/Binding/src/main/royale/org/apache/royale/binding/ApplicationDataBinding.as(27):
> col: 12 Warning: Definition org.apache.royale.core.IBead could not be
> found.
>
> import org.apache.royale.core.IBead;
>^
>
> Could it be because you removed the asjs_mvn_defines from
> ApproveRoyale.xml
> in your new commit that added inputstring="Yes"? I added that back in,
> and
> my change seemed to allow me to finish the script successfully with
> -Duse-flash=true.
>
> --
> Josh Tynjala
> Bowler Hat LLC <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7Cafc4989b7d61427d849a08d742a6bc57%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637051156201507168sdata=aZr5SvuHu%2Fo%2BWc1EF7MRosekWVMeAqC9yudOoLTe3uo%3Dreserved=0
> >
>
>
> On Thu, Sep 26, 2019 at 12:47 AM Alex Harui 
> wrote:
>
> > Looks like I missed a commit.  I just pushed the ApproveRoyale.xml I
> was
> > using to the release branch.
> >
> > Try that one and see if it works better.  It shouldn't require the
> > workaround you used.
> >
> > Thanks,
> > -Alex
> >
> > On 9/25/19, 4:16 PM, "Josh Tynjala" 
> wrote:
> >
> > To get the system property working with ApproveRoyale.xml, I
> added the
> > following line to each of the mvn commands in my local copy of
> > ApproveRoyale.xml:
> >
> >  >
> >
> value="-Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=499700b6"/>
> >
> > This should work for anyone using Bash's yes command to quickly
> > approve the
> > license headers (after you've already done it once manually, of
> > course).
> >
> > yes | ant -e -f ApproveRoyale.xml -Drelease.version=0.9.6 -Drc=3
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC <
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7Cafc4989b7d61427d849a08d742a6bc57%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637051156201507168sdata=aZr5SvuHu%2Fo%2BWc1EF7MRosekWVMeAqC9yudOoLTe3uo%3Dreserved=0
> > >
> >
> >
> > On Wed, Sep 25, 2019 at 2:58 PM Josh Tynjala <
> > joshtynj...@bowlerhat.dev>
> > wrote:
> >
> > > I deleted all com.adobe artifacts in my Maven .m2 folder, and
> I can
> > see
> > > the prompt to accept the license for the Adobe dependencies.
> > >
> > > The build output suggests that you can set a system property to
> > accept the
> > > agreement, so I tried adding that property to my command, like
> this:
> > >
> > > ant -e -f ApproveRoyale.xml -Drelease.version=0.9.6 -Drc=3
> > >
> >
> -Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=
> > >
> > > (Where  is replaced by my real system ID)
> > >
> > > However, it still asked me to accept the agreement. Perhaps
> this
>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-09-26 Thread Alex Harui
Yeah, I just saw that myself.  That's because I didn't merge in my changes 
correctly.  I just pushed one that seems to be working better.

-Alex

On 9/26/19, 10:27 AM, "Josh Tynjala"  wrote:

Thanks, Alex. The ApproveRoyale.mxml from the latest release/0.9.6 is
working for me if I delete all adobe/royale artifacts from my .m2, and if I
omit -Duse-flash=true. However, with -Duse-flash=true, I'm seeing compiler
errors when Maven tries to build the SWF version of Binding.swc.

A couple of examples of the errors (there are many more):


/Users/joshtynjala/Desktop/royale/apache-royale-0.9.6-maven-src/royale-asjs/frameworks/projects/Binding/src/main/royale/org/apache/royale/binding/ApplicationDataBinding.as(23):
col: 12 Warning: Definition org.apache.royale.core.IBinding could not be
found.

import org.apache.royale.core.IBinding;
   ^


/Users/joshtynjala/Desktop/royale/apache-royale-0.9.6-maven-src/royale-asjs/frameworks/projects/Binding/src/main/royale/org/apache/royale/binding/ApplicationDataBinding.as(27):
col: 12 Warning: Definition org.apache.royale.core.IBead could not be found.

import org.apache.royale.core.IBead;
   ^

Could it be because you removed the asjs_mvn_defines from ApproveRoyale.xml
in your new commit that added inputstring="Yes"? I added that back in, and
my change seemed to allow me to finish the script successfully with
-Duse-flash=true.

--
Josh Tynjala
Bowler Hat LLC 



On Thu, Sep 26, 2019 at 12:47 AM Alex Harui 
wrote:

> Looks like I missed a commit.  I just pushed the ApproveRoyale.xml I was
> using to the release branch.
>
> Try that one and see if it works better.  It shouldn't require the
> workaround you used.
>
> Thanks,
> -Alex
>
> On 9/25/19, 4:16 PM, "Josh Tynjala"  wrote:
>
> To get the system property working with ApproveRoyale.xml, I added the
> following line to each of the mvn commands in my local copy of
> ApproveRoyale.xml:
>
> 
> 
value="-Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=499700b6"/>
>
> This should work for anyone using Bash's yes command to quickly
> approve the
> license headers (after you've already done it once manually, of
> course).
>
> yes | ant -e -f ApproveRoyale.xml -Drelease.version=0.9.6 -Drc=3
>
> --
> Josh Tynjala
> Bowler Hat LLC <
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7Cafc4989b7d61427d849a08d742a6bc57%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637051156201507168sdata=aZr5SvuHu%2Fo%2BWc1EF7MRosekWVMeAqC9yudOoLTe3uo%3Dreserved=0
> >
>
>
> On Wed, Sep 25, 2019 at 2:58 PM Josh Tynjala <
> joshtynj...@bowlerhat.dev>
> wrote:
>
> > I deleted all com.adobe artifacts in my Maven .m2 folder, and I can
> see
> > the prompt to accept the license for the Adobe dependencies.
> >
> > The build output suggests that you can set a system property to
> accept the
> > agreement, so I tried adding that property to my command, like this:
> >
> > ant -e -f ApproveRoyale.xml -Drelease.version=0.9.6 -Drc=3
> >
> 
-Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=
> >
> > (Where  is replaced by my real system ID)
> >
> > However, it still asked me to accept the agreement. Perhaps this
> system
> > property isn't getting inherited by the Maven build.
> >
> > I am using the RC3 ApproveRoyale.xml linked from the Vote thread,
> and not
> > an older one.
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC <
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7Cafc4989b7d61427d849a08d742a6bc57%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637051156201507168sdata=aZr5SvuHu%2Fo%2BWc1EF7MRosekWVMeAqC9yudOoLTe3uo%3Dreserved=0
> >
> >
> >
> > On Wed, Sep 25, 2019 at 11:25 AM Carlos Rovira <
> carlosrov...@apache.org>
> > 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, 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-09-26 Thread Josh Tynjala
Thanks, Alex. The ApproveRoyale.mxml from the latest release/0.9.6 is
working for me if I delete all adobe/royale artifacts from my .m2, and if I
omit -Duse-flash=true. However, with -Duse-flash=true, I'm seeing compiler
errors when Maven tries to build the SWF version of Binding.swc.

A couple of examples of the errors (there are many more):

/Users/joshtynjala/Desktop/royale/apache-royale-0.9.6-maven-src/royale-asjs/frameworks/projects/Binding/src/main/royale/org/apache/royale/binding/ApplicationDataBinding.as(23):
col: 12 Warning: Definition org.apache.royale.core.IBinding could not be
found.

import org.apache.royale.core.IBinding;
   ^

/Users/joshtynjala/Desktop/royale/apache-royale-0.9.6-maven-src/royale-asjs/frameworks/projects/Binding/src/main/royale/org/apache/royale/binding/ApplicationDataBinding.as(27):
col: 12 Warning: Definition org.apache.royale.core.IBead could not be found.

import org.apache.royale.core.IBead;
   ^

Could it be because you removed the asjs_mvn_defines from ApproveRoyale.xml
in your new commit that added inputstring="Yes"? I added that back in, and
my change seemed to allow me to finish the script successfully with
-Duse-flash=true.

--
Josh Tynjala
Bowler Hat LLC 


On Thu, Sep 26, 2019 at 12:47 AM Alex Harui 
wrote:

> Looks like I missed a commit.  I just pushed the ApproveRoyale.xml I was
> using to the release branch.
>
> Try that one and see if it works better.  It shouldn't require the
> workaround you used.
>
> Thanks,
> -Alex
>
> On 9/25/19, 4:16 PM, "Josh Tynjala"  wrote:
>
> To get the system property working with ApproveRoyale.xml, I added the
> following line to each of the mvn commands in my local copy of
> ApproveRoyale.xml:
>
> 
> value="-Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=499700b6"/>
>
> This should work for anyone using Bash's yes command to quickly
> approve the
> license headers (after you've already done it once manually, of
> course).
>
> yes | ant -e -f ApproveRoyale.xml -Drelease.version=0.9.6 -Drc=3
>
> --
> Josh Tynjala
> Bowler Hat LLC <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7C69e4a3028e3e420535f808d7420e5b3a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637050501738714087sdata=hMkPguiNL2bdcHRmml%2Fjk0nEDkcn9TIaT%2BjcNV%2F7c5k%3Dreserved=0
> >
>
>
> On Wed, Sep 25, 2019 at 2:58 PM Josh Tynjala <
> joshtynj...@bowlerhat.dev>
> wrote:
>
> > I deleted all com.adobe artifacts in my Maven .m2 folder, and I can
> see
> > the prompt to accept the license for the Adobe dependencies.
> >
> > The build output suggests that you can set a system property to
> accept the
> > agreement, so I tried adding that property to my command, like this:
> >
> > ant -e -f ApproveRoyale.xml -Drelease.version=0.9.6 -Drc=3
> >
> -Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=
> >
> > (Where  is replaced by my real system ID)
> >
> > However, it still asked me to accept the agreement. Perhaps this
> system
> > property isn't getting inherited by the Maven build.
> >
> > I am using the RC3 ApproveRoyale.xml linked from the Vote thread,
> and not
> > an older one.
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7C69e4a3028e3e420535f808d7420e5b3a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637050501738724087sdata=oUzKXHUA9cU7gL5o09ultnH%2Bj7KnC%2FynBhv2J%2BNo%2FFg%3Dreserved=0
> >
> >
> >
> > On Wed, Sep 25, 2019 at 11:25 AM Carlos Rovira <
> carlosrov...@apache.org>
> > 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
> >> > > 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-09-26 Thread Alex Harui
Looks like I missed a commit.  I just pushed the ApproveRoyale.xml I was using 
to the release branch.

Try that one and see if it works better.  It shouldn't require the workaround 
you used.

Thanks,
-Alex

On 9/25/19, 4:16 PM, "Josh Tynjala"  wrote:

To get the system property working with ApproveRoyale.xml, I added the
following line to each of the mvn commands in my local copy of
ApproveRoyale.xml:



This should work for anyone using Bash's yes command to quickly approve the
license headers (after you've already done it once manually, of course).

yes | ant -e -f ApproveRoyale.xml -Drelease.version=0.9.6 -Drc=3

--
Josh Tynjala
Bowler Hat LLC 



On Wed, Sep 25, 2019 at 2:58 PM Josh Tynjala 
wrote:

> I deleted all com.adobe artifacts in my Maven .m2 folder, and I can see
> the prompt to accept the license for the Adobe dependencies.
>
> The build output suggests that you can set a system property to accept the
> agreement, so I tried adding that property to my command, like this:
>
> ant -e -f ApproveRoyale.xml -Drelease.version=0.9.6 -Drc=3
> 
-Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=
>
> (Where  is replaced by my real system ID)
>
> However, it still asked me to accept the agreement. Perhaps this system
> property isn't getting inherited by the Maven build.
>
> I am using the RC3 ApproveRoyale.xml linked from the Vote thread, and not
> an older one.
>
> --
> Josh Tynjala
> Bowler Hat LLC 

>
>
> On Wed, Sep 25, 2019 at 11:25 AM 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
>> > > 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-09-25 Thread Josh Tynjala
To get the system property working with ApproveRoyale.xml, I added the
following line to each of the mvn commands in my local copy of
ApproveRoyale.xml:



This should work for anyone using Bash's yes command to quickly approve the
license headers (after you've already done it once manually, of course).

yes | ant -e -f ApproveRoyale.xml -Drelease.version=0.9.6 -Drc=3

--
Josh Tynjala
Bowler Hat LLC 


On Wed, Sep 25, 2019 at 2:58 PM Josh Tynjala 
wrote:

> I deleted all com.adobe artifacts in my Maven .m2 folder, and I can see
> the prompt to accept the license for the Adobe dependencies.
>
> The build output suggests that you can set a system property to accept the
> agreement, so I tried adding that property to my command, like this:
>
> ant -e -f ApproveRoyale.xml -Drelease.version=0.9.6 -Drc=3
> -Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=
>
> (Where  is replaced by my real system ID)
>
> However, it still asked me to accept the agreement. Perhaps this system
> property isn't getting inherited by the Maven build.
>
> I am using the RC3 ApproveRoyale.xml linked from the Vote thread, and not
> an older one.
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>
>
> On Wed, Sep 25, 2019 at 11:25 AM 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: 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-09-25 Thread Josh Tynjala
I deleted all com.adobe artifacts in my Maven .m2 folder, and I can see the
prompt to accept the license for the Adobe dependencies.

The build output suggests that you can set a system property to accept the
agreement, so I tried adding that property to my command, like this:

ant -e -f ApproveRoyale.xml -Drelease.version=0.9.6 -Drc=3
-Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=

(Where  is replaced by my real system ID)

However, it still asked me to accept the agreement. Perhaps this system
property isn't getting inherited by the Maven build.

I am using the RC3 ApproveRoyale.xml linked from the Vote thread, and not
an older one.

--
Josh Tynjala
Bowler Hat LLC 


On Wed, Sep 25, 2019 at 11:25 AM 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] 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 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-09-25 Thread Alex Harui
It depends on what you want to test.

If you want to test the js-only (no Adobe stuff) paths, then yes, you need to 
make sure there are no Adobe environment variables:

AIR_HOME
PLAYERGLOBAL_HOME
FLASHPLAYER_DEBUGGER

If you want to test with the Adobe stuff, then you will need to set all 3 
environment variables.  I thought this was explained in the README.

Make sure you are using the latest ApproveRoyale.xml.  In theory the scripts 
uploaded it to SVN but if you are using an older one, then you will still get 
stuck in that loop about accepting the Adobe downloads.  The latest 
ApproveRoyale.xml should have a few "inputstring" attributes in it.

In theory, ApproveRoyale.xml will set -Dgenerate.swf.swcs if you have set the 
Adobe environment variables.  But if you want to skip tests, you will have to 
try to add that yourself.

HTH,
-Alex

On 9/25/19, 2:20 PM, "Carlos Rovira"  wrote:

Hi Josh,

you're right, I have AIR_HOME in my .bash_profile set, since I left all env
vars set (flex, air, playerglobal, royale)
So,
- should I remove some more in addition to AIR_HOME?

additionally:

- Should I use the settings from Piotr too?
- Should I add -Dgenerate.swf.swcs=true and -DskipTests=true ?

thanks!



El mié., 25 sept. 2019 a las 23:03, Josh Tynjala 
()
escribió:

> Carlos,
>
> Can you check to see if the AIR_HOME environment variable is set or not?
>
> If I'm understanding the logic in ApproveRoyale.xml, then you need to
> ensure that AIR_HOME is *NOT* set, unless you include -Duse-flash=true in
> your command. If AIR_HOME is set, then you should clear it. It may also be
> a good idea to clear both PLAYERGLOBAL_HOME and FLASHPLAYER_DEBUGGER too,
> just to be safe.
>
> --
> Josh Tynjala
> Bowler Hat LLC 

>
>
> On Wed, Sep 25, 2019 at 9:41 AM Carlos Rovira 
> wrote:
>
> > 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://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Freleases%2Fcom%2Fadobe%2Fflash%2Fframework%2Fplayerglobal%2F20.0%2Fplayerglobal-20.0.pomdata=02%7C01%7Caharui%40adobe.com%7C35b67c5a16164c43d24308d741fe326f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637050432341593892sdata=Fwg1B8TbdIZlGcYfsFw15xihc7H8j6281k7xTy%2Fy9aQ%3Dreserved=0
> >
> > Downloading from central:
> >
> >
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepo.maven.apache.org%2Fmaven2%2Fcom%2Fadobe%2Fflash%2Fframework%2Fplayerglobal%2F20.0%2Fplayerglobal-20.0.pomdata=02%7C01%7Caharui%40adobe.com%7C35b67c5a16164c43d24308d741fe326f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637050432341593892sdata=6g2aW%2FlTUVI%2FriS6Zs%2Bn1kKKNO9Y0fp15s1RKZtMqTs%3Dreserved=0
> >
> > [WARNING] The POM for com.adobe.flash.framework:playerglobal:swc:20.0 is
> > 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-09-25 Thread Carlos Rovira
Hi Josh,

you're right, I have AIR_HOME in my .bash_profile set, since I left all env
vars set (flex, air, playerglobal, royale)
So,
- should I remove some more in addition to AIR_HOME?

additionally:

- Should I use the settings from Piotr too?
- Should I add -Dgenerate.swf.swcs=true and -DskipTests=true ?

thanks!



El mié., 25 sept. 2019 a las 23:03, Josh Tynjala ()
escribió:

> Carlos,
>
> Can you check to see if the AIR_HOME environment variable is set or not?
>
> If I'm understanding the logic in ApproveRoyale.xml, then you need to
> ensure that AIR_HOME is *NOT* set, unless you include -Duse-flash=true in
> your command. If AIR_HOME is set, then you should clear it. It may also be
> a good idea to clear both PLAYERGLOBAL_HOME and FLASHPLAYER_DEBUGGER too,
> just to be safe.
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>
>
> On Wed, Sep 25, 2019 at 9:41 AM Carlos Rovira 
> wrote:
>
> > 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
> > 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-09-25 Thread Josh Tynjala
Carlos,

Can you check to see if the AIR_HOME environment variable is set or not?

If I'm understanding the logic in ApproveRoyale.xml, then you need to
ensure that AIR_HOME is *NOT* set, unless you include -Duse-flash=true in
your command. If AIR_HOME is set, then you should clear it. It may also be
a good idea to clear both PLAYERGLOBAL_HOME and FLASHPLAYER_DEBUGGER too,
just to be safe.

--
Josh Tynjala
Bowler Hat LLC 


On Wed, Sep 25, 2019 at 9:41 AM Carlos Rovira 
wrote:

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

Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-09-25 Thread Carlos Rovira
Let's wait to Alex, I suppose something was not working as expected with
the changes he did yesterday to solve this issue.

El mié., 25 sept. 2019 a las 22:57, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> 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=3
> > > > > >
> > > > > >
> > > > > > ache.org/maven2/org/antlr/antlr/3.4/antlr-3.4.jar (1.1 MB at 2.7
> > > > > > MB/s)[INFO]
> > > > > >
> > > >
> > 

[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=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] 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-09-25 Thread Carlos Rovira
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=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]
> > 

[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] 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 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-09-25 Thread Carlos Rovira
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] 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]
> >
> > 

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:
>
> [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: 27 minutes 17 seconds
>
> macbookpro:testrc3 carlosrovira$
>
>
> El mié., 25 sept. 2019 a las 17:56, Piotr Zarzycki 

Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-09-25 Thread Carlos Rovira
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:

[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: 27 minutes 17 seconds

macbookpro:testrc3 carlosrovira$


El mié., 25 sept. 2019 a las 17:56, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> 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 

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
> > *
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 

Piotr Zarzycki

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


Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-09-25 Thread Carlos Rovira
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  >
> napisał(a):
>
> > This is the discussion thread.
> >
> > Thanks,
> > Piotr
>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>


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


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
*


[DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-09-25 Thread Apache Royale CI Server
This is the discussion thread.

Thanks,
Piotr