Re: [Discuss] Start release process 0.9.3

[Piotr Zarzycki]

Hi Carlos,

Please do not move anything more. I think I had enough problems with
current situations. I will deal with all of that as is.

My suggestion is to restart discussion about all of that stuff after
release.

Thanks,
Piotr

On Fri, Aug 31, 2018, 12:18 AM Carlos Rovira 
wrote:

> Hi,
>
> as we discussed, the package names was the revert we said to do, so when we
> do a refactor of that package names, will be more consistent.
> Regarding movement of pieces, in the case of DataGroup I can move it from
> Core to Basic and create a version for Jewel.
> Let me know if this is ok for you.
>
> As well let me know if some more class is in Core to consider.
>
> Thanks
>
>
>
> El jue., 30 ago. 2018 a las 19:18, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > I was also thinking that this release won't have that changes, but
> > unfortunately they are there. I had big headache to make it working.
> >
> > Thank you Alex. I will try to deal with all of that.
> >
> > czw., 30 sie 2018 o 19:12 Alex Harui 
> > napisał(a):
> >
> > > I fixed the Maven build in feature/MXRoyale and merged it into the
> > > integration branch.  However, the Maven build in the integration branch
> > is
> > > still failing.  It appears to be because DataGroup got moved from Basic
> > to
> > > Core.  The Ant build should be failing there too.  I was under the
> > > impression that these sorts of changes were not going to be in this
> > > release.  Someone else will have to deal with resolving these issues.
> I
> > > don’t want to stop my other work to figure them out.
> > >
> > > Thanks,
> > > -Alex
> > >
> > > On 8/30/18, 9:08 AM, "Piotr Zarzycki" 
> > wrote:
> > >
> > > Great! Thanks Alex!
> > >
> > > czw., 30 sie 2018 o 18:05 Alex Harui 
> > > napisał(a):
> > >
> > > > I will fix the Maven build in feature/MXRoyale then you can pull
> > > those
> > > > changes into the integration branch.
> > > >
> > > > -Alex
> > > >
> > > > On 8/30/18, 7:42 AM, "Piotr Zarzycki"  >
> > > wrote:
> > > >
> > > > Hi Carlos,
> > > >
> > > > Nope. I build repo only using ANT. Do you know how to fix
> that
> > ?
> > > > Probably I
> > > > missed some conflicts, not sure why Maven complaining. :) If
> > you
> > > won't
> > > > have
> > > > time I will look into that tomorrow.
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > czw., 30 sie 2018 o 16:24 Carlos Rovira <
> > carlosrov...@apache.org
> > > >
> > > > napisał(a):
> > > >
> > > > > Hi Piotr,
> > > > >
> > > > > I switched to the feature/Merge_MXRoyale_To_Develop
> > > > > then try to pass maven and fails just at the begining
> > > > > I saw that has 2 rat check fails, so I fixed it
> > > > > but now I'm seeing more problems
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/Core/src/main/royale/org/apache/royale/html/supportClasses/DataGroup.as(39):
> > > > > col: 18 Error: interface method numItemRenderers in
> interface
> > > > > IItemRendererParent not implemented by class DataGroup
> > > > >
> > > > >
> > > > > public class DataGroup extends ContainerContentArea
> > > implements
> > > > > IItemRendererParent
> > > > >
> > > > >  ^
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/Core/src/main/royale/org/apache/royale/html/supportClasses/DataGroup.as(39):
> > > > > col: 18 interface method numItemRenderers in interface
> > > > IItemRendererParent
> > > > > not implemented by class DataGroup
> > > > >
> > > > >
> > > > > public class DataGroup extends ContainerContentArea
> > > implements
> > > > > IItemRendererParent
> > > > >
> > > > >  ^
> > > > >
> > > > >
> > > > > 1.666093134 seconds
> > > > >
> > > > > [*INFO*]
> > > > >
> > > >
> > >
> >
> **
> > > > >
> > > > > [*INFO*] *Reactor Summary:*
> > > > >
> > > > > [*INFO*]
> > > > >
> > > > > [*INFO*] Apache Royale: Framework: Parent 0.9.3-SNAPSHOT
> 
> > > > *SUCCESS* [
> > > > > 2.164 s]
> > > > >
> > > > > [*INFO*] Apache Royale: Framework
> ...
> > > > *SUCCESS* [
> > > > > 0.273 s]
> > > > >
> > > > > [*INFO*] Apache Royale: Framework: Fonts
> 
> > > > *SUCCESS* [
> > > > > 1.175 s]
> > > > >
> > > > > [*INFO*] Apache Royale: Framework: Libs
> 

RE: WORK ON EMULATION

[Pushmina Kazi]

Hi,
I am using 
Error:  " Internal problem during semantic analysis of MXML"

Thanks in Advance
 Pashmina kazi

-Original Message-
From: Alex Harui [mailto:aha...@adobe.com.INVALID] 
Sent: Wednesday, August 29, 2018 9:18 PM
To: dev@royale.apache.org
Subject: Re: WORK ON EMULATION

Hi Pashmina,

describeType is a "Reflection API".  If your application is using it, instead 
of directly emulating it, it is better to try to understand why you needed to 
use it in the first place and modify that code.  What does that function do 
with the describeType XML?  There might be a better way to write that code.

Thanks,
-Alex

On 8/29/18, 4:06 AM, "Pushmina Kazi"  wrote:


Hi,
i am using describetype(customVO) and passing it as a parameter in a 
function
added import of describeType but still error occurs
ERROR: "Implicit coercion of a value of type TypeDefinition to an unrelated 
type XML".

