Re: Nightly Builds Available

[Carlos Rovira]

I think what Piotr propose is very good for organization, revision and
matching with issues. The workflow I know (and I think works pretty well)
is the following.

Notice that this method tries to always develop in branches and ensures
develop is always stable and green. That should be our mantra, and people
coming to Royale should recognize a good methodology of development like
other well stablished projects out there.

1.- we should have an issue number (i.e: [#:

> If you are committing any changes use for example: "my commit message
> (reference #issuenumber)" - Than we will see on github all commits under
> issue and can review it.
>
> Piotr
>
> 2017-10-03 17:20 GMT+02:00 Alex Harui :
>
> > I"m not sure what you mean by "use issue number".  Where am I supposed to
> > use it?
> >
> > -Alex
> >
> > On 10/3/17, 1:02 AM, "Piotr Zarzycki"  wrote:
> >
> > >Alex,
> > >
> > >If you start renaming under some branch etc. please use issue number
> > >(reference #number) - we will have everything under our created issue.
> It
> > >help a lot with reviewing. I have found that is much worse for me
> looking
> > >into the emails than on github right now.
> > >
> > >Thanks,
> > >Piotr
> > >
> > >
> > >2017-10-03 7:25 GMT+02:00 Alex Harui :
> > >
> > >> OK, I merged packaging to develop.
> > >>
> > >> I think I see some consensus around the rename, so I will start on
> that
> > >> tomorrow in feature branches.
> > >>
> > >> -Alex
> > >>
> > >> On 10/2/17, 12:29 AM, "Piotr Zarzycki" 
> > >>wrote:
> > >>
> > >> >Alex,
> > >> >
> > >> >I think we should have separate branch for renaming. Packaging could
> be
> > >> >merge to develop, than we could create new branch for renaming. It
> > >>should
> > >> >be under folder feature/name - cause Maven build.a.o will pickup it
> > >> >automatically.
> > >> >
> > >> >That's how I think would be the best.
> > >> >
> > >> >Piotr
> > >> >
> > >> >2017-10-02 1:17 GMT+02:00 Alex Harui :
> > >> >
> > >> >> I'm tempted to just merge packaging into develop and start the
> rename
> > >> >>and
> > >> >> realize that things will likely be broken for several days.  Or we
> > >>can
> > >> >>do
> > >> >> the rename in branches.
> > >> >>
> > >> >> I'll poke at the packaging a bit more before merging.
> > >> >>
> > >> >> -Alex
> > >> >>
> > >> >> On 10/1/17, 12:07 PM, "Piotr Zarzycki" 
> > >> >>wrote:
> > >> >>
> > >> >> >Alex,
> > >> >> >
> > >> >> >Are you going to merge packaging branch to develop and then start
> > >> >>renaming
> > >> >> >process ? I'm asking cause maybe it would be good idea to move
> that
> > >> >>branch
> > >> >> >under folder feature/packaging - We will have to this
> automatically
> > >> >>under
> > >> >> >control of pipeline.
> > >> >> >
> > >> >> >Once renaming will start Maven build will tell us what is wrong
> > >>also.
> > >> >> >
> > >> >> >Piotr
> > >> >> >
> > >> >> >
> > >> >> >2017-10-01 20:03 GMT+02:00 Piotr Zarzycki
> > >>:
> > >> >> >
> > >> >> >> Alex,
> > >> >> >>
> > >> >> >> Thanks new nightly JS Only is working nicely with Moonshine
> along
> > >> >>with
> > >> >> >>my
> > >> >> >> fix. :)
> > >> >> >>
> > >> >> >> Thank you!
> > >> >> >> Piotr
> > >> >> >>
> > >> >> >>
> > >> >> >> 2017-10-01 16:13 GMT+02:00 Alex Harui  >:
> > >> >> >>
> > >> >> >>> Yes, you are correct that the SWCs got corrupted.  I made one
> > >>change
> > >> >> >>>but
> > >> >> >>> won't have time to test until later today.  Feel free to grab
> the
> > >> >> >>>latest
> > >> >> >>> build and try again.
> > >> >> >>>
> > >> >> >>> Thanks,
> > >> >> >>> -Alex
> > >> >> >>>
> > >> >> >>> On 9/30/17, 10:44 AM, "Piotr Zarzycki"
> > >>
> > >> >> >>>wrote:
> > >> >> >>>
> > >> >> >>> >I just made small experiment.
> > >> >> >>> >
> > >> >> >>> >1) I've downloaded FlexJS nightly using installer with Flash
> > >>Player
> > >> >> >>>23.
> > >> >> >>> >2) Create new project in Moonshine and build it with
> > >> >>-targets=JSFlex -
> > >> >> >>> >Build pass without the problem
> > >> >> >>> >3) I went to the folder 

Re: Nightly Builds Available

[Piotr Zarzycki]

If you are committing any changes use for example: "my commit message
(reference #issuenumber)" - Than we will see on github all commits under
issue and can review it.

Piotr

2017-10-03 17:20 GMT+02:00 Alex Harui :

> I"m not sure what you mean by "use issue number".  Where am I supposed to
> use it?
>
> -Alex
>
> On 10/3/17, 1:02 AM, "Piotr Zarzycki"  wrote:
>
> >Alex,
> >
> >If you start renaming under some branch etc. please use issue number
> >(reference #number) - we will have everything under our created issue. It
> >help a lot with reviewing. I have found that is much worse for me looking
> >into the emails than on github right now.
> >
> >Thanks,
> >Piotr
> >
> >
> >2017-10-03 7:25 GMT+02:00 Alex Harui :
> >
> >> OK, I merged packaging to develop.
> >>
> >> I think I see some consensus around the rename, so I will start on that
> >> tomorrow in feature branches.
> >>
> >> -Alex
> >>
> >> On 10/2/17, 12:29 AM, "Piotr Zarzycki" 
> >>wrote:
> >>
> >> >Alex,
> >> >
> >> >I think we should have separate branch for renaming. Packaging could be
> >> >merge to develop, than we could create new branch for renaming. It
> >>should
> >> >be under folder feature/name - cause Maven build.a.o will pickup it
> >> >automatically.
> >> >
> >> >That's how I think would be the best.
> >> >
> >> >Piotr
> >> >
> >> >2017-10-02 1:17 GMT+02:00 Alex Harui :
> >> >
> >> >> I'm tempted to just merge packaging into develop and start the rename
> >> >>and
> >> >> realize that things will likely be broken for several days.  Or we
> >>can
> >> >>do
> >> >> the rename in branches.
> >> >>
> >> >> I'll poke at the packaging a bit more before merging.
> >> >>
> >> >> -Alex
> >> >>
> >> >> On 10/1/17, 12:07 PM, "Piotr Zarzycki" 
> >> >>wrote:
> >> >>
> >> >> >Alex,
> >> >> >
> >> >> >Are you going to merge packaging branch to develop and then start
> >> >>renaming
> >> >> >process ? I'm asking cause maybe it would be good idea to move that
> >> >>branch
> >> >> >under folder feature/packaging - We will have to this automatically
> >> >>under
> >> >> >control of pipeline.
> >> >> >
> >> >> >Once renaming will start Maven build will tell us what is wrong
> >>also.
> >> >> >
> >> >> >Piotr
> >> >> >
> >> >> >
> >> >> >2017-10-01 20:03 GMT+02:00 Piotr Zarzycki
> >>:
> >> >> >
> >> >> >> Alex,
> >> >> >>
> >> >> >> Thanks new nightly JS Only is working nicely with Moonshine along
> >> >>with
> >> >> >>my
> >> >> >> fix. :)
> >> >> >>
> >> >> >> Thank you!
> >> >> >> Piotr
> >> >> >>
> >> >> >>
> >> >> >> 2017-10-01 16:13 GMT+02:00 Alex Harui :
> >> >> >>
> >> >> >>> Yes, you are correct that the SWCs got corrupted.  I made one
> >>change
> >> >> >>>but
> >> >> >>> won't have time to test until later today.  Feel free to grab the
> >> >> >>>latest
> >> >> >>> build and try again.
> >> >> >>>
> >> >> >>> Thanks,
> >> >> >>> -Alex
> >> >> >>>
> >> >> >>> On 9/30/17, 10:44 AM, "Piotr Zarzycki"
> >>
> >> >> >>>wrote:
> >> >> >>>
> >> >> >>> >I just made small experiment.
> >> >> >>> >
> >> >> >>> >1) I've downloaded FlexJS nightly using installer with Flash
> >>Player
> >> >> >>>23.
> >> >> >>> >2) Create new project in Moonshine and build it with
> >> >>-targets=JSFlex -
> >> >> >>> >Build pass without the problem
> >> >> >>> >3) I went to the folder "\frameworks\js\FlexJS\libs\" and
> >>removed
> >> >>all
> >> >> >>>swc
> >> >> >>> >4) I have copied swcs from your JS only version and build - it's
> >> >> >>>failed
> >> >> >>> >with same errors as it was through the console.
> >> >> >>> >
> >> >> >>> >Something is definitely wrong with those swcs.
> >> >> >>> >
> >> >> >>> >Piotr
> >> >> >>> >
> >> >> >>> >
> >> >> >>> >2017-09-30 19:32 GMT+02:00 Piotr Zarzycki
> >> >> >> >> >:
> >> >> >>> >
> >> >> >>> >> Alex,
> >> >> >>> >>
> >> >> >>> >> You are right. I have found issue in Moonshine it basically
> >> >>parsing
> >> >> >>>the
> >> >> >>> >> target player from flex-config.xml to 11.0.0 not 11.7.
> >>However I
> >> >> >>>think
> >> >> >>> >> something is wrong itself with SDK, cause I should be able to
> >> >>build
> >> >> >>> >>project
> >> >> >>> >> from console, but I'm getting strange errors for swcs. [1]
> >> >> >>> >>
> >> >> >>> >> [1]
> >> >> >>> >>https://na01.safelinks.protection.outlook.com/?url=https%
> >> >> >>> 3A%2F%2Fpaste.ap
> >> >> >>> >>ache.org%2FTY72=02%7C01%7C%7C12fdd85b1aec493aa8bc08d5
> >> >> >>> 082ae732%7Cfa7b
> >> >> >>> >>1b5a7b34438794aed2c178decee1%7C0%7C0%7C636423902740594589&
> >> >> >>> sdata=1E5qZgheJ
> >> >> >>> >>o3T7LqJlNOvhmEwhXVj3h6mLChHEERtKGc%3D=0
> >> >> >>> >>
> >> >> >>> >> Thanks, Piotr
> >> >> >>> >>
> >> >> >>> >> 2017-09-30 17:59 GMT+02:00 Alex Harui
> >> >> >:
> >> >> >>> >>
> >> >> >>> >>> The 

