Re: Failed build doing 'ant all' on the packaging branch

[Alex Harui]

When you log in to builds.a.o, do you get a "New Item" choice on the upper
left?  I do.  If you don't, we'll have to figure out why and I'll create
the jobs later tonight.  When you create a new job, you should be able to
choose to copy an existing job and then modify it.

Let me know,
-Alex

On 9/29/17, 4:39 PM, "Piotr Zarzycki"  wrote:

>Yep. That is good idea and I could point to the new repository. I can
>create on builds.a.o new project - I see such options - The question is
>whether I can from the infra point of view ? If someone have knowledge
>whether we can create new project on build.a.o without ask for some
>permission - let me know.
>
>I could create new build under Flex project but rather it's not the path
>which we should go.
>
>Piotr
>
>2017-09-29 22:52 GMT+02:00 Alex Harui :
>
>> It occurs to me that it will be "safer" to create new Jenkins builds on
>> builds.a.o called Royale instead of FlexJS instead of renaming the
>>FlexJS
>> builds or leaving them as FlexJS.
>>
>> I have time to do that now but I can save it for you if you want.
>>
>> -Alex
>>
>> On 9/29/17, 11:41 AM, "Piotr Zarzycki" 
>>wrote:
>>
>> >Understand. Let me change the repos for Maven build in the Apache infra
>> >resources. I think since we are using for Maven build Apache resources
>>-
>> >on
>> >your build machine we could block all Maven stuff.
>> >
>> >I was going to propose a while ago.
>> >
>> >Piotr
>> >
>> >On Fri, Sep 29, 2017, 20:31 Alex Harui 
>>wrote:
>> >
>> >> Hi Piotr,
>> >>
>> >> Last night, I got Maven to build the three Royale repos locally.  You
>> >>can
>> >> probably just try changing the repos used by the Maven builds on
>> >> builds.a.o.  Or I will do that after I get the Ant build to pass.
>>That
>> >> should produce the same artifacts (under org.apache.flex).  I'd like
>>to
>> >> prove we can build everything on the new repos with the old names
>>before
>> >> renaming everything.  Checkintests for Ant are currently the only
>>thing
>> >>I
>> >> know of for Ant.
>> >>
>> >> The packaging work won't affect Maven.  All of the changes are just
>>in
>> >>how
>> >> we package up IDE-friendly artifacts.  The Maven artifacts shouldn't
>> >> change.
>> >>
>> >> -Alex
>> >>
>> >> On 9/29/17, 11:11 AM, "Piotr Zarzycki" 
>> >>wrote:
>> >>
>> >> >Hi Alex,
>> >> >
>> >> >Since everything is happening about renaming etc on packaging
>>branch I
>> >> >will
>> >> >also take a look in the next hopefully couple of days into Maven
>>stuff.
>> >> >The
>> >> >question is does changes which you have in queue (if you have) are
>>on
>> >> >develop branch in case of typedefs and compiler ?
>> >> >
>> >> >I have to say that too bad that those branch packaging wasn't
>>created
>> >> >under
>> >> >feature/packaging folder - It would help me a lot with changes
>>around
>> >> >Maven.
>> >> >
>> >> >Thanks,
>> >> >Piotr
>> >> >
>> >> >2017-09-29 14:15 GMT+02:00 Piotr Zarzycki
>>:
>> >> >
>> >> >> Hi Erik,
>> >> >>
>> >> >> I have added comment to your commit. I believe we should start
>> >> >>commenting
>> >> >> our code in github.
>> >> >>
>> >> >> Thanks, Piotr
>> >> >>
>> >> >> 2017-09-29 14:11 GMT+02:00 Erik de Bruin :
>> >> >>
>> >> >>> >
>> >> >>> > I will also rewrite the READme a bit to make the procedure
>> >>clearer,
>> >> >>>and
>> >> >>> > convert it to MarkDown to make it look good on GitHub.
>> >> >>> >
>> >> >>>
>> >> >>> I have finished my version of the READme. I renamed it to
>>README.md
>> >>to
>> >> >>>get
>> >> >>> GitHub to render the MarkDown.
>> >> >>>
>> >> >>> You can check it out on GitHub:
>> >> >>>
>> >> >>>
>> >>
>> >https://na01.safelinks.protection.outlook.com/?url=
>> https%3A%2F%2Fgithu
>> >b
>> >> .
>> >>
>> >com%2Fapache%2Froyale-asjs%2Ftree%2Fpackaging=
>> 02%7C01%7C%7Cc63900
>> >5d
>> >>
>> >717244b35c3f08d5076583d3%7Cfa7b1b5a7b34438794aed2c178de
>> cee1%7C0%7C0%7C
>> >63
>> >>
>> >6423054940850238=LRbDB3BumPkw0YyI9PwTkw4rAe1pPW
>> HAj2H7ZfoxUwE%3D&
>> >re
>> >> >>>served=0
>> >> >>>
>> >> >>> Thanks,
>> >> >>>
>> >> >>> EdB
>> >> >>>
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >>
>> >> >> Piotr Zarzycki
>> >> >>
>> >> >> mobile: +48 880 859 557 <+48%20880%20859%20557>
>> >> >> skype: zarzycki10
>> >> >>
>> >> >> LinkedIn:
>> >> >>
>> >>
>> >>https://na01.safelinks.protection.outlook.com/?url=
>> http%3A%2F%2Fwww.linke
>> >> >>din.com
>> >> %2Fpiotrzarzycki=02%7C01%7C%7Cc639005d717244b35c3f08d5076583d
>> >>
>> 3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
>> 7C636423054940850238
>> =G
>> >> >>nd1iANnUWoQMPk1MLd5BZ%2BnTT5MwePKxpJnXmLlI2s%3D=0
>> >> >>
>> >> >><
>> >> https://na01.safelinks.protection.outlook.com/?url=
>> https%3A%2F%2Fpl.link
>> >> >>edin.com
>> >> %2Fin%2Fpiotr-zarzycki-92a53552=02%7C01%7C%7Cc639005d717244b
>> >>
>> 