Thanks in Advance
Pashmina kazi






-Original Message-
From: Yishay Weiss [mailto:yishayj...@hotmail.com] 
Sent: Tuesday, August 14, 2018 9:57 AM
To: us...@royale.apache.org; dev@royale.apache.org
Subject: RE: WORK ON EMULATION

There’s an example here [1]



[1] 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fyishayw%2FExamples%2Fblob%2FFileProxy%2FExamples.mxmldata=02%7C01%7Caharui%40adobe.com%7Ccc5c1dd1dd1f4c65f04908d60d9f6e2f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636711375728607957sdata=1wIBNayZSctR69trQG9YuhwFt0n6OhOu1w0x%2Flhn6tA%3Dreserved=0




From: Alex Harui 
Sent: Monday, August 13, 2018 6:48:50 PM
To: us...@royale.apache.org; dev@royale.apache.org
Subject: Re: WORK ON EMULATION

Hi Alina,

There is a bead called org.apache.royale.file.beads.FileBrowser.  I can't 
find any examples of use.  Looks like Yishay wrote it so maybe he can help.

There is also a class called 
Network/src/main/royale/org/apache/royale/net/URLBinaryUploader.as you might be 
able to use.

If you only have a few references to FileReference in your code, it is 
probably simpler to change your code to use these classes, otherwise you can 
try to write some emulation class that tries to present the FileReference API.

HTH,
-Alex

On 8/13/18, 2:19 AM, "Alina Kazi"  wrote:

Thanks Alex.
We are using Flash.net.FileReference in our Application
Methods and properties of FileReference are used:
loadFileRef.load();
loadFileRef.browse();
loadFileRef.name;
loadFileRef.data;

Do we have any alternate for this class in Apache Royale?

-Alina

-Original Message-
From: Alex Harui [mailto:aha...@adobe.com.INVALID]
Sent: Friday, August 10, 2018 8:46 PM
To: dev@royale.apache.org; us...@royale.apache.org
Subject: Re: WORK ON EMULATION

Hi Alina,

What is being loaded?  Flex apps should be using mx.controls.SWFLoader, 
mx.modules.ModuleLoader and mx.controls.Image (or their Spark equivalents) and 
not flash.display.Loader directly.  It would be better to change your 
application to not use flash.display.Loader unless there are lots of instances 
of using it.

-Alex

On 8/10/18, 2:27 AM, "Alina Kazi"  wrote:

Hi Alex,



flash.display.Loader

flash.display.Loader:content

flash.display.Loader:contentLoaderInfo

flash.display.Loader:height

flash.display.Loader:load

flash.display.Loader:loadBytes

flash.display.Loader:mask

flash.display.Loader:width

flash.display.Loader:x

flash.display.Loader:y



These properties and methods of API Loader are used.

Should I create mx Emulation for Loader?



Regards,

Alina Kazi

Re: [Discuss] Start release process 0.9.3

[Carlos Rovira]

Hi,

as we discussed, the package names was the revert we said to do, so when we
do a refactor of that package names, will be more consistent.
Regarding movement of pieces, in the case of DataGroup I can move it from
Core to Basic and create a version for Jewel.
Let me know if this is ok for you.

As well let me know if some more class is in Core to consider.

Thanks



El jue., 30 ago. 2018 a las 19:18, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> I was also thinking that this release won't have that changes, but
> unfortunately they are there. I had big headache to make it working.
>
> Thank you Alex. I will try to deal with all of that.
>
> czw., 30 sie 2018 o 19:12 Alex Harui 
> napisał(a):
>
> > I fixed the Maven build in feature/MXRoyale and merged it into the
> > integration branch.  However, the Maven build in the integration branch
> is
> > still failing.  It appears to be because DataGroup got moved from Basic
> to
> > Core.  The Ant build should be failing there too.  I was under the
> > impression that these sorts of changes were not going to be in this
> > release.  Someone else will have to deal with resolving these issues.  I
> > don’t want to stop my other work to figure them out.
> >
> > Thanks,
> > -Alex
> >
> > On 8/30/18, 9:08 AM, "Piotr Zarzycki" 
> wrote:
> >
> > Great! Thanks Alex!
> >
> > czw., 30 sie 2018 o 18:05 Alex Harui 
> > napisał(a):
> >
> > > I will fix the Maven build in feature/MXRoyale then you can pull
> > those
> > > changes into the integration branch.
> > >
> > > -Alex
> > >
> > > On 8/30/18, 7:42 AM, "Piotr Zarzycki" 
> > wrote:
> > >
> > > Hi Carlos,
> > >
> > > Nope. I build repo only using ANT. Do you know how to fix that
> ?
> > > Probably I
> > > missed some conflicts, not sure why Maven complaining. :) If
> you
> > won't
> > > have
> > > time I will look into that tomorrow.
> > >
> > > Thanks,
> > > Piotr
> > >
> > > czw., 30 sie 2018 o 16:24 Carlos Rovira <
> carlosrov...@apache.org
> > >
> > > napisał(a):
> > >
> > > > Hi Piotr,
> > > >
> > > > I switched to the feature/Merge_MXRoyale_To_Develop
> > > > then try to pass maven and fails just at the begining
> > > > I saw that has 2 rat check fails, so I fixed it
> > > > but now I'm seeing more problems
> > > >
> > > >
> > > >
> > > >
> > >
> >
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/Core/src/main/royale/org/apache/royale/html/supportClasses/DataGroup.as(39):
> > > > col: 18 Error: interface method numItemRenderers in interface
> > > > IItemRendererParent not implemented by class DataGroup
> > > >
> > > >
> > > > public class DataGroup extends ContainerContentArea
> > implements
> > > > IItemRendererParent
> > > >
> > > >  ^
> > > >
> > > >
> > > >
> > > >
> > >
> >
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/Core/src/main/royale/org/apache/royale/html/supportClasses/DataGroup.as(39):
> > > > col: 18 interface method numItemRenderers in interface
> > > IItemRendererParent
> > > > not implemented by class DataGroup
> > > >
> > > >
> > > > public class DataGroup extends ContainerContentArea
> > implements
> > > > IItemRendererParent
> > > >
> > > >  ^
> > > >
> > > >
> > > > 1.666093134 seconds
> > > >
> > > > [*INFO*]
> > > >
> > >
> >
> **
> > > >
> > > > [*INFO*] *Reactor Summary:*
> > > >
> > > > [*INFO*]
> > > >
> > > > [*INFO*] Apache Royale: Framework: Parent 0.9.3-SNAPSHOT 
> > > *SUCCESS* [
> > > > 2.164 s]
> > > >
> > > > [*INFO*] Apache Royale: Framework ...
> > > *SUCCESS* [
> > > > 0.273 s]
> > > >
> > > > [*INFO*] Apache Royale: Framework: Fonts 
> > > *SUCCESS* [
> > > > 1.175 s]
> > > >
> > > > [*INFO*] Apache Royale: Framework: Libs .
> > > *SUCCESS* [
> > > > 0.691 s]
> > > >
> > > > [*INFO*] Apache Royale: Framework: Libs: Core ...
> > > *FAILURE* [
> > > > 1.947 s]
> > > >
> > > > [*INFO*] Apache Royale: Framework: Libs: Binding 
> > > *SKIPPED*
> > > >
> > > > So I'm a bit confused. I thought the branch was compiling and
> > tested
> > > to
> > > > some point, but it seems that conflicts are still unsolved.
> > > >
> > > > For example in this error, seems MXRoyale 