Re: Nightly Builds Available

[Harbs]

Not sure what Piotr meant.

> On Oct 3, 2017, at 6:46 PM, Alex Harui  wrote:
> 
> Maybe I didn't get enough sleep last night.  There is already an issue
> open, yes?  Am I supposed to type that issue# in the commit message or
> something like that?  I didn't see that from the link you posted.
> 
> -Alex
> 
> On 10/3/17, 8:42 AM, "Harbs"  wrote:
> 
>> I think he means cross references between issues and commits. It’s also
>> possible to have a list of issues within and issue.[1]
>> 
>> Harbs
>> [1]https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fguides
>> .github.com%2Ffeatures%2Fissues%2F=02%7C01%7C%7Cfd6662b8df094bc1d6730
>> 8d50a75637d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63642642165312183
>> 2=EbeZSf5rIgdMahYddSbaihUPLb59eM18FpGN6rjePTU%3D=0
>> > ithub.com%2Ffeatures%2Fissues%2F=02%7C01%7C%7Cfd6662b8df094bc1d67308d
>> 50a75637d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636426421653121832&
>> sdata=EbeZSf5rIgdMahYddSbaihUPLb59eM18FpGN6rjePTU%3D=0>
>> 
>>> On Oct 3, 2017, at 6:20 PM, Alex Harui  wrote:
>>> 
>>> I"m not sure what you mean by "use issue number".  Where am I supposed
>>> to
>>> use it?
>>> 
>>> -Alex
>>> 
>>> On 10/3/17, 1:02 AM, "Piotr Zarzycki"  wrote:
>>> 
 Alex,
 
 If you start renaming under some branch etc. please use issue number
 (reference #number) - we will have everything under our created issue.
 It
 help a lot with reviewing. I have found that is much worse for me
 looking
 into the emails than on github right now.
 
 Thanks,
 Piotr
 
 
 2017-10-03 7:25 GMT+02:00 Alex Harui :
 
> OK, I merged packaging to develop.
> 
> I think I see some consensus around the rename, so I will start on
> that
> tomorrow in feature branches.
> 
> -Alex
> 
> On 10/2/17, 12:29 AM, "Piotr Zarzycki" 
> wrote:
> 
>> Alex,
>> 
>> I think we should have separate branch for renaming. Packaging could
>> be
>> merge to develop, than we could create new branch for renaming. It
> should
>> be under folder feature/name - cause Maven build.a.o will pickup it
>> automatically.
>> 
>> That's how I think would be the best.
>> 
>> Piotr
>> 
>> 2017-10-02 1:17 GMT+02:00 Alex Harui :
>> 
>>> I'm tempted to just merge packaging into develop and start the
>>> rename
>>> and
>>> realize that things will likely be broken for several days.  Or we
> can
>>> do
>>> the rename in branches.
>>> 
>>> I'll poke at the packaging a bit more before merging.
>>> 
>>> -Alex
>>> 
>>> On 10/1/17, 12:07 PM, "Piotr Zarzycki" 
>>> wrote:
>>> 
 Alex,
 
 Are you going to merge packaging branch to develop and then start
>>> renaming
 process ? I'm asking cause maybe it would be good idea to move that
>>> branch
 under folder feature/packaging - We will have to this automatically
>>> under
 control of pipeline.
 
 Once renaming will start Maven build will tell us what is wrong
> also.
 
 Piotr
 
 
 2017-10-01 20:03 GMT+02:00 Piotr Zarzycki
> :
 
> Alex,
> 
> Thanks new nightly JS Only is working nicely with Moonshine along
>>> with
> my
> fix. :)
> 
> Thank you!
> Piotr
> 
> 
> 2017-10-01 16:13 GMT+02:00 Alex Harui :
> 
>> Yes, you are correct that the SWCs got corrupted.  I made one
> change
>> but
>> won't have time to test until later today.  Feel free to grab the
>> latest
>> build and try again.
>> 
>> Thanks,
>> -Alex
>> 
>> On 9/30/17, 10:44 AM, "Piotr Zarzycki"
> 
>> wrote:
>> 
>>> I just made small experiment.
>>> 
>>> 1) I've downloaded FlexJS nightly using installer with Flash
> Player
>> 23.
>>> 2) Create new project in Moonshine and build it with
>>> -targets=JSFlex -
>>> Build pass without the problem
>>> 3) I went to the folder "\frameworks\js\FlexJS\libs\" and
> removed
>>> all
>> swc
>>> 4) I have copied swcs from your JS only version and build - it's
>> failed
>>> with same errors as it was through the console.
>>> 
>>> Something is definitely wrong with those swcs.
>>> 
>>> Piotr
>>> 
>>> 
>>> 2017-09-30 19:32 GMT+02:00 Piotr 

Re: Nightly Builds Available

[Alex Harui]

Maybe I didn't get enough sleep last night.  There is already an issue
open, yes?  Am I supposed to type that issue# in the commit message or
something like that?  I didn't see that from the link you posted.

-Alex

On 10/3/17, 8:42 AM, "Harbs"  wrote:

>I think he means cross references between issues and commits. It’s also
>possible to have a list of issues within and issue.[1]
>
>Harbs
>[1]https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fguides
>.github.com%2Ffeatures%2Fissues%2F=02%7C01%7C%7Cfd6662b8df094bc1d6730
>8d50a75637d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63642642165312183
>2=EbeZSf5rIgdMahYddSbaihUPLb59eM18FpGN6rjePTU%3D=0
>ithub.com%2Ffeatures%2Fissues%2F=02%7C01%7C%7Cfd6662b8df094bc1d67308d
>50a75637d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636426421653121832&
>sdata=EbeZSf5rIgdMahYddSbaihUPLb59eM18FpGN6rjePTU%3D=0>
>
>> On Oct 3, 2017, at 6:20 PM, Alex Harui  wrote:
>> 
>> I"m not sure what you mean by "use issue number".  Where am I supposed
>>to
>> use it?
>> 
>> -Alex
>> 
>> On 10/3/17, 1:02 AM, "Piotr Zarzycki"  wrote:
>> 
>>> Alex,
>>> 
>>> If you start renaming under some branch etc. please use issue number
>>> (reference #number) - we will have everything under our created issue.
>>>It
>>> help a lot with reviewing. I have found that is much worse for me
>>>looking
>>> into the emails than on github right now.
>>> 
>>> Thanks,
>>> Piotr
>>> 
>>> 
>>> 2017-10-03 7:25 GMT+02:00 Alex Harui :
>>> 
 OK, I merged packaging to develop.
 
 I think I see some consensus around the rename, so I will start on
that
 tomorrow in feature branches.
 
 -Alex
 
 On 10/2/17, 12:29 AM, "Piotr Zarzycki" 
 wrote:
 
> Alex,
> 
> I think we should have separate branch for renaming. Packaging could
>be
> merge to develop, than we could create new branch for renaming. It
 should
> be under folder feature/name - cause Maven build.a.o will pickup it
> automatically.
> 
> That's how I think would be the best.
> 
> Piotr
> 
> 2017-10-02 1:17 GMT+02:00 Alex Harui :
> 
>> I'm tempted to just merge packaging into develop and start the
>>rename
>> and
>> realize that things will likely be broken for several days.  Or we
 can
>> do
>> the rename in branches.
>> 
>> I'll poke at the packaging a bit more before merging.
>> 
>> -Alex
>> 
>> On 10/1/17, 12:07 PM, "Piotr Zarzycki" 
>> wrote:
>> 
>>> Alex,
>>> 
>>> Are you going to merge packaging branch to develop and then start
>> renaming
>>> process ? I'm asking cause maybe it would be good idea to move that
>> branch
>>> under folder feature/packaging - We will have to this automatically
>> under
>>> control of pipeline.
>>> 
>>> Once renaming will start Maven build will tell us what is wrong
 also.
>>> 
>>> Piotr
>>> 
>>> 
>>> 2017-10-01 20:03 GMT+02:00 Piotr Zarzycki
 :
>>> 
 Alex,
 
 Thanks new nightly JS Only is working nicely with Moonshine along
>> with
 my
 fix. :)
 
 Thank you!
 Piotr
 
 
 2017-10-01 16:13 GMT+02:00 Alex Harui :
 
> Yes, you are correct that the SWCs got corrupted.  I made one
 change
> but
> won't have time to test until later today.  Feel free to grab the
> latest
> build and try again.
> 
> Thanks,
> -Alex
> 
> On 9/30/17, 10:44 AM, "Piotr Zarzycki"
 
> wrote:
> 
>> I just made small experiment.
>> 
>> 1) I've downloaded FlexJS nightly using installer with Flash
 Player
> 23.
>> 2) Create new project in Moonshine and build it with
>> -targets=JSFlex -
>> Build pass without the problem
>> 3) I went to the folder "\frameworks\js\FlexJS\libs\" and
 removed
>> all
> swc
>> 4) I have copied swcs from your JS only version and build - it's
> failed
>> with same errors as it was through the console.
>> 
>> Something is definitely wrong with those swcs.
>> 
>> Piotr
>> 
>> 
>> 2017-09-30 19:32 GMT+02:00 Piotr Zarzycki
>> >> :
>> 
>>> Alex,
>>> 
>>> You are right. I have found issue in Moonshine it basically
>> parsing
> the
>>> target player from flex-config.xml to 11.0.0 not 11.7.
 However I
> think

Re: Nightly Builds Available

[Harbs]

I think he means cross references between issues and commits. It’s also 
possible to have a list of issues within and issue.[1]

Harbs
[1]https://guides.github.com/features/issues/ 