Re: Failed build doing 'ant all' on the packaging branch

[Alex Harui]

It occurs to me that it will be "safer" to create new Jenkins builds on
builds.a.o called Royale instead of FlexJS instead of renaming the FlexJS
builds or leaving them as FlexJS.

I have time to do that now but I can save it for you if you want.

-Alex

On 9/29/17, 11:41 AM, "Piotr Zarzycki"  wrote:

>Understand. Let me change the repos for Maven build in the Apache infra
>resources. I think since we are using for Maven build Apache resources -
>on
>your build machine we could block all Maven stuff.
>
>I was going to propose a while ago.
>
>Piotr
>
>On Fri, Sep 29, 2017, 20:31 Alex Harui  wrote:
>
>> Hi Piotr,
>>
>> Last night, I got Maven to build the three Royale repos locally.  You
>>can
>> probably just try changing the repos used by the Maven builds on
>> builds.a.o.  Or I will do that after I get the Ant build to pass.  That
>> should produce the same artifacts (under org.apache.flex).  I'd like to
>> prove we can build everything on the new repos with the old names before
>> renaming everything.  Checkintests for Ant are currently the only thing
>>I
>> know of for Ant.
>>
>> The packaging work won't affect Maven.  All of the changes are just in
>>how
>> we package up IDE-friendly artifacts.  The Maven artifacts shouldn't
>> change.
>>
>> -Alex
>>
>> On 9/29/17, 11:11 AM, "Piotr Zarzycki" 
>>wrote:
>>
>> >Hi Alex,
>> >
>> >Since everything is happening about renaming etc on packaging branch I
>> >will
>> >also take a look in the next hopefully couple of days into Maven stuff.
>> >The
>> >question is does changes which you have in queue (if you have) are on
>> >develop branch in case of typedefs and compiler ?
>> >
>> >I have to say that too bad that those branch packaging wasn't created
>> >under
>> >feature/packaging folder - It would help me a lot with changes around
>> >Maven.
>> >
>> >Thanks,
>> >Piotr
>> >
>> >2017-09-29 14:15 GMT+02:00 Piotr Zarzycki :
>> >
>> >> Hi Erik,
>> >>
>> >> I have added comment to your commit. I believe we should start
>> >>commenting
>> >> our code in github.
>> >>
>> >> Thanks, Piotr
>> >>
>> >> 2017-09-29 14:11 GMT+02:00 Erik de Bruin :
>> >>
>> >>> >
>> >>> > I will also rewrite the READme a bit to make the procedure
>>clearer,
>> >>>and
>> >>> > convert it to MarkDown to make it look good on GitHub.
>> >>> >
>> >>>
>> >>> I have finished my version of the READme. I renamed it to README.md
>>to
>> >>>get
>> >>> GitHub to render the MarkDown.
>> >>>
>> >>> You can check it out on GitHub:
>> >>>
>> >>>
>> 
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithu
>b
>> .
>> 
>com%2Fapache%2Froyale-asjs%2Ftree%2Fpackaging=02%7C01%7C%7Cc63900
>5d
>> 
>717244b35c3f08d5076583d3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C
>63
>> 
>6423054940850238=LRbDB3BumPkw0YyI9PwTkw4rAe1pPWHAj2H7ZfoxUwE%3D&
>re
>> >>>served=0
>> >>>
>> >>> Thanks,
>> >>>
>> >>> EdB
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >>
>> >> Piotr Zarzycki
>> >>
>> >> mobile: +48 880 859 557 <+48%20880%20859%20557>
>> >> skype: zarzycki10
>> >>
>> >> LinkedIn:
>> >>
>> 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linke
>> >>din.com
>> %2Fpiotrzarzycki=02%7C01%7C%7Cc639005d717244b35c3f08d5076583d
>> 
3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636423054940850238
=G
>> >>nd1iANnUWoQMPk1MLd5BZ%2BnTT5MwePKxpJnXmLlI2s%3D=0
>> >>
>> >><
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpl.link
>> >>edin.com
>> %2Fin%2Fpiotr-zarzycki-92a53552=02%7C01%7C%7Cc639005d717244b
>> 
35c3f08d5076583d3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63642305
49
>> 
40850238=PH12pV1A6ype2Uaa%2F3ZzvITtRl%2FXoKvELJVCSnKN5hQ%3D
ve
>> >>d=0>
>> >>
>> >> GitHub:
>> >>
>> 
>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.c
>> 
om%2Fpiotrzarzycki21=02%7C01%7C%7Cc639005d717244b35c3f08d5076583d3
%7
>> 
Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636423054940850238=on
Wd
>> >>jebvzE0LgoOHTseCdi8leAB%2Fa2%2FTtKpXCJd5NDE%3D=0
>> >>
>> >
>> >
>> >
>> >--
>> >
>> >Piotr Zarzycki
>> >
>> >mobile: +48 880 859 557
>> >skype: zarzycki10
>> >
>> >LinkedIn:
>> >
>> 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linke
>>d
>> >in.com
>> %2Fpiotrzarzycki=02%7C01%7C%7Cc639005d717244b35c3f08d5076583d3%
>> 
>>>7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636423054940850238=Gn
>>>d1
>> >iANnUWoQMPk1MLd5BZ%2BnTT5MwePKxpJnXmLlI2s%3D=0
>> ><
>> 
>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpl.linke
>> >din.com
>> %2Fin%2Fpiotr-zarzycki-92a53552=02%7C01%7C%7Cc639005d717244b35
>> 
>>>c3f08d5076583d3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63642305494
>>>08
>> 
>>>50238=PH12pV1A6ype2Uaa%2F3ZzvITtRl%2FXoKvELJVCSnKN5hQ%3D=
>>>0>
>> >
>> >GitHub:
>> >
>> 
>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.c
>>o