Jenkins build is back to normal : Royale-asjs_MXRoyale #96

[apacheroyaleci]

See 

Re: [Discuss] Start release process 0.9.3

[Piotr Zarzycki]

I was also thinking that this release won't have that changes, but
unfortunately they are there. I had big headache to make it working.

Thank you Alex. I will try to deal with all of that.

czw., 30 sie 2018 o 19:12 Alex Harui  napisał(a):

> I fixed the Maven build in feature/MXRoyale and merged it into the
> integration branch.  However, the Maven build in the integration branch is
> still failing.  It appears to be because DataGroup got moved from Basic to
> Core.  The Ant build should be failing there too.  I was under the
> impression that these sorts of changes were not going to be in this
> release.  Someone else will have to deal with resolving these issues.  I
> don’t want to stop my other work to figure them out.
>
> Thanks,
> -Alex
>
> On 8/30/18, 9:08 AM, "Piotr Zarzycki"  wrote:
>
> Great! Thanks Alex!
>
> czw., 30 sie 2018 o 18:05 Alex Harui 
> napisał(a):
>
> > I will fix the Maven build in feature/MXRoyale then you can pull
> those
> > changes into the integration branch.
> >
> > -Alex
> >
> > On 8/30/18, 7:42 AM, "Piotr Zarzycki" 
> wrote:
> >
> > Hi Carlos,
> >
> > Nope. I build repo only using ANT. Do you know how to fix that ?
> > Probably I
> > missed some conflicts, not sure why Maven complaining. :) If you
> won't
> > have
> > time I will look into that tomorrow.
> >
> > Thanks,
> > Piotr
> >
> > czw., 30 sie 2018 o 16:24 Carlos Rovira  >
> > napisał(a):
> >
> > > Hi Piotr,
> > >
> > > I switched to the feature/Merge_MXRoyale_To_Develop
> > > then try to pass maven and fails just at the begining
> > > I saw that has 2 rat check fails, so I fixed it
> > > but now I'm seeing more problems
> > >
> > >
> > >
> > >
> >
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/Core/src/main/royale/org/apache/royale/html/supportClasses/DataGroup.as(39):
> > > col: 18 Error: interface method numItemRenderers in interface
> > > IItemRendererParent not implemented by class DataGroup
> > >
> > >
> > > public class DataGroup extends ContainerContentArea
> implements
> > > IItemRendererParent
> > >
> > >  ^
> > >
> > >
> > >
> > >
> >
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/Core/src/main/royale/org/apache/royale/html/supportClasses/DataGroup.as(39):
> > > col: 18 interface method numItemRenderers in interface
> > IItemRendererParent
> > > not implemented by class DataGroup
> > >
> > >
> > > public class DataGroup extends ContainerContentArea
> implements
> > > IItemRendererParent
> > >
> > >  ^
> > >
> > >
> > > 1.666093134 seconds
> > >
> > > [*INFO*]
> > >
> >
> **
> > >
> > > [*INFO*] *Reactor Summary:*
> > >
> > > [*INFO*]
> > >
> > > [*INFO*] Apache Royale: Framework: Parent 0.9.3-SNAPSHOT 
> > *SUCCESS* [
> > > 2.164 s]
> > >
> > > [*INFO*] Apache Royale: Framework ...
> > *SUCCESS* [
> > > 0.273 s]
> > >
> > > [*INFO*] Apache Royale: Framework: Fonts 
> > *SUCCESS* [
> > > 1.175 s]
> > >
> > > [*INFO*] Apache Royale: Framework: Libs .
> > *SUCCESS* [
> > > 0.691 s]
> > >
> > > [*INFO*] Apache Royale: Framework: Libs: Core ...
> > *FAILURE* [
> > > 1.947 s]
> > >
> > > [*INFO*] Apache Royale: Framework: Libs: Binding 
> > *SKIPPED*
> > >
> > > So I'm a bit confused. I thought the branch was compiling and
> tested
> > to
> > > some point, but it seems that conflicts are still unsolved.
> > >
> > > For example in this error, seems MXRoyale introduced some MX
> API
> > that is
> > > not in Royale core classes until now, so it needs to add it.
> For now
> > it
> > > only reports this fails, but maybe when it reach Basic library
> it
> > could be
> > > much more than that...so my question is, did you try to
> compile with
> > maven
> > > the branch? if so did you find this problems?
> > >
> > > Or maybe I'm missing something?
> > >
> > > Let me know in order to know how to operate. I'll return to my
> Jewel
> > duties
> > > in the meanwhile
> > >
> > > Thanks!
> > > Carlos
> > >
> > >
> > >
> > >
> > >
> > > El jue., 30 ago. 2018 a las 