> On Oct 3, 2017, at 6:20 PM, Alex Harui  wrote:
> 
> I"m not sure what you mean by "use issue number".  Where am I supposed to
> use it?
> 
> -Alex
> 
> On 10/3/17, 1:02 AM, "Piotr Zarzycki"  wrote:
> 
>> Alex,
>> 
>> If you start renaming under some branch etc. please use issue number
>> (reference #number) - we will have everything under our created issue. It
>> help a lot with reviewing. I have found that is much worse for me looking
>> into the emails than on github right now.
>> 
>> Thanks,
>> Piotr
>> 
>> 
>> 2017-10-03 7:25 GMT+02:00 Alex Harui :
>> 
>>> OK, I merged packaging to develop.
>>> 
>>> I think I see some consensus around the rename, so I will start on that
>>> tomorrow in feature branches.
>>> 
>>> -Alex
>>> 
>>> On 10/2/17, 12:29 AM, "Piotr Zarzycki" 
>>> wrote:
>>> 
 Alex,
 
 I think we should have separate branch for renaming. Packaging could be
 merge to develop, than we could create new branch for renaming. It
>>> should
 be under folder feature/name - cause Maven build.a.o will pickup it
 automatically.
 
 That's how I think would be the best.
 
 Piotr
 
 2017-10-02 1:17 GMT+02:00 Alex Harui :
 
> I'm tempted to just merge packaging into develop and start the rename
> and
> realize that things will likely be broken for several days.  Or we
>>> can
> do
> the rename in branches.
> 
> I'll poke at the packaging a bit more before merging.
> 
> -Alex
> 
> On 10/1/17, 12:07 PM, "Piotr Zarzycki" 
> wrote:
> 
>> Alex,
>> 
>> Are you going to merge packaging branch to develop and then start
> renaming
>> process ? I'm asking cause maybe it would be good idea to move that
> branch
>> under folder feature/packaging - We will have to this automatically
> under
>> control of pipeline.
>> 
>> Once renaming will start Maven build will tell us what is wrong
>>> also.
>> 
>> Piotr
>> 
>> 
>> 2017-10-01 20:03 GMT+02:00 Piotr Zarzycki
>>> :
>> 
>>> Alex,
>>> 
>>> Thanks new nightly JS Only is working nicely with Moonshine along
> with
>>> my
>>> fix. :)
>>> 
>>> Thank you!
>>> Piotr
>>> 
>>> 
>>> 2017-10-01 16:13 GMT+02:00 Alex Harui :
>>> 
 Yes, you are correct that the SWCs got corrupted.  I made one
>>> change
 but
 won't have time to test until later today.  Feel free to grab the
 latest
 build and try again.
 
 Thanks,
 -Alex
 
 On 9/30/17, 10:44 AM, "Piotr Zarzycki"
>>> 
 wrote:
 
> I just made small experiment.
> 
> 1) I've downloaded FlexJS nightly using installer with Flash
>>> Player
 23.
> 2) Create new project in Moonshine and build it with
> -targets=JSFlex -
> Build pass without the problem
> 3) I went to the folder "\frameworks\js\FlexJS\libs\" and
>>> removed
> all
 swc
> 4) I have copied swcs from your JS only version and build - it's
 failed
> with same errors as it was through the console.
> 
> Something is definitely wrong with those swcs.
> 
> Piotr
> 
> 
> 2017-09-30 19:32 GMT+02:00 Piotr Zarzycki
> > :
> 
>> Alex,
>> 
>> You are right. I have found issue in Moonshine it basically
> parsing
 the
>> target player from flex-config.xml to 11.0.0 not 11.7.
>>> However I
 think
>> something is wrong itself with SDK, cause I should be able to
> build
>> project
>> from console, but I'm getting strange errors for swcs. [1]
>> 
>> [1]
>> https://na01.safelinks.protection.outlook.com/?url=https%
 3A%2F%2Fpaste.ap
>> ache.org%2FTY72=02%7C01%7C%7C12fdd85b1aec493aa8bc08d5
 082ae732%7Cfa7b
>> 1b5a7b34438794aed2c178decee1%7C0%7C0%7C636423902740594589&
 sdata=1E5qZgheJ
>> o3T7LqJlNOvhmEwhXVj3h6mLChHEERtKGc%3D=0
>> 
>> Thanks, Piotr
>> 
>> 2017-09-30 17:59 GMT+02:00 Alex Harui
>>> > 
>>> The flex-config.xml in the JSOnly package should have
 target-player of
>>> 11.7 and there should be a frameworks/libs/player/11.7/pl
 ayerglobal.swc
>>> 
>>> Are you not 

Re: Nightly Builds Available

[Alex Harui]

I"m not sure what you mean by "use issue number".  Where am I supposed to
use it?

-Alex

On 10/3/17, 1:02 AM, "Piotr Zarzycki"  wrote:

>Alex,
>
>If you start renaming under some branch etc. please use issue number
>(reference #number) - we will have everything under our created issue. It
>help a lot with reviewing. I have found that is much worse for me looking
>into the emails than on github right now.
>
>Thanks,
>Piotr
>
>
>2017-10-03 7:25 GMT+02:00 Alex Harui :
>
>> OK, I merged packaging to develop.
>>
>> I think I see some consensus around the rename, so I will start on that
>> tomorrow in feature branches.
>>
>> -Alex
>>
>> On 10/2/17, 12:29 AM, "Piotr Zarzycki" 
>>wrote:
>>
>> >Alex,
>> >
>> >I think we should have separate branch for renaming. Packaging could be
>> >merge to develop, than we could create new branch for renaming. It
>>should
>> >be under folder feature/name - cause Maven build.a.o will pickup it
>> >automatically.
>> >
>> >That's how I think would be the best.
>> >
>> >Piotr
>> >
>> >2017-10-02 1:17 GMT+02:00 Alex Harui :
>> >
>> >> I'm tempted to just merge packaging into develop and start the rename
>> >>and
>> >> realize that things will likely be broken for several days.  Or we
>>can
>> >>do
>> >> the rename in branches.
>> >>
>> >> I'll poke at the packaging a bit more before merging.
>> >>
>> >> -Alex
>> >>
>> >> On 10/1/17, 12:07 PM, "Piotr Zarzycki" 
>> >>wrote:
>> >>
>> >> >Alex,
>> >> >
>> >> >Are you going to merge packaging branch to develop and then start
>> >>renaming
>> >> >process ? I'm asking cause maybe it would be good idea to move that
>> >>branch
>> >> >under folder feature/packaging - We will have to this automatically
>> >>under
>> >> >control of pipeline.
>> >> >
>> >> >Once renaming will start Maven build will tell us what is wrong
>>also.
>> >> >
>> >> >Piotr
>> >> >
>> >> >
>> >> >2017-10-01 20:03 GMT+02:00 Piotr Zarzycki
>>:
>> >> >
>> >> >> Alex,
>> >> >>
>> >> >> Thanks new nightly JS Only is working nicely with Moonshine along
>> >>with
>> >> >>my
>> >> >> fix. :)
>> >> >>
>> >> >> Thank you!
>> >> >> Piotr
>> >> >>
>> >> >>
>> >> >> 2017-10-01 16:13 GMT+02:00 Alex Harui :
>> >> >>
>> >> >>> Yes, you are correct that the SWCs got corrupted.  I made one
>>change
>> >> >>>but
>> >> >>> won't have time to test until later today.  Feel free to grab the
>> >> >>>latest
>> >> >>> build and try again.
>> >> >>>
>> >> >>> Thanks,
>> >> >>> -Alex
>> >> >>>
>> >> >>> On 9/30/17, 10:44 AM, "Piotr Zarzycki"
>>
>> >> >>>wrote:
>> >> >>>
>> >> >>> >I just made small experiment.
>> >> >>> >
>> >> >>> >1) I've downloaded FlexJS nightly using installer with Flash
>>Player
>> >> >>>23.
>> >> >>> >2) Create new project in Moonshine and build it with
>> >>-targets=JSFlex -
>> >> >>> >Build pass without the problem
>> >> >>> >3) I went to the folder "\frameworks\js\FlexJS\libs\" and
>>removed
>> >>all
>> >> >>>swc
>> >> >>> >4) I have copied swcs from your JS only version and build - it's
>> >> >>>failed
>> >> >>> >with same errors as it was through the console.
>> >> >>> >
>> >> >>> >Something is definitely wrong with those swcs.
>> >> >>> >
>> >> >>> >Piotr
>> >> >>> >
>> >> >>> >
>> >> >>> >2017-09-30 19:32 GMT+02:00 Piotr Zarzycki
>> >>> >> >:
>> >> >>> >
>> >> >>> >> Alex,
>> >> >>> >>
>> >> >>> >> You are right. I have found issue in Moonshine it basically
>> >>parsing
>> >> >>>the
>> >> >>> >> target player from flex-config.xml to 11.0.0 not 11.7.
>>However I
>> >> >>>think
>> >> >>> >> something is wrong itself with SDK, cause I should be able to
>> >>build
>> >> >>> >>project
>> >> >>> >> from console, but I'm getting strange errors for swcs. [1]
>> >> >>> >>
>> >> >>> >> [1]
>> >> >>> >>https://na01.safelinks.protection.outlook.com/?url=https%
>> >> >>> 3A%2F%2Fpaste.ap
>> >> >>> >>ache.org%2FTY72=02%7C01%7C%7C12fdd85b1aec493aa8bc08d5
>> >> >>> 082ae732%7Cfa7b
>> >> >>> >>1b5a7b34438794aed2c178decee1%7C0%7C0%7C636423902740594589&
>> >> >>> sdata=1E5qZgheJ
>> >> >>> >>o3T7LqJlNOvhmEwhXVj3h6mLChHEERtKGc%3D=0
>> >> >>> >>
>> >> >>> >> Thanks, Piotr
>> >> >>> >>
>> >> >>> >> 2017-09-30 17:59 GMT+02:00 Alex Harui
>>> >:
>> >> >>> >>
>> >> >>> >>> The flex-config.xml in the JSOnly package should have
>> >> >>>target-player of
>> >> >>> >>> 11.7 and there should be a frameworks/libs/player/11.7/pl
>> >> >>> ayerglobal.swc
>> >> >>> >>>
>> >> >>> >>> Are you not seeing that?  Maybe Moonshine is changing
>>something?
>> >> >>>I'm
>> >> >>> >>>out
>> >> >>> >>> of time for this morning.  Won't have more time until about
>>13
>> >> >>>hours
>> >> >>> >>>from
>> >> >>> >>> now.
>> >> >>> >>>
>> >> >>> >>> Later,
>> >> >>> >>> -Alex
>> >> >>> >>>
>> >> >>> >>> On 9/30/17, 12:59 AM, "Piotr Zarzycki"
>> 

Re: Nightly Builds Available

[Piotr Zarzycki]

Alex,