Re: Failed build doing 'ant all' on the packaging branch

[Peter Ent]

Hi,

I've successfully build royale-asjs et al twice. I did it twice because
after the first time (and lunch) I noticed another change in the repo so I
picked that up and just did it again. I've built this in a clean directory
with minimal ENV vars set.

I'm in the middle of building royale-asjs/examples and so far, so good.

‹peter

On 9/29/17, 2:31 PM, "Alex Harui"  wrote:

>Hi Piotr,
>
>Last night, I got Maven to build the three Royale repos locally.  You can
>probably just try changing the repos used by the Maven builds on
>builds.a.o.  Or I will do that after I get the Ant build to pass.  That
>should produce the same artifacts (under org.apache.flex).  I'd like to
>prove we can build everything on the new repos with the old names before
>renaming everything.  Checkintests for Ant are currently the only thing I
>know of for Ant.
>
>The packaging work won't affect Maven.  All of the changes are just in how
>we package up IDE-friendly artifacts.  The Maven artifacts shouldn't
>change.
>
>-Alex
>
>On 9/29/17, 11:11 AM, "Piotr Zarzycki"  wrote:
>
>>Hi Alex,
>>
>>Since everything is happening about renaming etc on packaging branch I
>>will
>>also take a look in the next hopefully couple of days into Maven stuff.
>>The
>>question is does changes which you have in queue (if you have) are on
>>develop branch in case of typedefs and compiler ?
>>
>>I have to say that too bad that those branch packaging wasn't created
>>under
>>feature/packaging folder - It would help me a lot with changes around
>>Maven.
>>
>>Thanks,
>>Piotr
>>
>>2017-09-29 14:15 GMT+02:00 Piotr Zarzycki :
>>
>>> Hi Erik,
>>>
>>> I have added comment to your commit. I believe we should start
>>>commenting
>>> our code in github.
>>>
>>> Thanks, Piotr
>>>
>>> 2017-09-29 14:11 GMT+02:00 Erik de Bruin :
>>>
 >
 > I will also rewrite the READme a bit to make the procedure clearer,