Re: [Discuss] Start release process 0.9.3

[Alex Harui]

I fixed the Maven build in feature/MXRoyale and merged it into the integration 
branch.  However, the Maven build in the integration branch is still failing.  
It appears to be because DataGroup got moved from Basic to Core.  The Ant build 
should be failing there too.  I was under the impression that these sorts of 
changes were not going to be in this release.  Someone else will have to deal 
with resolving these issues.  I don’t want to stop my other work to figure them 
out.

Thanks,
-Alex

On 8/30/18, 9:08 AM, "Piotr Zarzycki"  wrote:

Great! Thanks Alex!

czw., 30 sie 2018 o 18:05 Alex Harui  napisał(a):

> I will fix the Maven build in feature/MXRoyale then you can pull those
> changes into the integration branch.
>
> -Alex
>
> On 8/30/18, 7:42 AM, "Piotr Zarzycki"  wrote:
>
> Hi Carlos,
>
> Nope. I build repo only using ANT. Do you know how to fix that ?
> Probably I
> missed some conflicts, not sure why Maven complaining. :) If you won't
> have
> time I will look into that tomorrow.
>
> Thanks,
> Piotr
>
> czw., 30 sie 2018 o 16:24 Carlos Rovira 
> napisał(a):
>
> > Hi Piotr,
> >
> > I switched to the feature/Merge_MXRoyale_To_Develop
> > then try to pass maven and fails just at the begining
> > I saw that has 2 rat check fails, so I fixed it
> > but now I'm seeing more problems
> >
> >
> >
> >
> 
/Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/Core/src/main/royale/org/apache/royale/html/supportClasses/DataGroup.as(39):
> > col: 18 Error: interface method numItemRenderers in interface
> > IItemRendererParent not implemented by class DataGroup
> >
> >
> > public class DataGroup extends ContainerContentArea implements
> > IItemRendererParent
> >
> >  ^
> >
> >
> >
> >
> 
/Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/Core/src/main/royale/org/apache/royale/html/supportClasses/DataGroup.as(39):
> > col: 18 interface method numItemRenderers in interface
> IItemRendererParent
> > not implemented by class DataGroup
> >
> >
> > public class DataGroup extends ContainerContentArea implements
> > IItemRendererParent
> >
> >  ^
> >
> >
> > 1.666093134 seconds
> >
> > [*INFO*]
> >
> **
> >
> > [*INFO*] *Reactor Summary:*
> >
> > [*INFO*]
> >
> > [*INFO*] Apache Royale: Framework: Parent 0.9.3-SNAPSHOT 
> *SUCCESS* [
> > 2.164 s]
> >
> > [*INFO*] Apache Royale: Framework ...
> *SUCCESS* [
> > 0.273 s]
> >
> > [*INFO*] Apache Royale: Framework: Fonts 
> *SUCCESS* [
> > 1.175 s]
> >
> > [*INFO*] Apache Royale: Framework: Libs .
> *SUCCESS* [
> > 0.691 s]
> >
> > [*INFO*] Apache Royale: Framework: Libs: Core ...
> *FAILURE* [
> > 1.947 s]
> >
> > [*INFO*] Apache Royale: Framework: Libs: Binding 
> *SKIPPED*
> >
> > So I'm a bit confused. I thought the branch was compiling and tested
> to
> > some point, but it seems that conflicts are still unsolved.
> >
> > For example in this error, seems MXRoyale introduced some MX API
> that is
> > not in Royale core classes until now, so it needs to add it. For now
> it
> > only reports this fails, but maybe when it reach Basic library it
> could be
> > much more than that...so my question is, did you try to compile with
> maven
> > the branch? if so did you find this problems?
> >
> > Or maybe I'm missing something?
> >
> > Let me know in order to know how to operate. I'll return to my Jewel
> duties
> > in the meanwhile
> >
> > Thanks!
> > Carlos
> >
> >
> >
> >
> >
> > El jue., 30 ago. 2018 a las 16:04, Carlos Rovira (<
> carlosrov...@apache.org
> > >)
> > escribió:
> >
> > > Hi Piotr,
> > >
> > > of course, I'll try all Jewel examples and report if I find some
> isuue.
> > > Thanks!
> > >
> > > El jue., 30 ago. 2018 a las 15:33, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>) escribió:
> > >
> > >> Hi Alina,
> > >>
> > >> I'm working on preparation to release next version of Royale. 

