Build failed in Jenkins: royale-asjs #1236

See -- [...truncated 2.20 MB...] [mxmlc] using source file:

Build failed in Jenkins: royale-asjs #1235

See -- [...truncated 2.18 MB...] [mxmlc]

Build failed in Jenkins: royale-asjs #1234

See -- [...truncated 2.18 MB...] [mxmlc]

Build failed in Jenkins: royale-asjs #1233

See Changes: [carlosrovira] avoid listeners to remain when change dataProvider [carlosrovira] fix remove a row in table component [carlosrovira] fix update in table component ---

Build failed in Jenkins: royale-asjs #1232

See -- [...truncated 2.18 MB...] [mxmlc]

Build failed in Jenkins: royale-asjs #1231

See Changes: [carlosrovira] Fix remove and update renderers in List component [carlosrovira] preparing to fix remove and update in table component

Re: [Discuss] Start release process 0.9.3

Hi Piotr, the recommended way is to create a integration branch, moreover since MXRoyale has gone many time in its own way. Then solve conflicts in that branch until you see is stable and all is compiling and working fine as expected, then merge into develop the integration branch. Good luck! :)

Re: Possible compiler error

Thanks, while I don't really need this for now since I get other path I'll left this, since I don't get it working, but is good to know that is possible. Thanks for letting me know! :) El mar., 28 ago. 2018 a las 18:45, Alex Harui () escribió: > If ListView is in a different SWC and that SWC doe

Re: Build failed in Jenkins: royale-asjs #1227

Do you have time to go back to the previous config and see what happened ? wt., 28 sie 2018 o 18:57 Alex Harui napisał(a): > Hi Piotr, > > I'd have to go back to find the failures. This "policy file" issue I > think still shows up on occasion after I switched the builds with UI tests > to the a

Re: [Discuss] Start release process 0.9.3

Master and agent have their own root folders for projects. I think Agent is running in c:\Jenkins\workspace and master may be running in wherever APPDATA is pointing. In theory, royale-compiler and royale-typedefs should be able to be built off master, and the other builds should be able to u

Re: [Discuss] Start release process 0.9.3

You should not have to merge develop into feature/MXRoyale. I would discourage doing so as it could break Alina or me or anyone else using those nightlies. Try to merge from feature/MXRoyale to develop, deal with conflicts, then see if tourdeflex works. If it does, then you can claim success.

Re: Build failed in Jenkins: royale-asjs #1227

Hi Piotr, I'd have to go back to find the failures. This "policy file" issue I think still shows up on occasion after I switched the builds with UI tests to the agent. I'm not sure if the tests are still running or not. One possibility is to suppress that output in MustellaResultsParser and

Re: [Discuss] Start release process 0.9.3

If I would like to merge feature/MXRoyale to develop, should I first merge develop into that branch and than go back to the develop with the results ? Thanks, Piotr wt., 28 sie 2018 o 18:49 Piotr Zarzycki napisał(a): > I see failing mustellaresultsparser [1] [2] It's pointing for some > reason

Re: [Discuss] Start release process 0.9.3

I see failing mustellaresultsparser [1] [2] It's pointing for some reason to c:/jenkins/workspace instead those one in Program Files. How this path is appear there ? What actually is ${env.APPDATA} ? *[1] **https://github.com/apache/royale-asjs/blob/b060cbd9eb5e31932fe06cd35d4a72c86a6c6761/bui

Re: Possible compiler error

If ListView is in a different SWC and that SWC doesn't get re-compiled, you can run into this sort of problem. If ListView is in a different SWC, make sure that SWC does compile cleanly by examining the console output. I think I've seen some errors fail to rebuild the SWC but still report succ

Re: Possible compiler error

There’s a number of places in the framework where there’s overrides with parameters that default to null: ElementWrapper has: override public function addEventListener(type:String, handler:Function, opt_capture:Boolean = false, opt_handlerScope:Object = null):void TableLeafElement has:

Re: Possible compiler error

Hi, thanks for the responses, but maybe I didn't express right. I mean the superclass signature is in ListView protected function selectionChangeHandler(event:Event):void and I want to change it to have default "= null": protected function selectionChangeHandler(event:Event = null):void then ch

Build failed in Jenkins: royale-asjs #1230

See Changes: [carlosrovira] minor fixes to example -- [...truncated 2.18 MB...] [mxmlc]

Build failed in Jenkins: royale-asjs #1229

See Changes: [carlosrovira] make external change in ComboBox fire change event [carlosrovira] fix fiere change event in List when change selectedIndex or selectedItem ---

Build failed in Jenkins: royale-asjs #1228

See Changes: [carlosrovira] Improve ddl & cmb examples [carlosrovira] fix numeric stepper positioning for phone/tablets [carlosrovira] update jewel themes with new DropDownStyles ---

Re: Build failed in Jenkins: royale-asjs #1227

Alex, Above error was the cause why you have created new agent on Jenkins ? Thanks, Piotr wt., 28 sie 2018 o 13:11 napisał(a): > See < > http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/1227/display/redirect?page=changes > > > > Changes: > > [carlosrovira] add labelField t

Build failed in Jenkins: royale-asjs #1227

See Changes: [carlosrovira] add labelField to CombBox and improve examples -- [...truncated 2.20 MB...] [mxmlc] using source file:

Re: Possible compiler error

Hi Carlos, as Harbs mentioned, my experience is also, that implemented interface methods or overridden methods always has to be implemented with the entire same signature, including optional (default parameters) and required parameters. >From the AS3 docs regarding interfaces [1]: "You also have s

Re: Possible compiler error

I’m not sure why, but I think this is normal. (I think it’s a limitation in Flash.) To use a default, you need to have the superclass support default values as well. > On Aug 28, 2018, at 12:39 PM, Carlos Rovira wrote: > > I'm finding this error, and don't know if is a problem or not. > > I'

Possible compiler error

I'm finding this error, and don't know if is a problem or not. I'm introducing in this signature protected function selectionChangeHandler(event:Event):void a "= null" protected function selectionChangeHandler(event:Event = null):void And I get this error: Error: Incompatible override.

Re: [MAVEN-BUILD] Royale-compiler - Build # 479 - Failure

Maybe this dates are difficult. At least here in Spain, many people are on vacation period...but maybe this doesn't apply for the rest of zones El mar., 28 ago. 2018 a las 11:03, Piotr Zarzycki (< piotrzarzyck...@gmail.com>) escribió: > In general there some weird things happen on the https://bui

Re: [MAVEN-BUILD] Royale-compiler - Build # 479 - Failure

In general there some weird things happen on the https://builds.apache.org and I didn't get any answer to my email on users infra. I will wait probably max till the end of the week and raise jira for them. Thanks, Piotr wt., 28 sie 2018 o 10:54 Carlos Rovira napisał(a): > This fail is strange:

Re: [MAVEN-BUILD] Royale-compiler - Build # 479 - Failure

This fail is strange: [INFO] Reactor Summary: [INFO] [INFO] Apache Royale: Compiler: Parent 0.9.3-SNAPSHOT . FAILURE [05:02 min] [INFO] Apache Royale: Compiler: Compiler-Common ... SUCCESS [ 12.314 s] [INFO] Apache Royale: Compiler: Test Utils SUCCESS [ 6.598 s] [INFO

Re: Build failed in Jenkins: royale-asjs #1226

Guys, This fail is different than previous one. What should we do in that case ? Any idea ? Thanks, Piotr wt., 28 sie 2018 o 06:35 napisał(a): > See < > http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/1226/display/redirect > > > > -