and
 > convert it to MarkDown to make it look good on GitHub.
 >

 I have finished my version of the READme. I renamed it to README.md to
get
 GitHub to render the MarkDown.

 You can check it out on GitHub:

 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub
.
com%2Fapache%2Froyale-asjs%2Ftree%2Fpackaging=02%7C01%7C%7Cc639005
d
717244b35c3f08d5076583d3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6
3
6423054940850238=LRbDB3BumPkw0YyI9PwTkw4rAe1pPWHAj2H7ZfoxUwE%3D
e
served=0

 Thanks,

 EdB

>>>
>>>
>>>
>>> --
>>>
>>> Piotr Zarzycki
>>>
>>> mobile: +48 880 859 557 <+48%20880%20859%20557>
>>> skype: zarzycki10
>>>
>>> LinkedIn: 
>>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.link
>>>e
>>>din.com%2Fpiotrzarzycki=02%7C01%7C%7Cc639005d717244b35c3f08d5076583
>>>d
>>>3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636423054940850238=
>>>G
>>>nd1iANnUWoQMPk1MLd5BZ%2BnTT5MwePKxpJnXmLlI2s%3D=0
>>> 
>>>>>k
>>>edin.com%2Fin%2Fpiotr-zarzycki-92a53552=02%7C01%7C%7Cc639005d717244
>>>b
>>>35c3f08d5076583d3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636423054
>>>9
>>>40850238=PH12pV1A6ype2Uaa%2F3ZzvITtRl%2FXoKvELJVCSnKN5hQ%3D
>>>e
>>>d=0>
>>>
>>> GitHub: 
>>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.
>>>c
>>>om%2Fpiotrzarzycki21=02%7C01%7C%7Cc639005d717244b35c3f08d5076583d3%
>>>7
>>>Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636423054940850238=onW
>>>d
>>>jebvzE0LgoOHTseCdi8leAB%2Fa2%2FTtKpXCJd5NDE%3D=0
>>>
>>
>>
>>
>>-- 
>>
>>Piotr Zarzycki
>>
>>mobile: +48 880 859 557
>>skype: zarzycki10
>>
>>LinkedIn: 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linke
>>d
>>in.com%2Fpiotrzarzycki=02%7C01%7C%7Cc639005d717244b35c3f08d5076583d3
>>%
>>7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636423054940850238=Gnd
>>1
>>iANnUWoQMPk1MLd5BZ%2BnTT5MwePKxpJnXmLlI2s%3D=0
>>>e
>>din.com%2Fin%2Fpiotr-zarzycki-92a53552=02%7C01%7C%7Cc639005d717244b3
>>5
>>c3f08d5076583d3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636423054940
>>8
>>50238=PH12pV1A6ype2Uaa%2F3ZzvITtRl%2FXoKvELJVCSnKN5hQ%3D=0
>>>
>>
>>GitHub: 
>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.c
>>o
>>m%2Fpiotrzarzycki21=02%7C01%7C%7Cc639005d717244b35c3f08d5076583d3%7C
>>f
>>a7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636423054940850238=onWdje
>>b
>>vzE0LgoOHTseCdi8leAB%2Fa2%2FTtKpXCJd5NDE%3D=0
>