Re: [Discuss] Start release process 0.9.3

[Piotr Zarzycki]

Great! Thanks Alex!

czw., 30 sie 2018 o 18:05 Alex Harui  napisał(a):

> I will fix the Maven build in feature/MXRoyale then you can pull those
> changes into the integration branch.
>
> -Alex
>
> On 8/30/18, 7:42 AM, "Piotr Zarzycki"  wrote:
>
> Hi Carlos,
>
> Nope. I build repo only using ANT. Do you know how to fix that ?
> Probably I
> missed some conflicts, not sure why Maven complaining. :) If you won't
> have
> time I will look into that tomorrow.
>
> Thanks,
> Piotr
>
> czw., 30 sie 2018 o 16:24 Carlos Rovira 
> napisał(a):
>
> > Hi Piotr,
> >
> > I switched to the feature/Merge_MXRoyale_To_Develop
> > then try to pass maven and fails just at the begining
> > I saw that has 2 rat check fails, so I fixed it
> > but now I'm seeing more problems
> >
> >
> >
> >
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/Core/src/main/royale/org/apache/royale/html/supportClasses/DataGroup.as(39):
> > col: 18 Error: interface method numItemRenderers in interface
> > IItemRendererParent not implemented by class DataGroup
> >
> >
> > public class DataGroup extends ContainerContentArea implements
> > IItemRendererParent
> >
> >  ^
> >
> >
> >
> >
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/Core/src/main/royale/org/apache/royale/html/supportClasses/DataGroup.as(39):
> > col: 18 interface method numItemRenderers in interface
> IItemRendererParent
> > not implemented by class DataGroup
> >
> >
> > public class DataGroup extends ContainerContentArea implements
> > IItemRendererParent
> >
> >  ^
> >
> >
> > 1.666093134 seconds
> >
> > [*INFO*]
> >
> **
> >
> > [*INFO*] *Reactor Summary:*
> >
> > [*INFO*]
> >
> > [*INFO*] Apache Royale: Framework: Parent 0.9.3-SNAPSHOT 
> *SUCCESS* [
> > 2.164 s]
> >
> > [*INFO*] Apache Royale: Framework ...
> *SUCCESS* [
> > 0.273 s]
> >
> > [*INFO*] Apache Royale: Framework: Fonts 
> *SUCCESS* [
> > 1.175 s]
> >
> > [*INFO*] Apache Royale: Framework: Libs .
> *SUCCESS* [
> > 0.691 s]
> >
> > [*INFO*] Apache Royale: Framework: Libs: Core ...
> *FAILURE* [
> > 1.947 s]
> >
> > [*INFO*] Apache Royale: Framework: Libs: Binding 
> *SKIPPED*
> >
> > So I'm a bit confused. I thought the branch was compiling and tested
> to
> > some point, but it seems that conflicts are still unsolved.
> >
> > For example in this error, seems MXRoyale introduced some MX API
> that is
> > not in Royale core classes until now, so it needs to add it. For now
> it
> > only reports this fails, but maybe when it reach Basic library it
> could be
> > much more than that...so my question is, did you try to compile with
> maven
> > the branch? if so did you find this problems?
> >
> > Or maybe I'm missing something?
> >
> > Let me know in order to know how to operate. I'll return to my Jewel
> duties
> > in the meanwhile
> >
> > Thanks!
> > Carlos
> >
> >
> >
> >
> >
> > El jue., 30 ago. 2018 a las 16:04, Carlos Rovira (<
> carlosrov...@apache.org
> > >)
> > escribió:
> >
> > > Hi Piotr,
> > >
> > > of course, I'll try all Jewel examples and report if I find some
> isuue.
> > > Thanks!
> > >
> > > El jue., 30 ago. 2018 a las 15:33, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>) escribió:
> > >
> > >> Hi Alina,
> > >>
> > >> I'm working on preparation to release next version of Royale. One
> of the
> > >> steps were to merge everything what is in MXRoyale branch to
> develop. I
> > >> just finished it and everything what was in MXRoyale and develop
> now is
> > >> being merged to special branch feature/Merge_MXRoyale_To_Develop.
> > >>
> > >> Before I merge all that stuff back to develop I would like to ask
> you to
> > >> switch to that branch and test on your end - whether I didn't
> break any
> > of
> > >> your stuff. Is something is being missed - please make changes and
> > commit
> > >> to that branch.
> > >>
> > >> Hi Carlos,
> > >>
> > >> Can you switch to that branch as well and test some Jewel
> examples ?
> > >>
> > >> I will try to build Tour De Flex tomorrow to see what is happen.
> > >>
> > >> Thanks,
> > >> Piotr
> > >>
> > >> wt., 28 sie 2018 o 19:18 Carlos Rovira 
> > >> napisał(a):
> > >>
> > >> > Hi Piotr,
> > >> >
> > >> > the recommended way is to create a integration branch, moreover
> since
> > >> > MXRoyale has gone many time in its 

Re: [Discuss] Start release process 0.9.3

[Piotr Zarzycki]

Hi Carlos,

Nope. I build repo only using ANT. Do you know how to fix that ? Probably I
missed some conflicts, not sure why Maven complaining. :) If you won't have
time I will look into that tomorrow.

Thanks,
Piotr

czw., 30 sie 2018 o 16:24 Carlos Rovira 
napisał(a):