If you start renaming under some branch etc. please use issue number
(reference #number) - we will have everything under our created issue. It
help a lot with reviewing. I have found that is much worse for me looking
into the emails than on github right now.

Thanks,
Piotr


2017-10-03 7:25 GMT+02:00 Alex Harui :

> OK, I merged packaging to develop.
>
> I think I see some consensus around the rename, so I will start on that
> tomorrow in feature branches.
>
> -Alex
>
> On 10/2/17, 12:29 AM, "Piotr Zarzycki"  wrote:
>
> >Alex,
> >
> >I think we should have separate branch for renaming. Packaging could be
> >merge to develop, than we could create new branch for renaming. It should
> >be under folder feature/name - cause Maven build.a.o will pickup it
> >automatically.
> >
> >That's how I think would be the best.
> >
> >Piotr
> >
> >2017-10-02 1:17 GMT+02:00 Alex Harui :
> >
> >> I'm tempted to just merge packaging into develop and start the rename
> >>and
> >> realize that things will likely be broken for several days.  Or we can
> >>do
> >> the rename in branches.
> >>
> >> I'll poke at the packaging a bit more before merging.
> >>
> >> -Alex
> >>
> >> On 10/1/17, 12:07 PM, "Piotr Zarzycki" 
> >>wrote:
> >>
> >> >Alex,
> >> >
> >> >Are you going to merge packaging branch to develop and then start
> >>renaming
> >> >process ? I'm asking cause maybe it would be good idea to move that
> >>branch
> >> >under folder feature/packaging - We will have to this automatically
> >>under
> >> >control of pipeline.
> >> >
> >> >Once renaming will start Maven build will tell us what is wrong also.
> >> >
> >> >Piotr
> >> >
> >> >
> >> >2017-10-01 20:03 GMT+02:00 Piotr Zarzycki :
> >> >
> >> >> Alex,
> >> >>
> >> >> Thanks new nightly JS Only is working nicely with Moonshine along
> >>with
> >> >>my
> >> >> fix. :)
> >> >>
> >> >> Thank you!
> >> >> Piotr
> >> >>
> >> >>
> >> >> 2017-10-01 16:13 GMT+02:00 Alex Harui :
> >> >>
> >> >>> Yes, you are correct that the SWCs got corrupted.  I made one change
> >> >>>but
> >> >>> won't have time to test until later today.  Feel free to grab the
> >> >>>latest
> >> >>> build and try again.
> >> >>>
> >> >>> Thanks,
> >> >>> -Alex
> >> >>>
> >> >>> On 9/30/17, 10:44 AM, "Piotr Zarzycki" 
> >> >>>wrote:
> >> >>>
> >> >>> >I just made small experiment.
> >> >>> >
> >> >>> >1) I've downloaded FlexJS nightly using installer with Flash Player
> >> >>>23.
> >> >>> >2) Create new project in Moonshine and build it with
> >>-targets=JSFlex -
> >> >>> >Build pass without the problem
> >> >>> >3) I went to the folder "\frameworks\js\FlexJS\libs\" and removed
> >>all
> >> >>>swc
> >> >>> >4) I have copied swcs from your JS only version and build - it's
> >> >>>failed
> >> >>> >with same errors as it was through the console.
> >> >>> >
> >> >>> >Something is definitely wrong with those swcs.
> >> >>> >
> >> >>> >Piotr
> >> >>> >
> >> >>> >
> >> >>> >2017-09-30 19:32 GMT+02:00 Piotr Zarzycki
> >> >> >:
> >> >>> >
> >> >>> >> Alex,
> >> >>> >>
> >> >>> >> You are right. I have found issue in Moonshine it basically
> >>parsing
> >> >>>the
> >> >>> >> target player from flex-config.xml to 11.0.0 not 11.7. However I
> >> >>>think
> >> >>> >> something is wrong itself with SDK, cause I should be able to
> >>build
> >> >>> >>project
> >> >>> >> from console, but I'm getting strange errors for swcs. [1]
> >> >>> >>
> >> >>> >> [1]
> >> >>> >>https://na01.safelinks.protection.outlook.com/?url=https%
> >> >>> 3A%2F%2Fpaste.ap
> >> >>> >>ache.org%2FTY72=02%7C01%7C%7C12fdd85b1aec493aa8bc08d5
> >> >>> 082ae732%7Cfa7b
> >> >>> >>1b5a7b34438794aed2c178decee1%7C0%7C0%7C636423902740594589&
> >> >>> sdata=1E5qZgheJ
> >> >>> >>o3T7LqJlNOvhmEwhXVj3h6mLChHEERtKGc%3D=0
> >> >>> >>
> >> >>> >> Thanks, Piotr
> >> >>> >>
> >> >>> >> 2017-09-30 17:59 GMT+02:00 Alex Harui  >:
> >> >>> >>
> >> >>> >>> The flex-config.xml in the JSOnly package should have
> >> >>>target-player of
> >> >>> >>> 11.7 and there should be a frameworks/libs/player/11.7/pl
> >> >>> ayerglobal.swc
> >> >>> >>>
> >> >>> >>> Are you not seeing that?  Maybe Moonshine is changing something?
> >> >>>I'm
> >> >>> >>>out
> >> >>> >>> of time for this morning.  Won't have more time until about 13
> >> >>>hours
> >> >>> >>>from
> >> >>> >>> now.
> >> >>> >>>
> >> >>> >>> Later,
> >> >>> >>> -Alex
> >> >>> >>>
> >> >>> >>> On 9/30/17, 12:59 AM, "Piotr Zarzycki"
> >>
> >> >>> >>>wrote:
> >> >>> >>>
> >> >>> >>> >Hi Alex,
> >> >>> >>> >
> >> >>> >>> >I just tried build with Moonshine and it's searching
> >>playerglobal
> >> >>> [1].
> >> >>> >>> I'm
> >> >>> >>> >not sure whether Moonshine need to change our generated config
> >>[2]
> >> >>> and
> >> >>> >>> >how.
> >> >>> >>> >It's 

Re: Nightly Builds Available

[Alex Harui]

OK, I merged packaging to develop.

I think I see some consensus around the rename, so I will start on that
tomorrow in feature branches.

-Alex

On 10/2/17, 12:29 AM, "Piotr Zarzycki"  wrote:

>Alex,
>
>I think we should have separate branch for renaming. Packaging could be
>merge to develop, than we could create new branch for renaming. It should
>be under folder feature/name - cause Maven build.a.o will pickup it
>automatically.
>
>That's how I think would be the best.
>
>Piotr
>
>2017-10-02 1:17 GMT+02:00 Alex Harui :
>
>> I'm tempted to just merge packaging into develop and start the rename
>>and
>> realize that things will likely be broken for several days.  Or we can
>>do
>> the rename in branches.
>>
>> I'll poke at the packaging a bit more before merging.
>>
>> -Alex
>>
>> On 10/1/17, 12:07 PM, "Piotr Zarzycki" 
>>wrote:
>>
>> >Alex,
>> >
>> >Are you going to merge packaging branch to develop and then start
>>renaming
>> >process ? I'm asking cause maybe it would be good idea to move that
>>branch
>> >under folder feature/packaging - We will have to this automatically
>>under
>> >control of pipeline.
>> >
>> >Once renaming will start Maven build will tell us what is wrong also.
>> >
>> >Piotr
>> >
>> >
>> >2017-10-01 20:03 GMT+02:00 Piotr Zarzycki :
>> >
>> >> Alex,
>> >>
>> >> Thanks new nightly JS Only is working nicely with Moonshine along
>>with
>> >>my
>> >> fix. :)
>> >>
>> >> Thank you!
>> >> Piotr
>> >>
>> >>
>> >> 2017-10-01 16:13 GMT+02:00 Alex Harui :
>> >>
>> >>> Yes, you are correct that the SWCs got corrupted.  I made one change
>> >>>but
>> >>> won't have time to test until later today.  Feel free to grab the
>> >>>latest
>> >>> build and try again.
>> >>>
>> >>> Thanks,
>> >>> -Alex
>> >>>
>> >>> On 9/30/17, 10:44 AM, "Piotr Zarzycki" 
>> >>>wrote:
>> >>>
>> >>> >I just made small experiment.
>> >>> >
>> >>> >1) I've downloaded FlexJS nightly using installer with Flash Player
>> >>>23.
>> >>> >2) Create new project in Moonshine and build it with
>>-targets=JSFlex -
>> >>> >Build pass without the problem
>> >>> >3) I went to the folder "\frameworks\js\FlexJS\libs\" and removed
>>all
>> >>>swc
>> >>> >4) I have copied swcs from your JS only version and build - it's
>> >>>failed
>> >>> >with same errors as it was through the console.
>> >>> >
>> >>> >Something is definitely wrong with those swcs.
>> >>> >
>> >>> >Piotr
>> >>> >
>> >>> >
>> >>> >2017-09-30 19:32 GMT+02:00 Piotr Zarzycki
>>> >:
>> >>> >
>> >>> >> Alex,
>> >>> >>
>> >>> >> You are right. I have found issue in Moonshine it basically
>>parsing
>> >>>the
>> >>> >> target player from flex-config.xml to 11.0.0 not 11.7. However I
>> >>>think
>> >>> >> something is wrong itself with SDK, cause I should be able to
>>build
>> >>> >>project
>> >>> >> from console, but I'm getting strange errors for swcs. [1]
>> >>> >>
>> >>> >> [1]
>> >>> >>https://na01.safelinks.protection.outlook.com/?url=https%
>> >>> 3A%2F%2Fpaste.ap
>> >>> >>ache.org%2FTY72=02%7C01%7C%7C12fdd85b1aec493aa8bc08d5
>> >>> 082ae732%7Cfa7b
>> >>> >>1b5a7b34438794aed2c178decee1%7C0%7C0%7C636423902740594589&
>> >>> sdata=1E5qZgheJ
>> >>> >>o3T7LqJlNOvhmEwhXVj3h6mLChHEERtKGc%3D=0
>> >>> >>
>> >>> >> Thanks, Piotr
>> >>> >>
>> >>> >> 2017-09-30 17:59 GMT+02:00 Alex Harui :
>> >>> >>
>> >>> >>> The flex-config.xml in the JSOnly package should have
>> >>>target-player of
>> >>> >>> 11.7 and there should be a frameworks/libs/player/11.7/pl
>> >>> ayerglobal.swc
>> >>> >>>
>> >>> >>> Are you not seeing that?  Maybe Moonshine is changing something?
>> >>>I'm
>> >>> >>>out
>> >>> >>> of time for this morning.  Won't have more time until about 13
>> >>>hours
>> >>> >>>from
>> >>> >>> now.
>> >>> >>>
>> >>> >>> Later,
>> >>> >>> -Alex
>> >>> >>>
>> >>> >>> On 9/30/17, 12:59 AM, "Piotr Zarzycki"
>>
>> >>> >>>wrote:
>> >>> >>>
>> >>> >>> >Hi Alex,
>> >>> >>> >
>> >>> >>> >I just tried build with Moonshine and it's searching
>>playerglobal
>> >>> [1].
>> >>> >>> I'm
>> >>> >>> >not sure whether Moonshine need to change our generated config
>>[2]
>> >>> and
>> >>> >>> >how.
>> >>> >>> >It's being generated by Moonshine and it's always contains
>> >>> >>>target-player.
>> >>> >>> >Maybe I should implement there checking whether flex-config.xml
>> >>>does
>> >>> >>> exist
>> >>> >>> >target-player ?
>> >>> >>> >
>> >>> >>> >[1]
>> >>> >>> >https://na01.safelinks.protection.outlook.com/?url=https%
>> >>> >>> 3A%2F%2Fpaste.apa
>> >>> >>> >che.org%2FBtco=02%7C01%7C%7C58c35153163b4fe45ee608d507
>> >>> >>> d93fff%7Cfa7b1b
>> >>> >>> >5a7b34438794aed2c178decee1%7C0%7C0%7C636423552028633728
>> >>> >>> ta=CYkAR9I4VUQW
>> >>> >>> >VWAfG4aU%2Fw8SiDDonwf61%2FxgAFbcJgc%3D=0
>> >>> >>> >[2]
>> >>> >>> 