Re: Failed build doing 'ant all' on the packaging branch

[Piotr Zarzycki]

Understand. Let me change the repos for Maven build in the Apache infra
resources. I think since we are using for Maven build Apache resources - on
your build machine we could block all Maven stuff.

I was going to propose a while ago.

Piotr

On Fri, Sep 29, 2017, 20:31 Alex Harui  wrote:

> Hi Piotr,
>
> Last night, I got Maven to build the three Royale repos locally.  You can
> probably just try changing the repos used by the Maven builds on
> builds.a.o.  Or I will do that after I get the Ant build to pass.  That
> should produce the same artifacts (under org.apache.flex).  I'd like to
> prove we can build everything on the new repos with the old names before
> renaming everything.  Checkintests for Ant are currently the only thing I
> know of for Ant.
>
> The packaging work won't affect Maven.  All of the changes are just in how
> we package up IDE-friendly artifacts.  The Maven artifacts shouldn't
> change.
>
> -Alex
>
> On 9/29/17, 11:11 AM, "Piotr Zarzycki"  wrote:
>
> >Hi Alex,
> >
> >Since everything is happening about renaming etc on packaging branch I
> >will
> >also take a look in the next hopefully couple of days into Maven stuff.
> >The
> >question is does changes which you have in queue (if you have) are on
> >develop branch in case of typedefs and compiler ?
> >
> >I have to say that too bad that those branch packaging wasn't created
> >under
> >feature/packaging folder - It would help me a lot with changes around
> >Maven.
> >
> >Thanks,
> >Piotr
> >
> >2017-09-29 14:15 GMT+02:00 Piotr Zarzycki :
> >
> >> Hi Erik,
> >>
> >> I have added comment to your commit. I believe we should start
> >>commenting
> >> our code in github.
> >>
> >> Thanks, Piotr
> >>
> >> 2017-09-29 14:11 GMT+02:00 Erik de Bruin :
> >>
> >>> >
> >>> > I will also rewrite the READme a bit to make the procedure clearer,
> >>>and
> >>> > convert it to MarkDown to make it look good on GitHub.
> >>> >
> >>>
> >>> I have finished my version of the READme. I renamed it to README.md to
> >>>get
> >>> GitHub to render the MarkDown.
> >>>
> >>> You can check it out on GitHub:
> >>>
> >>>
> >>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub
> .
> >>>com%2Fapache%2Froyale-asjs%2Ftree%2Fpackaging=02%7C01%7C%7Cc639005d
> >>>717244b35c3f08d5076583d3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63
> >>>6423054940850238=LRbDB3BumPkw0YyI9PwTkw4rAe1pPWHAj2H7ZfoxUwE%3D
> >>>served=0
> >>>
> >>> Thanks,
> >>>
> >>> EdB
> >>>
> >>
> >>
> >>
> >> --
> >>
> >> Piotr Zarzycki
> >>
> >> mobile: +48 880 859 557 <+48%20880%20859%20557>
> >> skype: zarzycki10
> >>
> >> LinkedIn:
> >>
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linke
> >>din.com
> %2Fpiotrzarzycki=02%7C01%7C%7Cc639005d717244b35c3f08d5076583d
> >>3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636423054940850238=G
> >>nd1iANnUWoQMPk1MLd5BZ%2BnTT5MwePKxpJnXmLlI2s%3D=0
> >>
> >><
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpl.link
> >>edin.com
> %2Fin%2Fpiotr-zarzycki-92a53552=02%7C01%7C%7Cc639005d717244b
> >>35c3f08d5076583d3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364230549
> >>40850238=PH12pV1A6ype2Uaa%2F3ZzvITtRl%2FXoKvELJVCSnKN5hQ%3D
> >>d=0>
> >>
> >> GitHub:
> >>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.c
> >>om%2Fpiotrzarzycki21=02%7C01%7C%7Cc639005d717244b35c3f08d5076583d3%7
> >>Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636423054940850238=onWd
> >>jebvzE0LgoOHTseCdi8leAB%2Fa2%2FTtKpXCJd5NDE%3D=0
> >>
> >
> >
> >
> >--
> >
> >Piotr Zarzycki
> >
> >mobile: +48 880 859 557
> >skype: zarzycki10
> >
> >LinkedIn:
> >
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linked
> >in.com
> %2Fpiotrzarzycki=02%7C01%7C%7Cc639005d717244b35c3f08d5076583d3%
> >7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636423054940850238=Gnd1
> >iANnUWoQMPk1MLd5BZ%2BnTT5MwePKxpJnXmLlI2s%3D=0
> ><
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpl.linke
> >din.com
> %2Fin%2Fpiotr-zarzycki-92a53552=02%7C01%7C%7Cc639005d717244b35
> >c3f08d5076583d3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364230549408
> >50238=PH12pV1A6ype2Uaa%2F3ZzvITtRl%2FXoKvELJVCSnKN5hQ%3D=0>
> >
> >GitHub:
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co
> >m%2Fpiotrzarzycki21=02%7C01%7C%7Cc639005d717244b35c3f08d5076583d3%7Cf
> >a7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636423054940850238=onWdjeb
> >vzE0LgoOHTseCdi8leAB%2Fa2%2FTtKpXCJd5NDE%3D=0
>
>