> Hi Piotr,
>
> I switched to the feature/Merge_MXRoyale_To_Develop
> then try to pass maven and fails just at the begining
> I saw that has 2 rat check fails, so I fixed it
> but now I'm seeing more problems
>
>
>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/Core/src/main/royale/org/apache/royale/html/supportClasses/DataGroup.as(39):
> col: 18 Error: interface method numItemRenderers in interface
> IItemRendererParent not implemented by class DataGroup
>
>
> public class DataGroup extends ContainerContentArea implements
> IItemRendererParent
>
>  ^
>
>
>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/Core/src/main/royale/org/apache/royale/html/supportClasses/DataGroup.as(39):
> col: 18 interface method numItemRenderers in interface IItemRendererParent
> not implemented by class DataGroup
>
>
> public class DataGroup extends ContainerContentArea implements
> IItemRendererParent
>
>  ^
>
>
> 1.666093134 seconds
>
> [*INFO*]
> **
>
> [*INFO*] *Reactor Summary:*
>
> [*INFO*]
>
> [*INFO*] Apache Royale: Framework: Parent 0.9.3-SNAPSHOT  *SUCCESS* [
> 2.164 s]
>
> [*INFO*] Apache Royale: Framework ... *SUCCESS* [
> 0.273 s]
>
> [*INFO*] Apache Royale: Framework: Fonts  *SUCCESS* [
> 1.175 s]
>
> [*INFO*] Apache Royale: Framework: Libs . *SUCCESS* [
> 0.691 s]
>
> [*INFO*] Apache Royale: Framework: Libs: Core ... *FAILURE* [
> 1.947 s]
>
> [*INFO*] Apache Royale: Framework: Libs: Binding  *SKIPPED*
>
> So I'm a bit confused. I thought the branch was compiling and tested to
> some point, but it seems that conflicts are still unsolved.
>
> For example in this error, seems MXRoyale introduced some MX API that is
> not in Royale core classes until now, so it needs to add it. For now it
> only reports this fails, but maybe when it reach Basic library it could be
> much more than that...so my question is, did you try to compile with maven
> the branch? if so did you find this problems?
>
> Or maybe I'm missing something?
>
> Let me know in order to know how to operate. I'll return to my Jewel duties
> in the meanwhile
>
> Thanks!
> Carlos
>
>
>
>
>
> El jue., 30 ago. 2018 a las 16:04, Carlos Rovira ( >)
> escribió:
>
> > Hi Piotr,
> >
> > of course, I'll try all Jewel examples and report if I find some isuue.
> > Thanks!
> >
> > El jue., 30 ago. 2018 a las 15:33, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>) escribió:
> >
> >> Hi Alina,
> >>
> >> I'm working on preparation to release next version of Royale. One of the
> >> steps were to merge everything what is in MXRoyale branch to develop. I
> >> just finished it and everything what was in MXRoyale and develop now is
> >> being merged to special branch feature/Merge_MXRoyale_To_Develop.
> >>
> >> Before I merge all that stuff back to develop I would like to ask you to
> >> switch to that branch and test on your end - whether I didn't break any
> of
> >> your stuff. Is something is being missed - please make changes and
> commit
> >> to that branch.
> >>
> >> Hi Carlos,
> >>
> >> Can you switch to that branch as well and test some Jewel examples ?
> >>
> >> I will try to build Tour De Flex tomorrow to see what is happen.
> >>
> >> Thanks,
> >> Piotr
> >>
> >> wt., 28 sie 2018 o 19:18 Carlos Rovira 
> >> napisał(a):
> >>
> >> > 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! :)
> >> >
> >> > Carlos
> >> >
> >> >
> >> > El mar., 28 ago. 2018 a las 19:00, Alex Harui
> ( >> >)
> >> > escribió:
> >> >
> >> > > 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 use Ant variables to point to the results of those builds.  If
> you
> >> > want
> >> > > to try switching everything off master to the agent that's fine as
> >> well.
> >> > > For me, there were some builds that would not run on master.
> >> > >
> >> > > HTH,
> >> > > -Alex
> >> > >
> >> > > On 8/28/18, 9:50 AM, "Piotr Zarzycki" 
> >> > wrote:
> >> > >
> >> > > I see failing mustellaresultsparser [1]  

Re: [Discuss] Start release process 0.9.3

[Carlos Rovira]

Hi Piotr,

I switched to the feature/Merge_MXRoyale_To_Develop
then try to pass maven and fails just at the begining
I saw that has 2 rat check fails, so I fixed it
but now I'm seeing more problems


/Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/Core/src/main/royale/org/apache/royale/html/supportClasses/DataGroup.as(39):
col: 18 Error: interface method numItemRenderers in interface
IItemRendererParent not implemented by class DataGroup


public class DataGroup extends ContainerContentArea implements
IItemRendererParent

 ^


/Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/Core/src/main/royale/org/apache/royale/html/supportClasses/DataGroup.as(39):
col: 18 interface method numItemRenderers in interface IItemRendererParent
not implemented by class DataGroup


public class DataGroup extends ContainerContentArea implements
IItemRendererParent

 ^


1.666093134 seconds

[*INFO*]
**

[*INFO*] *Reactor Summary:*

[*INFO*]

[*INFO*] Apache Royale: Framework: Parent 0.9.3-SNAPSHOT  *SUCCESS* [
2.164 s]

[*INFO*] Apache Royale: Framework ... *SUCCESS* [
0.273 s]

[*INFO*] Apache Royale: Framework: Fonts  *SUCCESS* [
1.175 s]