Re: Nightly Builds Available

[Piotr Zarzycki]

Hah! Harbs greate idea for creating issue. If you could do that.

Thanks,
Piotr

2017-10-02 9:32 GMT+02:00 Harbs :

> I was in middle of writing the same thing. :)
>
> I think we should create an issue with what needs to be done for the
> rename. The obvious is a find/replace of org.apache.flex to
> org.apache.royale.
>
> I’m sure there’s other things to do, and if there’s a list, we could split
> up the work.
>
> > On Oct 2, 2017, at 10:29 AM, Piotr Zarzycki 
> wrote:
> >
> > Alex,
> >
> > I think we should have separate branch for renaming. Packaging could be
> > merge to develop, than we could create new branch for renaming. It should
> > be under folder feature/name - cause Maven build.a.o will pickup it
> > automatically.
> >
> > That's how I think would be the best.
> >
> > Piotr
> >
> > 2017-10-02 1:17 GMT+02:00 Alex Harui :
> >
> >> I'm tempted to just merge packaging into develop and start the rename
> and
> >> realize that things will likely be broken for several days.  Or we can
> do
> >> the rename in branches.
> >>
> >> I'll poke at the packaging a bit more before merging.
> >>
> >> -Alex
> >>
> >> On 10/1/17, 12:07 PM, "Piotr Zarzycki" 
> wrote:
> >>
> >>> Alex,
> >>>
> >>> Are you going to merge packaging branch to develop and then start
> renaming
> >>> process ? I'm asking cause maybe it would be good idea to move that
> branch
> >>> under folder feature/packaging - We will have to this automatically
> under
> >>> control of pipeline.
> >>>
> >>> Once renaming will start Maven build will tell us what is wrong also.
> >>>
> >>> Piotr
> >>>
> >>>
> >>> 2017-10-01 20:03 GMT+02:00 Piotr Zarzycki :
> >>>
>  Alex,
> 
>  Thanks new nightly JS Only is working nicely with Moonshine along with
>  my
>  fix. :)
> 
>  Thank you!
>  Piotr
> 
> 
>  2017-10-01 16:13 GMT+02:00 Alex Harui :
> 
> > Yes, you are correct that the SWCs got corrupted.  I made one change
> > but
> > won't have time to test until later today.  Feel free to grab the
> > latest
> > build and try again.
> >
> > Thanks,
> > -Alex
> >
> > On 9/30/17, 10:44 AM, "Piotr Zarzycki" 
> > wrote:
> >
> >> I just made small experiment.
> >>
> >> 1) I've downloaded FlexJS nightly using installer with Flash Player
> > 23.
> >> 2) Create new project in Moonshine and build it with
> -targets=JSFlex -
> >> Build pass without the problem
> >> 3) I went to the folder "\frameworks\js\FlexJS\libs\" and removed
> all
> > swc
> >> 4) I have copied swcs from your JS only version and build - it's
> > failed
> >> with same errors as it was through the console.
> >>
> >> Something is definitely wrong with those swcs.
> >>
> >> Piotr
> >>
> >>
> >> 2017-09-30 19:32 GMT+02:00 Piotr Zarzycki <
> piotrzarzyck...@gmail.com
> >>> :
> >>
> >>> Alex,
> >>>
> >>> You are right. I have found issue in Moonshine it basically parsing
> > the
> >>> target player from flex-config.xml to 11.0.0 not 11.7. However I
> > think
> >>> something is wrong itself with SDK, cause I should be able to build
> >>> project
> >>> from console, but I'm getting strange errors for swcs. [1]
> >>>
> >>> [1]
> >>> https://na01.safelinks.protection.outlook.com/?url=https%
> > 3A%2F%2Fpaste.ap
> >>> ache.org%2FTY72=02%7C01%7C%7C12fdd85b1aec493aa8bc08d5
> > 082ae732%7Cfa7b
> >>> 1b5a7b34438794aed2c178decee1%7C0%7C0%7C636423902740594589&
> > sdata=1E5qZgheJ
> >>> o3T7LqJlNOvhmEwhXVj3h6mLChHEERtKGc%3D=0
> >>>
> >>> Thanks, Piotr
> >>>
> >>> 2017-09-30 17:59 GMT+02:00 Alex Harui :
> >>>
>  The flex-config.xml in the JSOnly package should have
> > target-player of
>  11.7 and there should be a frameworks/libs/player/11.7/pl
> > ayerglobal.swc
> 
>  Are you not seeing that?  Maybe Moonshine is changing something?
> > I'm
>  out
>  of time for this morning.  Won't have more time until about 13
> > hours
>  from
>  now.
> 
>  Later,
>  -Alex
> 
>  On 9/30/17, 12:59 AM, "Piotr Zarzycki"  >
>  wrote:
> 
> > Hi Alex,
> >
> > I just tried build with Moonshine and it's searching playerglobal
> > [1].
>  I'm
> > not sure whether Moonshine need to change our generated config
> [2]
> > and
> > how.
> > It's being generated by Moonshine and it's always contains
>  target-player.
> > Maybe I should implement there checking whether flex-config.xml
> > does
>  exist
> > target-player ?
> 

Re: Nightly Builds Available

[Piotr Zarzycki]

Alex,

Thanks new nightly JS Only is working nicely with Moonshine along with my
fix. :)

Thank you!
Piotr


2017-10-01 16:13 GMT+02:00 Alex Harui :

> Yes, you are correct that the SWCs got corrupted.  I made one change but
> won't have time to test until later today.  Feel free to grab the latest
> build and try again.
>
> Thanks,
> -Alex
>
> On 9/30/17, 10:44 AM, "Piotr Zarzycki"  wrote:
>
> >I just made small experiment.
> >
> >1) I've downloaded FlexJS nightly using installer with Flash Player 23.
> >2) Create new project in Moonshine and build it with -targets=JSFlex -
> >Build pass without the problem
> >3) I went to the folder "\frameworks\js\FlexJS\libs\" and removed all swc
> >4) I have copied swcs from your JS only version and build - it's failed
> >with same errors as it was through the console.
> >
> >Something is definitely wrong with those swcs.
> >
> >Piotr
> >
> >
> >2017-09-30 19:32 GMT+02:00 Piotr Zarzycki :
> >
> >> Alex,
> >>
> >> You are right. I have found issue in Moonshine it basically parsing the
> >> target player from flex-config.xml to 11.0.0 not 11.7. However I think
> >> something is wrong itself with SDK, cause I should be able to build
> >>project
> >> from console, but I'm getting strange errors for swcs. [1]
> >>
> >> [1]
> >>https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fpaste.ap
> >>ache.org%2FTY72=02%7C01%7C%7C12fdd85b1aec493aa8bc08d5082a
> e732%7Cfa7b
> >>1b5a7b34438794aed2c178decee1%7C0%7C0%7C636423902740594589&
> sdata=1E5qZgheJ
> >>o3T7LqJlNOvhmEwhXVj3h6mLChHEERtKGc%3D=0
> >>
> >> Thanks, Piotr
> >>
> >> 2017-09-30 17:59 GMT+02:00 Alex Harui :
> >>
> >>> The flex-config.xml in the JSOnly package should have target-player of
> >>> 11.7 and there should be a frameworks/libs/player/11.7/
> playerglobal.swc
> >>>
> >>> Are you not seeing that?  Maybe Moonshine is changing something?  I'm
> >>>out
> >>> of time for this morning.  Won't have more time until about 13 hours
> >>>from
> >>> now.
> >>>
> >>> Later,
> >>> -Alex
> >>>
> >>> On 9/30/17, 12:59 AM, "Piotr Zarzycki" 
> >>>wrote:
> >>>
> >>> >Hi Alex,
> >>> >
> >>> >I just tried build with Moonshine and it's searching playerglobal [1].
> >>> I'm
> >>> >not sure whether Moonshine need to change our generated config [2] and
> >>> >how.
> >>> >It's being generated by Moonshine and it's always contains
> >>>target-player.
> >>> >Maybe I should implement there checking whether flex-config.xml does
> >>> exist
> >>> >target-player ?
> >>> >
> >>> >[1]
> >>> >https://na01.safelinks.protection.outlook.com/?url=https%
> >>> 3A%2F%2Fpaste.apa
> >>> >che.org%2FBtco=02%7C01%7C%7C58c35153163b4fe45ee608d507
> >>> d93fff%7Cfa7b1b
> >>> >5a7b34438794aed2c178decee1%7C0%7C0%7C636423552028633728
> >>> ta=CYkAR9I4VUQW
> >>> >VWAfG4aU%2Fw8SiDDonwf61%2FxgAFbcJgc%3D=0
> >>> >[2]
> >>> >https://na01.safelinks.protection.outlook.com/?url=https%
> >>> 3A%2F%2Fpaste.apa
> >>> >che.org%2FYT9p=02%7C01%7C%7C58c35153163b4fe45ee608d507
> >>> d93fff%7Cfa7b1b
> >>> >5a7b34438794aed2c178decee1%7C0%7C0%7C636423552028633728
> >>> ta=XEiWErWJcW5l
> >>> >hlgnX5asnWJI4Dna9zqwTRQAsipmmEM%3D=0
> >>> >
> >>> >Piotr
> >>> >
> >>> >2017-09-30 9:40 GMT+02:00 Alex Harui :
> >>> >
> >>> >> Hi Folks,
> >>> >>
> >>> >> I have the Ant builds completing successfully on my CI server.
> >>>What is
> >>> >> different about the output for Royale is that we are experimenting
> >>>with
> >>> >> different packaging so we don't need to use the Apache Flex SDK
> >>> >>Installer,
> >>> >> which was having problems with large Adobe AIR SDKs.
> >>> >>
> >>> >> There are two kinds of packages, one I'm calling FlexJS which can
> >>> output
> >>> >> both SWF and JS, and one currently called JSOnly that will likely be
> >>> >>named
> >>> >> Royale later.  These packages may not work right now, but at least
> >>> >>should
> >>> >> serve as a starting point.  I've seen both be accepted by Flash
> >>>Builder
> >>> >>as
> >>> >> a valid Flex SDK, but haven't tested that they compile projects
> >>> >> successfully.
> >>> >>
> >>> >> The JSOnly packages are available here:
> >>> >>
> >>> >>
> >>> >>https://na01.safelinks.protection.outlook.com/?url=http%
> >>> 3A%2F%2Fapachefle
> >>> >>xbuild.cloudapp.net%3A8080%2Fjob%2Froyale-=02%7C01%7C
> >>> %7C58c35153163b
> >>> >>4fe45ee608d507d93fff%7Cfa7b1b5a7b34438794aed2c178decee1%
> >>> 7C0%7C0%7C6364235
> >>> >>52028633728=JeRvJNpWqUGGtCc5DtnD7oX5hwL9ryUIfbiLXhIp
> >>> XNw%3D
> >>> >>=0
> >>> >> asjs-jsonly/lastSuccess
> >>> >> fulBuild/artifact/out/apache-flex-jsonly-0.9.0-bin.tar.gz
> >>> >>
> >>> >>https://na01.safelinks.protection.outlook.com/?url=http%
> >>> 3A%2F%2Fapachefle
> >>> >>xbuild.cloudapp.net%3A8080%2Fjob%2Froyale-=02%7C01%7C
> >>> %7C58c35153163b
> >>> >>4fe45ee608d507d93fff%7Cfa7b1b5a7b34438794aed2c178decee1%
> >>> 7C0%7C0%7C6364235
> >>> 