Re: Failed build doing 'ant all' on the packaging branch

[Alex Harui]

Hi Piotr,

Last night, I got Maven to build the three Royale repos locally.  You can
probably just try changing the repos used by the Maven builds on
builds.a.o.  Or I will do that after I get the Ant build to pass.  That
should produce the same artifacts (under org.apache.flex).  I'd like to
prove we can build everything on the new repos with the old names before
renaming everything.  Checkintests for Ant are currently the only thing I
know of for Ant.

The packaging work won't affect Maven.  All of the changes are just in how
we package up IDE-friendly artifacts.  The Maven artifacts shouldn't
change.

-Alex

On 9/29/17, 11:11 AM, "Piotr Zarzycki"  wrote:

>Hi Alex,
>
>Since everything is happening about renaming etc on packaging branch I
>will
>also take a look in the next hopefully couple of days into Maven stuff.
>The
>question is does changes which you have in queue (if you have) are on
>develop branch in case of typedefs and compiler ?
>
>I have to say that too bad that those branch packaging wasn't created
>under
>feature/packaging folder - It would help me a lot with changes around
>Maven.
>
>Thanks,
>Piotr
>
>2017-09-29 14:15 GMT+02:00 Piotr Zarzycki :
>
>> Hi Erik,
>>
>> I have added comment to your commit. I believe we should start
>>commenting
>> our code in github.
>>
>> Thanks, Piotr
>>
>> 2017-09-29 14:11 GMT+02:00 Erik de Bruin :
>>
>>> >
>>> > I will also rewrite the READme a bit to make the procedure clearer,
>>>and
>>> > convert it to MarkDown to make it look good on GitHub.
>>> >
>>>
>>> I have finished my version of the READme. I renamed it to README.md to
>>>get
>>> GitHub to render the MarkDown.
>>>
>>> You can check it out on GitHub:
>>>
>>> 
>>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.
>>>com%2Fapache%2Froyale-asjs%2Ftree%2Fpackaging=02%7C01%7C%7Cc639005d
>>>717244b35c3f08d5076583d3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63
>>>6423054940850238=LRbDB3BumPkw0YyI9PwTkw4rAe1pPWHAj2H7ZfoxUwE%3D
>>>served=0
>>>
>>> Thanks,
>>>
>>> EdB
>>>
>>
>>
>>
>> --
>>
>> Piotr Zarzycki
>>
>> mobile: +48 880 859 557 <+48%20880%20859%20557>
>> skype: zarzycki10
>>
>> LinkedIn: 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linke
>>din.com%2Fpiotrzarzycki=02%7C01%7C%7Cc639005d717244b35c3f08d5076583d
>>3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636423054940850238=G
>>nd1iANnUWoQMPk1MLd5BZ%2BnTT5MwePKxpJnXmLlI2s%3D=0
>> 
>>>edin.com%2Fin%2Fpiotr-zarzycki-92a53552=02%7C01%7C%7Cc639005d717244b
>>35c3f08d5076583d3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364230549
>>40850238=PH12pV1A6ype2Uaa%2F3ZzvITtRl%2FXoKvELJVCSnKN5hQ%3D
>>d=0>
>>
>> GitHub: 
>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.c
>>om%2Fpiotrzarzycki21=02%7C01%7C%7Cc639005d717244b35c3f08d5076583d3%7
>>Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636423054940850238=onWd
>>jebvzE0LgoOHTseCdi8leAB%2Fa2%2FTtKpXCJd5NDE%3D=0
>>
>
>
>
>-- 
>
>Piotr Zarzycki
>
>mobile: +48 880 859 557
>skype: zarzycki10
>
>LinkedIn: 
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linked
>in.com%2Fpiotrzarzycki=02%7C01%7C%7Cc639005d717244b35c3f08d5076583d3%
>7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636423054940850238=Gnd1
>iANnUWoQMPk1MLd5BZ%2BnTT5MwePKxpJnXmLlI2s%3D=0
>din.com%2Fin%2Fpiotr-zarzycki-92a53552=02%7C01%7C%7Cc639005d717244b35
>c3f08d5076583d3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364230549408
>50238=PH12pV1A6ype2Uaa%2F3ZzvITtRl%2FXoKvELJVCSnKN5hQ%3D=0>
>
>GitHub: 
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co
>m%2Fpiotrzarzycki21=02%7C01%7C%7Cc639005d717244b35c3f08d5076583d3%7Cf
>a7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636423054940850238=onWdjeb
>vzE0LgoOHTseCdi8leAB%2Fa2%2FTtKpXCJd5NDE%3D=0