[*INFO*] Apache Royale: Framework: Libs . *SUCCESS* [
0.691 s]

[*INFO*] Apache Royale: Framework: Libs: Core ... *FAILURE* [
1.947 s]

[*INFO*] Apache Royale: Framework: Libs: Binding  *SKIPPED*

So I'm a bit confused. I thought the branch was compiling and tested to
some point, but it seems that conflicts are still unsolved.

For example in this error, seems MXRoyale introduced some MX API that is
not in Royale core classes until now, so it needs to add it. For now it
only reports this fails, but maybe when it reach Basic library it could be
much more than that...so my question is, did you try to compile with maven
the branch? if so did you find this problems?

Or maybe I'm missing something?

Let me know in order to know how to operate. I'll return to my Jewel duties
in the meanwhile

Thanks!
Carlos





El jue., 30 ago. 2018 a las 16:04, Carlos Rovira ()
escribió:

> Hi Piotr,
>
> of course, I'll try all Jewel examples and report if I find some isuue.
> Thanks!
>
> El jue., 30 ago. 2018 a las 15:33, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
>> Hi Alina,
>>
>> I'm working on preparation to release next version of Royale. One of the
>> steps were to merge everything what is in MXRoyale branch to develop. I
>> just finished it and everything what was in MXRoyale and develop now is
>> being merged to special branch feature/Merge_MXRoyale_To_Develop.
>>
>> Before I merge all that stuff back to develop I would like to ask you to
>> switch to that branch and test on your end - whether I didn't break any of
>> your stuff. Is something is being missed - please make changes and commit
>> to that branch.
>>
>> Hi Carlos,
>>
>> Can you switch to that branch as well and test some Jewel examples ?
>>
>> I will try to build Tour De Flex tomorrow to see what is happen.
>>
>> Thanks,
>> Piotr
>>
>> wt., 28 sie 2018 o 19:18 Carlos Rovira 
>> napisał(a):
>>
>> > 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! :)
>> >
>> > Carlos
>> >
>> >
>> > El mar., 28 ago. 2018 a las 19:00, Alex Harui (> >)
>> > escribió:
>> >
>> > > 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 use Ant variables to point to the results of those builds.  If you
>> > want
>> > > to try switching everything off master to the agent that's fine as
>> well.
>> > > For me, there were some builds that would not run on master.
>> > >
>> > > HTH,
>> > > -Alex
>> > >
>> > > On 8/28/18, 9:50 AM, "Piotr Zarzycki" 
>> > wrote:
>> > >
>> > > 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] **
>> > >
>> >
>> 

Re: [Discuss] Start release process 0.9.3

[Carlos Rovira]

Hi Piotr,

of course, I'll try all Jewel examples and report if I find some isuue.
Thanks!

El jue., 30 ago. 2018 a las 15:33, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> Hi Alina,
>
> I'm working on preparation to release next version of Royale. One of the
> steps were to merge everything what is in MXRoyale branch to develop. I
> just finished it and everything what was in MXRoyale and develop now is
> being merged to special branch feature/Merge_MXRoyale_To_Develop.
>
> Before I merge all that stuff back to develop I would like to ask you to
> switch to that branch and test on your end - whether I didn't break any of
> your stuff. Is something is being missed - please make changes and commit
> to that branch.
>
> Hi Carlos,
>
> Can you switch to that branch as well and test some Jewel examples ?
>
> I will try to build Tour De Flex tomorrow to see what is happen.
>
> Thanks,
> Piotr
>
> wt., 28 sie 2018 o 19:18 Carlos Rovira 
> napisał(a):
>
> > 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! :)
> >
> > Carlos
> >
> >
> > El mar., 28 ago. 2018 a las 19:00, Alex Harui ( >)
> > escribió:
> >
> > > 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 use Ant variables to point to the results of those builds.  If you
> > want
> > > to try switching everything off master to the agent that's fine as
> well.
> > > For me, there were some builds that would not run on master.
> > >
> > > HTH,
> > > -Alex
> > >
> > > On 8/28/18, 9:50 AM, "Piotr Zarzycki" 
> > wrote:
> > >
> > > 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://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fblob%2Fb060cbd9eb5e31932fe06cd35d4a72c86a6c6761%2Fbuild.xml%23L1510data=02%7C01%7Caharui%40adobe.com%7C114873bb0d0b47b418a008d60d064c6a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636710718037802929sdata=wX%2FF0p6jMtHpXCMsJnU82PFjtj%2BiFiHDxvShYcwS1Z8%3Dreserved=0
> > > <
> > >
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fblob%2Fb060cbd9eb5e31932fe06cd35d4a72c86a6c6761%2Fbuild.xml%23L1510data=02%7C01%7Caharui%40adobe.com%7C114873bb0d0b47b418a008d60d064c6a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636710718037802929sdata=wX%2FF0p6jMtHpXCMsJnU82PFjtj%2BiFiHDxvShYcwS1Z8%3Dreserved=0
> > > >*
> > > *[2]
> > >
> >
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs%2F1230%2FconsoleFulldata=02%7C01%7Caharui%40adobe.com%7C114873bb0d0b47b418a008d60d064c6a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636710718037802929sdata=Wr4WNLn8NvWJ2JMcefbaDDZykIIwmteio5UZP5IiBOw%3Dreserved=0
> > > <
> > >
> >
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs%2F1230%2FconsoleFulldata=02%7C01%7Caharui%40adobe.com%7C114873bb0d0b47b418a008d60d064c6a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636710718037812939sdata=NSZo2r9I6zZhqSkY1PAQxhKOD9dTQbJcmYCl8%2FXARYM%3Dreserved=0
> > > >*
> > >
> > > *Thanks,*
> > > *Piotr*
> > >
> > > pon., 27 sie 2018 o 20:18 Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> > > napisał(a):
> > >
> > > > Hi Harbs,
> > > >
> > > > Please give me some sign here once you will be done with all your
> > > changes!
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > pon., 27 sie 2018 o 20:12 Harbs 
> > napisał(a):
> > > >
> > > >> I have found that there’s an error with ACE on multiple
> machines.
> > I
> > > was
> > > >> only able to get it to build by first running ant on the
> typedefs
> > > repo and
> > > >> then the asjs repo succeeded.
> > > >>
> > > >> On my Mac, it worked fine, so I’m not really sure what triggered
> > the
> > > >> problem.
> > > >>
> > > >> Maybe this is related to the failures on apacheroyaleci? Dunno…
> > > >>
> > > >> I plan on making sure the current develop branch works for me
> and
> > > fixing
> > > >> any issues that might crop up in the next couple of days.
> > > >>
> > > >> There is also some code which needs to be cherry-picked 