Re: Nightly Builds Available

[Piotr Zarzycki]

I just fixed that issue in Moonshine. It will be available in upcoming
1.6.0 release. :)

Thanks!

2017-09-30 19:32 GMT+02:00 Piotr Zarzycki :

> Alex,
>
> You are right. I have found issue in Moonshine it basically parsing the
> target player from flex-config.xml to 11.0.0 not 11.7. However I think
> something is wrong itself with SDK, cause I should be able to build project
> from console, but I'm getting strange errors for swcs. [1]
>
> [1] https://paste.apache.org/TY72
>
> Thanks, Piotr
>
> 2017-09-30 17:59 GMT+02:00 Alex Harui :
>
>> The flex-config.xml in the JSOnly package should have target-player of
>> 11.7 and there should be a frameworks/libs/player/11.7/playerglobal.swc
>>
>> Are you not seeing that?  Maybe Moonshine is changing something?  I'm out
>> of time for this morning.  Won't have more time until about 13 hours from
>> now.
>>
>> Later,
>> -Alex
>>
>> On 9/30/17, 12:59 AM, "Piotr Zarzycki"  wrote:
>>
>> >Hi Alex,
>> >
>> >I just tried build with Moonshine and it's searching playerglobal [1].
>> I'm
>> >not sure whether Moonshine need to change our generated config [2] and
>> >how.
>> >It's being generated by Moonshine and it's always contains target-player.
>> >Maybe I should implement there checking whether flex-config.xml does
>> exist
>> >target-player ?
>> >
>> >[1]
>> >https://na01.safelinks.protection.outlook.com/?url=https%
>> 3A%2F%2Fpaste.apa
>> >che.org%2FBtco=02%7C01%7C%7C58c35153163b4fe45ee608d507
>> d93fff%7Cfa7b1b
>> >5a7b34438794aed2c178decee1%7C0%7C0%7C636423552028633728
>> ta=CYkAR9I4VUQW
>> >VWAfG4aU%2Fw8SiDDonwf61%2FxgAFbcJgc%3D=0
>> >[2]
>> >https://na01.safelinks.protection.outlook.com/?url=https%
>> 3A%2F%2Fpaste.apa
>> >che.org%2FYT9p=02%7C01%7C%7C58c35153163b4fe45ee608d507
>> d93fff%7Cfa7b1b
>> >5a7b34438794aed2c178decee1%7C0%7C0%7C636423552028633728
>> ta=XEiWErWJcW5l
>> >hlgnX5asnWJI4Dna9zqwTRQAsipmmEM%3D=0
>> >
>> >Piotr
>> >
>> >2017-09-30 9:40 GMT+02:00 Alex Harui :
>> >
>> >> Hi Folks,
>> >>
>> >> I have the Ant builds completing successfully on my CI server.  What is
>> >> different about the output for Royale is that we are experimenting with
>> >> different packaging so we don't need to use the Apache Flex SDK
>> >>Installer,
>> >> which was having problems with large Adobe AIR SDKs.
>> >>
>> >> There are two kinds of packages, one I'm calling FlexJS which can
>> output
>> >> both SWF and JS, and one currently called JSOnly that will likely be
>> >>named
>> >> Royale later.  These packages may not work right now, but at least
>> >>should
>> >> serve as a starting point.  I've seen both be accepted by Flash Builder
>> >>as
>> >> a valid Flex SDK, but haven't tested that they compile projects
>> >> successfully.
>> >>
>> >> The JSOnly packages are available here:
>> >>
>> >>
>> >>https://na01.safelinks.protection.outlook.com/?url=http%
>> 3A%2F%2Fapachefle
>> >>xbuild.cloudapp.net%3A8080%2Fjob%2Froyale-=02%7C01%7C
>> %7C58c35153163b
>> >>4fe45ee608d507d93fff%7Cfa7b1b5a7b34438794aed2c178decee1%
>> 7C0%7C0%7C6364235
>> >>52028633728=JeRvJNpWqUGGtCc5DtnD7oX5hwL9ryUIfbiLXhIp
>> XNw%3D
>> >>=0
>> >> asjs-jsonly/lastSuccess
>> >> fulBuild/artifact/out/apache-flex-jsonly-0.9.0-bin.tar.gz
>> >>
>> >>https://na01.safelinks.protection.outlook.com/?url=http%
>> 3A%2F%2Fapachefle
>> >>xbuild.cloudapp.net%3A8080%2Fjob%2Froyale-=02%7C01%7C
>> %7C58c35153163b
>> >>4fe45ee608d507d93fff%7Cfa7b1b5a7b34438794aed2c178decee1%
>> 7C0%7C0%7C6364235
>> >>52028633728=JeRvJNpWqUGGtCc5DtnD7oX5hwL9ryUIfbiLXhIp
>> XNw%3D
>> >>=0
>> >> asjs-jsonly/lastSuccess
>> >> fulBuild/artifact/out/apache-flex-jsonly-0.9.0-bin.zip
>> >>
>> >>
>> >> You should be able to just unzip this package and use it in Flash
>> >>Builder.
>> >>  Hopefully other IDEs as well.  I've only tried in on my Mac.
>> >>
>> >> The FlexJS packages are available here:
>> >>
>> >>
>> >>https://na01.safelinks.protection.outlook.com/?url=http%
>> 3A%2F%2Fapachefle
>> >>xbuild.cloudapp.net%3A8080%2Fjob%2Froyale-=02%7C01%7C
>> %7C58c35153163b
>> >>4fe45ee608d507d93fff%7Cfa7b1b5a7b34438794aed2c178decee1%
>> 7C0%7C0%7C6364235
>> >>52028633728=JeRvJNpWqUGGtCc5DtnD7oX5hwL9ryUIfbiLXhIp
>> XNw%3D
>> >>=0
>> >> asjs/lastSuccessfulBuil
>> >> d/artifact/out/apache-flex-flexjs-0.9.0-bin.tar.gz
>> >>
>> >>https://na01.safelinks.protection.outlook.com/?url=http%
>> 3A%2F%2Fapachefle
>> >>xbuild.cloudapp.net%3A8080%2Fjob%2Froyale-=02%7C01%7C
>> %7C58c35153163b
>> >>4fe45ee608d507d93fff%7Cfa7b1b5a7b34438794aed2c178decee1%
>> 7C0%7C0%7C6364235
>> >>52028633728=JeRvJNpWqUGGtCc5DtnD7oX5hwL9ryUIfbiLXhIp
>> XNw%3D
>> >>=0
>> >> asjs/lastSuccessfulBuil
>> >> d/artifact/out/apache-flex-flexjs-0.9.0-bin.zip
>> >>
>> >>
>> >> These packages need the AIR SDK and playerglobal.swc.  First, unzip
>> this
>> >> package into a folder, then from that folder, run:
>> >>
>> >>   ant -f InstallAdobeSDKs.xml
>> >>
>> >> It should provide instructions on 

Re: Nightly Builds Available

[Piotr Zarzycki]

I just made small experiment.

1) I've downloaded FlexJS nightly using installer with Flash Player 23.
2) Create new project in Moonshine and build it with -targets=JSFlex -
Build pass without the problem
3) I went to the folder "\frameworks\js\FlexJS\libs\" and removed all swc
4) I have copied swcs from your JS only version and build - it's failed
with same errors as it was through the console.

Something is definitely wrong with those swcs.

Piotr


2017-09-30 19:32 GMT+02:00 Piotr Zarzycki :