Re: Failed build doing 'ant all' on the packaging branch

[Piotr Zarzycki]

Hi Alex,

Since everything is happening about renaming etc on packaging branch I will
also take a look in the next hopefully couple of days into Maven stuff. The
question is does changes which you have in queue (if you have) are on
develop branch in case of typedefs and compiler ?

I have to say that too bad that those branch packaging wasn't created under
feature/packaging folder - It would help me a lot with changes around
Maven.

Thanks,
Piotr

2017-09-29 14:15 GMT+02:00 Piotr Zarzycki :

> Hi Erik,
>
> I have added comment to your commit. I believe we should start commenting
> our code in github.
>
> Thanks, Piotr
>
> 2017-09-29 14:11 GMT+02:00 Erik de Bruin :
>
>> >
>> > I will also rewrite the READme a bit to make the procedure clearer, and
>> > convert it to MarkDown to make it look good on GitHub.
>> >
>>
>> I have finished my version of the READme. I renamed it to README.md to get
>> GitHub to render the MarkDown.
>>
>> You can check it out on GitHub:
>>
>> https://github.com/apache/royale-asjs/tree/packaging
>>
>> Thanks,
>>
>> EdB
>>
>
>
>
> --
>
> Piotr Zarzycki
>
> mobile: +48 880 859 557 <+48%20880%20859%20557>
> skype: zarzycki10
>
> LinkedIn: http://www.linkedin.com/piotrzarzycki
> 
>
> GitHub: https://github.com/piotrzarzycki21
>