Re: [Discuss] Start release process 0.9.3

[Piotr Zarzycki]

Hi Alina,

I'm working on preparation to release next version of Royale. One of the
steps were to merge everything what is in MXRoyale branch to develop. I
just finished it and everything what was in MXRoyale and develop now is
being merged to special branch feature/Merge_MXRoyale_To_Develop.

Before I merge all that stuff back to develop I would like to ask you to
switch to that branch and test on your end - whether I didn't break any of
your stuff. Is something is being missed - please make changes and commit
to that branch.

Hi Carlos,

Can you switch to that branch as well and test some Jewel examples ?

I will try to build Tour De Flex tomorrow to see what is happen.

Thanks,
Piotr

wt., 28 sie 2018 o 19:18 Carlos Rovira  napisał(a):

> 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! :)
>
> Carlos
>
>
> El mar., 28 ago. 2018 a las 19:00, Alex Harui ()
> escribió:
>
> > 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 use Ant variables to point to the results of those builds.  If you
> want
> > to try switching everything off master to the agent that's fine as well.
> > For me, there were some builds that would not run on master.
> >
> > HTH,
> > -Alex
> >
> > On 8/28/18, 9:50 AM, "Piotr Zarzycki" 
> wrote:
> >
> > 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://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fblob%2Fb060cbd9eb5e31932fe06cd35d4a72c86a6c6761%2Fbuild.xml%23L1510data=02%7C01%7Caharui%40adobe.com%7C114873bb0d0b47b418a008d60d064c6a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636710718037802929sdata=wX%2FF0p6jMtHpXCMsJnU82PFjtj%2BiFiHDxvShYcwS1Z8%3Dreserved=0
> > <
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fblob%2Fb060cbd9eb5e31932fe06cd35d4a72c86a6c6761%2Fbuild.xml%23L1510data=02%7C01%7Caharui%40adobe.com%7C114873bb0d0b47b418a008d60d064c6a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636710718037802929sdata=wX%2FF0p6jMtHpXCMsJnU82PFjtj%2BiFiHDxvShYcwS1Z8%3Dreserved=0
> > >*
> > *[2]
> >
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs%2F1230%2FconsoleFulldata=02%7C01%7Caharui%40adobe.com%7C114873bb0d0b47b418a008d60d064c6a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636710718037802929sdata=Wr4WNLn8NvWJ2JMcefbaDDZykIIwmteio5UZP5IiBOw%3Dreserved=0
> > <
> >
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs%2F1230%2FconsoleFulldata=02%7C01%7Caharui%40adobe.com%7C114873bb0d0b47b418a008d60d064c6a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636710718037812939sdata=NSZo2r9I6zZhqSkY1PAQxhKOD9dTQbJcmYCl8%2FXARYM%3Dreserved=0
> > >*
> >
> > *Thanks,*
> > *Piotr*
> >
> > pon., 27 sie 2018 o 20:18 Piotr Zarzycki 
> > napisał(a):
> >
> > > Hi Harbs,
> > >
> > > Please give me some sign here once you will be done with all your
> > changes!
> > >
> > > Thanks,
> > > Piotr
> > >
> > > pon., 27 sie 2018 o 20:12 Harbs 
> napisał(a):
> > >
> > >> I have found that there’s an error with ACE on multiple machines.
> I
> > was
> > >> only able to get it to build by first running ant on the typedefs
> > repo and
> > >> then the asjs repo succeeded.
> > >>
> > >> On my Mac, it worked fine, so I’m not really sure what triggered
> the
> > >> problem.
> > >>
> > >> Maybe this is related to the failures on apacheroyaleci? Dunno…
> > >>
> > >> I plan on making sure the current develop branch works for me and
> > fixing
> > >> any issues that might crop up in the next couple of days.
> > >>
> > >> There is also some code which needs to be cherry-picked from the
> > >> revert-refactor branch.
> > >>
> > >> > On Aug 27, 2018, at 8:25 PM, Alex Harui
>  > >
> > >> wrote:
> > >> >
> > >> > I thought I'd sent an email about this, but I can't find it so I
> > guess
> > >> not.
> > >> >
> > >> > For some reason, some weeks ago, the builds began to fail on
> > >> apacheroyaleci.  The only way I was able to fix it was to create a
> > Jenkins
> > >> agent and move