> Alex,
>
> You are right. I have found issue in Moonshine it basically parsing the
> target player from flex-config.xml to 11.0.0 not 11.7. However I think
> something is wrong itself with SDK, cause I should be able to build project
> from console, but I'm getting strange errors for swcs. [1]
>
> [1] https://paste.apache.org/TY72
>
> Thanks, Piotr
>
> 2017-09-30 17:59 GMT+02:00 Alex Harui :
>
>> The flex-config.xml in the JSOnly package should have target-player of
>> 11.7 and there should be a frameworks/libs/player/11.7/playerglobal.swc
>>
>> Are you not seeing that?  Maybe Moonshine is changing something?  I'm out
>> of time for this morning.  Won't have more time until about 13 hours from
>> now.
>>
>> Later,
>> -Alex
>>
>> On 9/30/17, 12:59 AM, "Piotr Zarzycki"  wrote:
>>
>> >Hi Alex,
>> >
>> >I just tried build with Moonshine and it's searching playerglobal [1].
>> I'm
>> >not sure whether Moonshine need to change our generated config [2] and
>> >how.
>> >It's being generated by Moonshine and it's always contains target-player.
>> >Maybe I should implement there checking whether flex-config.xml does
>> exist
>> >target-player ?
>> >
>> >[1]
>> >https://na01.safelinks.protection.outlook.com/?url=https%
>> 3A%2F%2Fpaste.apa
>> >che.org%2FBtco=02%7C01%7C%7C58c35153163b4fe45ee608d507
>> d93fff%7Cfa7b1b
>> >5a7b34438794aed2c178decee1%7C0%7C0%7C636423552028633728
>> ta=CYkAR9I4VUQW
>> >VWAfG4aU%2Fw8SiDDonwf61%2FxgAFbcJgc%3D=0
>> >[2]
>> >https://na01.safelinks.protection.outlook.com/?url=https%
>> 3A%2F%2Fpaste.apa
>> >che.org%2FYT9p=02%7C01%7C%7C58c35153163b4fe45ee608d507
>> d93fff%7Cfa7b1b
>> >5a7b34438794aed2c178decee1%7C0%7C0%7C636423552028633728
>> ta=XEiWErWJcW5l
>> >hlgnX5asnWJI4Dna9zqwTRQAsipmmEM%3D=0
>> >
>> >Piotr
>> >
>> >2017-09-30 9:40 GMT+02:00 Alex Harui :
>> >
>> >> Hi Folks,
>> >>
>> >> I have the Ant builds completing successfully on my CI server.  What is
>> >> different about the output for Royale is that we are experimenting with
>> >> different packaging so we don't need to use the Apache Flex SDK
>> >>Installer,
>> >> which was having problems with large Adobe AIR SDKs.
>> >>
>> >> There are two kinds of packages, one I'm calling FlexJS which can
>> output
>> >> both SWF and JS, and one currently called JSOnly that will likely be
>> >>named
>> >> Royale later.  These packages may not work right now, but at least
>> >>should
>> >> serve as a starting point.  I've seen both be accepted by Flash Builder
>> >>as
>> >> a valid Flex SDK, but haven't tested that they compile projects
>> >> successfully.
>> >>
>> >> The JSOnly packages are available here:
>> >>
>> >>
>> >>https://na01.safelinks.protection.outlook.com/?url=http%
>> 3A%2F%2Fapachefle
>> >>xbuild.cloudapp.net%3A8080%2Fjob%2Froyale-=02%7C01%7C
>> %7C58c35153163b
>> >>4fe45ee608d507d93fff%7Cfa7b1b5a7b34438794aed2c178decee1%
>> 7C0%7C0%7C6364235
>> >>52028633728=JeRvJNpWqUGGtCc5DtnD7oX5hwL9ryUIfbiLXhIp
>> XNw%3D
>> >>=0
>> >> asjs-jsonly/lastSuccess
>> >> fulBuild/artifact/out/apache-flex-jsonly-0.9.0-bin.tar.gz
>> >>
>> >>https://na01.safelinks.protection.outlook.com/?url=http%
>> 3A%2F%2Fapachefle
>> >>xbuild.cloudapp.net%3A8080%2Fjob%2Froyale-=02%7C01%7C
>> %7C58c35153163b
>> >>4fe45ee608d507d93fff%7Cfa7b1b5a7b34438794aed2c178decee1%
>> 7C0%7C0%7C6364235
>> >>52028633728=JeRvJNpWqUGGtCc5DtnD7oX5hwL9ryUIfbiLXhIp
>> XNw%3D
>> >>=0
>> >> asjs-jsonly/lastSuccess
>> >> fulBuild/artifact/out/apache-flex-jsonly-0.9.0-bin.zip
>> >>
>> >>
>> >> You should be able to just unzip this package and use it in Flash
>> >>Builder.
>> >>  Hopefully other IDEs as well.  I've only tried in on my Mac.
>> >>
>> >> The FlexJS packages are available here:
>> >>
>> >>
>> >>https://na01.safelinks.protection.outlook.com/?url=http%
>> 3A%2F%2Fapachefle
>> >>xbuild.cloudapp.net%3A8080%2Fjob%2Froyale-=02%7C01%7C
>> %7C58c35153163b
>> >>4fe45ee608d507d93fff%7Cfa7b1b5a7b34438794aed2c178decee1%
>> 7C0%7C0%7C6364235
>> >>52028633728=JeRvJNpWqUGGtCc5DtnD7oX5hwL9ryUIfbiLXhIp
>> XNw%3D
>> >>=0
>> >> asjs/lastSuccessfulBuil
>> >> d/artifact/out/apache-flex-flexjs-0.9.0-bin.tar.gz
>> >>
>> >>https://na01.safelinks.protection.outlook.com/?url=http%
>> 3A%2F%2Fapachefle
>> >>xbuild.cloudapp.net%3A8080%2Fjob%2Froyale-=02%7C01%7C
>> %7C58c35153163b
>> >>4fe45ee608d507d93fff%7Cfa7b1b5a7b34438794aed2c178decee1%
>> 7C0%7C0%7C6364235
>> 

Re: Nightly Builds Available

[Piotr Zarzycki]

Alex,

You are right. I have found issue in Moonshine it basically parsing the
target player from flex-config.xml to 11.0.0 not 11.7. However I think
something is wrong itself with SDK, cause I should be able to build project
from console, but I'm getting strange errors for swcs. [1]

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

Thanks, Piotr

2017-09-30 17:59 GMT+02:00 Alex Harui :

> The flex-config.xml in the JSOnly package should have target-player of
> 11.7 and there should be a frameworks/libs/player/11.7/playerglobal.swc
>
> Are you not seeing that?  Maybe Moonshine is changing something?  I'm out
> of time for this morning.  Won't have more time until about 13 hours from
> now.
>
> Later,
> -Alex
>
> On 9/30/17, 12:59 AM, "Piotr Zarzycki"  wrote:
>
> >Hi Alex,
> >
> >I just tried build with Moonshine and it's searching playerglobal [1]. I'm
> >not sure whether Moonshine need to change our generated config [2] and
> >how.
> >It's being generated by Moonshine and it's always contains target-player.
> >Maybe I should implement there checking whether flex-config.xml does exist
> >target-player ?
> >
> >[1]
> >https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fpaste.apa
> >che.org%2FBtco=02%7C01%7C%7C58c35153163b4fe45ee608d507d9
> 3fff%7Cfa7b1b
> >5a7b34438794aed2c178decee1%7C0%7C0%7C636423552028633728&
> sdata=CYkAR9I4VUQW
> >VWAfG4aU%2Fw8SiDDonwf61%2FxgAFbcJgc%3D=0
> >[2]
> >https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fpaste.apa
> >che.org%2FYT9p=02%7C01%7C%7C58c35153163b4fe45ee608d507d9
> 3fff%7Cfa7b1b
> >5a7b34438794aed2c178decee1%7C0%7C0%7C636423552028633728&
> sdata=XEiWErWJcW5l
> >hlgnX5asnWJI4Dna9zqwTRQAsipmmEM%3D=0
> >
> >Piotr
> >
> >2017-09-30 9:40 GMT+02:00 Alex Harui :
> >
> >> Hi Folks,
> >>
> >> I have the Ant builds completing successfully on my CI server.  What is
> >> different about the output for Royale is that we are experimenting with
> >> different packaging so we don't need to use the Apache Flex SDK
> >>Installer,
> >> which was having problems with large Adobe AIR SDKs.
> >>
> >> There are two kinds of packages, one I'm calling FlexJS which can output
> >> both SWF and JS, and one currently called JSOnly that will likely be
> >>named
> >> Royale later.  These packages may not work right now, but at least
> >>should
> >> serve as a starting point.  I've seen both be accepted by Flash Builder
> >>as
> >> a valid Flex SDK, but haven't tested that they compile projects
> >> successfully.
> >>
> >> The JSOnly packages are available here:
> >>
> >>
> >>https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fapachefle
> >>xbuild.cloudapp.net%3A8080%2Fjob%2Froyale-=02%7C01%
> 7C%7C58c35153163b
> >>4fe45ee608d507d93fff%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6364235
> >>52028633728=JeRvJNpWqUGGtCc5DtnD7oX5hwL9ry
> UIfbiLXhIpXNw%3D
> >>=0
> >> asjs-jsonly/lastSuccess
> >> fulBuild/artifact/out/apache-flex-jsonly-0.9.0-bin.tar.gz
> >>
> >>https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fapachefle
> >>xbuild.cloudapp.net%3A8080%2Fjob%2Froyale-=02%7C01%
> 7C%7C58c35153163b
> >>4fe45ee608d507d93fff%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6364235
> >>52028633728=JeRvJNpWqUGGtCc5DtnD7oX5hwL9ry
> UIfbiLXhIpXNw%3D
> >>=0
> >> asjs-jsonly/lastSuccess
> >> fulBuild/artifact/out/apache-flex-jsonly-0.9.0-bin.zip
> >>
> >>
> >> You should be able to just unzip this package and use it in Flash
> >>Builder.
> >>  Hopefully other IDEs as well.  I've only tried in on my Mac.
> >>
> >> The FlexJS packages are available here:
> >>
> >>
> >>https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fapachefle
> >>xbuild.cloudapp.net%3A8080%2Fjob%2Froyale-=02%7C01%
> 7C%7C58c35153163b
> >>4fe45ee608d507d93fff%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6364235
> >>52028633728=JeRvJNpWqUGGtCc5DtnD7oX5hwL9ry
> UIfbiLXhIpXNw%3D
> >>=0
> >> asjs/lastSuccessfulBuil
> >> d/artifact/out/apache-flex-flexjs-0.9.0-bin.tar.gz
> >>
> >>https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fapachefle
> >>xbuild.cloudapp.net%3A8080%2Fjob%2Froyale-=02%7C01%
> 7C%7C58c35153163b
> >>4fe45ee608d507d93fff%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6364235
> >>52028633728=JeRvJNpWqUGGtCc5DtnD7oX5hwL9ry
> UIfbiLXhIpXNw%3D
> >>=0
> >> asjs/lastSuccessfulBuil
> >> d/artifact/out/apache-flex-flexjs-0.9.0-bin.zip
> >>
> >>
> >> These packages need the AIR SDK and playerglobal.swc.  First, unzip this
> >> package into a folder, then from that folder, run:
> >>
> >>   ant -f InstallAdobeSDKs.xml
> >>
> >> It should provide instructions on how to get the AIR SDK and
> >>playerglobal.
> >>  This is just one idea for how to do this.  I'm not sure it is the best
> >> way, but my goal was to get us out of the game of presenting Adobe's
> >> licensing acceptance in our code.  I think there are plans to use NPM as
> >> well.  Other ideas are welcome.
> >>
> >> 

