Re: MXRoyale build problem

2018-04-10 Thread Carlos Rovira
ok Alex,

if that makes a problem I'll not use it.
Regarding the problem you have, my work is mostly Jewel projects that are
separate from other things you're doing.
I think there was few files that I must to fix due to when I added
classList methods and Harbs added it to develop, and made me to solve
conflicts at that time.




2018-04-10 17:28 GMT+02:00 Alex Harui <aha...@adobe.com>:

> Carlos,
>
> I was unable to know how to work on the Jewel branch back when you were
> still working on it because I got concerned about the status showing some
> number of commits ahead and behind against my working copy.  If this is
> somehow related to your use of force push, I would strongly recommend that
> you not use it, especially on the develop branch.   Whatever workflow you
> think is right for remote branches is clearly not right.
>
> Thanks,
> -Alex
>
> From: <carlos.rov...@gmail.com> on behalf of Carlos Rovira <
> carlosrov...@apache.org>
> Reply-To: "users@royale.apache.org" <users@royale.apache.org>
> Date: Tuesday, April 10, 2018 at 4:03 AM
>
> To: "users@royale.apache.org" <users@royale.apache.org>
> Subject: Re: MXRoyale build problem
>
> jewel branch was already merged, so since some days I'm not using it. I
> didn't remove it totally, but I'll do in some days (maybe after 0.9.3
> release)
> Maybe for this reason you are a bit confused with that branch, since is
> now deprecated and not synced.
>
> I think my use of rebase is totally ok, so don't worry since I'm using it
> since the beginning with MDL and now with Jewel, and branches are ok.
>
> 2018-04-10 9:21 GMT+02:00 Harbs <harbs.li...@gmail.com>:
>
>> I suspect that Carlos is doing something different because the
>> jewel-ui-set branch currently shows 22 commits ahead and 127 behind on my
>> machine.
>>
>> Considering I made no local changes, I should not be *any* commits
>> ahead. That would seem like origin has had its history modified which is
>> not good. The only way I would be able to pull in the jewel branch would be
>> to rebase locally...
>>
>> My $0.02,
>> Harbs
>>
>> On Apr 10, 2018, at 7:52 AM, Alex Harui <aha...@adobe.com> wrote:
>>
>> Hi Carlos,
>>
>> Does that mean you are using "force push" when rebasing?  I don't use it
>> when rebasing and lots of internet articles advise against using it.  If it
>> is working for you, fine, but I wouldn't want any "forcing" to be a
>> recommended practice for others given the advice I see out there.
>>
>> The key thing for any of us is to understand the differences between
>> merging and rebasing and using them appropriately.  I don't want to take
>> the time to go through it now, but the recommended practice AIUI, is to use
>> merge for public branches and rebase when possible for non-public
>> branches.  MXRoyale is a public branch.
>>
>> Thanks,
>> -Alex
>>
>> From: <carlos.rov...@gmail.com> on behalf of Carlos Rovira <
>> carlosrov...@apache.org>
>> Reply-To: "users@royale.apache.org" <users@royale.apache.org>
>> Date: Monday, April 9, 2018 at 3:01 PM
>> To: "users@royale.apache.org" <users@royale.apache.org>
>> Subject: Re: MXRoyale build problem
>>
>> Hi Alex,
>>
>> my problem as I started to use again was that I forgot to check "force
>> push" completely. Without that you are not able to do a rebase, instead you
>> end with a corrupt branch. That was my problem, and I finaly remember that
>> I need to set up that. The way I use to rebase was teach to me by a
>> recognized expert in Git use, and sometimes I use to ask him when I have
>> doubts about how to do something. Rebase is completely a best practice in
>> some scenarios, like the one I use, work in separate branch and rebase over
>> develop, then merge to develop, since you end with a set of consecutive
>> clean commits as if all that commits will be done in that point. No
>> intricate tree object graphs and if some external person comes to see the
>> graph will understand far better that something that is intrincated. Jewel
>> branch was done in this way, and you can see that is very clean.
>>
>> said that (as well I understand now what Piotr said), I only want to
>> express a way that is working for me, but if you all think is not good for
>> you, it's ok, as I said is all subjective, and each one should use what he
>> want (always that doesn't break anything , of course)
>>
>> Thanks
>>
>>
>> 2018-04-09 19:05 GMT+02:00 Alex Harui <aha...@

Re: MXRoyale build problem

2018-04-10 Thread Alex Harui
Carlos,

I was unable to know how to work on the Jewel branch back when you were still 
working on it because I got concerned about the status showing some number of 
commits ahead and behind against my working copy.  If this is somehow related 
to your use of force push, I would strongly recommend that you not use it, 
especially on the develop branch.   Whatever workflow you think is right for 
remote branches is clearly not right.

Thanks,
-Alex

From: <carlos.rov...@gmail.com<mailto:carlos.rov...@gmail.com>> on behalf of 
Carlos Rovira <carlosrov...@apache.org<mailto:carlosrov...@apache.org>>
Reply-To: "users@royale.apache.org<mailto:users@royale.apache.org>" 
<users@royale.apache.org<mailto:users@royale.apache.org>>
Date: Tuesday, April 10, 2018 at 4:03 AM
To: "users@royale.apache.org<mailto:users@royale.apache.org>" 
<users@royale.apache.org<mailto:users@royale.apache.org>>
Subject: Re: MXRoyale build problem

jewel branch was already merged, so since some days I'm not using it. I didn't 
remove it totally, but I'll do in some days (maybe after 0.9.3 release)
Maybe for this reason you are a bit confused with that branch, since is now 
deprecated and not synced.

I think my use of rebase is totally ok, so don't worry since I'm using it since 
the beginning with MDL and now with Jewel, and branches are ok.

2018-04-10 9:21 GMT+02:00 Harbs 
<harbs.li...@gmail.com<mailto:harbs.li...@gmail.com>>:
I suspect that Carlos is doing something different because the jewel-ui-set 
branch currently shows 22 commits ahead and 127 behind on my machine.

Considering I made no local changes, I should not be any commits ahead. That 
would seem like origin has had its history modified which is not good. The only 
way I would be able to pull in the jewel branch would be to rebase locally...

My $0.02,
Harbs

On Apr 10, 2018, at 7:52 AM, Alex Harui 
<aha...@adobe.com<mailto:aha...@adobe.com>> wrote:

Hi Carlos,

Does that mean you are using "force push" when rebasing?  I don't use it when 
rebasing and lots of internet articles advise against using it.  If it is 
working for you, fine, but I wouldn't want any "forcing" to be a recommended 
practice for others given the advice I see out there.

The key thing for any of us is to understand the differences between merging 
and rebasing and using them appropriately.  I don't want to take the time to go 
through it now, but the recommended practice AIUI, is to use merge for public 
branches and rebase when possible for non-public branches.  MXRoyale is a 
public branch.

Thanks,
-Alex

From: <carlos.rov...@gmail.com<mailto:carlos.rov...@gmail.com>> on behalf of 
Carlos Rovira <carlosrov...@apache.org<mailto:carlosrov...@apache.org>>
Reply-To: "users@royale.apache.org<mailto:users@royale.apache.org>" 
<users@royale.apache.org<mailto:users@royale.apache.org>>
Date: Monday, April 9, 2018 at 3:01 PM
To: "users@royale.apache.org<mailto:users@royale.apache.org>" 
<users@royale.apache.org<mailto:users@royale.apache.org>>
Subject: Re: MXRoyale build problem

Hi Alex,

my problem as I started to use again was that I forgot to check "force push" 
completely. Without that you are not able to do a rebase, instead you end with 
a corrupt branch. That was my problem, and I finaly remember that I need to set 
up that. The way I use to rebase was teach to me by a recognized expert in Git 
use, and sometimes I use to ask him when I have doubts about how to do 
something. Rebase is completely a best practice in some scenarios, like the one 
I use, work in separate branch and rebase over develop, then merge to develop, 
since you end with a set of consecutive clean commits as if all that commits 
will be done in that point. No intricate tree object graphs and if some 
external person comes to see the graph will understand far better that 
something that is intrincated. Jewel branch was done in this way, and you can 
see that is very clean.

said that (as well I understand now what Piotr said), I only want to express a 
way that is working for me, but if you all think is not good for you, it's ok, 
as I said is all subjective, and each one should use what he want (always that 
doesn't break anything , of course)

Thanks


2018-04-09 19:05 GMT+02:00 Alex Harui 
<aha...@adobe.com<mailto:aha...@adobe.com>>:
Hi Carlos,

Using "force push" sounds scary/wrong to me.  Note also that I had trouble 
working with your branches and you reported similar problems.  The general 
advice on the internet is to not rebase public branches, and I think I've hit 
scenarios around that often enough to want to give up on rebase when merging 
public branches.

I always use rebase when pulling changes in from the branch I'm working from.  
That's where it makes sense to me.

My 2 cen

Re: MXRoyale build problem

2018-04-10 Thread Carlos Rovira
jewel branch was already merged, so since some days I'm not using it. I
didn't remove it totally, but I'll do in some days (maybe after 0.9.3
release)
Maybe for this reason you are a bit confused with that branch, since is now
deprecated and not synced.

I think my use of rebase is totally ok, so don't worry since I'm using it
since the beginning with MDL and now with Jewel, and branches are ok.

2018-04-10 9:21 GMT+02:00 Harbs <harbs.li...@gmail.com>:

> I suspect that Carlos is doing something different because the
> jewel-ui-set branch currently shows 22 commits ahead and 127 behind on my
> machine.
>
> Considering I made no local changes, I should not be *any* commits ahead.
> That would seem like origin has had its history modified which is not good.
> The only way I would be able to pull in the jewel branch would be to rebase
> locally...
>
> My $0.02,
> Harbs
>
> On Apr 10, 2018, at 7:52 AM, Alex Harui <aha...@adobe.com> wrote:
>
> Hi Carlos,
>
> Does that mean you are using "force push" when rebasing?  I don't use it
> when rebasing and lots of internet articles advise against using it.  If it
> is working for you, fine, but I wouldn't want any "forcing" to be a
> recommended practice for others given the advice I see out there.
>
> The key thing for any of us is to understand the differences between
> merging and rebasing and using them appropriately.  I don't want to take
> the time to go through it now, but the recommended practice AIUI, is to use
> merge for public branches and rebase when possible for non-public
> branches.  MXRoyale is a public branch.
>
> Thanks,
> -Alex
>
> From: <carlos.rov...@gmail.com> on behalf of Carlos Rovira <
> carlosrov...@apache.org>
> Reply-To: "users@royale.apache.org" <users@royale.apache.org>
> Date: Monday, April 9, 2018 at 3:01 PM
> To: "users@royale.apache.org" <users@royale.apache.org>
> Subject: Re: MXRoyale build problem
>
> Hi Alex,
>
> my problem as I started to use again was that I forgot to check "force
> push" completely. Without that you are not able to do a rebase, instead you
> end with a corrupt branch. That was my problem, and I finaly remember that
> I need to set up that. The way I use to rebase was teach to me by a
> recognized expert in Git use, and sometimes I use to ask him when I have
> doubts about how to do something. Rebase is completely a best practice in
> some scenarios, like the one I use, work in separate branch and rebase over
> develop, then merge to develop, since you end with a set of consecutive
> clean commits as if all that commits will be done in that point. No
> intricate tree object graphs and if some external person comes to see the
> graph will understand far better that something that is intrincated. Jewel
> branch was done in this way, and you can see that is very clean.
>
> said that (as well I understand now what Piotr said), I only want to
> express a way that is working for me, but if you all think is not good for
> you, it's ok, as I said is all subjective, and each one should use what he
> want (always that doesn't break anything , of course)
>
> Thanks
>
>
> 2018-04-09 19:05 GMT+02:00 Alex Harui <aha...@adobe.com>:
>
>> Hi Carlos,
>>
>> Using "force push" sounds scary/wrong to me.  Note also that I had
>> trouble working with your branches and you reported similar problems.  The
>> general advice on the internet is to not rebase public branches, and I
>> think I've hit scenarios around that often enough to want to give up on
>> rebase when merging public branches.
>>
>> I always use rebase when pulling changes in from the branch I'm working
>> from.  That's where it makes sense to me.
>>
>> My 2 cents,
>> -Alex
>>
>> From: <carlos.rov...@gmail.com> on behalf of Carlos Rovira <
>> carlosrov...@apache.org>
>> Reply-To: "users@royale.apache.org" <users@royale.apache.org>
>> Date: Monday, April 9, 2018 at 9:46 AM
>>
>> To: "users@royale.apache.org" <users@royale.apache.org>
>> Subject: Re: MXRoyale build problem
>>
>> Hi,
>>
>> @Alex, the trick with rebase at least for me is that I must to have very
>> clear the steps to do or I can fail. For example, as I come again this
>> month to work on  Royale, I forget how to do that, and have to re-learn
>> all. For example in Sourcetree you must to set in preferences and option to
>> enable the "force push" or if you find conflicts, you must to solve and
>> recall do a "continue rebase" instead of commit the resolution of
>> conflicts. Bu

Re: MXRoyale build problem

2018-04-10 Thread Alex Harui
t-NoFlat-Primary-Topaz-Theme SKIPPED
>[INFO] Apache Royale: Framework: Themes:
>Jewel-Light-NoFlat-Secondary-Topaz-Theme SKIPPED
>[INFO] Apache Royale: Framework: Themes:
>Jewel-Light-NoFlat-Emphasized-Topaz-Theme SKIPPED
>[INFO] Apache Royale: Framework: Themes:
>Jewel-Light-NoFlat-Primary-Emerald-Theme SKIPPED
>[INFO] Apache Royale: Framework: Themes:
>Jewel-Light-NoFlat-Secondary-Emerald-Theme SKIPPED
>[INFO] Apache Royale: Framework: Themes:
>Jewel-Light-NoFlat-Emphasized-Emerald-Theme SKIPPED
>[INFO] Apache Royale: Framework: Archetypes ... SKIPPED
>[INFO] Apache Royale: Framework: Archetypes: Simple Royale Application
>SKIPPED
>[INFO] Apache Royale: Framework: Archetypes: Simple Royale Pure-JS
>Application SKIPPED
>[INFO] Apache Royale: Framework: Archetypes: Simple Royale Pure-SWF
>Application SKIPPED
>[INFO] Apache Royale: Framework: Archetypes: Simple Royale Library SKIPPED
>[INFO] Apache Royale: Framework: Archetypes: Simple Royale Typedef
>Library 0.9.3-SNAPSHOT SKIPPED
>[INFO]  
>
>[INFO] BUILD FAILURE
>[INFO]  
>
>[INFO] Total time: 2.227 s
>[INFO] Finished at: 2018-04-10T09:07:09+03:00
>[INFO]  
>
>[ERROR] Failed to execute goal
>org.apache.rat:apache-rat-plugin:0.12:check (license-check) on project
>royale-framework-parent: Too many files with unapproved license: 1 See
>RAT report in: /royale/royale-asjs/target/rat.txt -> [Help 1]
>[ERROR]
>[ERROR] To see the full stack trace of the errors, re-run Maven with
>the -e switch.
>[ERROR] Re-run Maven using the -X switch to enable full debug logging.
>[ERROR]
>[ERROR] For more information about the errors and possible solutions,
>please read the following articles:
>[ERROR] [Help 1]  
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcwiki.apac
>he.org%2Fconfluence%2Fdisplay%2FMAVEN%2FMojoFailureException=02%7C01%
>7Caharui%40adobe.com%7Cbfd92e266d0d43ca7aaf08d59ea9ae44%7Cfa7b1b5a7b344387
>94aed2c178decee1%7C0%7C0%7C636589373983398257=e84%2FMV%2BAiMt8frdZpg
>cl7K9uH9yVOIf%2FA%2FeDDEa8Jio%3D=0
>hostname:~/royale/royale-asjs$
>
>
>
>
>******
>
>
>
>Quoting Alex Harui <aha...@adobe.com>:
>
>> Hi Serkan,
>>
>> That implies that the Basic snapshot is out-of-date.  Run "mvn clean
>> install" from the royale-asjs folder and check the console to make
>> sure it rebuilt the Basic artifact, that its version is 0.9.3, and
>> that MXRoyale is trying to use that version.
>>
>> HTH,
>> -Alex
>>
>> From: Serkan Taş
>> <serkan@likyateknoloji.com<mailto:serkan@likyateknoloji.com>>
>> Reply-To: "users@royale.apache.org<mailto:users@royale.apache.org>"
>> <users@royale.apache.org<mailto:users@royale.apache.org>>
>> Date: Monday, April 9, 2018 at 1:29 PM
>> To: "users@royale.apache.org<mailto:users@royale.apache.org>"
>> <users@royale.apache.org<mailto:users@royale.apache.org>>
>> Subject: Re: MXRoyale build problem
>>
>>
>> typedefs and the compiler was ok before but asjs/MXRoyale still has
>>errors :
>>
>> 
>>D:\dev\git\emulation_works\royale-asjs\frameworks\projects\MXRoyale\src\m
>>ain\royale\mx\controls\beads\CSSImageAndTextButtonView.as(122): col: 27
>>Error: Call to a possibly
>> undefined
>>  method $addChild through a reference with static type UIBase.
>>
>> UIBase(value).$addChild(upSprite);
>>   ^
>>
>> 
>>D:\dev\git\emulation_works\royale-asjs\frameworks\projects\MXRoyale\src\m
>>ain\royale\mx\controls\beads\CheckBoxView.as(132): col: 27 Error: Call
>>to a possibly undefined method
>> $addC
>> hild through a reference with static type UIBase.
>>
>> UIBase(value).$addChild(upSprite);
>>   ^
>>
>> 
>>D:\dev\git\emulation_works\royale-asjs\frameworks\projects\MXRoyale\src\m
>>ain\royale\mx\controls\beads\CheckBoxView.as(236): col: 33 Error: Call
>>to a possibly undefined method
>> $addC
>> hild through a reference with static type UIBase.
>>
>> UIBase(_strand).$addChild(upAndSelectedSprite);
>> ^
>>
>> 
>>D:\dev\git\emulation_works\royale-asjs\frameworks\projects\MXRoyale\src\m
>>ain\royale\mx\controls\beads\CheckBoxView.as(244

Re: MXRoyale build problem

2018-04-10 Thread serkan . tas
Themes:  
Jewel-Light-NoFlat-Primary-Emerald-Theme SKIPPED
[INFO] Apache Royale: Framework: Themes:  
Jewel-Light-NoFlat-Secondary-Emerald-Theme SKIPPED
[INFO] Apache Royale: Framework: Themes:  
Jewel-Light-NoFlat-Emphasized-Emerald-Theme SKIPPED

[INFO] Apache Royale: Framework: Archetypes ... SKIPPED
[INFO] Apache Royale: Framework: Archetypes: Simple Royale Application SKIPPED
[INFO] Apache Royale: Framework: Archetypes: Simple Royale Pure-JS  
Application SKIPPED
[INFO] Apache Royale: Framework: Archetypes: Simple Royale Pure-SWF  
Application SKIPPED

[INFO] Apache Royale: Framework: Archetypes: Simple Royale Library SKIPPED
[INFO] Apache Royale: Framework: Archetypes: Simple Royale Typedef  
Library 0.9.3-SNAPSHOT SKIPPED
[INFO]  


[INFO] BUILD FAILURE
[INFO]  


[INFO] Total time: 2.227 s
[INFO] Finished at: 2018-04-10T09:07:09+03:00
[INFO]  

[ERROR] Failed to execute goal  
org.apache.rat:apache-rat-plugin:0.12:check (license-check) on project  
royale-framework-parent: Too many files with unapproved license: 1 See  
RAT report in: /royale/royale-asjs/target/rat.txt -> [Help 1]

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

[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,  
please read the following articles:
[ERROR] [Help 1]  
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

hostname:~/royale/royale-asjs$




**


Quoting Alex Harui <aha...@adobe.com>:


Hi Serkan,

That implies that the Basic snapshot is out-of-date.  Run "mvn clean  
install" from the royale-asjs folder and check the console to make  
sure it rebuilt the Basic artifact, that its version is 0.9.3, and  
that MXRoyale is trying to use that version.


HTH,
-Alex

From: Serkan Taş  
<serkan@likyateknoloji.com<mailto:serkan@likyateknoloji.com>>
Reply-To: "users@royale.apache.org<mailto:users@royale.apache.org>"  
<users@royale.apache.org<mailto:users@royale.apache.org>>

Date: Monday, April 9, 2018 at 1:29 PM
To: "users@royale.apache.org<mailto:users@royale.apache.org>"  
<users@royale.apache.org<mailto:users@royale.apache.org>>

Subject: Re: MXRoyale build problem


typedefs and the compiler was ok before but asjs/MXRoyale still has errors :

D:\dev\git\emulation_works\royale-asjs\frameworks\projects\MXRoyale\src\main\royale\mx\controls\beads\CSSImageAndTextButtonView.as(122): col: 27 Error: Call to a possibly  
undefined

 method $addChild through a reference with static type UIBase.

UIBase(value).$addChild(upSprite);
  ^

D:\dev\git\emulation_works\royale-asjs\frameworks\projects\MXRoyale\src\main\royale\mx\controls\beads\CheckBoxView.as(132): col: 27 Error: Call to a possibly undefined method  
$addC

hild through a reference with static type UIBase.

UIBase(value).$addChild(upSprite);
  ^

D:\dev\git\emulation_works\royale-asjs\frameworks\projects\MXRoyale\src\main\royale\mx\controls\beads\CheckBoxView.as(236): col: 33 Error: Call to a possibly undefined method  
$addC

hild through a reference with static type UIBase.

UIBase(_strand).$addChild(upAndSelectedSprite);
^

D:\dev\git\emulation_works\royale-asjs\frameworks\projects\MXRoyale\src\main\royale\mx\controls\beads\CheckBoxView.as(244): col: 33 Error: Call to a possibly undefined method  
$addC

hild through a reference with static type UIBase.

UIBase(_strand).$addChild(upSprite);
^

D:\dev\git\emulation_works\royale-asjs\frameworks\projects\MXRoyale\src\main\royale\mx\controls\beads\RadioButtonView.as(133): col: 27 Error: Call to a possibly undefined method  
$a

ddChild through a reference with static type UIBase.

UIBase(value).$addChild(upSprite);
  ^

D:\dev\git\emulation_works\royale-asjs\frameworks\projects\MXRoyale\src\main\royale\mx\controls\beads\RadioButtonView.as(134): col: 27 Error: Call to a possibly undefined method  
$a

ddChild through a reference with static type UIBase.

UIBase(value).$addChild(downSprite);
  ^

D:\dev\git\emulation_works\royale-asjs\frameworks\projects\MXRoyale\src\main\royale\mx\controls\beads\RadioButtonView.as(135): col: 27 Error: Call to a possibly undefined method  
$a

ddChild through a reference with static type UIBase.

UIBase(value).$addChild(overSprite);
  ^

D:\dev\git\emulation_works\

Re: MXRoyale build problem

2018-04-09 Thread serkan . tas
  ^


D:\dev\git\emulation_works\royale-asjs\frameworks\projects\MXRoyale\src\main\royale\mx\core\UIComponent.as(1189):

   col: 25 Overriding a function that is not marked for override

       public function get measuredHeight():Number
       ^


D:\dev\git\emulation_works\royale-asjs\frameworks\projects\MXRoyale\src\main\royale\mx\core\UIComponent.as(1205):

   col: 25 Overriding a function that is not marked for override

       public function set measuredHeight(value:Number):void
       ^


D:\dev\git\emulation_works\royale-asjs\frameworks\projects\MXRoyale\src\main\royale\mx\core\UIComponent.as(1265):

   col: 13 Attempted access of inaccessible property
   _explicitWidth t
   hrough a reference with static type UIComponent.

       _explicitWidth = NaN;
       ^


D:\dev\git\emulation_works\royale-asjs\frameworks\projects\MXRoyale\src\main\royale\mx\core\UIComponent.as(1321):

   col: 13 Attempted access of inaccessible property _explicitHeight
   through a reference with static type UIComponent.

       _explicitHeight = NaN;
       ^


D:\dev\git\emulation_works\royale-asjs\frameworks\projects\MXRoyale\src\main\royale\mx\core\UIComponent.as(2980):

   col: 46 Type was not found or was not a compile-time
   constant: Tex
   tLineMetrics.

       public function measureText(text:String):TextLineMetrics
   ^

   4.325211432 seconds
   [INFO]



   [INFO] BUILD FAILURE
   [INFO]



   [INFO] Total time: 7.806 s
   [INFO] Finished at: 2018-04-09T22:49:02+03:00
   [INFO]



   [ERROR] Failed to execute goal

org.apache.royale.compiler:royale-maven-plugin:0.9.3-SNAPSHOT:compile-as

   (default-compile-as) on project MXRoyale: There were errors
   during the build
   . Got return code 3 -> [Help 1]
   [ERROR]
   [ERROR] To see the full stack trace of the errors, re-run
   Maven with the -e switch.
   [ERROR] Re-run Maven using the -X switch to enable full debug
   logging.
   [ERROR]
   [ERROR] For more information about the errors and possible
   solutions, please read the following articles:
   [ERROR] [Help 1]

http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

<http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException>



   09.04.2018 10:35 tarihinde Alex Harui yazdı:

   OK, the merge went smoothly so I pushed it.  Serkan, you can
   try again with Maven.

   HTH,
   -Alex

   From: Alex Harui <aha...@adobe.com <mailto:aha...@adobe.com>>
   Reply-To: "users@royale.apache.org
   <mailto:users@royale.apache.org>" <users@royale.apache.org
   <mailto:users@royale.apache.org>>
   Date: Monday, April 9, 2018 at 12:19 AM
   To: "users@royale.apache.org
   <mailto:users@royale.apache.org>" <users@royale.apache.org
   <mailto:users@royale.apache.org>>
   Subject: Re: MXRoyale build problem

   I think MXRoyale is out of sync with the Maven versioning. 
   I will try to merge the royale-asjs develop branch into
   MXRoyale and make sure the Maven build works.

   I'm thinking of merging MXRoyale into develop for the 0.9.3
   release.  Any opinions on that?

   -Alex

   From: Piotr Zarzycki <piotrzarzyck...@gmail.com
   <mailto:piotrzarzyck...@gmail.com>>
   Reply-To: "users@royale.apache.org
   <mailto:users@royale.apache.org>" <users@royale.apache.org
   <mailto:users@royale.apache.org>>
   Date: Sunday, April 8, 2018 at 5:21 AM
   To: "users@royale.apache.org
   <mailto:users@royale.apache.org>" <users@royale.apache.org
   <mailto:users@royale.apache.org>>
   Subject: Re: MXRoyale build problem

   Are you sure that you are on the right branch in case of
   royale-asjs. You have been asked in the stack traces for
   0.9.2-SNAPSHOT version. It should be 0.9.3-SNAPSHOT

   I think in order to work on emulation you have to be:

   royale-compiler - develop branch
   royale-typedefs - develop branch
   royale-asjs - feature/MXRoyale

   Are you using those branches ?

   Thanks,
   Piotr

   2018-04-08 14:12 GMT+02:00 Serkan Taş
   <serkan@likyateknoloji.com
   <mailto:serkan@likyateknoloji.com>>:

   I prefer mvn Piotr,

   I first compiled the typedefs and compiler success

Re: MXRoyale build problem

2018-04-09 Thread Piotr Zarzycki
t; MXRoyale\src\main\royale\mx\controls\beads\CheckBoxView.as(244): col: 33
>> Call to a possibly undefined method $addChild th
>> rough a reference with static type UIBase.
>>
>> UIBase(_strand).$addChild(upSprite);
>> ^
>>
>> D:\dev\git\emulation_works\royale-asjs\frameworks\projects\
>> MXRoyale\src\main\royale\mx\controls\beads\RadioButtonView.as(133): col:
>> 27 Call to a possibly undefined method $addChild
>>  through a reference with static type UIBase.
>>
>> UIBase(value).$addChild(upSprite);
>>   ^
>>
>> D:\dev\git\emulation_works\royale-asjs\frameworks\projects\
>> MXRoyale\src\main\royale\mx\controls\beads\RadioButtonView.as(134): col:
>> 27 Call to a possibly undefined method $addChild
>>  through a reference with static type UIBase.
>>
>> UIBase(value).$addChild(downSprite);
>>   ^
>>
>> D:\dev\git\emulation_works\royale-asjs\frameworks\projects\
>> MXRoyale\src\main\royale\mx\controls\beads\RadioButtonView.as(135): col:
>> 27 Call to a possibly undefined method $addChild
>>  through a reference with static type UIBase.
>>
>> UIBase(value).$addChild(overSprite);
>>   ^
>>
>> D:\dev\git\emulation_works\royale-asjs\frameworks\projects\
>> MXRoyale\src\main\royale\mx\controls\beads\RadioButtonView.as(136): col:
>> 27 Call to a possibly undefined method $addChild
>>  through a reference with static type UIBase.
>>
>> UIBase(value).$addChild(upAndSelectedSprite);
>>   ^
>>
>> D:\dev\git\emulation_works\royale-asjs\frameworks\projects\
>> MXRoyale\src\main\royale\mx\controls\beads\RadioButtonView.as(137): col:
>> 27 Call to a possibly undefined method $addChild
>>  through a reference with static type UIBase.
>>
>> UIBase(value).$addChild(downAndSelectedSprite);
>>   ^
>>
>> D:\dev\git\emulation_works\royale-asjs\frameworks\projects\
>> MXRoyale\src\main\royale\mx\controls\beads\RadioButtonView.as(138): col:
>> 27 Call to a possibly undefined method $addChild
>>  through a reference with static type UIBase.
>>
>> UIBase(value).$addChild(overAndSelectedSprite);
>>   ^
>>
>> D:\dev\git\emulation_works\royale-asjs\frameworks\projects\
>> MXRoyale\src\main\royale\mx\core\Application.as(358): col: 19 Access of
>> possibly undefined property $parent.
>>
>> var p:* = $parent;
>>   ^
>>
>> D:\dev\git\emulation_works\royale-asjs\frameworks\projects\
>> MXRoyale\src\main\royale\mx\core\UIComponent.as(56): col: 8 Definition
>> org.apache.royale.core.TextLineMetrics could not b
>> e found.
>>
>> import org.apache.royale.core.TextLineMetrics;
>>^
>>
>> D:\dev\git\emulation_works\royale-asjs\frameworks\projects\
>> MXRoyale\src\main\royale\mx\core\UIComponent.as(1147): col: 25
>> Overriding a function that is not marked for override
>>
>> public function get measuredWidth():Number
>> ^
>>
>> D:\dev\git\emulation_works\royale-asjs\frameworks\projects\
>> MXRoyale\src\main\royale\mx\core\UIComponent.as(1163): col: 25
>> Overriding a function that is not marked for override
>>
>> public function set measuredWidth(value:Number):void
>> ^
>>
>> D:\dev\git\emulation_works\royale-asjs\frameworks\projects\
>> MXRoyale\src\main\royale\mx\core\UIComponent.as(1189): col: 25
>> Overriding a function that is not marked for override
>>
>> public function get measuredHeight():Number
>> ^
>>
>> D:\dev\git\emulation_works\royale-asjs\frameworks\projects\
>> MXRoyale\src\main\royale\mx\core\UIComponent.as(1205): col: 25
>> Overriding a function that is not marked for override
>>
>> public function set measuredHeight(value:Number):void
>> ^
>>
>> D:\dev\git\emulation_works\royale-asjs\frameworks\projects\
>> MXRoyale\src\main\royale\mx\core\UIComponent.as(1265): col: 13 Attempted
>> access of inaccessible property _explicitWidth t
>> hrough a reference with static type UIComponent.
>>
>> _explicitWidth = NaN;
>> ^
>>
>> D:\dev\git\emulation_works\royale-asjs\frameworks\projects\
>> MXRoyale\src\main\royale\mx\core\UIComponent.as(1321): col: 13 Attempted
>> access of ina

Re: MXRoyale build problem

2018-04-09 Thread Alex Harui
If you want to do daily rebasing, feel free.  I personally would not want to 
start my morning dealing with rebase conflicts.  IMO, some of these 
long-running branches like MXRoyale should be merged with develop sooner rather 
than later.

My 2 cents,
-Alex

From: Piotr Zarzycki 
<piotrzarzyck...@gmail.com<mailto:piotrzarzyck...@gmail.com>>
Reply-To: "users@royale.apache.org<mailto:users@royale.apache.org>" 
<users@royale.apache.org<mailto:users@royale.apache.org>>
Date: Monday, April 9, 2018 at 9:32 AM
To: "users@royale.apache.org<mailto:users@royale.apache.org>" 
<users@royale.apache.org<mailto:users@royale.apache.org>>
Subject: Re: MXRoyale build problem

To me rebasing have always sense when there are many branches created, daily. 
In that case structures were much more cleaner if you rebase from time to time.

2018-04-09 18:27 GMT+02:00 Alex Harui 
<aha...@adobe.com<mailto:aha...@adobe.com>>:
Hi Carlos,

I've had too many difficulties rebasing branches that I no longer do it.  I 
always use straight merging these days when merging between branches.  I 
suppose we can try rebasing and aborting if it fails and then falling back to 
merging, but for sure, it doesn't seem time-efficient to try to fix rebase 
conflicts in many cases.

My 2 cents,
-Alex

From: <carlos.rov...@gmail.com<mailto:carlos.rov...@gmail.com>> on behalf of 
Carlos Rovira <carlosrov...@apache.org<mailto:carlosrov...@apache.org>>
Reply-To: "users@royale.apache.org<mailto:users@royale.apache.org>" 
<users@royale.apache.org<mailto:users@royale.apache.org>>
Date: Monday, April 9, 2018 at 1:57 AM
To: "users@royale.apache.org<mailto:users@royale.apache.org>" 
<users@royale.apache.org<mailto:users@royale.apache.org>>
Subject: Re: MXRoyale build problem

Hi Alex (and others)

I'm a huge advocate of Rebase in GIT. Please check this [1], since it could 
make your life easier.
Doing in a branch rebase periodically helps you to solve conflicts soon and 
ensure your work are synced with develop, so when you need to merge the entire 
branch you'll find no conflicts and your code should just work.

As many of this workflows, are completely subjective and could be of your 
liking or not...I only give to you so you can see if it fits for you as it fits 
for me.

thanks


[1] Rebase in 
git<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmarkmail.org%2Fmessage%2Fp4rp4kqdsa3xddxd%3Fq%3Dlist%3Aorg%252Eapache%252Eincubator%252Eflex-dev%2Brebase%2Bin%2Bgit=02%7C01%7Caharui%40adobe.com%7C34cd7613299a4b3dbac908d59df801be%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636588610876456379=jrDAG9%2Bkg6neD6GnpXMUAjTfZC%2ByyBQuYjo5LV2xSp0%3D=0>



2018-04-09 9:51 GMT+02:00 
<serkan@likyateknoloji.com<mailto:serkan@likyateknoloji.com>>:

Quoting Serkan Taş 
<serkan@likyateknoloji.com<mailto:serkan@likyateknoloji.com>>:

I realised that issue but tought it is normal...

Here is th branch info...


D:\dev\git\emulation_works\royale-asjs>git status
On branch feature/MXRoyale
Your branch is up to date with 'origin/feature/MXRoyale'.

nothing to commit, working tree clean

D:\dev\git\emulation_works\royale-asjs>cd ..

D:\dev\git\emulation_works>cd royale-compiler

D:\dev\git\emulation_works\royale-compiler>git status
On branch develop
Your branch is up to date with 'origin/develop'.

nothing to commit, working tree clean

D:\dev\git\emulation_works\royale-compiler>cd ..

D:\dev\git\emulation_works>cd royale-typedefs

D:\dev\git\emulation_works\royale-typedefs>git status
On branch develop
Your branch is up to date with 'origin/develop'.

nothing to commit, working tree clean

D:\dev\git\emulation_works\royale-typedefs>


08.04.2018 15:21 tarihinde Piotr Zarzycki yazdı:
Are you sure that you are on the right branch in case of royale-asjs. You have 
been asked in the stack traces for 0.9.2-SNAPSHOT version. It should be 
0.9.3-SNAPSHOT

I think in order to work on emulation you have to be:

royale-compiler - develop branch
royale-typedefs - develop branch
royale-asjs - feature/MXRoyale

Are you using those branches ?

Thanks,
Piotr

2018-04-08 14:12 GMT+02:00 Serkan Taş 
<serkan@likyateknoloji.com<mailto:serkan@likyateknoloji.com> 
<mailto:serkan@likyateknoloji.com<mailto:serkan@likyateknoloji.com>>>:


   I prefer mvn Piotr,

   I first compiled the typedefs and compiler successfuly as Alex
   informed but i got the same error as earlier.

   and here is the report :

   cd royale-typedefs

   mvn clean   : success
   mvn install : success

   
**

   (due to the bug in code generator - related to locale dependent
   capitalizing u-case i to İ - I had to change the jvm params)

Re: MXRoyale build problem

2018-04-09 Thread Piotr Zarzycki
To me rebasing have always sense when there are many branches created,
daily. In that case structures were much more cleaner if you rebase from
time to time.

2018-04-09 18:27 GMT+02:00 Alex Harui <aha...@adobe.com>:

> Hi Carlos,
>
> I've had too many difficulties rebasing branches that I no longer do it.
> I always use straight merging these days when merging between branches.  I
> suppose we can try rebasing and aborting if it fails and then falling back
> to merging, but for sure, it doesn't seem time-efficient to try to fix
> rebase conflicts in many cases.
>
> My 2 cents,
> -Alex
>
> From: <carlos.rov...@gmail.com> on behalf of Carlos Rovira <
> carlosrov...@apache.org>
> Reply-To: "users@royale.apache.org" <users@royale.apache.org>
> Date: Monday, April 9, 2018 at 1:57 AM
> To: "users@royale.apache.org" <users@royale.apache.org>
> Subject: Re: MXRoyale build problem
>
> Hi Alex (and others)
>
> I'm a huge advocate of Rebase in GIT. Please check this [1], since it
> could make your life easier.
> Doing in a branch rebase periodically helps you to solve conflicts soon
> and ensure your work are synced with develop, so when you need to merge the
> entire branch you'll find no conflicts and your code should just work.
>
> As many of this workflows, are completely subjective and could be of your
> liking or not...I only give to you so you can see if it fits for you as it
> fits for me.
>
> thanks
>
>
> [1] Rebase in git
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmarkmail.org%2Fmessage%2Fp4rp4kqdsa3xddxd%3Fq%3Dlist%3Aorg%252Eapache%252Eincubator%252Eflex-dev%2Brebase%2Bin%2Bgit=02%7C01%7Caharui%40adobe.com%7C34cd7613299a4b3dbac908d59df801be%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636588610876456379=jrDAG9%2Bkg6neD6GnpXMUAjTfZC%2ByyBQuYjo5LV2xSp0%3D=0>
>
>
>
> 2018-04-09 9:51 GMT+02:00 <serkan@likyateknoloji.com>:
>
>>
>> Quoting Serkan Taş <serkan@likyateknoloji.com>:
>>
>> I realised that issue but tought it is normal...
>>>>
>>>> Here is th branch info...
>>>>
>>>>
>>>> D:\dev\git\emulation_works\royale-asjs>git status
>>>> On branch feature/MXRoyale
>>>> Your branch is up to date with 'origin/feature/MXRoyale'.
>>>>
>>>> nothing to commit, working tree clean
>>>>
>>>> D:\dev\git\emulation_works\royale-asjs>cd ..
>>>>
>>>> D:\dev\git\emulation_works>cd royale-compiler
>>>>
>>>> D:\dev\git\emulation_works\royale-compiler>git status
>>>> On branch develop
>>>> Your branch is up to date with 'origin/develop'.
>>>>
>>>> nothing to commit, working tree clean
>>>>
>>>> D:\dev\git\emulation_works\royale-compiler>cd ..
>>>>
>>>> D:\dev\git\emulation_works>cd royale-typedefs
>>>>
>>>> D:\dev\git\emulation_works\royale-typedefs>git status
>>>> On branch develop
>>>> Your branch is up to date with 'origin/develop'.
>>>>
>>>> nothing to commit, working tree clean
>>>>
>>>> D:\dev\git\emulation_works\royale-typedefs>
>>>>
>>>>
>>>> 08.04.2018 15:21 tarihinde Piotr Zarzycki yazdı:
>>>>
>>>>> Are you sure that you are on the right branch in case of royale-asjs.
>>>>> You have been asked in the stack traces for 0.9.2-SNAPSHOT version. It
>>>>> should be 0.9.3-SNAPSHOT
>>>>>
>>>>> I think in order to work on emulation you have to be:
>>>>>
>>>>> royale-compiler - develop branch
>>>>> royale-typedefs - develop branch
>>>>> royale-asjs - feature/MXRoyale
>>>>>
>>>>> Are you using those branches ?
>>>>>
>>>>> Thanks,
>>>>> Piotr
>>>>>
>>>>> 2018-04-08 14:12 GMT+02:00 Serkan Taş <serkan@likyateknoloji.com
>>>>> <mailto:serkan@likyateknoloji.com>>:
>>>>>
>>>>>
>>>>>I prefer mvn Piotr,
>>>>>
>>>>>I first compiled the typedefs and compiler successfuly as Alex
>>>>>informed but i got the same error as earlier.
>>>>>
>>>>>and here is the report :
>>>>>
>>>>>cd royale-typedefs
>>>>>
>>>>>mvn clean   : success
>>>>>mvn install : success
>>>>>

Re: MXRoyale build problem

2018-04-09 Thread Alex Harui
Hi Carlos,

I've had too many difficulties rebasing branches that I no longer do it.  I 
always use straight merging these days when merging between branches.  I 
suppose we can try rebasing and aborting if it fails and then falling back to 
merging, but for sure, it doesn't seem time-efficient to try to fix rebase 
conflicts in many cases.

My 2 cents,
-Alex

From: <carlos.rov...@gmail.com<mailto:carlos.rov...@gmail.com>> on behalf of 
Carlos Rovira <carlosrov...@apache.org<mailto:carlosrov...@apache.org>>
Reply-To: "users@royale.apache.org<mailto:users@royale.apache.org>" 
<users@royale.apache.org<mailto:users@royale.apache.org>>
Date: Monday, April 9, 2018 at 1:57 AM
To: "users@royale.apache.org<mailto:users@royale.apache.org>" 
<users@royale.apache.org<mailto:users@royale.apache.org>>
Subject: Re: MXRoyale build problem

Hi Alex (and others)

I'm a huge advocate of Rebase in GIT. Please check this [1], since it could 
make your life easier.
Doing in a branch rebase periodically helps you to solve conflicts soon and 
ensure your work are synced with develop, so when you need to merge the entire 
branch you'll find no conflicts and your code should just work.

As many of this workflows, are completely subjective and could be of your 
liking or not...I only give to you so you can see if it fits for you as it fits 
for me.

thanks


[1] Rebase in 
git<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmarkmail.org%2Fmessage%2Fp4rp4kqdsa3xddxd%3Fq%3Dlist%3Aorg%252Eapache%252Eincubator%252Eflex-dev%2Brebase%2Bin%2Bgit=02%7C01%7Caharui%40adobe.com%7C34cd7613299a4b3dbac908d59df801be%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636588610876456379=jrDAG9%2Bkg6neD6GnpXMUAjTfZC%2ByyBQuYjo5LV2xSp0%3D=0>



2018-04-09 9:51 GMT+02:00 
<serkan@likyateknoloji.com<mailto:serkan@likyateknoloji.com>>:

Quoting Serkan Taş 
<serkan@likyateknoloji.com<mailto:serkan@likyateknoloji.com>>:

I realised that issue but tought it is normal...

Here is th branch info...


D:\dev\git\emulation_works\royale-asjs>git status
On branch feature/MXRoyale
Your branch is up to date with 'origin/feature/MXRoyale'.

nothing to commit, working tree clean

D:\dev\git\emulation_works\royale-asjs>cd ..

D:\dev\git\emulation_works>cd royale-compiler

D:\dev\git\emulation_works\royale-compiler>git status
On branch develop
Your branch is up to date with 'origin/develop'.

nothing to commit, working tree clean

D:\dev\git\emulation_works\royale-compiler>cd ..

D:\dev\git\emulation_works>cd royale-typedefs

D:\dev\git\emulation_works\royale-typedefs>git status
On branch develop
Your branch is up to date with 'origin/develop'.

nothing to commit, working tree clean

D:\dev\git\emulation_works\royale-typedefs>


08.04.2018 15:21 tarihinde Piotr Zarzycki yazdı:
Are you sure that you are on the right branch in case of royale-asjs. You have 
been asked in the stack traces for 0.9.2-SNAPSHOT version. It should be 
0.9.3-SNAPSHOT

I think in order to work on emulation you have to be:

royale-compiler - develop branch
royale-typedefs - develop branch
royale-asjs - feature/MXRoyale

Are you using those branches ?

Thanks,
Piotr

2018-04-08 14:12 GMT+02:00 Serkan Taş 
<serkan@likyateknoloji.com<mailto:serkan@likyateknoloji.com> 
<mailto:serkan@likyateknoloji.com<mailto:serkan@likyateknoloji.com>>>:


   I prefer mvn Piotr,

   I first compiled the typedefs and compiler successfuly as Alex
   informed but i got the same error as earlier.

   and here is the report :

   cd royale-typedefs

   mvn clean   : success
   mvn install : success

   
**

   (due to the bug in code generator - related to locale dependent
   capitalizing u-case i to İ - I had to change the jvm params)

   cd royale-compiler

   mvn clean -Djvm.options="-Duser.country=EN -Duser.language=en" :
   success

   mvn install -Djvm.options="-Duser.country=EN -Duser.language=en"

   Tests run: 1145, Failures: 4, Errors: 6, Skipped: 4

   [INFO]
   
   [INFO] Reactor Summary:
   [INFO]
   [INFO] Apache Royale: Compiler: Parent 0.9.3-SNAPSHOT .
   SUCCESS [  4.600 s]
   [INFO] Apache Royale: Compiler: Compiler-Common ...
   SUCCESS [  6.545 s]
   [INFO] Apache Royale: Compiler: Test Utils 
   SUCCESS [  1.344 s]
   [INFO] Apache Royale: Compiler: Externc ...
   SUCCESS [ 16.432 s]
   [INFO] Apache Royale: Compiler: Compiler ..
   SUCCESS [02:26 min]
   [INFO] Apache Royale: Compiler: Compiler-JX ...
   FAILURE [ 49.945 s]
   [INFO] Apache Royale: Compiler: SWFUtils .. SKIPPED
   [INFO] Apache Royale: Compiler:

Re: MXRoyale build problem

2018-04-09 Thread Carlos Rovira
ache.org/confluence/display/MAVEN/ProjectBu
>>>> ildingException>
>>>>[ERROR] [Help 2]
>>>>http://cwiki.apache.org/confluence/display/MAVEN/PluginMana
>>>> gerException
>>>><http://cwiki.apache.org/confluence/display/MAVEN/PluginMan
>>>> agerException>
>>>>
>>>>
>>>>
>>>>08.04.2018 13:56 tarihinde Piotr Zarzycki yazdı:
>>>>
>>>>>Serkan,
>>>>>
>>>>>It depends where you will feel comfortable. Maven scripts are
>>>>>quite clean and self explanatory. With ANT it does not so
>>>>>obvious. However you probably won't change anything in scripts.
>>>>>
>>>>>If ANT worked for you go with ANT. Going with Maven you will be
>>>>>able to rebuild one module and test it. With ANT it is probably
>>>>>also possible.
>>>>>
>>>>>Piotr
>>>>>
>>>>>2018-04-08 12:50 GMT+02:00 Serkan Taş
>>>>><serkan@likyateknoloji.com
>>>>><mailto:serkan@likyateknoloji.com>>:
>>>>>
>>>>>Here is the last result :
>>>>>
>>>>>1. git clone https://github.com/apache/royale-asjs.git
>>>>><https://na01.safelinks.protection.outlook.com/?url=https%
>>>>> 3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs.git=02%
>>>>> 7C01%7Caharui%40adobe.com%7C79ddabf4e3994a9db38908d59d1bde7c
>>>>> %7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63658766548133
>>>>> 8047=Vt%2FkEc6N8JZOQ6lviXl5apzi8hwZFJMlYPVWklcSItc%3D=0
>>>>> >
>>>>>
>>>>>2.cd royale-asjs
>>>>>
>>>>>3. git checkout feature/MXRoyale
>>>>>
>>>>>4.ant all : failed; details in the mail below
>>>>>
>>>>>5.cd ..\royale-typedefs
>>>>>
>>>>>6.ant : completed with success
>>>>>
>>>>>7.cd ..\royale-asjs
>>>>>
>>>>>8.ant main : completed with success
>>>>>
>>>>>9.ant frameworks : completed with success
>>>>>
>>>>>10.cd
>>>>>D:\dev\git\emulation_works\royale-asjs\frameworks\projects\
>>>>> MXRoyale
>>>>>
>>>>>11.ant : completed with success
>>>>>
>>>>>If it is ok, i can move on with this.
>>>>>
>>>>>Piotr, i just saw your mail, do you want me to move with
>>>>>maven ?
>>>>>
>>>>>
>>>>>
>>>>>1. git clone https://github.com/apache/royale-asjs.git
>>>>>><https://na01.safelinks.protection.outlook.com/?url=https%
>>>>>> 3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs.git=02%
>>>>>> 7C01%7Caharui%40adobe.com%7C79ddabf4e3994a9db38908d59d1bde7c
>>>>>> %7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63658766548133
>>>>>> 8047=Vt%2FkEc6N8JZOQ6lviXl5apzi8hwZFJMlYPVWklcSItc%3D&
>>>>>> reserved=0>
>>>>>>
>>>>>>2. git checkout feature/MXRoyale
>>>>>>
>>>>>>Folder view :
>>>>>>
>>>>>>
>>>>>>3.ant all
>>>>>>
>>>>>>Folder View :
>>>>>>
>>>>>>
>>>>>>
>>>>>>Fails and the result :
>>>>>>https://drive.google.com/open?id=1XZNfN8exZ_x_F4bTY5xIf
>>>>>> xO328eWHIQ4
>>>>>><https://drive.google.com/open?id=1XZNfN8exZ_x_F4bTY5xIfxO3
>>>>>> 28eWHIQ4>
>>>>>>
>>>>>>Next : i am going to check-out all tree repo manually and
>>>>>>then build with ant saperately.
>>>>>>
>>>>>>08.04.2018 10:02 tarihinde Alex Harui yazdı:
>>>>>>
>>>>>>>If you are using Maven, you may need to build the
>>>>>>>royale-compiler and royale-typedefs repos first. See the
>>>>>>>README in each of those repos.  You can also use A

Re: MXRoyale build problem

2018-04-09 Thread serkan . tas
on

<http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException>

   [ERROR] [Help 2]
   http://cwiki.apache.org/confluence/display/MAVEN/PluginManagerException

<http://cwiki.apache.org/confluence/display/MAVEN/PluginManagerException>




   08.04.2018 13:56 tarihinde Piotr Zarzycki yazdı:

   Serkan,

   It depends where you will feel comfortable. Maven scripts are
   quite clean and self explanatory. With ANT it does not so
   obvious. However you probably won't change anything in scripts.

   If ANT worked for you go with ANT. Going with Maven you will be
   able to rebuild one module and test it. With ANT it is probably
   also possible.

   Piotr

   2018-04-08 12:50 GMT+02:00 Serkan Taş
   <serkan@likyateknoloji.com
   <mailto:serkan@likyateknoloji.com>>:

   Here is the last result :

   1.     git clone https://github.com/apache/royale-asjs.git

<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs.git=02%7C01%7Caharui%40adobe.com%7C79ddabf4e3994a9db38908d59d1bde7c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636587665481338047=Vt%2FkEc6N8JZOQ6lviXl5apzi8hwZFJMlYPVWklcSItc%3D=0>


   2.    cd royale-asjs

   3.     git checkout feature/MXRoyale

   4.    ant all : failed; details in the mail below

   5.    cd ..\royale-typedefs

   6.    ant : completed with success

   7.    cd ..\royale-asjs

   8.    ant main : completed with success

   9.    ant frameworks : completed with success

   10.    cd
   D:\dev\git\emulation_works\royale-asjs\frameworks\projects\MXRoyale

   11.    ant : completed with success

   If it is ok, i can move on with this.

   Piotr, i just saw your mail, do you want me to move with
   maven ?




   1.     git clone https://github.com/apache/royale-asjs.git

<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs.git=02%7C01%7Caharui%40adobe.com%7C79ddabf4e3994a9db38908d59d1bde7c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636587665481338047=Vt%2FkEc6N8JZOQ6lviXl5apzi8hwZFJMlYPVWklcSItc%3D=0>


   2.     git checkout feature/MXRoyale

       Folder view :


   3.    ant all

           Folder View :



           Fails and the result :
   https://drive.google.com/open?id=1XZNfN8exZ_x_F4bTY5xIfxO328eWHIQ4

<https://drive.google.com/open?id=1XZNfN8exZ_x_F4bTY5xIfxO328eWHIQ4>


   Next : i am going to check-out all tree repo manually and
   then build with ant saperately.

   08.04.2018 10:02 tarihinde Alex Harui yazdı:

   If you are using Maven, you may need to build the
   royale-compiler and royale-typedefs repos first. See the
   README in each of those repos.  You can also use Ant
   instead of Maven.

   HTH,
   -Alex

   From: Serkan Taş <serkan@likyateknoloji.com
   <mailto:serkan@likyateknoloji.com>>
   Reply-To: "users@royale.apache.org
   <mailto:users@royale.apache.org>" <users@royale.apache.org
   <mailto:users@royale.apache.org>>
   Date: Saturday, April 7, 2018 at 11:41 PM
   To: "users@royale.apache.org
   <mailto:users@royale.apache.org>" <users@royale.apache.org
   <mailto:users@royale.apache.org>>
   Subject: MXRoyale build problem

   Hi Alex,

   Here is the steps and result (i spent some time but could
   not find a resolution) :

   git clone https://github.com/apache/royale-asjs.git

<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs.git=02%7C01%7Caharui%40adobe.com%7C79ddabf4e3994a9db38908d59d1bde7c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636587665481338047=Vt%2FkEc6N8JZOQ6lviXl5apzi8hwZFJMlYPVWklcSItc%3D=0>


   cd royale-asjs

   git checkout feature/MXRoyale

   mvn celan

   Result :




   07.04.2018 17:51 tarihinde Alex Harui yazdı:

   Hi Serkan,

   That would be great.  We need the help.

   We have a wiki page about Emulation components here [1].
   And one person has been learning how to help in this  
long thread[2].


   [1] has an API list, but it does not take into account  
your API usage.  If
   you want to integrate your list with the current list,  
that might be

   useful.

   Let us know if you have other questions or need help  
getting started.


   Thanks,
   -Alex


[1]https://github.com/apache/royale-asjs/wiki/emulation-components

<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2Femulation-components=02%7C01%7Caharui%40adobe.com%7C79ddabf4e3994a9db38908d59d1bde7c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636587665481338047=BVdRuWskUsnCNLp1IM49Dvi3%2BN6zg5O0VmBJ9hRG60M%3D=0&

Re: MXRoyale build problem

2018-04-09 Thread Alex Harui
OK, the merge went smoothly so I pushed it.  Serkan, you can try again with 
Maven.

HTH,
-Alex

From: Alex Harui <aha...@adobe.com<mailto:aha...@adobe.com>>
Reply-To: "users@royale.apache.org<mailto:users@royale.apache.org>" 
<users@royale.apache.org<mailto:users@royale.apache.org>>
Date: Monday, April 9, 2018 at 12:19 AM
To: "users@royale.apache.org<mailto:users@royale.apache.org>" 
<users@royale.apache.org<mailto:users@royale.apache.org>>
Subject: Re: MXRoyale build problem

I think MXRoyale is out of sync with the Maven versioning.  I will try to merge 
the royale-asjs develop branch into MXRoyale and make sure the Maven build 
works.

I'm thinking of merging MXRoyale into develop for the 0.9.3 release.  Any 
opinions on that?

-Alex

From: Piotr Zarzycki 
<piotrzarzyck...@gmail.com<mailto:piotrzarzyck...@gmail.com>>
Reply-To: "users@royale.apache.org<mailto:users@royale.apache.org>" 
<users@royale.apache.org<mailto:users@royale.apache.org>>
Date: Sunday, April 8, 2018 at 5:21 AM
To: "users@royale.apache.org<mailto:users@royale.apache.org>" 
<users@royale.apache.org<mailto:users@royale.apache.org>>
Subject: Re: MXRoyale build problem

Are you sure that you are on the right branch in case of royale-asjs. You have 
been asked in the stack traces for 0.9.2-SNAPSHOT version. It should be 
0.9.3-SNAPSHOT

I think in order to work on emulation you have to be:

royale-compiler - develop branch
royale-typedefs - develop branch
royale-asjs - feature/MXRoyale

Are you using those branches ?

Thanks,
Piotr

2018-04-08 14:12 GMT+02:00 Serkan Taş 
<serkan@likyateknoloji.com<mailto:serkan@likyateknoloji.com>>:

I prefer mvn Piotr,

I first compiled the typedefs and compiler successfuly as Alex  informed but i 
got the same error as earlier.

and here is the report :

cd royale-typedefs

mvn clean   : success
mvn install : success

**

(due to the bug in code generator - related to locale dependent capitalizing 
u-case i to İ - I had to change the jvm params)

cd royale-compiler

mvn clean -Djvm.options="-Duser.country=EN -Duser.language=en" : success

mvn install -Djvm.options="-Duser.country=EN -Duser.language=en"

Tests run: 1145, Failures: 4, Errors: 6, Skipped: 4

[INFO] 
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Royale: Compiler: Parent 0.9.3-SNAPSHOT . SUCCESS [  4.600 s]
[INFO] Apache Royale: Compiler: Compiler-Common ... SUCCESS [  6.545 s]
[INFO] Apache Royale: Compiler: Test Utils  SUCCESS [  1.344 s]
[INFO] Apache Royale: Compiler: Externc ... SUCCESS [ 16.432 s]
[INFO] Apache Royale: Compiler: Compiler .. SUCCESS [02:26 min]
[INFO] Apache Royale: Compiler: Compiler-JX ... FAILURE [ 49.945 s]
[INFO] Apache Royale: Compiler: SWFUtils .. SKIPPED
[INFO] Apache Royale: Compiler: Debugger .. SKIPPED
[INFO] Apache Royale: Compiler: OEM Layer . SKIPPED
[INFO] Apache Royale: Royale Ant Tasks  SKIPPED
[INFO] Apache Royale: Royale Maven Plugin 0.9.3-SNAPSHOT .. SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 03:46 min
[INFO] Finished at: 2018-04-08T14:56:46+03:00
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.19:test (default-test) on 
project compiler-jx: There are test failures.
[ERROR]
[ERROR] Please refer to 
D:\dev\git\emulation_works\royale-compiler\compiler-jx\target\surefire-reports 
for the individual test results.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FMAVEN%2FMojoFailureException=02%7C01%7Caharui%40adobe.com%7C5eb63ff23edc4e4289d108d59d4b3b12%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636587868802712227=Vg%2BtZF%2BWajFf89VFfiCIu0%2BFasGPwlS1SAPL%2FH%2FH9JM%3D=0>
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :compiler-jx


I added params to skip tests

mvn -DskipTests -Drat.skip=tr

Re: MXRoyale build problem

2018-04-09 Thread Alex Harui
I think MXRoyale is out of sync with the Maven versioning.  I will try to merge 
the royale-asjs develop branch into MXRoyale and make sure the Maven build 
works.

I'm thinking of merging MXRoyale into develop for the 0.9.3 release.  Any 
opinions on that?

-Alex

From: Piotr Zarzycki 
<piotrzarzyck...@gmail.com<mailto:piotrzarzyck...@gmail.com>>
Reply-To: "users@royale.apache.org<mailto:users@royale.apache.org>" 
<users@royale.apache.org<mailto:users@royale.apache.org>>
Date: Sunday, April 8, 2018 at 5:21 AM
To: "users@royale.apache.org<mailto:users@royale.apache.org>" 
<users@royale.apache.org<mailto:users@royale.apache.org>>
Subject: Re: MXRoyale build problem

Are you sure that you are on the right branch in case of royale-asjs. You have 
been asked in the stack traces for 0.9.2-SNAPSHOT version. It should be 
0.9.3-SNAPSHOT

I think in order to work on emulation you have to be:

royale-compiler - develop branch
royale-typedefs - develop branch
royale-asjs - feature/MXRoyale

Are you using those branches ?

Thanks,
Piotr

2018-04-08 14:12 GMT+02:00 Serkan Taş 
<serkan@likyateknoloji.com<mailto:serkan@likyateknoloji.com>>:

I prefer mvn Piotr,

I first compiled the typedefs and compiler successfuly as Alex  informed but i 
got the same error as earlier.

and here is the report :

cd royale-typedefs

mvn clean   : success
mvn install : success

**

(due to the bug in code generator - related to locale dependent capitalizing 
u-case i to İ - I had to change the jvm params)

cd royale-compiler

mvn clean -Djvm.options="-Duser.country=EN -Duser.language=en" : success

mvn install -Djvm.options="-Duser.country=EN -Duser.language=en"

Tests run: 1145, Failures: 4, Errors: 6, Skipped: 4

[INFO] 
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Royale: Compiler: Parent 0.9.3-SNAPSHOT . SUCCESS [  4.600 s]
[INFO] Apache Royale: Compiler: Compiler-Common ... SUCCESS [  6.545 s]
[INFO] Apache Royale: Compiler: Test Utils  SUCCESS [  1.344 s]
[INFO] Apache Royale: Compiler: Externc ... SUCCESS [ 16.432 s]
[INFO] Apache Royale: Compiler: Compiler .. SUCCESS [02:26 min]
[INFO] Apache Royale: Compiler: Compiler-JX ... FAILURE [ 49.945 s]
[INFO] Apache Royale: Compiler: SWFUtils .. SKIPPED
[INFO] Apache Royale: Compiler: Debugger .. SKIPPED
[INFO] Apache Royale: Compiler: OEM Layer . SKIPPED
[INFO] Apache Royale: Royale Ant Tasks  SKIPPED
[INFO] Apache Royale: Royale Maven Plugin 0.9.3-SNAPSHOT .. SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 03:46 min
[INFO] Finished at: 2018-04-08T14:56:46+03:00
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.19:test (default-test) on 
project compiler-jx: There are test failures.
[ERROR]
[ERROR] Please refer to 
D:\dev\git\emulation_works\royale-compiler\compiler-jx\target\surefire-reports 
for the individual test results.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FMAVEN%2FMojoFailureException=02%7C01%7Caharui%40adobe.com%7C5eb63ff23edc4e4289d108d59d4b3b12%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636587868802712227=Vg%2BtZF%2BWajFf89VFfiCIu0%2BFasGPwlS1SAPL%2FH%2FH9JM%3D=0>
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :compiler-jx


I added params to skip tests

mvn -DskipTests -Drat.skip=true clean -Djvm.options="-Duser.country=EN 
-Duser.language=en" : success

mvn -DskipTests -Drat.skip=true install -Djvm.options="-Duser.country=EN 
-Duser.language=en" : success

**

D:\dev\git\emulation_works>cd royale-asjs

D:\dev\git\emulation_works\royale-asjs>mvn clean

[WARNING] The POM for 
org.apache.flex.utilities.converter:flex-sdk-converter-maven-extension:jar:1.0.0-SNAPSHOT
 is missing, no dependency i

Re: MXRoyale build problem

2018-04-08 Thread Piotr Zarzycki
wZFJMlYPVWklcSItc%3D=0>
>>
>> 2.cd royale-asjs
>>
>> 3. git checkout feature/MXRoyale
>> 4.ant all : failed; details in the mail below
>>
>> 5.cd ..\royale-typedefs
>>
>> 6.ant : completed with success
>>
>> 7.cd ..\royale-asjs
>>
>> 8.ant main : completed with success
>>
>> 9.ant frameworks : completed with success
>>
>> 10.cd D:\dev\git\emulation_works\royale-asjs\frameworks\projects\
>> MXRoyale
>>
>> 11.ant : completed with success
>>
>> If it is ok, i can move on with this.
>>
>> Piotr, i just saw your mail, do you want me to move with maven ?
>>
>>
>>
>> 1. git clone https://github.com/apache/royale-asjs.git
>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs.git=02%7C01%7Caharui%40adobe.com%7C79ddabf4e3994a9db38908d59d1bde7c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636587665481338047=Vt%2FkEc6N8JZOQ6lviXl5apzi8hwZFJMlYPVWklcSItc%3D=0>
>>
>> 2. git checkout feature/MXRoyale
>>
>> Folder view :
>>
>>
>> 3.ant all
>>
>> Folder View :
>>
>>
>>
>> Fails and the result :
>> https://drive.google.com/open?id=1XZNfN8exZ_x_F4bTY5xIfxO328
>> eWHIQ4
>>
>> Next : i am going to check-out all tree repo manually and then build with
>> ant saperately.
>>
>> 08.04.2018 10:02 tarihinde Alex Harui yazdı:
>>
>> If you are using Maven, you may need to build the royale-compiler and
>> royale-typedefs repos first.  See the README in each of those repos.  You
>> can also use Ant instead of Maven.
>>
>> HTH,
>> -Alex
>>
>> From: Serkan Taş <serkan@likyateknoloji.com>
>> Reply-To: "users@royale.apache.org" <users@royale.apache.org>
>> Date: Saturday, April 7, 2018 at 11:41 PM
>> To: "users@royale.apache.org" <users@royale.apache.org>
>> Subject: MXRoyale build problem
>>
>> Hi Alex,
>>
>> Here is the steps and result (i spent some time but could not find a
>> resolution) :
>>
>> git clone https://github.com/apache/royale-asjs.git
>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs.git=02%7C01%7Caharui%40adobe.com%7C79ddabf4e3994a9db38908d59d1bde7c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636587665481338047=Vt%2FkEc6N8JZOQ6lviXl5apzi8hwZFJMlYPVWklcSItc%3D=0>
>>
>> cd royale-asjs
>>
>> git checkout feature/MXRoyale
>> mvn celan
>>
>> Result :
>>
>>
>>
>>
>> 07.04.2018 17:51 tarihinde Alex Harui yazdı:
>>
>> Hi Serkan,
>>
>> That would be great.  We need the help.
>>
>> We have a wiki page about Emulation components here [1].
>> And one person has been learning how to help in this long thread[2].
>>
>> [1] has an API list, but it does not take into account your API usage.  If
>> you want to integrate your list with the current list, that might be
>> useful.
>>
>> Let us know if you have other questions or need help getting started.
>>
>> Thanks,
>> -Alex
>>
>> [1] https://github.com/apache/royale-asjs/wiki/emulation-components 
>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2Femulation-components=02%7C01%7Caharui%40adobe.com%7C79ddabf4e3994a9db38908d59d1bde7c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636587665481338047=BVdRuWskUsnCNLp1IM49Dvi3%2BN6zg5O0VmBJ9hRG60M%3D=0>
>> [2] 
>> https://lists.apache.org/thread.html/f05b54c5721a3c96a6ef5f74180461240ab1a3 
>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2Ff05b54c5721a3c96a6ef5f74180461240ab1a3=02%7C01%7Caharui%40adobe.com%7C79ddabf4e3994a9db38908d59d1bde7c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636587665481338047=r1FEpWeuAka37dOHYtAYofsM2Ol5rq6h8LhSWkQTUUw%3D=0>f764dc9b4f0cb0e33a@%3Cusers.royale.apache.org%3E
>>
>> On 4/7/18, 4:17 AM, "Serkan Taş" <serkan@likyateknoloji.com> 
>> <serkan@likyateknoloji.com> wrote:
>>
>>
>> Hi Alex,
>>
>> I am going to be happy to help you and can try to do something valuable
>> for the process of emulation creation.
>>
>> Serkan
>>
>> 07.04.2018 09:20 tarihinde Alex Harui yazdı:
>>
>> Hi Serkan,
>>
>> You are correct that are several buttons.  Basic Button just creates a
>> simple HTML .  There are limits to how nice you can make it
>> look.
>> Other buttons try to make nicer looking buttons that you can control
>> more
>> aspects of the visuals.
>>
>> We are in the process of creating even more buttons that emulate the
>> most
>> popular APIs on MX and Spark Button.  It might be better for you to help
>> us create and polish these emulations.  Then you may not have to change
>> your code as much.
>>
>> HTH,
>> -Alex
>>
>> On 4/6/18, 1:05 PM, "Serkan Taş" <serkan@likyateknoloji.com> 
>> <serkan@likyateknoloji.com> wrote:
>>
>>
>> Hi,
>>
>> I see that there are several buttons, js, svg and now j. I was using mx
>> and s ones previously.
>>
>> I am not sure which one fits best, need advice.
>>
>> Second one, is there any equivalent of Form and FormItem structure ?
>>
>> It is takin time tp make the examples work on moonshine and check for
>> the needed component if exist and then learn :)
>>
>> Thanks in advance
>>
>> Regards,
>>
>> Serkan.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>
>
>


-- 

Piotr Zarzycki

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


Re: MXRoyale build problem

2018-04-08 Thread Serkan Taş
and then
build with ant saperately.

08.04.2018 10:02 tarihinde Alex Harui yazdı:

If you are using Maven, you may need to build the
royale-compiler and royale-typedefs repos first.  See the README
in each of those repos. You can also use Ant instead of Maven.

HTH,
-Alex

From: Serkan Taş <serkan@likyateknoloji.com
<mailto:serkan@likyateknoloji.com>>
Reply-To: "users@royale.apache.org
<mailto:users@royale.apache.org>" <users@royale.apache.org
<mailto:users@royale.apache.org>>
Date: Saturday, April 7, 2018 at 11:41 PM
To: "users@royale.apache.org <mailto:users@royale.apache.org>"
<users@royale.apache.org <mailto:users@royale.apache.org>>
Subject: MXRoyale build problem

Hi Alex,

Here is the steps and result (i spent some time but could not
find a resolution) :

git clone https://github.com/apache/royale-asjs.git

<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs.git=02%7C01%7Caharui%40adobe.com%7C79ddabf4e3994a9db38908d59d1bde7c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636587665481338047=Vt%2FkEc6N8JZOQ6lviXl5apzi8hwZFJMlYPVWklcSItc%3D=0>

cd royale-asjs

git checkout feature/MXRoyale

mvn celan

Result :




07.04.2018 17:51 tarihinde Alex Harui yazdı:

Hi Serkan,

That would be great.  We need the help.

We have a wiki page about Emulation components here [1].
And one person has been learning how to help in this long thread[2].

[1] has an API list, but it does not take into account your API usage.  If
you want to integrate your list with the current list, that might be
useful.

Let us know if you have other questions or need help getting started.

Thanks,
-Alex

[1]https://github.com/apache/royale-asjs/wiki/emulation-components

<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2Femulation-components=02%7C01%7Caharui%40adobe.com%7C79ddabf4e3994a9db38908d59d1bde7c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636587665481338047=BVdRuWskUsnCNLp1IM49Dvi3%2BN6zg5O0VmBJ9hRG60M%3D=0>
[2]
https://lists.apache.org/thread.html/f05b54c5721a3c96a6ef5f74180461240ab1a3

<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2Ff05b54c5721a3c96a6ef5f74180461240ab1a3=02%7C01%7Caharui%40adobe.com%7C79ddabf4e3994a9db38908d59d1bde7c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636587665481338047=r1FEpWeuAka37dOHYtAYofsM2Ol5rq6h8LhSWkQTUUw%3D=0>f764dc9b4f0cb0e33a@%3Cusers.royale.apache.org%3E
<mailto:f764dc9b4f0cb0e33a@%3Cusers.royale.apache.org%3E>

On 4/7/18, 4:17 AM, "Serkan Taş"<serkan@likyateknoloji.com>
<mailto:serkan@likyateknoloji.com>  wrote:


Hi Alex,

I am going to be happy to help you and can try to do something valuable
for the process of emulation creation.

Serkan

07.04.2018 09:20 tarihinde Alex Harui yazdı:

Hi Serkan,

You are correct that are several buttons.  Basic Button just creates a
simple HTML .  There are limits to how nice you can make it
look.
Other buttons try to make nicer looking buttons that you can control
more
aspects of the visuals.

We are in the process of creating even more buttons that emulate the
most
popular APIs on MX and Spark Button.  It might be better for you to help
us create and polish these emulations.  Then you may not have to change
your code as much.

HTH,
-Alex

On 4/6/18, 1:05 PM, "Serkan Taş"<serkan@likyateknoloji.com>
<mailto:serkan@likyateknoloji.com>  wrote:


Hi,

I see that there are several buttons, js, svg and now j. I was using mx
and s ones previously.

I am not sure which one fits best, need advice.

Second one, is there any equivalent of Form and FormItem structure ?

It is takin time tp make the examples work on moonshine and check for
the needed component if exist and then learn :)

Thanks in advance

Regards,

Serkan.













--

Piotr Zarzycki

Patreon: _https://www.patreon.com/piotrzarzycki_





Re: MXRoyale build problem

2018-04-08 Thread Piotr Zarzycki
Serkan,

It depends where you will feel comfortable. Maven scripts are quite clean
and self explanatory. With ANT it does not so obvious. However you probably
won't change anything in scripts.

If ANT worked for you go with ANT. Going with Maven you will be able to
rebuild one module and test it. With ANT it is probably also possible.

Piotr

2018-04-08 12:50 GMT+02:00 Serkan Taş <serkan@likyateknoloji.com>:

> Here is the last result :
> 1. git clone https://github.com/apache/royale-asjs.git
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs.git=02%7C01%7Caharui%40adobe.com%7C79ddabf4e3994a9db38908d59d1bde7c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636587665481338047=Vt%2FkEc6N8JZOQ6lviXl5apzi8hwZFJMlYPVWklcSItc%3D=0>
>
> 2.cd royale-asjs
>
> 3. git checkout feature/MXRoyale
> 4.ant all : failed; details in the mail below
>
> 5.cd ..\royale-typedefs
>
> 6.ant : completed with success
>
> 7.cd ..\royale-asjs
>
> 8.ant main : completed with success
>
> 9.ant frameworks : completed with success
>
> 10.cd D:\dev\git\emulation_works\royale-asjs\frameworks\
> projects\MXRoyale
>
> 11.ant : completed with success
>
> If it is ok, i can move on with this.
>
> Piotr, i just saw your mail, do you want me to move with maven ?
>
>
>
> 1. git clone https://github.com/apache/royale-asjs.git
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs.git=02%7C01%7Caharui%40adobe.com%7C79ddabf4e3994a9db38908d59d1bde7c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636587665481338047=Vt%2FkEc6N8JZOQ6lviXl5apzi8hwZFJMlYPVWklcSItc%3D=0>
>
> 2. git checkout feature/MXRoyale
>
> Folder view :
>
>
> 3.ant all
>
> Folder View :
>
>
>
> Fails and the result :
> https://drive.google.com/open?id=1XZNfN8exZ_x_F4bTY5xIfxO328eWHIQ4
>
> Next : i am going to check-out all tree repo manually and then build with
> ant saperately.
>
> 08.04.2018 10:02 tarihinde Alex Harui yazdı:
>
> If you are using Maven, you may need to build the royale-compiler and
> royale-typedefs repos first.  See the README in each of those repos.  You
> can also use Ant instead of Maven.
>
> HTH,
> -Alex
>
> From: Serkan Taş <serkan....@likyateknoloji.com>
> Reply-To: "users@royale.apache.org" <users@royale.apache.org>
> Date: Saturday, April 7, 2018 at 11:41 PM
> To: "users@royale.apache.org" <users@royale.apache.org>
> Subject: MXRoyale build problem
>
> Hi Alex,
>
> Here is the steps and result (i spent some time but could not find a
> resolution) :
>
> git clone https://github.com/apache/royale-asjs.git
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs.git=02%7C01%7Caharui%40adobe.com%7C79ddabf4e3994a9db38908d59d1bde7c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636587665481338047=Vt%2FkEc6N8JZOQ6lviXl5apzi8hwZFJMlYPVWklcSItc%3D=0>
>
> cd royale-asjs
>
> git checkout feature/MXRoyale
> mvn celan
>
> Result :
>
>
>
>
> 07.04.2018 17:51 tarihinde Alex Harui yazdı:
>
> Hi Serkan,
>
> That would be great.  We need the help.
>
> We have a wiki page about Emulation components here [1].
> And one person has been learning how to help in this long thread[2].
>
> [1] has an API list, but it does not take into account your API usage.  If
> you want to integrate your list with the current list, that might be
> useful.
>
> Let us know if you have other questions or need help getting started.
>
> Thanks,
> -Alex
>
> [1] https://github.com/apache/royale-asjs/wiki/emulation-components 
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2Femulation-components=02%7C01%7Caharui%40adobe.com%7C79ddabf4e3994a9db38908d59d1bde7c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636587665481338047=BVdRuWskUsnCNLp1IM49Dvi3%2BN6zg5O0VmBJ9hRG60M%3D=0>
> [2] 
> https://lists.apache.org/thread.html/f05b54c5721a3c96a6ef5f74180461240ab1a3 
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2Ff05b54c5721a3c96a6ef5f74180461240ab1a3=02%7C01%7Caharui%40adobe.com%7C79ddabf4e3994a9db38908d59d1bde7c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636587665481338047=r1FEpWeuAka37dOHYtAYofsM2Ol5rq6h8LhSWkQTUUw%3D=0>f764dc9b4f0cb0e33a@%3Cusers.royale.apache.org%3E
>
> On 4/7/18, 4:17 AM, "Serkan Taş" <serkan@likyateknoloji.com> 
> <serkan@likyateknoloji.com> wrote:
>
>
> Hi Alex,
>
> I am going to be happy to help you and can try

Re: MXRoyale build problem

2018-04-08 Thread Serkan Taş

Here is the last result :

1.     git clone https://github.com/apache/royale-asjs.git

2.    cd royale-asjs

3.     git checkout feature/MXRoyale

4.    ant all : failed; details in the mail below

5.    cd ..\royale-typedefs

6.    ant : completed with success

7.    cd ..\royale-asjs

8.    ant main : completed with success

9.    ant frameworks : completed with success

10.    cd 
D:\dev\git\emulation_works\royale-asjs\frameworks\projects\MXRoyale


11.    ant : completed with success

If it is ok, i can move on with this.

Piotr, i just saw your mail, do you want me to move with maven ?



1.     git clone https://github.com/apache/royale-asjs.git

2.     git checkout feature/MXRoyale

        Folder view :


3.    ant all

        Folder View :



        Fails and the result :
https://drive.google.com/open?id=1XZNfN8exZ_x_F4bTY5xIfxO328eWHIQ4

Next : i am going to check-out all tree repo manually and then build 
with ant saperately.


08.04.2018 10:02 tarihinde Alex Harui yazdı:
If you are using Maven, you may need to build the royale-compiler and 
royale-typedefs repos first.  See the README in each of those repos. 
 You can also use Ant instead of Maven.


HTH,
-Alex

From: Serkan Taş <serkan@likyateknoloji.com 
<mailto:serkan@likyateknoloji.com>>
Reply-To: "users@royale.apache.org <mailto:users@royale.apache.org>" 
<users@royale.apache.org <mailto:users@royale.apache.org>>

Date: Saturday, April 7, 2018 at 11:41 PM
To: "users@royale.apache.org <mailto:users@royale.apache.org>" 
<users@royale.apache.org <mailto:users@royale.apache.org>>

Subject: MXRoyale build problem

Hi Alex,

Here is the steps and result (i spent some time but could not find a 
resolution) :


git clone https://github.com/apache/royale-asjs.git

cd royale-asjs

git checkout feature/MXRoyale

mvn celan

Result :




07.04.2018 17:51 tarihinde Alex Harui yazdı:

Hi Serkan,

That would be great.  We need the help.

We have a wiki page about Emulation components here [1].
And one person has been learning how to help in this long thread[2].

[1] has an API list, but it does not take into account your API usage.  If
you want to integrate your list with the current list, that might be
useful.

Let us know if you have other questions or need help getting started.

Thanks,
-Alex

[1]https://github.com/apache/royale-asjs/wiki/emulation-components
[2]
https://lists.apache.org/thread.html/f05b54c5721a3c96a6ef5f74180461240ab1a3f764dc9b4f0cb0e33a@%3Cusers.royale.apache.org%3E

On 4/7/18, 4:17 AM, "Serkan Taş"<serkan@likyateknoloji.com>  wrote:


Hi Alex,

I am going to be happy to help you and can try to do something valuable
for the process of emulation creation.

Serkan

07.04.2018 09:20 tarihinde Alex Harui yazdı:

Hi Serkan,

You are correct that are several buttons.  Basic Button just creates a
simple HTML .  There are limits to how nice you can make it
look.
Other buttons try to make nicer looking buttons that you can control
more
aspects of the visuals.

We are in the process of creating even more buttons that emulate the
most
popular APIs on MX and Spark Button.  It might be better for you to help
us create and polish these emulations.  Then you may not have to change
your code as much.

HTH,
-Alex

On 4/6/18, 1:05 PM, "Serkan Taş"<serkan@likyateknoloji.com>  wrote:


Hi,

I see that there are several buttons, js, svg and now j. I was using mx
and s ones previously.

I am not sure which one fits best, need advice.

Second one, is there any equivalent of Form and FormItem structure ?

It is takin time tp make the examples work on moonshine and check for
the needed component if exist and then learn :)

Thanks in advance

Regards,

Serkan.












Re: MXRoyale build problem

2018-04-08 Thread Alex Harui
If you are using Maven, you may need to build the royale-compiler and 
royale-typedefs repos first.  See the README in each of those repos.  You can 
also use Ant instead of Maven.

HTH,
-Alex

From: Serkan Taş 
<serkan@likyateknoloji.com<mailto:serkan@likyateknoloji.com>>
Reply-To: "users@royale.apache.org<mailto:users@royale.apache.org>" 
<users@royale.apache.org<mailto:users@royale.apache.org>>
Date: Saturday, April 7, 2018 at 11:41 PM
To: "users@royale.apache.org<mailto:users@royale.apache.org>" 
<users@royale.apache.org<mailto:users@royale.apache.org>>
Subject: MXRoyale build problem


Hi Alex,

Here is the steps and result (i spent some time but could not find a 
resolution) :

git clone 
https://github.com/apache/royale-asjs.git<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs.git=02%7C01%7Caharui%40adobe.com%7C79ddabf4e3994a9db38908d59d1bde7c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636587665481338047=Vt%2FkEc6N8JZOQ6lviXl5apzi8hwZFJMlYPVWklcSItc%3D=0>

cd royale-asjs

git checkout feature/MXRoyale

mvn celan

Result :

[cid:part1.68AE0871.5F16C1D8@likyateknoloji.com]


07.04.2018 17:51 tarihinde Alex Harui yazdı:

Hi Serkan,

That would be great.  We need the help.

We have a wiki page about Emulation components here [1].
And one person has been learning how to help in this long thread[2].

[1] has an API list, but it does not take into account your API usage.  If
you want to integrate your list with the current list, that might be
useful.

Let us know if you have other questions or need help getting started.

Thanks,
-Alex

[1] 
https://github.com/apache/royale-asjs/wiki/emulation-components<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2Femulation-components=02%7C01%7Caharui%40adobe.com%7C79ddabf4e3994a9db38908d59d1bde7c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636587665481338047=BVdRuWskUsnCNLp1IM49Dvi3%2BN6zg5O0VmBJ9hRG60M%3D=0>
[2]
https://lists.apache.org/thread.html/f05b54c5721a3c96a6ef5f74180461240ab1a3<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2Ff05b54c5721a3c96a6ef5f74180461240ab1a3=02%7C01%7Caharui%40adobe.com%7C79ddabf4e3994a9db38908d59d1bde7c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636587665481338047=r1FEpWeuAka37dOHYtAYofsM2Ol5rq6h8LhSWkQTUUw%3D=0>f764dc9b4f0cb0e33a@%3Cusers.royale.apache.org%3E<mailto:f764dc9b4f0cb0e33a@%3Cusers.royale.apache.org%3E>

On 4/7/18, 4:17 AM, "Serkan Taş" 
<serkan@likyateknoloji.com><mailto:serkan@likyateknoloji.com> wrote:



Hi Alex,

I am going to be happy to help you and can try to do something valuable
for the process of emulation creation.

Serkan

07.04.2018 09:20 tarihinde Alex Harui yazdı:


Hi Serkan,

You are correct that are several buttons.  Basic Button just creates a
simple HTML .  There are limits to how nice you can make it
look.
Other buttons try to make nicer looking buttons that you can control
more
aspects of the visuals.

We are in the process of creating even more buttons that emulate the
most
popular APIs on MX and Spark Button.  It might be better for you to help
us create and polish these emulations.  Then you may not have to change
your code as much.

HTH,
-Alex

On 4/6/18, 1:05 PM, "Serkan Taş" 
<serkan@likyateknoloji.com><mailto:serkan@likyateknoloji.com> wrote:



Hi,

I see that there are several buttons, js, svg and now j. I was using mx
and s ones previously.

I am not sure which one fits best, need advice.

Second one, is there any equivalent of Form and FormItem structure ?

It is takin time tp make the examples work on moonshine and check for
the needed component if exist and then learn :)

Thanks in advance

Regards,

Serkan.








MXRoyale build problem

2018-04-08 Thread Serkan Taş

Hi Alex,

Here is the steps and result (i spent some time but could not find a 
resolution) :


git clone https://github.com/apache/royale-asjs.git

cd royale-asjs

git checkout feature/MXRoyale

mvn celan

Result :




07.04.2018 17:51 tarihinde Alex Harui yazdı:

Hi Serkan,

That would be great.  We need the help.

We have a wiki page about Emulation components here [1].
And one person has been learning how to help in this long thread[2].

[1] has an API list, but it does not take into account your API usage.  If
you want to integrate your list with the current list, that might be
useful.

Let us know if you have other questions or need help getting started.

Thanks,
-Alex

[1] https://github.com/apache/royale-asjs/wiki/emulation-components
[2]
https://lists.apache.org/thread.html/f05b54c5721a3c96a6ef5f74180461240ab1a3
f764dc9b4f0cb0e33a@%3Cusers.royale.apache.org%3E

On 4/7/18, 4:17 AM, "Serkan Taş"  wrote:


Hi Alex,

I am going to be happy to help you and can try to do something valuable
for the process of emulation creation.

Serkan

07.04.2018 09:20 tarihinde Alex Harui yazdı:

Hi Serkan,

You are correct that are several buttons.  Basic Button just creates a
simple HTML .  There are limits to how nice you can make it
look.
Other buttons try to make nicer looking buttons that you can control
more
aspects of the visuals.

We are in the process of creating even more buttons that emulate the
most
popular APIs on MX and Spark Button.  It might be better for you to help
us create and polish these emulations.  Then you may not have to change
your code as much.

HTH,
-Alex

On 4/6/18, 1:05 PM, "Serkan Taş"  wrote:


Hi,

I see that there are several buttons, js, svg and now j. I was using mx
and s ones previously.

I am not sure which one fits best, need advice.

Second one, is there any equivalent of Form and FormItem structure ?

It is takin time tp make the examples work on moonshine and check for
the needed component if exist and then learn :)

Thanks in advance

Regards,

Serkan.