Build failed in Jenkins: royale-asjs_MXTests #873

2019-06-19 Thread Apache Royale CI Server
See 


--
[...truncated 2.34 MB...]
[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

Re: Jewel Module not working on release mode when deferred the load

2019-06-19 Thread Greg Dove
Hi Carlos,

This was manifesting as a minification problem, but actually that was a bit
misleading as the root cause was a compiler bug with localId.
I will push a fix for that today which means the release build will work
the same as debug build for the module example.




On Thu, Jun 20, 2019 at 7:38 AM Carlos Rovira 
wrote:

> Hi,
>
> I continue working on the blog example for modules. I think is almost done
> but I have a final issue. It works on debug but not on release
>
> On release when I hit button and load the module I get the following error
> on console:
>
> [Error] TypeError: undefined is not an object (evaluating 'this.yh.ja')
> ja (MainJewelApp.js:393:142)
> pd (MainJewelApp.js:393:223)
> (función anónima)
> Wf (MainJewelApp.js:34:244)
> fg (MainJewelApp.js:43:281)
> Rf (MainJewelApp.js:36)
> (función anónima) (MainJewelApp.js:32)
>
> Do you have some hint about what could be wrong?
> I was thinking that this could be need due to some magnification problem so
> I tried for now -js-dynamic-access-unknown-members=true, but this does not
> make any change
>
> Until now, in Basic Modules, it was loading as the ModuleLoader is
> addedToParent, in Jewel ModuleLoader I put more control, since the user
> normally would want to load the module on demand.
>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


Re: [MAVEN-BUILD] Royale-asjs - Build # 1920 - Still Failing

2019-06-19 Thread Alex Harui
I think I figured it out.  The Jenkins config on build@ did not have the "main" 
profile in the list of profiles so it never rebuilt the framework SWCs (so 
Module was not in the Jewel SWC).  I compared output of my local build against 
the CI build and saw that the Reactor was never building the framework SWCs.

-Alex

On 6/19/19, 9:41 AM, "Carlos Rovira"  wrote:

Strangely #1922 fails for the same reason, but locally worked right.
I need to investigate this further

El mié., 19 jun. 2019 a las 18:13, Carlos Rovira ()
escribió:

> Hi Piotr,
>
> I fixed this updating the pom in the new example to just use JSRoyale
> thanks for reporting it
>
> El mié., 19 jun. 2019 a las 13:38, Carlos Rovira 
()
> escribió:
>
>> Hi Piotr,
>>
>> I'll take a look at it in few hours, thanks for letting me know
>>
>> El mié., 19 jun. 2019 a las 8:38, Piotr Zarzycki (<
>> piotrzarzyck...@gmail.com>) escribió:
>>
>>> Hi Carlos,
>>>
>>> Jewel module is failing here. Did you notice that on your end ?
>>>
>>> Thanks,
>>> Piotr
>>>
>>> śr., 19 cze 2019 o 08:35 Apache Jenkins Server <
>>> jenk...@builds.apache.org>
>>> napisał(a):
>>>
>>> > The Apache Jenkins build system has built Royale-asjs (build #1920)
>>> >
>>> > Status: Still Failing
>>> >
>>> > Check console output at
>>> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuilds.apache.org%2Fjob%2FRoyale-asjs%2F1920%2Fdata=02%7C01%7Caharui%40adobe.com%7C4ea8a6b0b96743b6983b08d6f4d50277%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636965593045633116sdata=SzPqhZVcZjsONHK5ZpiiUQslIA3zeR1EhHG67n46%2BwU%3Dreserved=0
>>> > to view the results.
>>>
>>>
>>>
>>> --
>>>
>>> Piotr Zarzycki
>>>
>>> Patreon: 
*https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7C4ea8a6b0b96743b6983b08d6f4d50277%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636965593045633116sdata=GGdshPsPAX2KgPEg7ROrbajbV5YA3bv9G8W%2FvHjedwY%3Dreserved=0
>>> 
*
>>>
>>
>>
>> --
>> Carlos Rovira
>> 
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C4ea8a6b0b96743b6983b08d6f4d50277%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636965593045633116sdata=7a9r2noNaOa%2By5R6qkCJQ%2FlhNUbjC0NACaHc6j62DDM%3Dreserved=0
>>
>>
>
> --
> Carlos Rovira
> 
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C4ea8a6b0b96743b6983b08d6f4d50277%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636965593045633116sdata=7a9r2noNaOa%2By5R6qkCJQ%2FlhNUbjC0NACaHc6j62DDM%3Dreserved=0
>
>

-- 
Carlos Rovira

https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C4ea8a6b0b96743b6983b08d6f4d50277%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636965593045633116sdata=7a9r2noNaOa%2By5R6qkCJQ%2FlhNUbjC0NACaHc6j62DDM%3Dreserved=0




Jenkins build is back to normal : royale-asjs_MXTests #871

2019-06-19 Thread Apache Royale CI Server
See 




Re: Implicit casts and skipAsCercions

2019-06-19 Thread Greg Dove
Harbs,

js-complex-implicit-coercions is on by default. The default behavior is
therefore now the same as swf. It is an optimization to turn it off.
You need to switch it off if you want to avoid it. But if you are seeing
runtime errors, then it is likely indicating something that would not work
at runtime in swf, so you may also want to review that first.

If you want code to work as before, you need to do this:

-js-complex-implicit-coercions=false;
-js-vector-index-checks=false;
-js-resolve-uncertain=false;

or to add them to the -config.xml

There is also the option to output Vector as Array, if you want the legacy
approach for Vectors. I outlined these in an earlier post, but I will add
something more detailed to docs this week.

For XML, I'm sorry if something is not working right now. I did port a lot
of your adhoc tests to the manualtests project. And added quite a few more
new tests. The implementation was not working correctly for quite a few
things. So while I addressed some new issues,there is still a lot more to
do. It's entirely possible that I broke something that did not have a test
yet. Unless we focus more on test coverage, it will be easy to break things
as other things get fixed, particularly with something like XML, which is
reasonably complex. With inadequate test coverage, it can even be possible
to start relying on an implementation that does not work as it should.
Yishay: can you please give me a simple test case for the XML issue you are
seeing? I will look into it today.





On Thu, Jun 20, 2019 at 8:33 AM Harbs  wrote:

> The code has /* implicit cast */ and we do not have the
> complex-implicit-coresions set.
>
> FYI, XML is also broken due to empty nodes which did not used to be there,
> but I’ll let Yishay comment on the details.
>
> > On Jun 19, 2019, at 11:29 PM, Greg Dove  wrote:
> >
> > Hi Yishay,
> >
> > If there's a problem with this I will address it asap.
> > The setting was not working correctly before. I think it is now, so that
> > may have affected the output, but perhaps there are some test cases I did
> > not cover.
> >
> > skipAsCoercions only relates to explicit coercions, and should not have
> an
> > effect on the implicit coercions
> >
> > (But it does make me wonder if I have implemented the new config level
> > option correctly, maybe it should be added as one of the
> > -js-output-optimization options instead of being another top level
> option.
> > I can revisit this in another thread.)
> >
> > For now, the equivalent is
> > false
> >
> > or
> > -js-complex-implicit-coercions=false
> >
> > Do you have either of those set? If so then you should not see the
> implicit
> > coercions unless they are toggled on locally and therefore it is an error
> >
> > Can you please also use 'find in files' with your js-debug output,
> > searching for the text:
> > /* implicit cast */
> > and inspect the site of the runtime error?
> >
> > Is it generating the right cast on the right for the expected type on the
> > left if it is assignment?
> >
> >
> >
> >
> >
> >
> >
> > On Thu, Jun 20, 2019 at 2:00 AM Yishay Weiss 
> wrote:
> >
> >> After updating the compiler we’re getting a runtime type coercion
> failure
> >> which didn’t exist before.
> >>
> >> A quick question: should ‘skipAsCoercions’ suppress implicit casts?
> Could
> >> the latest commit [1] have changed that?
> >>
> >> [1]
> >>
> https://github.com/apache/royale-compiler/commit/73caf20e03b72bb9e1717f2339c14cb79c6082b9
> >>
> >> Thanks.
> >>
>
>


Re: Implicit casts and skipAsCercions

2019-06-19 Thread Harbs
The code has /* implicit cast */ and we do not have the 
complex-implicit-coresions set.

FYI, XML is also broken due to empty nodes which did not used to be there, but 
I’ll let Yishay comment on the details.

> On Jun 19, 2019, at 11:29 PM, Greg Dove  wrote:
> 
> Hi Yishay,
> 
> If there's a problem with this I will address it asap.
> The setting was not working correctly before. I think it is now, so that
> may have affected the output, but perhaps there are some test cases I did
> not cover.
> 
> skipAsCoercions only relates to explicit coercions, and should not have an
> effect on the implicit coercions
> 
> (But it does make me wonder if I have implemented the new config level
> option correctly, maybe it should be added as one of the
> -js-output-optimization options instead of being another top level option.
> I can revisit this in another thread.)
> 
> For now, the equivalent is
> false
> 
> or
> -js-complex-implicit-coercions=false
> 
> Do you have either of those set? If so then you should not see the implicit
> coercions unless they are toggled on locally and therefore it is an error
> 
> Can you please also use 'find in files' with your js-debug output,
> searching for the text:
> /* implicit cast */
> and inspect the site of the runtime error?
> 
> Is it generating the right cast on the right for the expected type on the
> left if it is assignment?
> 
> 
> 
> 
> 
> 
> 
> On Thu, Jun 20, 2019 at 2:00 AM Yishay Weiss  wrote:
> 
>> After updating the compiler we’re getting a runtime type coercion failure
>> which didn’t exist before.
>> 
>> A quick question: should ‘skipAsCoercions’ suppress implicit casts? Could
>> the latest commit [1] have changed that?
>> 
>> [1]
>> https://github.com/apache/royale-compiler/commit/73caf20e03b72bb9e1717f2339c14cb79c6082b9
>> 
>> Thanks.
>> 



Re: Implicit casts and skipAsCercions

2019-06-19 Thread Greg Dove
Hi Yishay,

If there's a problem with this I will address it asap.
The setting was not working correctly before. I think it is now, so that
may have affected the output, but perhaps there are some test cases I did
not cover.

skipAsCoercions only relates to explicit coercions, and should not have an
effect on the implicit coercions

(But it does make me wonder if I have implemented the new config level
option correctly, maybe it should be added as one of the
-js-output-optimization options instead of being another top level option.
I can revisit this in another thread.)

For now, the equivalent is
false

or
-js-complex-implicit-coercions=false

Do you have either of those set? If so then you should not see the implicit
coercions unless they are toggled on locally and therefore it is an error

Can you please also use 'find in files' with your js-debug output,
searching for the text:
/* implicit cast */
and inspect the site of the runtime error?

Is it generating the right cast on the right for the expected type on the
left if it is assignment?







On Thu, Jun 20, 2019 at 2:00 AM Yishay Weiss  wrote:

> After updating the compiler we’re getting a runtime type coercion failure
> which didn’t exist before.
>
> A quick question: should ‘skipAsCoercions’ suppress implicit casts? Could
> the latest commit [1] have changed that?
>
> [1]
> https://github.com/apache/royale-compiler/commit/73caf20e03b72bb9e1717f2339c14cb79c6082b9
>
> Thanks.
>


Build failed in Jenkins: royale-asjs_MXTests #870

2019-06-19 Thread Apache Royale CI Server
See 


Changes:

[carlosrovira] BE0013: fix js-release and js-debug module copy correctly to 
Application

[carlosrovira] jewel-moduleloader: New ModuleLoader. We need to avoid 
inheritance to

[carlosrovira] BE0013: use new Jewel ModuleLoader

[carlosrovira] basic-modules: clean imports

[carlosrovira] ModuleExample: make maven copy files from module to app so 
target is

[carlosrovira] jewel-modules: clean imports and avoid module to load by 
default. Users

[carlosrovira] BE0013: ModuleLoader now can load a module on request, works on 
debug

[carlosrovira] jewel-moduleloader: add autoload, so you users can load a module

--
[...truncated 2.41 MB...]
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/ISelectable.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/CheckBox.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/ITextItemRenderer.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/supportClasses/StringItemRenderer.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/utils/loadBeadFromValuesManager.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/events/ItemClickedEvent.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IScrollingViewport.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/supportClasses/ScrollingViewport.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/debugging/throwError.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/ISpinnerView.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/SpinnerView.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IImageModel.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/models/ImageModel.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/mx/utils/ArrayUtil.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/SimpleCSSStylesWithFlex.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/layouts/TileLayout.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/mx/managers/IFocusManagerComponent.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/MenuBar.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/TitleBarTitle.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/layout/LayoutData.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/spark/layouts/supportClasses/SparkLayoutBead.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IBinding.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/binding/ConstantBinding.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/controllers/ItemRendererMouseController.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/utils/BinaryData.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IDataGrid.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/graphics/SolidColorStroke.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/DataGridButtonBar.js
[mxmlc] 

Jewel Module not working on release mode when deferred the load

2019-06-19 Thread Carlos Rovira
Hi,

I continue working on the blog example for modules. I think is almost done
but I have a final issue. It works on debug but not on release

On release when I hit button and load the module I get the following error
on console:

[Error] TypeError: undefined is not an object (evaluating 'this.yh.ja')
ja (MainJewelApp.js:393:142)
pd (MainJewelApp.js:393:223)
(función anónima)
Wf (MainJewelApp.js:34:244)
fg (MainJewelApp.js:43:281)
Rf (MainJewelApp.js:36)
(función anónima) (MainJewelApp.js:32)

Do you have some hint about what could be wrong?
I was thinking that this could be need due to some magnification problem so
I tried for now -js-dynamic-access-unknown-members=true, but this does not
make any change

Until now, in Basic Modules, it was loading as the ModuleLoader is
addedToParent, in Jewel ModuleLoader I put more control, since the user
normally would want to load the module on demand.



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


Re: [MAVEN-BUILD] Royale-asjs - Build # 1920 - Still Failing

2019-06-19 Thread Carlos Rovira
Strangely #1922 fails for the same reason, but locally worked right.
I need to investigate this further

El mié., 19 jun. 2019 a las 18:13, Carlos Rovira ()
escribió:

> Hi Piotr,
>
> I fixed this updating the pom in the new example to just use JSRoyale
> thanks for reporting it
>
> El mié., 19 jun. 2019 a las 13:38, Carlos Rovira ()
> escribió:
>
>> Hi Piotr,
>>
>> I'll take a look at it in few hours, thanks for letting me know
>>
>> El mié., 19 jun. 2019 a las 8:38, Piotr Zarzycki (<
>> piotrzarzyck...@gmail.com>) escribió:
>>
>>> Hi Carlos,
>>>
>>> Jewel module is failing here. Did you notice that on your end ?
>>>
>>> Thanks,
>>> Piotr
>>>
>>> śr., 19 cze 2019 o 08:35 Apache Jenkins Server <
>>> jenk...@builds.apache.org>
>>> napisał(a):
>>>
>>> > The Apache Jenkins build system has built Royale-asjs (build #1920)
>>> >
>>> > Status: Still Failing
>>> >
>>> > Check console output at
>>> https://builds.apache.org/job/Royale-asjs/1920/
>>> > to view the results.
>>>
>>>
>>>
>>> --
>>>
>>> Piotr Zarzycki
>>>
>>> Patreon: *https://www.patreon.com/piotrzarzycki
>>> *
>>>
>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

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


Re: [MAVEN-BUILD] Royale-asjs - Build # 1920 - Still Failing

2019-06-19 Thread Carlos Rovira
Hi Piotr,

I fixed this updating the pom in the new example to just use JSRoyale
thanks for reporting it

El mié., 19 jun. 2019 a las 13:38, Carlos Rovira ()
escribió:

> Hi Piotr,
>
> I'll take a look at it in few hours, thanks for letting me know
>
> El mié., 19 jun. 2019 a las 8:38, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
>> Hi Carlos,
>>
>> Jewel module is failing here. Did you notice that on your end ?
>>
>> Thanks,
>> Piotr
>>
>> śr., 19 cze 2019 o 08:35 Apache Jenkins Server > >
>> napisał(a):
>>
>> > The Apache Jenkins build system has built Royale-asjs (build #1920)
>> >
>> > Status: Still Failing
>> >
>> > Check console output at https://builds.apache.org/job/Royale-asjs/1920/
>> > to view the results.
>>
>>
>>
>> --
>>
>> Piotr Zarzycki
>>
>> Patreon: *https://www.patreon.com/piotrzarzycki
>> *
>>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

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


Re: [MAVEN-BUILD] Royale-asjs - Build # 1905 - Still Failing

2019-06-19 Thread Carlos Rovira
Thanks Alex,

I update wiki here:

https://github.com/apache/royale-asjs/wiki/Build-Apache-Royale-with-Maven

with that info



El jue., 13 jun. 2019 a las 17:43, Alex Harui ()
escribió:

> So yes, to build all SWCs for Maven, you need to use the profiles that
> create the SWF SWCs.  We changed the default to not require the Adobe
> artifacts.
>
> I think the command line is actually:
>
>   mvn clean install -P generate-swcs-for-swf,main
>
>
> And similarly, when building examples, to get the SWF output you have to
> specify
>
>   mvn clean install -P generate-swf
>
> However, for the particular blog example that was failing, you also have
> the option of disabling the SWF build for that example since I'm not sure
> it would ever run in Flash/AIR without an emulation of that third-party
> library.  I think there are already some POMs that disable the SWF build.
>
> HTH,
> -Alex
>
> On 6/13/19, 5:32 AM, "Carlos Rovira"  wrote:
>
> Hi Piotr,
>
> I mean that I run all days a script that runs maven on all repos and
> then
> ant to build sdk. Seems now we need to update from normal "man clean
> install" to "mvn clean install -Pgenerate-swcs-for-swf"
> in that script to make all days swf swc builds be update and notice
> that
> kind of problems. I understand from what Alex said in this thread that
> I
> didn't see that kind of error locally due to not running with that
> profile
> in the command line. So from now on I should notice if a problem like
> that
> arise.
>
>
> El jue., 13 jun. 2019 a las 14:22, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > Hi Carlos,
> >
> > I don't get last part - Are you going to change something on your end
> > locally or in framework build?
> >
> >
> > czw., 13 cze 2019 o 14:04 Carlos Rovira 
> > napisał(a):
> >
> > > Thanks Alex, Piotr,
> > >
> > > Greg told me that he changed the build script due to changes done
> in
> > latest
> > > months to:
> > >
> > > mvn clean install -Pgenerate-swcs-for-swf
> > >
> > > the swf swc builds were not updating
> > >
> > > so I'll change to that too, and I guess I should be able to notice
> that
> > > kind of problems in the future
> > >
> > > Let me know if that has sense
> > >
> > > Thanks
> > >
> > > El jue., 13 jun. 2019 a las 8:40, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>)
> > > escribió:
> > >
> > > > Thanks Alex for the tip. Probably each of those examples is
> building
> > with
> > > > JSRoyale and SWF switch. Surrounding by COMPILE::JS was the right
> > choice.
> > > > We have working build.
> > > >
> > > > czw., 13 cze 2019 o 00:35 Alex Harui 
> > > > napisał(a):
> > > >
> > > > > I was able to reproduce the error when building the SWF
> version of
> > the
> > > > > example.
> > > > >
> > > > > mvn clean install -P generate-swf
> > > > >
> > > > > HTH,
> > > > > -Alex
> > > > >
> > > > > On 6/12/19, 2:22 PM, "Piotr Zarzycki" <
> piotrzarzyck...@gmail.com>
> > > > wrote:
> > > > >
> > > > > Carlos,
> > > > >
> > > > > Maybe surrounding that line hljs by COMPILE::JS ?
> > > > >
> > > > > Thanks,
> > > > > Piotr
> > > > >
> > > > > śr., 12 cze 2019 o 21:11 Alex Harui
> 
> > > > > napisał(a):
> > > > >
> > > > > > Using ** got me past the rat issue.  My Windows builds
> are
> > > hanging
> > > > > getting
> > > > > > downloads from apache snapshots.
> > > > > >
> > > > > > I pushed the ** change.  Hopefully it won't break on
> some other
> > > > > machine.
> > > > > > Still no idea why it is suddenly so sensitive.
> > > > > >
> > > > > > -Alex
> > > > > >
> > > > > > On 6/12/19, 11:54 AM, "Carlos Rovira" <
> carlosrov...@apache.org
> > >
> > > > > wrote:
> > > > > >
> > > > > > ok, I was thinking to do the same, but since I can
> see if
> > it
> > > > > could work
> > > > > > prefer not to mess.
> > > > > > So I'll not commit my change waiting for yours Alex
> > > > > >
> > > > > > Thanks
> > > > > >
> > > > > >
> > > > > >
> > > > > > El mié., 12 jun. 2019 a las 20:50, Alex Harui
> > > > > > ()
> > > > > > escribió:
> > > > > >
> > > > > > > I get that too after picking up Piotr's change.  I
> think
> > > > > somehow
> > > > > > something
> > > > > > > changed in Rat and it is now interpreting paths
> > differently
> > > > > than it
> > > > > > used
> > > > > > > to.  I'm trying a fix using **/fb.properties.  I'll
> > commit
> > > it
> > > > > if it
> > > > > > works.
> > > > > > >
> 

Implicit casts and skipAsCercions

2019-06-19 Thread Yishay Weiss
After updating the compiler we’re getting a runtime type coercion failure which 
didn’t exist before.

A quick question: should ‘skipAsCoercions’ suppress implicit casts? Could the 
latest commit [1] have changed that?

[1] 
https://github.com/apache/royale-compiler/commit/73caf20e03b72bb9e1717f2339c14cb79c6082b9

Thanks.


Re: [MAVEN-BUILD] Royale-asjs - Build # 1920 - Still Failing

2019-06-19 Thread Carlos Rovira
Hi Piotr,

I'll take a look at it in few hours, thanks for letting me know

El mié., 19 jun. 2019 a las 8:38, Piotr Zarzycki ()
escribió:

> Hi Carlos,
>
> Jewel module is failing here. Did you notice that on your end ?
>
> Thanks,
> Piotr
>
> śr., 19 cze 2019 o 08:35 Apache Jenkins Server 
> napisał(a):
>
> > The Apache Jenkins build system has built Royale-asjs (build #1920)
> >
> > Status: Still Failing
> >
> > Check console output at https://builds.apache.org/job/Royale-asjs/1920/
> > to view the results.
>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>


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


RE: [royale-asjs] branch develop updated: Adding a resizable load inicator.

2019-06-19 Thread Yishay Weiss
I changed that in



a45f3638697492642ee93c60e74f8995dfcf79a9



Thanks.






From: Alex Harui 
Sent: Wednesday, June 19, 2019 9:20:47 AM
To: dev@royale.apache.org; comm...@royale.apache.org
Subject: Re: [royale-asjs] branch develop updated: Adding a resizable load 
inicator.

Yishay,

Are you still using 3rd party load indicators?  If so, I think the MIT License 
attribution is actually supposed to go in LICENSE not NOTICE.  See
http://www.apache.org/dev/licensing-howto.html#permissive-deps

Thanks,
-Alex

On 6/18/19, 10:18 PM, "yish...@apache.org"  wrote:

This is an automated email from the ASF dual-hosted git repository.

yishayw pushed a commit to branch develop
in repository 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitbox.apache.org%2Frepos%2Fasf%2Froyale-asjs.gitdata=02%7C01%7Caharui%40adobe.com%7C2ba16cc8f2674c5d5cc008d6f47583c6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636965182894920969sdata=Hp6LAoMXu11PUFmzN20wUMkP6Z9f5rGE%2Fh%2BvrHR6po4%3Dreserved=0


The following commit(s) were added to refs/heads/develop by this push:
 new 9c2d5ca  Adding a resizable load inicator.
9c2d5ca is described below

commit 9c2d5ca53ef0c67950ff76753f5f2834568de90a
Author: DESKTOP-RH4S838\Yishay 
AuthorDate: Wed Jun 19 08:16:50 2019 +0300

Adding a resizable load inicator.
---
 .../Basic/src/main/resources/basic-manifest.xml|  1 +
 .../apache/royale/html/beads/DisableLoaderBead.as  |  6 +-
 .../html/beads/ShrinkableDisableLoaderBead.as  | 87 
++
 3 files changed, 91 insertions(+), 3 deletions(-)

diff --git 
a/frameworks/projects/Basic/src/main/resources/basic-manifest.xml 
b/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
index a2239a7..284cf5c 100644
--- a/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
+++ b/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
@@ -161,6 +161,7 @@
 
 
 
+
 
 
 
diff --git 
a/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/beads/DisableLoaderBead.as
 
b/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/beads/DisableLoaderBead.as
index a233bdf..19ef75b 100644
--- 
a/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/beads/DisableLoaderBead.as
+++ 
b/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/beads/DisableLoaderBead.as
@@ -56,8 +56,8 @@ package org.apache.royale.html.beads
 {
 }

-   private var _strand:IStrand;
-   private var _loader:IUIBase;
+   protected var _strand:IStrand;
+   protected var _loader:IUIBase;

 /**
  *  @copy org.apache.royale.core.IBead#strand
@@ -85,7 +85,7 @@ package org.apache.royale.html.beads
 /**
  * @royaleignorecoercion org.apache.royale.core.IUIBase
  */
-   private function get host():IUIBase
+   protected function get host():IUIBase
 {
 return _strand as IUIBase;
 }
diff --git 
a/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/beads/ShrinkableDisableLoaderBead.as
 
b/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/beads/ShrinkableDisableLoaderBead.as
new file mode 100644
index 000..d0f697b
--- /dev/null
+++ 
b/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/beads/ShrinkableDisableLoaderBead.as
@@ -0,0 +1,87 @@

+
+//
+//  Licensed to the Apache Software Foundation (ASF) under one or more
+//  contributor license agreements.  See the NOTICE file distributed with
+//  this work for additional information regarding copyright ownership.
+//  The ASF licenses this file to You under the Apache License, Version 2.0
+//  (the "License"); you may not use this file except in compliance with
+//  the License.  You may obtain a copy of the License at
+//
+//  
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache.org%2Flicenses%2FLICENSE-2.0data=02%7C01%7Caharui%40adobe.com%7C2ba16cc8f2674c5d5cc008d6f47583c6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636965182894920969sdata=nNR5Vhcim4ONetL%2F%2Fcvj3uQVSGVd5Kfbsy%2BpGAtSPis%3Dreserved=0
+//
+//  Unless required by applicable law or agreed to in writing, software
+//  distributed under the License is distributed on an "AS IS" BASIS,
+//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 
implied.
+//  See the License for the specific language governing permissions and
+//  limitations under the License.
+//


Re: [MAVEN-BUILD] Royale-asjs - Build # 1920 - Still Failing

2019-06-19 Thread Piotr Zarzycki
Hi Carlos,

Jewel module is failing here. Did you notice that on your end ?

Thanks,
Piotr

śr., 19 cze 2019 o 08:35 Apache Jenkins Server 
napisał(a):

> The Apache Jenkins build system has built Royale-asjs (build #1920)
>
> Status: Still Failing
>
> Check console output at https://builds.apache.org/job/Royale-asjs/1920/
> to view the results.



-- 

Piotr Zarzycki

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


Re: [royale-asjs] branch develop updated: Adding a resizable load inicator.

2019-06-19 Thread Alex Harui
Yishay,

Are you still using 3rd party load indicators?  If so, I think the MIT License 
attribution is actually supposed to go in LICENSE not NOTICE.  See
http://www.apache.org/dev/licensing-howto.html#permissive-deps

Thanks,
-Alex

On 6/18/19, 10:18 PM, "yish...@apache.org"  wrote:

This is an automated email from the ASF dual-hosted git repository.

yishayw pushed a commit to branch develop
in repository 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitbox.apache.org%2Frepos%2Fasf%2Froyale-asjs.gitdata=02%7C01%7Caharui%40adobe.com%7C2ba16cc8f2674c5d5cc008d6f47583c6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636965182894920969sdata=Hp6LAoMXu11PUFmzN20wUMkP6Z9f5rGE%2Fh%2BvrHR6po4%3Dreserved=0


The following commit(s) were added to refs/heads/develop by this push:
 new 9c2d5ca  Adding a resizable load inicator.
9c2d5ca is described below

commit 9c2d5ca53ef0c67950ff76753f5f2834568de90a
Author: DESKTOP-RH4S838\Yishay 
AuthorDate: Wed Jun 19 08:16:50 2019 +0300

Adding a resizable load inicator.
---
 .../Basic/src/main/resources/basic-manifest.xml|  1 +
 .../apache/royale/html/beads/DisableLoaderBead.as  |  6 +-
 .../html/beads/ShrinkableDisableLoaderBead.as  | 87 
++
 3 files changed, 91 insertions(+), 3 deletions(-)

diff --git 
a/frameworks/projects/Basic/src/main/resources/basic-manifest.xml 
b/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
index a2239a7..284cf5c 100644
--- a/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
+++ b/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
@@ -161,6 +161,7 @@
 
 
 
+
 
 
 
diff --git 
a/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/beads/DisableLoaderBead.as
 
b/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/beads/DisableLoaderBead.as
index a233bdf..19ef75b 100644
--- 
a/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/beads/DisableLoaderBead.as
+++ 
b/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/beads/DisableLoaderBead.as
@@ -56,8 +56,8 @@ package org.apache.royale.html.beads
{
}

-   private var _strand:IStrand;
-   private var _loader:IUIBase;
+   protected var _strand:IStrand;
+   protected var _loader:IUIBase;
 
/**
 *  @copy org.apache.royale.core.IBead#strand
@@ -85,7 +85,7 @@ package org.apache.royale.html.beads
 /**
  * @royaleignorecoercion org.apache.royale.core.IUIBase
  */
-   private function get host():IUIBase
+   protected function get host():IUIBase
{
return _strand as IUIBase;
}
diff --git 
a/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/beads/ShrinkableDisableLoaderBead.as
 
b/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/beads/ShrinkableDisableLoaderBead.as
new file mode 100644
index 000..d0f697b
--- /dev/null
+++ 
b/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/beads/ShrinkableDisableLoaderBead.as
@@ -0,0 +1,87 @@

+
+//
+//  Licensed to the Apache Software Foundation (ASF) under one or more
+//  contributor license agreements.  See the NOTICE file distributed with
+//  this work for additional information regarding copyright ownership.
+//  The ASF licenses this file to You under the Apache License, Version 2.0
+//  (the "License"); you may not use this file except in compliance with
+//  the License.  You may obtain a copy of the License at
+//
+//  
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache.org%2Flicenses%2FLICENSE-2.0data=02%7C01%7Caharui%40adobe.com%7C2ba16cc8f2674c5d5cc008d6f47583c6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636965182894920969sdata=nNR5Vhcim4ONetL%2F%2Fcvj3uQVSGVd5Kfbsy%2BpGAtSPis%3Dreserved=0
+//
+//  Unless required by applicable law or agreed to in writing, software
+//  distributed under the License is distributed on an "AS IS" BASIS,
+//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 
implied.
+//  See the License for the specific language governing permissions and
+//  limitations under the License.
+//

+
+package org.apache.royale.html.beads
+{
+   import org.apache.royale.html.LoadIndicator;
+   import org.apache.royale.utils.PointUtils;
+   import org.apache.royale.core.IPopUpHost;
+   import