-- 

Piotr Zarzycki

mobile: +48 880 859 557
skype: zarzycki10

LinkedIn: http://www.linkedin.com/piotrzarzycki


GitHub: https://github.com/piotrzarzycki21

Re: Failed build doing 'ant all' on the packaging branch

[Piotr Zarzycki]

Hi Erik,

I have added comment to your commit. I believe we should start commenting
our code in github.

Thanks, Piotr

2017-09-29 14:11 GMT+02:00 Erik de Bruin :

> >
> > I will also rewrite the READme a bit to make the procedure clearer, and
> > convert it to MarkDown to make it look good on GitHub.
> >
>
> I have finished my version of the READme. I renamed it to README.md to get
> GitHub to render the MarkDown.
>
> You can check it out on GitHub:
>
> https://github.com/apache/royale-asjs/tree/packaging
>
> Thanks,
>
> EdB
>



-- 

Piotr Zarzycki

mobile: +48 880 859 557
skype: zarzycki10

LinkedIn: http://www.linkedin.com/piotrzarzycki


GitHub: https://github.com/piotrzarzycki21

Re: Failed build doing 'ant all' on the packaging branch

[Erik de Bruin]

>
> I will also rewrite the READme a bit to make the procedure clearer, and
> convert it to MarkDown to make it look good on GitHub.
>

I have finished my version of the READme. I renamed it to README.md to get
GitHub to render the MarkDown.

You can check it out on GitHub:

https://github.com/apache/royale-asjs/tree/packaging

Thanks,

EdB

Failed build doing 'ant all' on the packaging branch

[Erik de Bruin]

Hi,

Currently, when I do an 'ant all' on the packaging branch, with just
JAVA_HOME and ANT_HOME set, I get a failed build.

[Error]
BUILD FAILED
/Users/erik/Desktop/royale/royale-asjs/build.xml:1545: The following error
occurred while executing this line:
/Users/erik/Desktop/royale/royale-asjs/build.xml:1618: The following error
occurred while executing this line:
/Users/erik/Desktop/royale/royale-compiler/build.xml:107: The following
error occurred while executing this line:
/Users/erik/Desktop/royale/royale-compiler/compiler/build.xml:711: The
following error occurred while executing this line:
/Users/erik/Desktop/royale/royale-compiler/compiler/src/test/build.xml:279:
Tests failed
[/Error]

Turns out that you do need to set PLAYERGLOBAL_HOME and
FLASHPLAYER_DEBUGGER, otherwise some of the tests on royale-compiler fail.
I'll make adjustments to the READme to reflect this.

I will also rewrite the READme a bit to make the procedure clearer, and
convert it to MarkDown to make it look good on GitHub.

Thanks,

EdB