Re: Nightly Builds Available

[Alex Harui]

The flex-config.xml in the JSOnly package should have target-player of
11.7 and there should be a frameworks/libs/player/11.7/playerglobal.swc

Are you not seeing that?  Maybe Moonshine is changing something?  I'm out
of time for this morning.  Won't have more time until about 13 hours from
now.

Later,
-Alex

On 9/30/17, 12:59 AM, "Piotr Zarzycki"  wrote:

>Hi Alex,
>
>I just tried build with Moonshine and it's searching playerglobal [1]. I'm
>not sure whether Moonshine need to change our generated config [2] and
>how.
>It's being generated by Moonshine and it's always contains target-player.
>Maybe I should implement there checking whether flex-config.xml does exist
>target-player ?
>
>[1] 
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apa
>che.org%2FBtco=02%7C01%7C%7C58c35153163b4fe45ee608d507d93fff%7Cfa7b1b
>5a7b34438794aed2c178decee1%7C0%7C0%7C636423552028633728=CYkAR9I4VUQW
>VWAfG4aU%2Fw8SiDDonwf61%2FxgAFbcJgc%3D=0
>[2] 
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apa
>che.org%2FYT9p=02%7C01%7C%7C58c35153163b4fe45ee608d507d93fff%7Cfa7b1b
>5a7b34438794aed2c178decee1%7C0%7C0%7C636423552028633728=XEiWErWJcW5l
>hlgnX5asnWJI4Dna9zqwTRQAsipmmEM%3D=0
>
>Piotr
>
>2017-09-30 9:40 GMT+02:00 Alex Harui :
>
>> Hi Folks,
>>
>> I have the Ant builds completing successfully on my CI server.  What is
>> different about the output for Royale is that we are experimenting with
>> different packaging so we don't need to use the Apache Flex SDK
>>Installer,
>> which was having problems with large Adobe AIR SDKs.
>>
>> There are two kinds of packages, one I'm calling FlexJS which can output
>> both SWF and JS, and one currently called JSOnly that will likely be
>>named
>> Royale later.  These packages may not work right now, but at least
>>should
>> serve as a starting point.  I've seen both be accepted by Flash Builder
>>as
>> a valid Flex SDK, but haven't tested that they compile projects
>> successfully.
>>
>> The JSOnly packages are available here:
>>
>> 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapachefle
>>xbuild.cloudapp.net%3A8080%2Fjob%2Froyale-=02%7C01%7C%7C58c35153163b
>>4fe45ee608d507d93fff%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364235
>>52028633728=JeRvJNpWqUGGtCc5DtnD7oX5hwL9ryUIfbiLXhIpXNw%3D
>>=0
>> asjs-jsonly/lastSuccess
>> fulBuild/artifact/out/apache-flex-jsonly-0.9.0-bin.tar.gz
>> 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapachefle
>>xbuild.cloudapp.net%3A8080%2Fjob%2Froyale-=02%7C01%7C%7C58c35153163b
>>4fe45ee608d507d93fff%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364235
>>52028633728=JeRvJNpWqUGGtCc5DtnD7oX5hwL9ryUIfbiLXhIpXNw%3D
>>=0
>> asjs-jsonly/lastSuccess
>> fulBuild/artifact/out/apache-flex-jsonly-0.9.0-bin.zip
>>
>>
>> You should be able to just unzip this package and use it in Flash
>>Builder.
>>  Hopefully other IDEs as well.  I've only tried in on my Mac.
>>
>> The FlexJS packages are available here:
>>
>> 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapachefle
>>xbuild.cloudapp.net%3A8080%2Fjob%2Froyale-=02%7C01%7C%7C58c35153163b
>>4fe45ee608d507d93fff%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364235
>>52028633728=JeRvJNpWqUGGtCc5DtnD7oX5hwL9ryUIfbiLXhIpXNw%3D
>>=0
>> asjs/lastSuccessfulBuil
>> d/artifact/out/apache-flex-flexjs-0.9.0-bin.tar.gz
>> 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapachefle
>>xbuild.cloudapp.net%3A8080%2Fjob%2Froyale-=02%7C01%7C%7C58c35153163b
>>4fe45ee608d507d93fff%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364235
>>52028633728=JeRvJNpWqUGGtCc5DtnD7oX5hwL9ryUIfbiLXhIpXNw%3D
>>=0
>> asjs/lastSuccessfulBuil
>> d/artifact/out/apache-flex-flexjs-0.9.0-bin.zip
>>
>>
>> These packages need the AIR SDK and playerglobal.swc.  First, unzip this
>> package into a folder, then from that folder, run:
>>
>>   ant -f InstallAdobeSDKs.xml
>>
>> It should provide instructions on how to get the AIR SDK and
>>playerglobal.
>>  This is just one idea for how to do this.  I'm not sure it is the best
>> way, but my goal was to get us out of the game of presenting Adobe's
>> licensing acceptance in our code.  I think there are plans to use NPM as
>> well.  Other ideas are welcome.
>>
>> Hopefully Maven builds will be available soon.  Note that the code is
>> still referencing Flex and FlexJS everywhere.  That will likely change
>> next week and be replaced by Royale.
>>
>> Later,
>> -Alex
>>
>>
>>
>
>
>-- 
>
>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%7C58c35153163b4fe45ee608d507d93fff%
>7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636423552028633728=G4fo
>DFkHDTxyLBQSChod2qgtf9i%2BJmAup1Qmbt9rB3M%3D=0
>

Re: Nightly Builds Available

[Piotr Zarzycki]

The last test was using console and it's failed with similar stack as ANT
failed. [1]

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

Thanks,
Piotr

2017-09-30 10:49 GMT+02:00 Piotr Zarzycki :

> I just did also try to build project by build.xml ant file which I've
> prepared for Moonshine. - It will be attached to each created new FlexJS
> project as an option of alternative build.
>
> It also failed - it was working with Installer version of FlexJS. [1][2]
>
> [1] https://paste.apache.org/VOHp
> [2] https://paste.apache.org/oDmp
>
> Thanks,
> Piotr
>
>
> 2017-09-30 9:59 GMT+02:00 Piotr Zarzycki :
>
>> Hi Alex,
>>
>> I just tried build with Moonshine and it's searching playerglobal [1].
>> I'm not sure whether Moonshine need to change our generated config [2] and
>> how.
>> It's being generated by Moonshine and it's always contains target-player.
>> Maybe I should implement there checking whether flex-config.xml does exist
>> target-player ?
>>
>> [1] https://paste.apache.org/Btco
>> [2] https://paste.apache.org/YT9p
>>
>> Piotr
>>
>> 2017-09-30 9:40 GMT+02:00 Alex Harui :
>>
>>> Hi Folks,
>>>
>>> I have the Ant builds completing successfully on my CI server.  What is
>>> different about the output for Royale is that we are experimenting with
>>> different packaging so we don't need to use the Apache Flex SDK
>>> Installer,
>>> which was having problems with large Adobe AIR SDKs.
>>>
>>> There are two kinds of packages, one I'm calling FlexJS which can output
>>> both SWF and JS, and one currently called JSOnly that will likely be
>>> named
>>> Royale later.  These packages may not work right now, but at least should
>>> serve as a starting point.  I've seen both be accepted by Flash Builder
>>> as
>>> a valid Flex SDK, but haven't tested that they compile projects
>>> successfully.
>>>
>>> The JSOnly packages are available here:
>>>
>>> http://apacheflexbuild.cloudapp.net:8080/job/royale-asjs-jso
>>> nly/lastSuccess
>>> fulBuild/artifact/out/apache-flex-jsonly-0.9.0-bin.tar.gz
>>> 
>>> http://apacheflexbuild.cloudapp.net:8080/job/royale-asjs-jso
>>> nly/lastSuccess
>>> fulBuild/artifact/out/apache-flex-jsonly-0.9.0-bin.zip
>>> 
>>>
>>>
>>> You should be able to just unzip this package and use it in Flash
>>> Builder.
>>>  Hopefully other IDEs as well.  I've only tried in on my Mac.
>>>
>>> The FlexJS packages are available here:
>>>
>>> http://apacheflexbuild.cloudapp.net:8080/job/royale-asjs/las
>>> tSuccessfulBuil
>>> d/artifact/out/apache-flex-flexjs-0.9.0-bin.tar.gz
>>> 
>>> http://apacheflexbuild.cloudapp.net:8080/job/royale-asjs/las
>>> tSuccessfulBuil
>>> d/artifact/out/apache-flex-flexjs-0.9.0-bin.zip
>>> 
>>>
>>>
>>> These packages need the AIR SDK and playerglobal.swc.  First, unzip this
>>> package into a folder, then from that folder, run:
>>>
>>>   ant -f InstallAdobeSDKs.xml
>>>
>>> It should provide instructions on how to get the AIR SDK and
>>> playerglobal.
>>>  This is just one idea for how to do this.  I'm not sure it is the best
>>> way, but my goal was to get us out of the game of presenting Adobe's
>>> licensing acceptance in our code.  I think there are plans to use NPM as
>>> well.  Other ideas are welcome.
>>>
>>> Hopefully Maven builds will be available soon.  Note that the code is
>>> still referencing Flex and FlexJS everywhere.  That will likely change
>>> next week and be replaced by Royale.
>>>
>>> Later,
>>> -Alex
>>>
>>>
>>>
>>
>>
>> --
>>
>> 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 <+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