Build failed in Jenkins: royale-asjs_MXTests #1129

2019-09-06 Thread Apache Royale CI Server
See 


--
[...truncated 966.64 KB...]
[mxmlc] scanning for overrides: ObjectUtil
[mxmlc] scanning for overrides: SolidBorderUtil
[mxmlc] scanning for overrides: StringTrimmer
[mxmlc] scanning for overrides: StringUtil
[mxmlc] scanning for overrides: Timer
[mxmlc] scanning for overrides: UIUtils
[mxmlc] scanning for overrides: Effect
[mxmlc] scanning for overrides: Transition
[mxmlc] scanning for overrides: IFill
[mxmlc] scanning for overrides: SolidColor
[mxmlc] scanning for overrides: IExternalizable
[mxmlc] scanning for overrides: Proxy
[mxmlc] scanning for overrides: CursorBookmark
[mxmlc] scanning for overrides: ICollectionView
[mxmlc] scanning for overrides: IList
[mxmlc] scanning for overrides: IViewCursor
[mxmlc] scanning for overrides: ListCollectionView
[mxmlc] scanning for overrides: ListCollectionViewCursor
[mxmlc] scanning for overrides: ListCollectionViewBookmark
[mxmlc] scanning for overrides: ArrayCollection
[mxmlc] scanning for overrides: ArrayList
[mxmlc] scanning for overrides: XMLListCollection
[mxmlc] scanning for overrides: CanvasLayout
[mxmlc] scanning for overrides: Flex
[mxmlc] scanning for overrides: BoxDirection
[mxmlc] scanning for overrides: HBox
[mxmlc] scanning for overrides: PanelTitleBar
[mxmlc] scanning for overrides: DataGridColumn
[mxmlc] scanning for overrides: Button
[mxmlc] scanning for overrides: ISelectable
[mxmlc] scanning for overrides: CheckBox
[mxmlc] scanning for overrides: IFocusManagerComponent
[mxmlc] scanning for overrides: ComboBase
[mxmlc] scanning for overrides: ComboBox
[mxmlc] scanning for overrides: ScrollControlBase
[mxmlc] scanning for overrides: ListBase
[mxmlc] scanning for overrides: DataGrid
[mxmlc] scanning for overrides: DateField
[mxmlc] scanning for overrides: Label
[mxmlc] scanning for overrides: List
[mxmlc] scanning for overrides: MenuBar
[mxmlc] scanning for overrides: NumericStepper
[mxmlc] scanning for overrides: RadioButton
[mxmlc] scanning for overrides: RadioButtonGroup
[mxmlc] scanning for overrides: TextArea
[mxmlc] scanning for overrides: ITextInput
[mxmlc] scanning for overrides: TextInput
[mxmlc] scanning for overrides: ITextFieldFactory
[mxmlc] scanning for overrides: Singleton
[mxmlc] scanning for overrides: ItemClickEvent
[mxmlc] scanning for overrides: ListEvent
[mxmlc] scanning for overrides: MenuEvent
[mxmlc] scanning for overrides: MouseEvent
[mxmlc] scanning for overrides: PropertyChangeEventKind
[mxmlc] scanning for overrides: Matrix
[mxmlc] scanning for overrides: Matrix
[mxmlc] scanning for overrides: IFocusManagerComplexComponent
[mxmlc] scanning for overrides: IFocusManagerGroup
[mxmlc] scanning for overrides: IResourceBundle
[mxmlc] scanning for overrides: ResourceManagerImpl
[mxmlc] scanning for overrides: ResourceModuleInfo
[mxmlc] scanning for overrides: ResourceEventDispatcher
[mxmlc] scanning for overrides: ResourceBundleProxy
[mxmlc] scanning for overrides: GroupBase
[mxmlc] scanning for overrides: SkinnableComponent
[mxmlc] scanning for overrides: ButtonBase
[mxmlc] scanning for overrides: Button
[mxmlc] scanning for overrides: ErrorArray
[mxmlc] scanning for overrides: RunCodeEvent
[mxmlc] scanning for overrides: PasswordInputBead
[mxmlc] scanning for overrides: ITileLayout
[mxmlc] scanning for overrides: TileLayout
[mxmlc] scanning for overrides: LocaleUtils
[mxmlc] scanning for overrides: StringPadder
[mxmlc] scanning for overrides: UIDUtil
[mxmlc] scanning for overrides: IStroke
[mxmlc] scanning for overrides: CursorError
[mxmlc] scanning for overrides: SortError
[mxmlc] scanning for overrides: ISort
[mxmlc] scanning for overrides: Sort
[mxmlc] scanning for overrides: IXMLNotifiable
[mxmlc] scanning for overrides: XMLListAdapter
[mxmlc] scanning for overrides: FlexChildInfo
[mxmlc] scanning for overrides: BaseListData
[mxmlc] scanning for overrides: IFactory
[mxmlc] scanning for overrides: IUITextField
[mxmlc] scanning for overrides: UITextField
[mxmlc] scanning for overrides: CollectionEvent
[mxmlc] scanning for overrides: CollectionEventKind
[mxmlc] scanning for overrides: LocaleSorter
[mxmlc] scanning for overrides: LocaleID
[mxmlc] scanning for overrides: LocaleRegistry
[mxmlc] scanning for overrides: ResourceBundle
[mxmlc] scanning for overrides: ArrayUtil
[mxmlc] scanning for overrides: StringUtil
[mxmlc] scanning for overrides: UIDUtil
[mxmlc] scanning for overrides: DataGroup
[mxmlc] scanning for overrides: LayoutBase
[mxmlc] scanning for overrides: BasicLayout

Re: Heads up on XML

2019-09-06 Thread Greg Dove
'I think that SWFDump will generate valid XML and there is a way to get
DITA files from Flex ASDoc that are valid XML.'
Sounds like a good idea for some large xml files. I did not use that yet,
so will take a look and see if I can figure it out. Thanks!


On Sat, Sep 7, 2019 at 12:30 PM Greg Dove  wrote:

>
> Just to clarify I was referring to this stuff here:
>
>
> https://github.com/apache/royale-asjs/blob/8ab1d813ee2f72bab957f9485e56ad89dcf6e1ab/frameworks/projects/MXRoyale/src/main/royale/mx/rpc/http/AbstractOperation.as#L1038
>
>
> with '//old XML style'
>
>
>
>
> On Sat, Sep 7, 2019 at 12:24 PM Alex Harui 
> wrote:
>
>> I haven't looked at what XML is used/supported by MX HTTPService.  It
>> looks like WebService does use MX HTTPService.  I am currently migrating
>> other things that WebService needs (XMLEncoder/Decoder,
>> SOAPEncoder/Decoder).  These are new files that aren't in the repo yet, so
>> HTTPService couldn't be relying on them or else their use is commented
>> out.   The goal is to change as little as possible to get it to compile and
>> then see if it runs.  I have no idea yet if the XML improvements you are
>> working on are going to be impactful on what I'm doing or not.
>>
>> BTW, I could be wrong, but I think that SWFDump will generate valid XML
>> and there is a way to get DITA files from Flex ASDoc that are valid XML.
>>
>> Thanks for the heads up,
>> -Alex
>>
>> On 9/6/19, 5:14 PM, "Greg Dove"  wrote:
>>
>> Actually I know you are looking into the WSDL stuff maybe this is
>> going
>> to be important for that (not sure)?
>> My goal is to get the XML stuff tidied up and ready to push by end of
>> day
>> tomorrow, worst case the following morning, local time (UTC+12). I
>> also
>> need to find some big XML test cases to check the memory side of
>> things.
>> FYI there is also some XMLDocument stuff missing (commented out) from
>> some
>> of the MX HttpService code, which came up in a recent issue. I don't
>> know
>> if it shares any of the code from the WSDL stuff you are looking at or
>> not...
>> If it does then I don't want to double up on things, but otherwise I
>> will
>> try to look at that on my Monday.
>>
>>
>>
>> On Sat, Sep 7, 2019 at 12:02 PM Greg Dove 
>> wrote:
>>
>> > Thanks for checking that.
>> >
>> > child is specified in 13.4.4.6 and essentially calls [[Get]]
>> > (After cycling through this kind of thing a few times, I found the
>> easiest
>> > way to find methods is to search in the spec for 'e.mehodName'
>> which gets
>> > you XML.prototype.methodName)
>> >
>> > and [[Get]] is specified in 9.1.1.1
>> >
>> > So I assume it is a bug. As discussed I think it is good to match
>> the
>> > behavior. If we can verify 100% it is off spec, we could add
>> something as a
>> > define to avoid the 'fix' for people who want to be on-spec.
>> >
>> >
>> >
>> >
>> >
>> > On Sat, Sep 7, 2019 at 11:30 AM Alex Harui > >
>> > wrote:
>> >
>> >> FWIW, I went and looked at the ABC.
>> >>
>> >> The first syntax sets up a getProperty just like any other property
>> >> fetch.  The second (as expected) calls "child()".  I've looked at
>> the E4X
>> >> spec a couple of times now and cannot see where the behavior we
>> are seeing
>> >> in child() is specified so I am going to assume it is a bug, and
>> that we
>> >> just have to live with it.
>> >>
>> >> I expect that getProperty does not call child().  I haven't looked
>> at the
>> >> AVM code to see what getProperty does for XML.
>> >>
>> >> HTH,
>> >> -Alex
>> >>
>> >> On 9/5/19, 12:05 PM, "Greg Dove"  wrote:
>> >>
>> >> Oh that is a good find! And perfect timing :)
>> >> Thanks Alex, I am pretty sure that answers the question! (It
>> quite
>> >> specifically describes what I was seeing, I don't think it
>> makes a
>> >> difference whether it is attributes or elements)
>> >>
>> >> And yes, I agree it should be the implemented to give the same
>> >> results as
>> >> swf.
>> >> I will add this to the other work I have over the weekend
>> before I
>> >> get it
>> >> in. It only seems relevant for when child (or descendants, I
>> don't
>> >> expect
>> >> that will be different) method call is explicit (as opposed to
>> the
>> >> compiler-generated method calls from e4x 'member access') with
>> QName
>> >> argument only. I think most people won't use this approach with
>> >> explicit
>> >> QNames, but it is one of those things that will cause misery
>> if you do
>> >> (when porting legacy code), so it should be the same IMO also.
>> I will
>> >> make
>> >> sure it costs nothing for the more common (other) use cases. I
>> have
>> >> had to
>> >> do something similar to support 'use namespace' 

Re: Heads up on XML

2019-09-06 Thread Alex Harui
Thanks.  Yeah I remember that is commented out.  In a quick look, it wasn't 
clear why XMLDocument was used instead of E4x in the WebService code.  I will 
probably just use e4x and see what happens.

-Alex

On 9/6/19, 5:30 PM, "Greg Dove"  wrote:

Just to clarify I was referring to this stuff here:


https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fblob%2F8ab1d813ee2f72bab957f9485e56ad89dcf6e1ab%2Fframeworks%2Fprojects%2FMXRoyale%2Fsrc%2Fmain%2Froyale%2Fmx%2Frpc%2Fhttp%2FAbstractOperation.as%23L1038data=02%7C01%7Caharui%40adobe.com%7Cb03f4d24bb5b4c3b297c08d7332a944b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637034130321301841sdata=HKh9b5WI%2BFiclvbOKLNCFoVpj8cIh%2FUUHREeCef%2BNEU%3Dreserved=0


with '//old XML style'




On Sat, Sep 7, 2019 at 12:24 PM Alex Harui  wrote:

> I haven't looked at what XML is used/supported by MX HTTPService.  It
> looks like WebService does use MX HTTPService.  I am currently migrating
> other things that WebService needs (XMLEncoder/Decoder,
> SOAPEncoder/Decoder).  These are new files that aren't in the repo yet, so
> HTTPService couldn't be relying on them or else their use is commented
> out.   The goal is to change as little as possible to get it to compile 
and
> then see if it runs.  I have no idea yet if the XML improvements you are
> working on are going to be impactful on what I'm doing or not.
>
> BTW, I could be wrong, but I think that SWFDump will generate valid XML
> and there is a way to get DITA files from Flex ASDoc that are valid XML.
>
> Thanks for the heads up,
> -Alex
>
> On 9/6/19, 5:14 PM, "Greg Dove"  wrote:
>
> Actually I know you are looking into the WSDL stuff maybe this is
> going
> to be important for that (not sure)?
> My goal is to get the XML stuff tidied up and ready to push by end of
> day
> tomorrow, worst case the following morning, local time (UTC+12). I 
also
> need to find some big XML test cases to check the memory side of
> things.
> FYI there is also some XMLDocument stuff missing (commented out) from
> some
> of the MX HttpService code, which came up in a recent issue. I don't
> know
> if it shares any of the code from the WSDL stuff you are looking at or
> not...
> If it does then I don't want to double up on things, but otherwise I
> will
> try to look at that on my Monday.
>
>
>
> On Sat, Sep 7, 2019 at 12:02 PM Greg Dove  wrote:
>
> > Thanks for checking that.
> >
> > child is specified in 13.4.4.6 and essentially calls [[Get]]
> > (After cycling through this kind of thing a few times, I found the
> easiest
> > way to find methods is to search in the spec for 'e.mehodName' which
> gets
> > you XML.prototype.methodName)
> >
> > and [[Get]] is specified in 9.1.1.1
> >
> > So I assume it is a bug. As discussed I think it is good to match 
the
> > behavior. If we can verify 100% it is off spec, we could add
> something as a
> > define to avoid the 'fix' for people who want to be on-spec.
> >
> >
> >
> >
> >
> > On Sat, Sep 7, 2019 at 11:30 AM Alex Harui  >
> > wrote:
> >
> >> FWIW, I went and looked at the ABC.
> >>
> >> The first syntax sets up a getProperty just like any other property
> >> fetch.  The second (as expected) calls "child()".  I've looked at
> the E4X
> >> spec a couple of times now and cannot see where the behavior we are
> seeing
> >> in child() is specified so I am going to assume it is a bug, and
> that we
> >> just have to live with it.
> >>
> >> I expect that getProperty does not call child().  I haven't looked
> at the
> >> AVM code to see what getProperty does for XML.
> >>
> >> HTH,
> >> -Alex
> >>
> >> On 9/5/19, 12:05 PM, "Greg Dove"  wrote:
> >>
> >> Oh that is a good find! And perfect timing :)
> >> Thanks Alex, I am pretty sure that answers the question! (It
> quite
> >> specifically describes what I was seeing, I don't think it
> makes a
> >> difference whether it is attributes or elements)
> >>
> >> And yes, I agree it should be the implemented to give the same
> >> results as
> >> swf.
> >> I will add this to the other work I have over the weekend
> before I
> >> get it
> >> in. It only seems relevant for when child (or descendants, I
> don't
> >> expect
> >> that will be different) method call is explicit (as opposed to

Re: Heads up on XML

2019-09-06 Thread Greg Dove
Just to clarify I was referring to this stuff here:

https://github.com/apache/royale-asjs/blob/8ab1d813ee2f72bab957f9485e56ad89dcf6e1ab/frameworks/projects/MXRoyale/src/main/royale/mx/rpc/http/AbstractOperation.as#L1038


with '//old XML style'




On Sat, Sep 7, 2019 at 12:24 PM Alex Harui  wrote:

> I haven't looked at what XML is used/supported by MX HTTPService.  It
> looks like WebService does use MX HTTPService.  I am currently migrating
> other things that WebService needs (XMLEncoder/Decoder,
> SOAPEncoder/Decoder).  These are new files that aren't in the repo yet, so
> HTTPService couldn't be relying on them or else their use is commented
> out.   The goal is to change as little as possible to get it to compile and
> then see if it runs.  I have no idea yet if the XML improvements you are
> working on are going to be impactful on what I'm doing or not.
>
> BTW, I could be wrong, but I think that SWFDump will generate valid XML
> and there is a way to get DITA files from Flex ASDoc that are valid XML.
>
> Thanks for the heads up,
> -Alex
>
> On 9/6/19, 5:14 PM, "Greg Dove"  wrote:
>
> Actually I know you are looking into the WSDL stuff maybe this is
> going
> to be important for that (not sure)?
> My goal is to get the XML stuff tidied up and ready to push by end of
> day
> tomorrow, worst case the following morning, local time (UTC+12). I also
> need to find some big XML test cases to check the memory side of
> things.
> FYI there is also some XMLDocument stuff missing (commented out) from
> some
> of the MX HttpService code, which came up in a recent issue. I don't
> know
> if it shares any of the code from the WSDL stuff you are looking at or
> not...
> If it does then I don't want to double up on things, but otherwise I
> will
> try to look at that on my Monday.
>
>
>
> On Sat, Sep 7, 2019 at 12:02 PM Greg Dove  wrote:
>
> > Thanks for checking that.
> >
> > child is specified in 13.4.4.6 and essentially calls [[Get]]
> > (After cycling through this kind of thing a few times, I found the
> easiest
> > way to find methods is to search in the spec for 'e.mehodName' which
> gets
> > you XML.prototype.methodName)
> >
> > and [[Get]] is specified in 9.1.1.1
> >
> > So I assume it is a bug. As discussed I think it is good to match the
> > behavior. If we can verify 100% it is off spec, we could add
> something as a
> > define to avoid the 'fix' for people who want to be on-spec.
> >
> >
> >
> >
> >
> > On Sat, Sep 7, 2019 at 11:30 AM Alex Harui  >
> > wrote:
> >
> >> FWIW, I went and looked at the ABC.
> >>
> >> The first syntax sets up a getProperty just like any other property
> >> fetch.  The second (as expected) calls "child()".  I've looked at
> the E4X
> >> spec a couple of times now and cannot see where the behavior we are
> seeing
> >> in child() is specified so I am going to assume it is a bug, and
> that we
> >> just have to live with it.
> >>
> >> I expect that getProperty does not call child().  I haven't looked
> at the
> >> AVM code to see what getProperty does for XML.
> >>
> >> HTH,
> >> -Alex
> >>
> >> On 9/5/19, 12:05 PM, "Greg Dove"  wrote:
> >>
> >> Oh that is a good find! And perfect timing :)
> >> Thanks Alex, I am pretty sure that answers the question! (It
> quite
> >> specifically describes what I was seeing, I don't think it
> makes a
> >> difference whether it is attributes or elements)
> >>
> >> And yes, I agree it should be the implemented to give the same
> >> results as
> >> swf.
> >> I will add this to the other work I have over the weekend
> before I
> >> get it
> >> in. It only seems relevant for when child (or descendants, I
> don't
> >> expect
> >> that will be different) method call is explicit (as opposed to
> the
> >> compiler-generated method calls from e4x 'member access') with
> QName
> >> argument only. I think most people won't use this approach with
> >> explicit
> >> QNames, but it is one of those things that will cause misery if
> you do
> >> (when porting legacy code), so it should be the same IMO also.
> I will
> >> make
> >> sure it costs nothing for the more common (other) use cases. I
> have
> >> had to
> >> do something similar to support 'use namespace' directives which
> >> create a
> >> MultiName-like variant of QName in my local change that
> includes the
> >> default namespace and the specified set of other 'used'/open
> >> namespace uris
> >> in the current execution scope. (That 'use namespace' pattern
> was
> >> being
> >> used quite a bit in the codebase I have been working on)
> >>
> >> Thanks again, that will save me investigating it with 

Re: Heads up on XML

2019-09-06 Thread Alex Harui
I haven't looked at what XML is used/supported by MX HTTPService.  It looks 
like WebService does use MX HTTPService.  I am currently migrating other things 
that WebService needs (XMLEncoder/Decoder, SOAPEncoder/Decoder).  These are new 
files that aren't in the repo yet, so HTTPService couldn't be relying on them 
or else their use is commented out.   The goal is to change as little as 
possible to get it to compile and then see if it runs.  I have no idea yet if 
the XML improvements you are working on are going to be impactful on what I'm 
doing or not.

BTW, I could be wrong, but I think that SWFDump will generate valid XML and 
there is a way to get DITA files from Flex ASDoc that are valid XML.

Thanks for the heads up,
-Alex

On 9/6/19, 5:14 PM, "Greg Dove"  wrote:

Actually I know you are looking into the WSDL stuff maybe this is going
to be important for that (not sure)?
My goal is to get the XML stuff tidied up and ready to push by end of day
tomorrow, worst case the following morning, local time (UTC+12). I also
need to find some big XML test cases to check the memory side of things.
FYI there is also some XMLDocument stuff missing (commented out) from some
of the MX HttpService code, which came up in a recent issue. I don't know
if it shares any of the code from the WSDL stuff you are looking at or
not...
If it does then I don't want to double up on things, but otherwise I will
try to look at that on my Monday.



On Sat, Sep 7, 2019 at 12:02 PM Greg Dove  wrote:

> Thanks for checking that.
>
> child is specified in 13.4.4.6 and essentially calls [[Get]]
> (After cycling through this kind of thing a few times, I found the easiest
> way to find methods is to search in the spec for 'e.mehodName' which gets
> you XML.prototype.methodName)
>
> and [[Get]] is specified in 9.1.1.1
>
> So I assume it is a bug. As discussed I think it is good to match the
> behavior. If we can verify 100% it is off spec, we could add something as 
a
> define to avoid the 'fix' for people who want to be on-spec.
>
>
>
>
>
> On Sat, Sep 7, 2019 at 11:30 AM Alex Harui 
> wrote:
>
>> FWIW, I went and looked at the ABC.
>>
>> The first syntax sets up a getProperty just like any other property
>> fetch.  The second (as expected) calls "child()".  I've looked at the E4X
>> spec a couple of times now and cannot see where the behavior we are 
seeing
>> in child() is specified so I am going to assume it is a bug, and that we
>> just have to live with it.
>>
>> I expect that getProperty does not call child().  I haven't looked at the
>> AVM code to see what getProperty does for XML.
>>
>> HTH,
>> -Alex
>>
>> On 9/5/19, 12:05 PM, "Greg Dove"  wrote:
>>
>> Oh that is a good find! And perfect timing :)
>> Thanks Alex, I am pretty sure that answers the question! (It quite
>> specifically describes what I was seeing, I don't think it makes a
>> difference whether it is attributes or elements)
>>
>> And yes, I agree it should be the implemented to give the same
>> results as
>> swf.
>> I will add this to the other work I have over the weekend before I
>> get it
>> in. It only seems relevant for when child (or descendants, I don't
>> expect
>> that will be different) method call is explicit (as opposed to the
>> compiler-generated method calls from e4x 'member access') with QName
>> argument only. I think most people won't use this approach with
>> explicit
>> QNames, but it is one of those things that will cause misery if you 
do
>> (when porting legacy code), so it should be the same IMO also. I will
>> make
>> sure it costs nothing for the more common (other) use cases. I have
>> had to
>> do something similar to support 'use namespace' directives which
>> create a
>> MultiName-like variant of QName in my local change that includes the
>> default namespace and the specified set of other 'used'/open
>> namespace uris
>> in the current execution scope. (That 'use namespace' pattern was
>> being
>> used quite a bit in the codebase I have been working on)
>>
>> Thanks again, that will save me investigating it with bytecode.
>>
>>
>>
>>
>> On Fri, Sep 6, 2019 at 6:37 AM Alex Harui 
>> wrote:
>>
>> > Out of pure random chance, I was starting the migration of
>> WebService
>> > which had a dependency on XMLUtil which contained the comment:
>> >
>> > //xml.attribute(QName) will also return local no-namespace
>> > attributes
>> > //even if we are looking for a specific full qualified 
name.
>> >
>> > So, still could 

Re: Heads up on XML

2019-09-06 Thread Greg Dove
Actually I know you are looking into the WSDL stuff maybe this is going
to be important for that (not sure)?
My goal is to get the XML stuff tidied up and ready to push by end of day
tomorrow, worst case the following morning, local time (UTC+12). I also
need to find some big XML test cases to check the memory side of things.
FYI there is also some XMLDocument stuff missing (commented out) from some
of the MX HttpService code, which came up in a recent issue. I don't know
if it shares any of the code from the WSDL stuff you are looking at or
not...
If it does then I don't want to double up on things, but otherwise I will
try to look at that on my Monday.



On Sat, Sep 7, 2019 at 12:02 PM Greg Dove  wrote:

> Thanks for checking that.
>
> child is specified in 13.4.4.6 and essentially calls [[Get]]
> (After cycling through this kind of thing a few times, I found the easiest
> way to find methods is to search in the spec for 'e.mehodName' which gets
> you XML.prototype.methodName)
>
> and [[Get]] is specified in 9.1.1.1
>
> So I assume it is a bug. As discussed I think it is good to match the
> behavior. If we can verify 100% it is off spec, we could add something as a
> define to avoid the 'fix' for people who want to be on-spec.
>
>
>
>
>
> On Sat, Sep 7, 2019 at 11:30 AM Alex Harui 
> wrote:
>
>> FWIW, I went and looked at the ABC.
>>
>> The first syntax sets up a getProperty just like any other property
>> fetch.  The second (as expected) calls "child()".  I've looked at the E4X
>> spec a couple of times now and cannot see where the behavior we are seeing
>> in child() is specified so I am going to assume it is a bug, and that we
>> just have to live with it.
>>
>> I expect that getProperty does not call child().  I haven't looked at the
>> AVM code to see what getProperty does for XML.
>>
>> HTH,
>> -Alex
>>
>> On 9/5/19, 12:05 PM, "Greg Dove"  wrote:
>>
>> Oh that is a good find! And perfect timing :)
>> Thanks Alex, I am pretty sure that answers the question! (It quite
>> specifically describes what I was seeing, I don't think it makes a
>> difference whether it is attributes or elements)
>>
>> And yes, I agree it should be the implemented to give the same
>> results as
>> swf.
>> I will add this to the other work I have over the weekend before I
>> get it
>> in. It only seems relevant for when child (or descendants, I don't
>> expect
>> that will be different) method call is explicit (as opposed to the
>> compiler-generated method calls from e4x 'member access') with QName
>> argument only. I think most people won't use this approach with
>> explicit
>> QNames, but it is one of those things that will cause misery if you do
>> (when porting legacy code), so it should be the same IMO also. I will
>> make
>> sure it costs nothing for the more common (other) use cases. I have
>> had to
>> do something similar to support 'use namespace' directives which
>> create a
>> MultiName-like variant of QName in my local change that includes the
>> default namespace and the specified set of other 'used'/open
>> namespace uris
>> in the current execution scope. (That 'use namespace' pattern was
>> being
>> used quite a bit in the codebase I have been working on)
>>
>> Thanks again, that will save me investigating it with bytecode.
>>
>>
>>
>>
>> On Fri, Sep 6, 2019 at 6:37 AM Alex Harui 
>> wrote:
>>
>> > Out of pure random chance, I was starting the migration of
>> WebService
>> > which had a dependency on XMLUtil which contained the comment:
>> >
>> > //xml.attribute(QName) will also return local no-namespace
>> > attributes
>> > //even if we are looking for a specific full qualified name.
>> >
>> > So, still could be a bug in Flash, but maybe we should just make our
>> > implementation work the same way to reduce migration effort in case
>> someone
>> > is relying on this behavior.
>> >
>> > Thoughts?
>> > -Alex
>> >
>> > On 9/4/19, 1:47 PM, "Alex Harui"  wrote:
>> >
>> > I read the example incorrectly.  So yeah, it should return 0
>> and empty
>> > string in both cases, IMO.  There might be some subtlety in how the
>> > namespaces are specified for a QName or how QName works in child().
>> >
>> > HTH,
>> > -Alex
>> >
>> > On 9/4/19, 11:33 AM, "Greg Dove"  wrote:
>> >
>> > Good idea. I'll check the swf output, although probably
>> tomorrow
>> > as I need
>> > to focus on something else today.
>> > ' I would have expected both to return "1" and the node.  '
>> >
>> > In that example I would expect the opposite (because the
>> the link
>> > node
>> > being returned by the second query is not in the specified
>> explicit
>> > namespace of the QName), so I am curious to understand why
>> you
>> > think
>> >  

Re: Heads up on XML

2019-09-06 Thread Greg Dove
Thanks for checking that.

child is specified in 13.4.4.6 and essentially calls [[Get]]
(After cycling through this kind of thing a few times, I found the easiest
way to find methods is to search in the spec for 'e.mehodName' which gets
you XML.prototype.methodName)

and [[Get]] is specified in 9.1.1.1

So I assume it is a bug. As discussed I think it is good to match the
behavior. If we can verify 100% it is off spec, we could add something as a
define to avoid the 'fix' for people who want to be on-spec.





On Sat, Sep 7, 2019 at 11:30 AM Alex Harui  wrote:

> FWIW, I went and looked at the ABC.
>
> The first syntax sets up a getProperty just like any other property
> fetch.  The second (as expected) calls "child()".  I've looked at the E4X
> spec a couple of times now and cannot see where the behavior we are seeing
> in child() is specified so I am going to assume it is a bug, and that we
> just have to live with it.
>
> I expect that getProperty does not call child().  I haven't looked at the
> AVM code to see what getProperty does for XML.
>
> HTH,
> -Alex
>
> On 9/5/19, 12:05 PM, "Greg Dove"  wrote:
>
> Oh that is a good find! And perfect timing :)
> Thanks Alex, I am pretty sure that answers the question! (It quite
> specifically describes what I was seeing, I don't think it makes a
> difference whether it is attributes or elements)
>
> And yes, I agree it should be the implemented to give the same results
> as
> swf.
> I will add this to the other work I have over the weekend before I get
> it
> in. It only seems relevant for when child (or descendants, I don't
> expect
> that will be different) method call is explicit (as opposed to the
> compiler-generated method calls from e4x 'member access') with QName
> argument only. I think most people won't use this approach with
> explicit
> QNames, but it is one of those things that will cause misery if you do
> (when porting legacy code), so it should be the same IMO also. I will
> make
> sure it costs nothing for the more common (other) use cases. I have
> had to
> do something similar to support 'use namespace' directives which
> create a
> MultiName-like variant of QName in my local change that includes the
> default namespace and the specified set of other 'used'/open namespace
> uris
> in the current execution scope. (That 'use namespace' pattern was being
> used quite a bit in the codebase I have been working on)
>
> Thanks again, that will save me investigating it with bytecode.
>
>
>
>
> On Fri, Sep 6, 2019 at 6:37 AM Alex Harui 
> wrote:
>
> > Out of pure random chance, I was starting the migration of WebService
> > which had a dependency on XMLUtil which contained the comment:
> >
> > //xml.attribute(QName) will also return local no-namespace
> > attributes
> > //even if we are looking for a specific full qualified name.
> >
> > So, still could be a bug in Flash, but maybe we should just make our
> > implementation work the same way to reduce migration effort in case
> someone
> > is relying on this behavior.
> >
> > Thoughts?
> > -Alex
> >
> > On 9/4/19, 1:47 PM, "Alex Harui"  wrote:
> >
> > I read the example incorrectly.  So yeah, it should return 0 and
> empty
> > string in both cases, IMO.  There might be some subtlety in how the
> > namespaces are specified for a QName or how QName works in child().
> >
> > HTH,
> > -Alex
> >
> > On 9/4/19, 11:33 AM, "Greg Dove"  wrote:
> >
> > Good idea. I'll check the swf output, although probably
> tomorrow
> > as I need
> > to focus on something else today.
> > ' I would have expected both to return "1" and the node.  '
> >
> > In that example I would expect the opposite (because the the
> link
> > node
> > being returned by the second query is not in the specified
> explicit
> > namespace of the QName), so I am curious to understand why
> you
> > think
> > that... maybe it will help me understand.
> >
> > When I use feed.atom::link I expect only links that are
> bound to
> > the atom
> > namespace (uri). Because  node has no prefix
> bound to
> > the uri
> > that the atom namespace defines, and it is in the default
> > namespace, I
> > would not expect it to be included.
> > At the moment the atom::link part is working the same as
> swf, so
> > I'm happy
> > with that at least for what I am working on. All the explicit
> > calls to
> > child(name) or descendants(name) in the app I am working on
> use
> > string args
> > so these all work correctly as well.
> > I'm just trying to cover things for the future... while my
> head is
> > still in
> > 

Re: Heads up on XML

2019-09-06 Thread Alex Harui
FWIW, I went and looked at the ABC.

The first syntax sets up a getProperty just like any other property fetch.  The 
second (as expected) calls "child()".  I've looked at the E4X spec a couple of 
times now and cannot see where the behavior we are seeing in child() is 
specified so I am going to assume it is a bug, and that we just have to live 
with it.

I expect that getProperty does not call child().  I haven't looked at the AVM 
code to see what getProperty does for XML.

HTH,
-Alex

On 9/5/19, 12:05 PM, "Greg Dove"  wrote:

Oh that is a good find! And perfect timing :)
Thanks Alex, I am pretty sure that answers the question! (It quite
specifically describes what I was seeing, I don't think it makes a
difference whether it is attributes or elements)

And yes, I agree it should be the implemented to give the same results as
swf.
I will add this to the other work I have over the weekend before I get it
in. It only seems relevant for when child (or descendants, I don't expect
that will be different) method call is explicit (as opposed to the
compiler-generated method calls from e4x 'member access') with QName
argument only. I think most people won't use this approach with explicit
QNames, but it is one of those things that will cause misery if you do
(when porting legacy code), so it should be the same IMO also. I will make
sure it costs nothing for the more common (other) use cases. I have had to
do something similar to support 'use namespace' directives which create a
MultiName-like variant of QName in my local change that includes the
default namespace and the specified set of other 'used'/open namespace uris
in the current execution scope. (That 'use namespace' pattern was being
used quite a bit in the codebase I have been working on)

Thanks again, that will save me investigating it with bytecode.




On Fri, Sep 6, 2019 at 6:37 AM Alex Harui  wrote:

> Out of pure random chance, I was starting the migration of WebService
> which had a dependency on XMLUtil which contained the comment:
>
> //xml.attribute(QName) will also return local no-namespace
> attributes
> //even if we are looking for a specific full qualified name.
>
> So, still could be a bug in Flash, but maybe we should just make our
> implementation work the same way to reduce migration effort in case 
someone
> is relying on this behavior.
>
> Thoughts?
> -Alex
>
> On 9/4/19, 1:47 PM, "Alex Harui"  wrote:
>
> I read the example incorrectly.  So yeah, it should return 0 and empty
> string in both cases, IMO.  There might be some subtlety in how the
> namespaces are specified for a QName or how QName works in child().
>
> HTH,
> -Alex
>
> On 9/4/19, 11:33 AM, "Greg Dove"  wrote:
>
> Good idea. I'll check the swf output, although probably tomorrow
> as I need
> to focus on something else today.
> ' I would have expected both to return "1" and the node.  '
>
> In that example I would expect the opposite (because the the link
> node
> being returned by the second query is not in the specified 
explicit
> namespace of the QName), so I am curious to understand why you
> think
> that... maybe it will help me understand.
>
> When I use feed.atom::link I expect only links that are bound to
> the atom
> namespace (uri). Because  node has no prefix bound to
> the uri
> that the atom namespace defines, and it is in the default
> namespace, I
> would not expect it to be included.
> At the moment the atom::link part is working the same as swf, so
> I'm happy
> with that at least for what I am working on. All the explicit
> calls to
> child(name) or descendants(name) in the app I am working on use
> string args
> so these all work correctly as well.
> I'm just trying to cover things for the future... while my head is
> still in
> this stuff.
>
>
>
> On Thu, Sep 5, 2019 at 6:11 AM Alex Harui 

> wrote:
>
> > Speaking of multinames, what is the ABC code generated by the
> Flex
> > compiler for the two cases?  It might contain some clues.  I
> would have
> > expected both to return "1" and the node.  But I did see in the
> spec the
> > notion of "InScopeNamespaces".  I generally hate reading specs
> like these
> > so I am not very knowledgeable about what the spec says.
> >
> > HTH,
> > -Alex
> >
> > On 9/4/19, 11:05 AM, "Greg Dove"  wrote:
> >
> > 'Have you rummaged through 

Re: ${body} in index template

2019-09-06 Thread Alex Harui
FWIW, the current implementation was just a quick hack to get something 
working.  No serious thought went into it so feel free to change it.

I think there are "projectName" and "mainClassQName" variables in the compiler. 
 IIRC, projectName maps to the output file name and mainClassQName maps to the 
name of the file that subclasses some Application that becomes the source file 
passed into the compiler.  Most of our examples have them as the same, but 
Carlos likes to build examples where the main class is App.mxml.

IIRC, Flex always named the SystemManager subclass after the mainClassQName.  
In Royale, any framework can use [FactoryClass] to setup some sort of 
SystemManager-like thing that loads the Application, so in my mind, there is an 
"EntryPointClass" or "StartupClass" and the main Application subclass.  
Sometimes they are the same (for Basic and probably Jewel).

I'm not concerned about breaking existing templates by not injection the 
 tags around the entry point code.  But that's just me.

My 2 cents,
-Alex

On 9/6/19, 2:20 PM, "Greg Dove"  wrote:

Hi Carlos,

Based on the variation that happens, I'm not sure ${application} is useful
in its current form, although at first glance it appeared to be when I used
it.

Probably we just need
${applicationclass}

The code that handles this is here:

https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-compiler%2Fblob%2Fa9fcf4f1f1b71508c7f9bf984975a27fbb13b8d5%2Fcompiler-jx%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Froyale%2Fcompiler%2Finternal%2Fcodegen%2Fmxml%2Froyale%2FMXMLRoyalePublisher.java%23L832&data=02%7C01%7Caharui%40adobe.com%7C4eaa963c03ce49e1239808d733101497%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637034016499897671&sdata=cG%2FSBE05253%2BIduhPc8gbkyX0kStLLeHjizbKoHsXy8%3D&reserved=0

And based on what it seems to be doing I think the ${applicationclass}
token would just need to be substituted with the same value that is passed
as the argument to getTemplateBody call here:

https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-compiler%2Fblob%2Fa9fcf4f1f1b71508c7f9bf984975a27fbb13b8d5%2Fcompiler-jx%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Froyale%2Fcompiler%2Finternal%2Fcodegen%2Fmxml%2Froyale%2FMXMLRoyalePublisher.java%23L879&data=02%7C01%7Caharui%40adobe.com%7C4eaa963c03ce49e1239808d733101497%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637034016499897671&sdata=OemmdJGiY6f9Nj1iLLgPUIee0E1GTZyQSr7Jvp4xNwE%3D&reserved=0

so I'm guessing all it needs is:
if (type.equals("release")) {
result = input.replaceAll("\\$\\{applicationclass\\}",
projectName );
} else {
result = input.replaceAll("\\$\\{applicationclass\\}",
mainClassName );
}

But I did not check the variation between projectName and mainClassName
between release and debug for that, so I don't fully understand that part
yet. Maybe @aharui can confirm.




On Fri, Sep 6, 2019 at 7:36 PM Carlos Rovira 
wrote:

> Hi Greg,
>
> so the proposal is to end with:
>
> -body
> -application (used for standard Royale apps)
> -AppClassName (for Flex emulated apps that will have
> "_mx_managers_SystemManager" as part of the string. so this is really
> "{application}" + "_mx_managers_SystemManager")
>
> right?
>
> what do you think about
>
> -body
> -application
> -flexapplication
>
> ?
>
> (just trying to have the same style for names and simplifying to something
> more human readable)
>
> thanks!
>
>
> El vie., 6 sept. 2019 a las 5:16, Greg Dove ()
> escribió:
>
> > This seems 

Re: ${body} in index template

2019-09-06 Thread Greg Dove
Hi Carlos,

Based on the variation that happens, I'm not sure ${application} is useful
in its current form, although at first glance it appeared to be when I used
it.

Probably we just need
${applicationclass}

The code that handles this is here:
https://github.com/apache/royale-compiler/blob/a9fcf4f1f1b71508c7f9bf984975a27fbb13b8d5/compiler-jx/src/main/java/org/apache/royale/compiler/internal/codegen/mxml/royale/MXMLRoyalePublisher.java#L832

And based on what it seems to be doing I think the ${applicationclass}
token would just need to be substituted with the same value that is passed
as the argument to getTemplateBody call here:
https://github.com/apache/royale-compiler/blob/a9fcf4f1f1b71508c7f9bf984975a27fbb13b8d5/compiler-jx/src/main/java/org/apache/royale/compiler/internal/codegen/mxml/royale/MXMLRoyalePublisher.java#L879

so I'm guessing all it needs is:
if (type.equals("release")) {
result = input.replaceAll("\\$\\{applicationclass\\}",
projectName );
} else {
result = input.replaceAll("\\$\\{applicationclass\\}",
mainClassName );
}

But I did not check the variation between projectName and mainClassName
between release and debug for that, so I don't fully understand that part
yet. Maybe @aharui can confirm.




On Fri, Sep 6, 2019 at 7:36 PM Carlos Rovira 
wrote:

> Hi Greg,
>
> so the proposal is to end with:
>
> -body
> -application (used for standard Royale apps)
> -AppClassName (for Flex emulated apps that will have
> "_mx_managers_SystemManager" as part of the string. so this is really
> "{application}" + "_mx_managers_SystemManager")
>
> right?
>
> what do you think about
>
> -body
> -application
> -flexapplication
>
> ?
>
> (just trying to have the same style for names and simplifying to something
> more human readable)
>
> thanks!
>
>
> El vie., 6 sept. 2019 a las 5:16, Greg Dove ()
> escribió:
>
> > This seems like an easy thing to fix (unless I missed something).
> > So I think we just need to decide what the token should be.
> >
> > What does everyone think of:
> > ${AppClassName}
> >
> > Input welcome...
> >
> >
> >
> > On Fri, Sep 6, 2019 at 3:05 PM Greg Dove  wrote:
> >
> > > It looks like that only works for debug builds because it gets '.min'
> > > appended in the release build template.
> > > And it seems that MXRoyale Application builds append the system manager
> > > part as a variation.
> > > So we need a new token probably just for the main class name.
> > >
> > > For now it is possible to do:
> > > ${application}_mx_managers_SystemManager
> > > for debug builds of mx apps.
> > >
> > >
> > >
> > > On Fri, Sep 6, 2019 at 1:17 PM Greg Dove  wrote:
> > >
> > >>
> > >> Just to add to this thread:
> > >>
> > >> this type of thing also works if you need the name of the application
> > >> injected (which seems quite helpful for injecting into customised
> > >> javascript):
> > >>
> > >> 
> > >> // the name of my app is:${application}
> > >> 
> > >>
> > >>
> > >> On Wed, Aug 28, 2019 at 8:02 PM Carlos Rovira <
> carlosrov...@apache.org>
> > >> wrote:
> > >>
> > >>> Hi Chris,
> > >>>
> > >>> ua-parser-js seems very complete. I'll have into account for my own
> > >>> projects :).
> > >>> Thanks for sharing.
> > >>>
> > >>> El mié., 28 ago. 2019 a las 5:59, Chris Velevitch (<
> > >>> chris.velevi...@gmail.com>) escribió:
> > >>>
> > >>> > On Tue, 27 Aug 2019 at 16:34, Carlos Rovira <
> carlosrov...@apache.org
> > >
> > >>> > wrote:
> > >>> >
> > >>> > > maybe the actual way compiler deal with this is a bit restricted,
> > >>> and we
> > >>> > > can update that part including the 

Build failed in Jenkins: royale-asjs_MXTests #1128

2019-09-06 Thread Apache Royale CI Server
See 


Changes:

[joshtynjala] added RoyaleUnit to release notes for 0.9.6

--
[...truncated 966.80 KB...]
[mxmlc] scanning for overrides: ObjectUtil
[mxmlc] scanning for overrides: SolidBorderUtil
[mxmlc] scanning for overrides: StringTrimmer
[mxmlc] scanning for overrides: StringUtil
[mxmlc] scanning for overrides: Timer
[mxmlc] scanning for overrides: UIUtils
[mxmlc] scanning for overrides: Effect
[mxmlc] scanning for overrides: Transition
[mxmlc] scanning for overrides: IFill
[mxmlc] scanning for overrides: SolidColor
[mxmlc] scanning for overrides: IExternalizable
[mxmlc] scanning for overrides: Proxy
[mxmlc] scanning for overrides: CursorBookmark
[mxmlc] scanning for overrides: ICollectionView
[mxmlc] scanning for overrides: IList
[mxmlc] scanning for overrides: IViewCursor
[mxmlc] scanning for overrides: ListCollectionView
[mxmlc] scanning for overrides: ListCollectionViewCursor
[mxmlc] scanning for overrides: ListCollectionViewBookmark
[mxmlc] scanning for overrides: ArrayCollection
[mxmlc] scanning for overrides: ArrayList
[mxmlc] scanning for overrides: XMLListCollection
[mxmlc] scanning for overrides: CanvasLayout
[mxmlc] scanning for overrides: Flex
[mxmlc] scanning for overrides: BoxDirection
[mxmlc] scanning for overrides: HBox
[mxmlc] scanning for overrides: PanelTitleBar
[mxmlc] scanning for overrides: DataGridColumn
[mxmlc] scanning for overrides: Button
[mxmlc] scanning for overrides: ISelectable
[mxmlc] scanning for overrides: CheckBox
[mxmlc] scanning for overrides: IFocusManagerComponent
[mxmlc] scanning for overrides: ComboBase
[mxmlc] scanning for overrides: ComboBox
[mxmlc] scanning for overrides: ScrollControlBase
[mxmlc] scanning for overrides: ListBase
[mxmlc] scanning for overrides: DataGrid
[mxmlc] scanning for overrides: DateField
[mxmlc] scanning for overrides: Label
[mxmlc] scanning for overrides: List
[mxmlc] scanning for overrides: MenuBar
[mxmlc] scanning for overrides: NumericStepper
[mxmlc] scanning for overrides: RadioButton
[mxmlc] scanning for overrides: RadioButtonGroup
[mxmlc] scanning for overrides: TextArea
[mxmlc] scanning for overrides: ITextInput
[mxmlc] scanning for overrides: TextInput
[mxmlc] scanning for overrides: ITextFieldFactory
[mxmlc] scanning for overrides: Singleton
[mxmlc] scanning for overrides: ItemClickEvent
[mxmlc] scanning for overrides: ListEvent
[mxmlc] scanning for overrides: MenuEvent
[mxmlc] scanning for overrides: MouseEvent
[mxmlc] scanning for overrides: PropertyChangeEventKind
[mxmlc] scanning for overrides: Matrix
[mxmlc] scanning for overrides: Matrix
[mxmlc] scanning for overrides: IFocusManagerComplexComponent
[mxmlc] scanning for overrides: IFocusManagerGroup
[mxmlc] scanning for overrides: IResourceBundle
[mxmlc] scanning for overrides: ResourceManagerImpl
[mxmlc] scanning for overrides: ResourceModuleInfo
[mxmlc] scanning for overrides: ResourceEventDispatcher
[mxmlc] scanning for overrides: ResourceBundleProxy
[mxmlc] scanning for overrides: GroupBase
[mxmlc] scanning for overrides: SkinnableComponent
[mxmlc] scanning for overrides: ButtonBase
[mxmlc] scanning for overrides: Button
[mxmlc] scanning for overrides: ErrorArray
[mxmlc] scanning for overrides: RunCodeEvent
[mxmlc] scanning for overrides: PasswordInputBead
[mxmlc] scanning for overrides: ITileLayout
[mxmlc] scanning for overrides: TileLayout
[mxmlc] scanning for overrides: LocaleUtils
[mxmlc] scanning for overrides: StringPadder
[mxmlc] scanning for overrides: UIDUtil
[mxmlc] scanning for overrides: IStroke
[mxmlc] scanning for overrides: CursorError
[mxmlc] scanning for overrides: SortError
[mxmlc] scanning for overrides: ISort
[mxmlc] scanning for overrides: Sort
[mxmlc] scanning for overrides: IXMLNotifiable
[mxmlc] scanning for overrides: XMLListAdapter
[mxmlc] scanning for overrides: FlexChildInfo
[mxmlc] scanning for overrides: BaseListData
[mxmlc] scanning for overrides: IFactory
[mxmlc] scanning for overrides: IUITextField
[mxmlc] scanning for overrides: UITextField
[mxmlc] scanning for overrides: CollectionEvent
[mxmlc] scanning for overrides: CollectionEventKind
[mxmlc] scanning for overrides: LocaleSorter
[mxmlc] scanning for overrides: LocaleID
[mxmlc] scanning for overrides: LocaleRegistry
[mxmlc] scanning for overrides: ResourceBundle
[mxmlc] scanning for overrides: ArrayUtil
[mxmlc] scanning for overrides: StringUtil
[mxmlc] scanning for overrides: UIDUtil
[mxmlc] scanning for overrides: DataGroup
[mxmlc] scanning 

Jenkins build is back to normal : royale-asjs_jsonly #3510

2019-09-06 Thread Apache Royale CI Server
See 




Re: Testing the npm install error fixes

2019-09-06 Thread OmPrakash Muppirala
Thanks Carlos, this is useful!

Can you send the path for the dependencies.js file you have shown here?

Regards,
Om

On Fri, Sep 6, 2019 at 12:42 AM Carlos Rovira 
wrote:

> Hi,
>
> I'll try to see Om links as I have time. In the mean while here is the log:
>
> https://paste.apache.org/p/pomzf
>
> and dependencies.js
>
> https://paste.apache.org/p/6nu70
>
>
> HTH
>
> Carlos
>
>
>
>
>
>
> El jue., 5 sept. 2019 a las 18:32, OmPrakash Muppirala (<
> bigosma...@apache.org>) escribió:
>
> > If you have to use sudo that usually means that your node/npm is not
> setup
> > correctly.
> >
> > Some more info here :
> >
> https://medium.com/@ExplosionPills/dont-use-sudo-with-npm-still-66e609f5f92
> >
> > https://stackoverflow.com/a/18296178
> >
> > That said, this issue is not related to sudo or otherwise.
> >
> > But it is a good idea to not sudo anything related to npm.  For instance,
> > our installation scripts downloads and does a bunch of things during the
> > installation.  Imagine allowing a random script sudo access to your
> > computer.
> >
> > Thanks,
> > Om
> >
> > On Thu, Sep 5, 2019, 9:00 AM Alex Harui 
> wrote:
> >
> > > Pretty sure if you use -g on MacOS you need sudo.  However, I don't
> think
> > > that's the issue here.
> > > I think Carlos should post his:
> > > - dependencies/download_dependencies.js`
> > > - /Users/carlosrovira/.npm/_logs/2019-09-05T09_39_50_359Z-debug.log
> > >
> > > HTH,
> > > -Alex
> > >
> > > On 9/5/19, 7:28 AM, "OmPrakash Muppirala" 
> wrote:
> > >
> > > And oh, what is your node version?
> > >
> > > On Thu, Sep 5, 2019, 7:27 AM OmPrakash Muppirala <
> > bigosma...@gmail.com
> > > >
> > > wrote:
> > >
> > > > We should never have to install any npm package with sudo.
> > > >
> > > > I will dig deeper into this and see what I can do.
> > > >
> > > > Thanks for testing!
> > > >
> > > > Om
> > > >
> > > >
> > > > On Thu, Sep 5, 2019, 2:41 AM Carlos Rovira <
> > carlosrov...@apache.org>
> > > > wrote:
> > > >
> > > >> Thanks Harbs,
> > > >> that seems not to fix the problem:
> > > >>
> > > >> macbookpro:~ carlosrovira$ sudo npm i
> > > >> @apache-royale/royale-js-swf@0.9.6-beta0 -g
> > > >>
> > > >> Password:
> > > >>
> > > >> /usr/local/bin/asjsc ->
> > > >>
> > > >>
> > >
> >
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/asjscnpm
> > > >>
> > > >> /usr/local/bin/asjscompc ->
> > > >>
> > > >>
> > >
> >
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/asjscompcnpm
> > > >>
> > > >> /usr/local/bin/mxmlc ->
> > > >>
> > > >>
> > >
> >
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/mxmlcnpm
> > > >>
> > > >> /usr/local/bin/asnodec ->
> > > >>
> > > >>
> > >
> >
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/asnodecnpm
> > > >>
> > > >> /usr/local/bin/compc ->
> > > >>
> > > >>
> > >
> >
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/compcnpm
> > > >>
> > > >> /usr/local/bin/externc ->
> > > >>
> > > >>
> > >
> >
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/externcnpm
> > > >>
> > > >>
> > > >> > @apache-royale/royale-js-swf@0.9.6-beta0 postinstall
> > > >> /usr/local/lib/node_modules/@apache-royale/royale-js-swf
> > > >>
> > > >> > node dependencies/download_dependencies.js
> > > >>
> > > >>
> > > >> internal/modules/cjs/loader.js:582
> > > >>
> > > >> throw err;
> > > >>
> > > >> ^
> > > >>
> > > >>
> > > >> Error: Cannot find module
> > > >>
> > > >>
> > >
> >
> '/usr/local/lib/node_modules/@apache-royale/royale-js-swf/dependencies/download_dependencies.js'
> > > >>
> > > >> at Function.Module._resolveFilename
> > > >> (internal/modules/cjs/loader.js:580:15)
> > > >>
> > > >> at Function.Module._load
> > (internal/modules/cjs/loader.js:506:25)
> > > >>
> > > >> at Function.Module.runMain
> > > (internal/modules/cjs/loader.js:741:12)
> > > >>
> > > >> at startup (internal/bootstrap/node.js:285:19)
> > > >>
> > > >> at bootstrapNodeJSCore (internal/bootstrap/node.js:739:3)
> > > >>
> > > >> npm ERR! code ELIFECYCLE
> > > >>
> > > >> npm ERR! errno 1
> > > >>
> > > >> npm ERR! @apache-royale/royale-js-swf@0.9.6-beta0 postinstall:
> > > `node
> > > >> dependencies/download_dependencies.js`
> > > >>
> > > >> npm ERR! Exit status 1
> > > >>
> > > >> npm ERR!
> > > >>
> > > >> npm ERR! Failed at the @apache-royale/royale-js-swf@0.9.6-beta0
> > > >> postinstall
> > > >> script.
> > > >>
> > > >> npm ERR! This is probably not a problem with npm. There is
> likely
> > > >> additional logging output above.
> > 

Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-06 Thread Andrew Wetmore
I have only looked at the top-level release notes and readme files. Should
I wait a day or so before digging down to look at the similar files in
folders?

On Fri, Sep 6, 2019 at 1:45 PM Josh Tynjala 
wrote:

> I just updated the royale-compiler and royale-asjs release notes with the
> things that I worked on. They're in the develop branch for now.
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>
>
> On Fri, Sep 6, 2019 at 9:37 AM Piotr Zarzycki 
> wrote:
>
> > I was thinking about that in a very brave way at the beginning ! I was
> > going to go trough commits from our last 0.9.4 release and prepare nice
> > list for CHANGELOG, but since everything took double time then I assume.
> -
> > It's not going to happen from my sight.
> >
> > On Fri, Sep 6, 2019, 5:13 PM Andrew Wetmore  wrote:
> >
> > > The release notes file doesn't seem to have a section about what's in
> > > 0.9.6, the current release.
> > >
> > > a
> > >
> > > On Fri, Sep 6, 2019 at 11:29 AM Piotr Zarzycki <
> > piotrzarzyck...@gmail.com>
> > > wrote:
> > >
> > > > Hi Carlos,
> > > >
> > > > IT depends on what commit MX is failing. I did branch for this RC
> > couple
> > > of
> > > > days ago. In that time I was seeing some commits to develop related
> to
> > > MX.
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > On Fri, Sep 6, 2019, 4:02 PM Carlos Rovira 
> > > > wrote:
> > > >
> > > > > Hi Piotr,
> > > > >
> > > > > thanks. One question I have is: I think MX Test was failing, does
> it
> > > > > affects the release or are not crucial to get the bits out?
> > > > >
> > > > > Thanks
> > > > >
> > > > > El vie., 6 sept. 2019 a las 13:10, Piotr Zarzycki (<
> > > > > piotrzarzyck...@gmail.com>) escribió:
> > > > >
> > > > > > Hi Guys,
> > > > > >
> > > > > > I have upload manually ant artifacts. Please start reviewing
> stuff.
> > > > What
> > > > > if
> > > > > > vote passes - Should we merge 0.9.6 tag to develop ?
> > > > > >
> > > > > > Thanks,
> > > > > > Piotr
> > > > > >
> > > > > > pt., 6 wrz 2019 o 13:09 Apache Royale CI Server <
> > > > > apacheroyal...@gmail.com>
> > > > > > napisał(a):
> > > > > >
> > > > > > > This is the discussion thread.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Piotr Zarzycki
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > >
> > > > > > Piotr Zarzycki
> > > > > >
> > > > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > > *
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Carlos Rovira
> > > > > http://about.me/carlosrovira
> > > > >
> > > >
> > >
> > >
> > > --
> > > Andrew Wetmore
> > >
> > > http://cottage14.blogspot.com/
> > >
> >
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: Discuss of release steps preparation

2019-09-06 Thread OmPrakash Muppirala
On Fri, Sep 6, 2019 at 3:59 AM Carlos Rovira 
wrote:

> Hi,
>
> maybe is not so bad to end this 0.9.6 manually, since there was many
> progress in that front. Does not need necessarily be "all or nothing". Or
> 100% success.
> Releasing now 0.9.6 can make lower the stress a bit and make a the 0.9.7 in
> few more weeks catch the final problems. As soon as we have this working
> and documentation more polished we can go to 1.0. We can even go from 0.9.7
> to 1.0 without necessarily do releases for 0.9.8 and 0.9.9
>
> just my 2ctns
>

+1

Having gone through the same process unsuccessfully a few months ago, I can
relate to Piotr's state of mind :-)
Let's get through the last bits manually, document what happened and
continue to improve the automated process in the next releases.

Thanks,
Om



>
>
>
> El vie., 6 sept. 2019 a las 11:00, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > Hi Alex,
> >
> > I would love to encourage more people to be RM, but unfortunately my time
> > which I should spend on that release was exceeded at least double. I
> prefer
> > make now manually commit than deal with it - I'm sorry about that.
> >
> > As for console output - you are saying that previous steps matters to
> that
> > one ? I sounds like I should do previous step in the same console window
> > cause it's influences current one.
> >
> > Thanks,
> > Piotr
> >
> > śr., 4 wrz 2019 o 18:52 Alex Harui 
> napisał(a):
> >
> > > Piotr,
> > >
> > > Well, I can't tell you what to do, but if we want to encourage more
> > > frequent releases and more people volunteering to be the RM, at some
> > point,
> > > somebody else besides me has to either create a rather complex
> > step-by-step
> > > manual/runbook or help debug these scripts.  I'm willing to help with
> the
> > > latter, but I cannot without seeing the console output of prior steps.
> > > This is a process or sequence.  The steps you run before matter to the
> > step
> > > you are trying to run now.
> > >
> > > -Alex
> > >
> > > On 9/4/19, 9:19 AM, "Piotr Zarzycki" 
> wrote:
> > >
> > > Hi Alex,
> > >
> > > I know that is the goal, but I simply failed to meet those goals
> and
> > I
> > > gave
> > > up on that. I have artifacts and I would like to release Royale -
> > > that's
> > > may goal, whether I do this in 90% automatically and 10% manually
> > > after so
> > > many hours of work it doesn't matter to me now.
> > >
> > > You are seeing full console output actually. Nothing more happen
> > there.
> > >
> > > Thanks,
> > > Piotr
> > >
> > > śr., 4 wrz 2019 o 18:11 Alex Harui 
> > > napisał(a):
> > >
> > > > Again, the goal is here to debug the scripts, not to skip them.
> > > >
> > > > And it is hard to help without console output to examine.
> > > >
> > > > Yes, you have set the variables, but have the other steps run
> that
> > > > generate an SVN working copy at that destination?  Show the
> console
> > > output
> > > > related to it.
> > > >
> > > > HTH,
> > > > -Alex
> > > >
> > > > On 9/4/19, 9:01 AM, "Piotr Zarzycki" 
> > > wrote:
> > > >
> > > > From that point I will probably upload artifacts manually and
> > > run RC1.
> > > >
> > > > śr., 4 wrz 2019 o 16:30 Piotr Zarzycki <
> > > piotrzarzyck...@gmail.com>
> > > > napisał(a):
> > > >
> > > > > It looks like I have another problems. Target for uploading
> > ant
> > > > artifacts
> > > > > is failing:
> > > > >
> > > > > ant -f releasesteps_asjs.xml Release_Step_013_Upload
> > > > > -Drelease.version=0.9.6 -Drc=1
> > > > >
> > > > > Buildfile:
> > /Users/piotr/Downloads/royale/releasesteps_asjs.xml
> > > > >
> > > > > check-name-and-svn:
> > > > >  [echo] Name: 'Piotr Zarzycki'
> > > > >  [echo] svn.dist.dev:
> > > /Users/piotr/Downloads/royale/dist/dev
> > > > >  [echo] svn.dist.release:
> > > > /Users/piotr/Downloads/royale/dist/release
> > > > >  [echo] svn: /usr/bin/svn
> > > > >
> > > > > BUILD FAILED
> > > > > /Users/piotr/Downloads/royale/releasesteps_asjs.xml:1537:
> The
> > > > svn.dist.dev
> > > > > property is not set to the working copy for
> > > > >
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdevdata=02%7C01%7Caharui%40adobe.com%7C7a223df6f5d4435c17c008d731539953%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637032107443413136sdata=Et8HJHapB3FvMonYzhnsfNoonvUfRd1VNr5GUktMcDs%3Dreserved=0
> > > > .
> > > > >
> > > > > As you can see above I have all properties setup cause I
> made
> > > an
> > > > echo. I
> > > > > don't understand what is happening...
> > > > >
> > > > > Thanks,
> > > > > Piotr
> > > > >
> > > > > śr., 4 wrz 2019 o 13:13 Piotr 

Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-06 Thread Josh Tynjala
I just updated the royale-compiler and royale-asjs release notes with the
things that I worked on. They're in the develop branch for now.

--
Josh Tynjala
Bowler Hat LLC 


On Fri, Sep 6, 2019 at 9:37 AM Piotr Zarzycki 
wrote:

> I was thinking about that in a very brave way at the beginning ! I was
> going to go trough commits from our last 0.9.4 release and prepare nice
> list for CHANGELOG, but since everything took double time then I assume. -
> It's not going to happen from my sight.
>
> On Fri, Sep 6, 2019, 5:13 PM Andrew Wetmore  wrote:
>
> > The release notes file doesn't seem to have a section about what's in
> > 0.9.6, the current release.
> >
> > a
> >
> > On Fri, Sep 6, 2019 at 11:29 AM Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> > wrote:
> >
> > > Hi Carlos,
> > >
> > > IT depends on what commit MX is failing. I did branch for this RC
> couple
> > of
> > > days ago. In that time I was seeing some commits to develop related to
> > MX.
> > >
> > > Thanks,
> > > Piotr
> > >
> > > On Fri, Sep 6, 2019, 4:02 PM Carlos Rovira 
> > > wrote:
> > >
> > > > Hi Piotr,
> > > >
> > > > thanks. One question I have is: I think MX Test was failing, does it
> > > > affects the release or are not crucial to get the bits out?
> > > >
> > > > Thanks
> > > >
> > > > El vie., 6 sept. 2019 a las 13:10, Piotr Zarzycki (<
> > > > piotrzarzyck...@gmail.com>) escribió:
> > > >
> > > > > Hi Guys,
> > > > >
> > > > > I have upload manually ant artifacts. Please start reviewing stuff.
> > > What
> > > > if
> > > > > vote passes - Should we merge 0.9.6 tag to develop ?
> > > > >
> > > > > Thanks,
> > > > > Piotr
> > > > >
> > > > > pt., 6 wrz 2019 o 13:09 Apache Royale CI Server <
> > > > apacheroyal...@gmail.com>
> > > > > napisał(a):
> > > > >
> > > > > > This is the discussion thread.
> > > > > >
> > > > > > Thanks,
> > > > > > Piotr Zarzycki
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > Piotr Zarzycki
> > > > >
> > > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > *
> > > > >
> > > >
> > > >
> > > > --
> > > > Carlos Rovira
> > > > http://about.me/carlosrovira
> > > >
> > >
> >
> >
> > --
> > Andrew Wetmore
> >
> > http://cottage14.blogspot.com/
> >
>


[DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-06 Thread Piotr Zarzycki
I was thinking about that in a very brave way at the beginning ! I was
going to go trough commits from our last 0.9.4 release and prepare nice
list for CHANGELOG, but since everything took double time then I assume. -
It's not going to happen from my sight.

On Fri, Sep 6, 2019, 5:13 PM Andrew Wetmore  wrote:

> The release notes file doesn't seem to have a section about what's in
> 0.9.6, the current release.
>
> a
>
> On Fri, Sep 6, 2019 at 11:29 AM Piotr Zarzycki 
> wrote:
>
> > Hi Carlos,
> >
> > IT depends on what commit MX is failing. I did branch for this RC couple
> of
> > days ago. In that time I was seeing some commits to develop related to
> MX.
> >
> > Thanks,
> > Piotr
> >
> > On Fri, Sep 6, 2019, 4:02 PM Carlos Rovira 
> > wrote:
> >
> > > Hi Piotr,
> > >
> > > thanks. One question I have is: I think MX Test was failing, does it
> > > affects the release or are not crucial to get the bits out?
> > >
> > > Thanks
> > >
> > > El vie., 6 sept. 2019 a las 13:10, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>) escribió:
> > >
> > > > Hi Guys,
> > > >
> > > > I have upload manually ant artifacts. Please start reviewing stuff.
> > What
> > > if
> > > > vote passes - Should we merge 0.9.6 tag to develop ?
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > pt., 6 wrz 2019 o 13:09 Apache Royale CI Server <
> > > apacheroyal...@gmail.com>
> > > > napisał(a):
> > > >
> > > > > This is the discussion thread.
> > > > >
> > > > > Thanks,
> > > > > Piotr Zarzycki
> > > >
> > > >
> > > >
> > > > --
> > > >
> > > > Piotr Zarzycki
> > > >
> > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > *
> > > >
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> >
>
>
> --
> Andrew Wetmore
>
> http://cottage14.blogspot.com/
>


Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-06 Thread Andrew Wetmore
The release notes file doesn't seem to have a section about what's in
0.9.6, the current release.

a

On Fri, Sep 6, 2019 at 11:29 AM Piotr Zarzycki 
wrote:

> Hi Carlos,
>
> IT depends on what commit MX is failing. I did branch for this RC couple of
> days ago. In that time I was seeing some commits to develop related to MX.
>
> Thanks,
> Piotr
>
> On Fri, Sep 6, 2019, 4:02 PM Carlos Rovira 
> wrote:
>
> > Hi Piotr,
> >
> > thanks. One question I have is: I think MX Test was failing, does it
> > affects the release or are not crucial to get the bits out?
> >
> > Thanks
> >
> > El vie., 6 sept. 2019 a las 13:10, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>) escribió:
> >
> > > Hi Guys,
> > >
> > > I have upload manually ant artifacts. Please start reviewing stuff.
> What
> > if
> > > vote passes - Should we merge 0.9.6 tag to develop ?
> > >
> > > Thanks,
> > > Piotr
> > >
> > > pt., 6 wrz 2019 o 13:09 Apache Royale CI Server <
> > apacheroyal...@gmail.com>
> > > napisał(a):
> > >
> > > > This is the discussion thread.
> > > >
> > > > Thanks,
> > > > Piotr Zarzycki
> > >
> > >
> > >
> > > --
> > >
> > > Piotr Zarzycki
> > >
> > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > *
> > >
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


[DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-06 Thread Piotr Zarzycki
Hi Carlos,

IT depends on what commit MX is failing. I did branch for this RC couple of
days ago. In that time I was seeing some commits to develop related to MX.

Thanks,
Piotr

On Fri, Sep 6, 2019, 4:02 PM Carlos Rovira  wrote:

> Hi Piotr,
>
> thanks. One question I have is: I think MX Test was failing, does it
> affects the release or are not crucial to get the bits out?
>
> Thanks
>
> El vie., 6 sept. 2019 a las 13:10, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > Hi Guys,
> >
> > I have upload manually ant artifacts. Please start reviewing stuff. What
> if
> > vote passes - Should we merge 0.9.6 tag to develop ?
> >
> > Thanks,
> > Piotr
> >
> > pt., 6 wrz 2019 o 13:09 Apache Royale CI Server <
> apacheroyal...@gmail.com>
> > napisał(a):
> >
> > > This is the discussion thread.
> > >
> > > Thanks,
> > > Piotr Zarzycki
> >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > *
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


Build failed in Jenkins: royale-asjs_MXTests #1127

2019-09-06 Thread Apache Royale CI Server
See 


--
[...truncated 968.27 KB...]
[mxmlc] scanning for overrides: ObjectUtil
[mxmlc] scanning for overrides: SolidBorderUtil
[mxmlc] scanning for overrides: StringTrimmer
[mxmlc] scanning for overrides: StringUtil
[mxmlc] scanning for overrides: Timer
[mxmlc] scanning for overrides: UIUtils
[mxmlc] scanning for overrides: Effect
[mxmlc] scanning for overrides: Transition
[mxmlc] scanning for overrides: IFill
[mxmlc] scanning for overrides: SolidColor
[mxmlc] scanning for overrides: IExternalizable
[mxmlc] scanning for overrides: Proxy
[mxmlc] scanning for overrides: CursorBookmark
[mxmlc] scanning for overrides: ICollectionView
[mxmlc] scanning for overrides: IList
[mxmlc] scanning for overrides: IViewCursor
[mxmlc] scanning for overrides: ListCollectionView
[mxmlc] scanning for overrides: ListCollectionViewCursor
[mxmlc] scanning for overrides: ListCollectionViewBookmark
[mxmlc] scanning for overrides: ArrayCollection
[mxmlc] scanning for overrides: ArrayList
[mxmlc] scanning for overrides: XMLListCollection
[mxmlc] scanning for overrides: CanvasLayout
[mxmlc] scanning for overrides: Flex
[mxmlc] scanning for overrides: BoxDirection
[mxmlc] scanning for overrides: HBox
[mxmlc] scanning for overrides: PanelTitleBar
[mxmlc] scanning for overrides: DataGridColumn
[mxmlc] scanning for overrides: Button
[mxmlc] scanning for overrides: ISelectable
[mxmlc] scanning for overrides: CheckBox
[mxmlc] scanning for overrides: IFocusManagerComponent
[mxmlc] scanning for overrides: ComboBase
[mxmlc] scanning for overrides: ComboBox
[mxmlc] scanning for overrides: ScrollControlBase
[mxmlc] scanning for overrides: ListBase
[mxmlc] scanning for overrides: DataGrid
[mxmlc] scanning for overrides: DateField
[mxmlc] scanning for overrides: Label
[mxmlc] scanning for overrides: List
[mxmlc] scanning for overrides: MenuBar
[mxmlc] scanning for overrides: NumericStepper
[mxmlc] scanning for overrides: RadioButton
[mxmlc] scanning for overrides: RadioButtonGroup
[mxmlc] scanning for overrides: TextArea
[mxmlc] scanning for overrides: ITextInput
[mxmlc] scanning for overrides: TextInput
[mxmlc] scanning for overrides: ITextFieldFactory
[mxmlc] scanning for overrides: Singleton
[mxmlc] scanning for overrides: ItemClickEvent
[mxmlc] scanning for overrides: ListEvent
[mxmlc] scanning for overrides: MenuEvent
[mxmlc] scanning for overrides: MouseEvent
[mxmlc] scanning for overrides: PropertyChangeEventKind
[mxmlc] scanning for overrides: Matrix
[mxmlc] scanning for overrides: Matrix
[mxmlc] scanning for overrides: IFocusManagerComplexComponent
[mxmlc] scanning for overrides: IFocusManagerGroup
[mxmlc] scanning for overrides: IResourceBundle
[mxmlc] scanning for overrides: ResourceManagerImpl
[mxmlc] scanning for overrides: ResourceModuleInfo
[mxmlc] scanning for overrides: ResourceEventDispatcher
[mxmlc] scanning for overrides: ResourceBundleProxy
[mxmlc] scanning for overrides: GroupBase
[mxmlc] scanning for overrides: SkinnableComponent
[mxmlc] scanning for overrides: ButtonBase
[mxmlc] scanning for overrides: Button
[mxmlc] scanning for overrides: ErrorArray
[mxmlc] scanning for overrides: RunCodeEvent
[mxmlc] scanning for overrides: PasswordInputBead
[mxmlc] scanning for overrides: ITileLayout
[mxmlc] scanning for overrides: TileLayout
[mxmlc] scanning for overrides: LocaleUtils
[mxmlc] scanning for overrides: StringPadder
[mxmlc] scanning for overrides: UIDUtil
[mxmlc] scanning for overrides: IStroke
[mxmlc] scanning for overrides: CursorError
[mxmlc] scanning for overrides: SortError
[mxmlc] scanning for overrides: ISort
[mxmlc] scanning for overrides: Sort
[mxmlc] scanning for overrides: IXMLNotifiable
[mxmlc] scanning for overrides: XMLListAdapter
[mxmlc] scanning for overrides: FlexChildInfo
[mxmlc] scanning for overrides: BaseListData
[mxmlc] scanning for overrides: IFactory
[mxmlc] scanning for overrides: IUITextField
[mxmlc] scanning for overrides: UITextField
[mxmlc] scanning for overrides: CollectionEvent
[mxmlc] scanning for overrides: CollectionEventKind
[mxmlc] scanning for overrides: LocaleSorter
[mxmlc] scanning for overrides: LocaleID
[mxmlc] scanning for overrides: LocaleRegistry
[mxmlc] scanning for overrides: ResourceBundle
[mxmlc] scanning for overrides: ArrayUtil
[mxmlc] scanning for overrides: StringUtil
[mxmlc] scanning for overrides: UIDUtil
[mxmlc] scanning for overrides: DataGroup
[mxmlc] scanning for overrides: LayoutBase
[mxmlc] scanning for overrides: BasicLayout

Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-06 Thread Carlos Rovira
Hi Piotr,

thanks. One question I have is: I think MX Test was failing, does it
affects the release or are not crucial to get the bits out?

Thanks

El vie., 6 sept. 2019 a las 13:10, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> Hi Guys,
>
> I have upload manually ant artifacts. Please start reviewing stuff. What if
> vote passes - Should we merge 0.9.6 tag to develop ?
>
> Thanks,
> Piotr
>
> pt., 6 wrz 2019 o 13:09 Apache Royale CI Server 
> napisał(a):
>
> > This is the discussion thread.
> >
> > Thanks,
> > Piotr Zarzycki
>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>


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


[DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-06 Thread Piotr Zarzycki
Hi Guys,

I have upload manually ant artifacts. Please start reviewing stuff. What if
vote passes - Should we merge 0.9.6 tag to develop ?

Thanks,
Piotr

pt., 6 wrz 2019 o 13:09 Apache Royale CI Server 
napisał(a):

> This is the discussion thread.
>
> Thanks,
> Piotr Zarzycki



-- 

Piotr Zarzycki

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


[VOTE] Release Apache Royale 0.9.6 RC1

2019-09-06 Thread Apache Royale CI Server
Hi,

This is the vote for the 0.9.6 release of Apache Royale.

The release candidate can be found here;
https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc1/

Before voting please review the section,'What are the ASF requirements on
approving a release?', at:
http://www.apache.org/dev/release.html#approving-a-release

At a minimum you would be expected to check that:
- SHA and signed packages are correct
- README, RELEASE_NOTES, NOTICE and LICENSE files are all fine
- That the build script completes successfully
- That you can compile and cross-compile a simple example using the SDK.

The KEYS file is at https://dist.apache.org/repos/dist/release/royale/KEYS

The source package is a combination of the 3 main Royale repos.

To use the binary package, unzip it into a folder.  The -js package is
ready-to-use in an IDE or command-line.  If you need SWF output, use the
-js-swf package and use Apache Ant to run the InstallAdobeSDKs script via:
  ant -f InstallAdobeSDKs.xml

You may also get the binary packages via NPM.  The -js package can be installed 
via:

npm install 
https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc1/binaries/apache-royale-0.9.6-bin-js.tar.gz
 -g

The full package with SWF support can be installed via:

npm install 
https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc1/binaries/apache-royale-0.9.6-bin-js-swf.tar.gz
 -g

Maven artifacts are staged here:
https://repository.apache.org/content/repositories/orgapacheroyale-1053

Please vote to approve this release:
+1 Approve the release
-1 Disapprove the release (please provide specific comments to why)

This vote will be open for 72 hours or until a result can be called.

The vote passes if there is:
- At least 3 +1 votes from the PMC
- More positive votes than negative votes

Remember that this is a 'beta-quality' release so expect there
will be many bugs found.  IMO the goal is not to try to find and fix bugs
in the RC, but to make sure we have the packaging right, and enough
functionality that folks will have some success trying to use it.

People who are not in PMC are also encouraged to test out the release and
vote, although their votes will not be binding, they can influence how the
PMC votes.

When voting please indicate what OS, IDE, Flash Player version and AIR version 
you tested with.

For your convenience, there is an ant script that automates the common steps to 
validate a release.  Instead of individually downloading the package and 
signature files, unzipping, etc, you can instead:
1) create an empty folder,
2) download into that folder this file:
https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc1/ApproveRoyale.xml
3) run the script:
   ant -e -f ApproveRoyale.xml -Drelease.version=0.9.6 -Drc=1
   If you want to test SWF support during the approval, use:
   ant -e -f ApproveRoyale.xml -Drelease.version=0.9.6 -Drc=1 -Duse-flash=true

You are not required to use this script, and more testing of the packages and 
build results are always encouraged.

Please put all discussion about this release in the DISCUSSION thread not this 
VOTE thread.

Thanks,
Piotr Zarzycki

[DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-06 Thread Apache Royale CI Server
This is the discussion thread.

Thanks,
Piotr Zarzycki

[TEST] Release Apache Royale 0.9.6 RC1

2019-09-06 Thread Apache Royale CI Server
Hi,

This is the vote for the 0.9.6 release of Apache Royale.

The release candidate can be found here;
https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc1/

Before voting please review the section,'What are the ASF requirements on
approving a release?', at:
http://www.apache.org/dev/release.html#approving-a-release

At a minimum you would be expected to check that:
- SHA and signed packages are correct
- README, RELEASE_NOTES, NOTICE and LICENSE files are all fine
- That the build script completes successfully
- That you can compile and cross-compile a simple example using the SDK.

The KEYS file is at https://dist.apache.org/repos/dist/release/royale/KEYS

The source package is a combination of the 3 main Royale repos.

To use the binary package, unzip it into a folder.  The -js package is
ready-to-use in an IDE or command-line.  If you need SWF output, use the
-js-swf package and use Apache Ant to run the InstallAdobeSDKs script via:
  ant -f InstallAdobeSDKs.xml

You may also get the binary packages via NPM.  The -js package can be installed 
via:

npm install 
https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc1/binaries/apache-royale-0.9.6-bin-js.tar.gz
 -g

The full package with SWF support can be installed via:

npm install 
https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc1/binaries/apache-royale-0.9.6-bin-js-swf.tar.gz
 -g

Maven artifacts are staged here:
https://repository.apache.org/content/repositories/orgapacheroyale-1053

Please vote to approve this release:
+1 Approve the release
-1 Disapprove the release (please provide specific comments to why)

This vote will be open for 72 hours or until a result can be called.

The vote passes if there is:
- At least 3 +1 votes from the PMC
- More positive votes than negative votes

Remember that this is a 'beta-quality' release so expect there
will be many bugs found.  IMO the goal is not to try to find and fix bugs
in the RC, but to make sure we have the packaging right, and enough
functionality that folks will have some success trying to use it.

People who are not in PMC are also encouraged to test out the release and
vote, although their votes will not be binding, they can influence how the
PMC votes.

When voting please indicate what OS, IDE, Flash Player version and AIR version 
you tested with.

For your convenience, there is an ant script that automates the common steps to 
validate a release.  Instead of individually downloading the package and 
signature files, unzipping, etc, you can instead:
1) create an empty folder,
2) download into that folder this file:
https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc1/ApproveRoyale.xml
3) run the script:
   ant -e -f ApproveRoyale.xml -Drelease.version=0.9.6 -Drc=1
   If you want to test SWF support during the approval, use:
   ant -e -f ApproveRoyale.xml -Drelease.version=0.9.6 -Drc=1 -Duse-flash=true

You are not required to use this script, and more testing of the packages and 
build results are always encouraged.

Please put all discussion about this release in the DISCUSSION thread not this 
VOTE thread.

Thanks,
Piotr Zarzycki

[TEST2] Release Apache Royale 0.9.6 RC1

2019-09-06 Thread Apache Royale CI Server
This is the discussion thread.

Thanks,
Piotr Zarzycki

Re: Discuss of release steps preparation

2019-09-06 Thread Carlos Rovira
Hi,

maybe is not so bad to end this 0.9.6 manually, since there was many
progress in that front. Does not need necessarily be "all or nothing". Or
100% success.
Releasing now 0.9.6 can make lower the stress a bit and make a the 0.9.7 in
few more weeks catch the final problems. As soon as we have this working
and documentation more polished we can go to 1.0. We can even go from 0.9.7
to 1.0 without necessarily do releases for 0.9.8 and 0.9.9

just my 2ctns



El vie., 6 sept. 2019 a las 11:00, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> Hi Alex,
>
> I would love to encourage more people to be RM, but unfortunately my time
> which I should spend on that release was exceeded at least double. I prefer
> make now manually commit than deal with it - I'm sorry about that.
>
> As for console output - you are saying that previous steps matters to that
> one ? I sounds like I should do previous step in the same console window
> cause it's influences current one.
>
> Thanks,
> Piotr
>
> śr., 4 wrz 2019 o 18:52 Alex Harui  napisał(a):
>
> > Piotr,
> >
> > Well, I can't tell you what to do, but if we want to encourage more
> > frequent releases and more people volunteering to be the RM, at some
> point,
> > somebody else besides me has to either create a rather complex
> step-by-step
> > manual/runbook or help debug these scripts.  I'm willing to help with the
> > latter, but I cannot without seeing the console output of prior steps.
> > This is a process or sequence.  The steps you run before matter to the
> step
> > you are trying to run now.
> >
> > -Alex
> >
> > On 9/4/19, 9:19 AM, "Piotr Zarzycki"  wrote:
> >
> > Hi Alex,
> >
> > I know that is the goal, but I simply failed to meet those goals and
> I
> > gave
> > up on that. I have artifacts and I would like to release Royale -
> > that's
> > may goal, whether I do this in 90% automatically and 10% manually
> > after so
> > many hours of work it doesn't matter to me now.
> >
> > You are seeing full console output actually. Nothing more happen
> there.
> >
> > Thanks,
> > Piotr
> >
> > śr., 4 wrz 2019 o 18:11 Alex Harui 
> > napisał(a):
> >
> > > Again, the goal is here to debug the scripts, not to skip them.
> > >
> > > And it is hard to help without console output to examine.
> > >
> > > Yes, you have set the variables, but have the other steps run that
> > > generate an SVN working copy at that destination?  Show the console
> > output
> > > related to it.
> > >
> > > HTH,
> > > -Alex
> > >
> > > On 9/4/19, 9:01 AM, "Piotr Zarzycki" 
> > wrote:
> > >
> > > From that point I will probably upload artifacts manually and
> > run RC1.
> > >
> > > śr., 4 wrz 2019 o 16:30 Piotr Zarzycki <
> > piotrzarzyck...@gmail.com>
> > > napisał(a):
> > >
> > > > It looks like I have another problems. Target for uploading
> ant
> > > artifacts
> > > > is failing:
> > > >
> > > > ant -f releasesteps_asjs.xml Release_Step_013_Upload
> > > > -Drelease.version=0.9.6 -Drc=1
> > > >
> > > > Buildfile:
> /Users/piotr/Downloads/royale/releasesteps_asjs.xml
> > > >
> > > > check-name-and-svn:
> > > >  [echo] Name: 'Piotr Zarzycki'
> > > >  [echo] svn.dist.dev:
> > /Users/piotr/Downloads/royale/dist/dev
> > > >  [echo] svn.dist.release:
> > > /Users/piotr/Downloads/royale/dist/release
> > > >  [echo] svn: /usr/bin/svn
> > > >
> > > > BUILD FAILED
> > > > /Users/piotr/Downloads/royale/releasesteps_asjs.xml:1537: The
> > > svn.dist.dev
> > > > property is not set to the working copy for
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdevdata=02%7C01%7Caharui%40adobe.com%7C7a223df6f5d4435c17c008d731539953%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637032107443413136sdata=Et8HJHapB3FvMonYzhnsfNoonvUfRd1VNr5GUktMcDs%3Dreserved=0
> > > .
> > > >
> > > > As you can see above I have all properties setup cause I made
> > an
> > > echo. I
> > > > don't understand what is happening...
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > śr., 4 wrz 2019 o 13:13 Piotr Zarzycki <
> > piotrzarzyck...@gmail.com>
> > > > napisał(a):
> > > >
> > > >> I was able to produce ant artifacts on Mac! I will try get
> an
> > RC1
> > > today.
> > > >>
> > > >> śr., 4 wrz 2019 o 11:11 Yishay Weiss <
> yishayj...@hotmail.com>
> > > napisał(a):
> > > >>
> > > >>> Here’s what I’ve got.
> > > >>>
> > > >>>
> > > >>>
> > > >>> ANT_HOME
> > > >>>
> > > >>> C:\dev\ant\apache-ant-1.10.1
> > > >>>
> > > >>>
> > > >>>
> > > >>> 

Re: Discuss of release steps preparation

2019-09-06 Thread Piotr Zarzycki
Hi Alex,

I would love to encourage more people to be RM, but unfortunately my time
which I should spend on that release was exceeded at least double. I prefer
make now manually commit than deal with it - I'm sorry about that.

As for console output - you are saying that previous steps matters to that
one ? I sounds like I should do previous step in the same console window
cause it's influences current one.

Thanks,
Piotr

śr., 4 wrz 2019 o 18:52 Alex Harui  napisał(a):

> Piotr,
>
> Well, I can't tell you what to do, but if we want to encourage more
> frequent releases and more people volunteering to be the RM, at some point,
> somebody else besides me has to either create a rather complex step-by-step
> manual/runbook or help debug these scripts.  I'm willing to help with the
> latter, but I cannot without seeing the console output of prior steps.
> This is a process or sequence.  The steps you run before matter to the step
> you are trying to run now.
>
> -Alex
>
> On 9/4/19, 9:19 AM, "Piotr Zarzycki"  wrote:
>
> Hi Alex,
>
> I know that is the goal, but I simply failed to meet those goals and I
> gave
> up on that. I have artifacts and I would like to release Royale -
> that's
> may goal, whether I do this in 90% automatically and 10% manually
> after so
> many hours of work it doesn't matter to me now.
>
> You are seeing full console output actually. Nothing more happen there.
>
> Thanks,
> Piotr
>
> śr., 4 wrz 2019 o 18:11 Alex Harui 
> napisał(a):
>
> > Again, the goal is here to debug the scripts, not to skip them.
> >
> > And it is hard to help without console output to examine.
> >
> > Yes, you have set the variables, but have the other steps run that
> > generate an SVN working copy at that destination?  Show the console
> output
> > related to it.
> >
> > HTH,
> > -Alex
> >
> > On 9/4/19, 9:01 AM, "Piotr Zarzycki" 
> wrote:
> >
> > From that point I will probably upload artifacts manually and
> run RC1.
> >
> > śr., 4 wrz 2019 o 16:30 Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> > napisał(a):
> >
> > > It looks like I have another problems. Target for uploading ant
> > artifacts
> > > is failing:
> > >
> > > ant -f releasesteps_asjs.xml Release_Step_013_Upload
> > > -Drelease.version=0.9.6 -Drc=1
> > >
> > > Buildfile: /Users/piotr/Downloads/royale/releasesteps_asjs.xml
> > >
> > > check-name-and-svn:
> > >  [echo] Name: 'Piotr Zarzycki'
> > >  [echo] svn.dist.dev:
> /Users/piotr/Downloads/royale/dist/dev
> > >  [echo] svn.dist.release:
> > /Users/piotr/Downloads/royale/dist/release
> > >  [echo] svn: /usr/bin/svn
> > >
> > > BUILD FAILED
> > > /Users/piotr/Downloads/royale/releasesteps_asjs.xml:1537: The
> > svn.dist.dev
> > > property is not set to the working copy for
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdevdata=02%7C01%7Caharui%40adobe.com%7C7a223df6f5d4435c17c008d731539953%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637032107443413136sdata=Et8HJHapB3FvMonYzhnsfNoonvUfRd1VNr5GUktMcDs%3Dreserved=0
> > .
> > >
> > > As you can see above I have all properties setup cause I made
> an
> > echo. I
> > > don't understand what is happening...
> > >
> > > Thanks,
> > > Piotr
> > >
> > > śr., 4 wrz 2019 o 13:13 Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> > > napisał(a):
> > >
> > >> I was able to produce ant artifacts on Mac! I will try get an
> RC1
> > today.
> > >>
> > >> śr., 4 wrz 2019 o 11:11 Yishay Weiss 
> > napisał(a):
> > >>
> > >>> Here’s what I’ve got.
> > >>>
> > >>>
> > >>>
> > >>> ANT_HOME
> > >>>
> > >>> C:\dev\ant\apache-ant-1.10.1
> > >>>
> > >>>
> > >>>
> > >>> 
> > >>> From: Piotr Zarzycki 
> > >>> Sent: Wednesday, September 4, 2019 11:56:02 AM
> > >>> To: dev@royale.apache.org 
> > >>> Subject: Re: Discuss of release steps preparation
> > >>>
> > >>> Hi Yishay,
> > >>>
> > >>> It was pretty stupid from my sight. I was certain that I
> have this
> > env
> > >>> variable setup, cause ant is working for me. I have no idea
> how.
> > Let me
> > >>> set
> > >>> it and see whether it help.
> > >>>
> > >>> Thanks,
> > >>> Piotr
> > >>>
> > >>> śr., 4 wrz 2019 o 10:37 Yishay Weiss  >
> > >>> napisał(a):
> > >>>
> > >>> > >
> > >>> >
> > >>>
> >
> 

Re: Testing the npm install error fixes

2019-09-06 Thread Carlos Rovira
Hi,

I'll try to see Om links as I have time. In the mean while here is the log:

https://paste.apache.org/p/pomzf

and dependencies.js

https://paste.apache.org/p/6nu70


HTH

Carlos






El jue., 5 sept. 2019 a las 18:32, OmPrakash Muppirala (<
bigosma...@apache.org>) escribió:

> If you have to use sudo that usually means that your node/npm is not setup
> correctly.
>
> Some more info here :
> https://medium.com/@ExplosionPills/dont-use-sudo-with-npm-still-66e609f5f92
>
> https://stackoverflow.com/a/18296178
>
> That said, this issue is not related to sudo or otherwise.
>
> But it is a good idea to not sudo anything related to npm.  For instance,
> our installation scripts downloads and does a bunch of things during the
> installation.  Imagine allowing a random script sudo access to your
> computer.
>
> Thanks,
> Om
>
> On Thu, Sep 5, 2019, 9:00 AM Alex Harui  wrote:
>
> > Pretty sure if you use -g on MacOS you need sudo.  However, I don't think
> > that's the issue here.
> > I think Carlos should post his:
> > - dependencies/download_dependencies.js`
> > - /Users/carlosrovira/.npm/_logs/2019-09-05T09_39_50_359Z-debug.log
> >
> > HTH,
> > -Alex
> >
> > On 9/5/19, 7:28 AM, "OmPrakash Muppirala"  wrote:
> >
> > And oh, what is your node version?
> >
> > On Thu, Sep 5, 2019, 7:27 AM OmPrakash Muppirala <
> bigosma...@gmail.com
> > >
> > wrote:
> >
> > > We should never have to install any npm package with sudo.
> > >
> > > I will dig deeper into this and see what I can do.
> > >
> > > Thanks for testing!
> > >
> > > Om
> > >
> > >
> > > On Thu, Sep 5, 2019, 2:41 AM Carlos Rovira <
> carlosrov...@apache.org>
> > > wrote:
> > >
> > >> Thanks Harbs,
> > >> that seems not to fix the problem:
> > >>
> > >> macbookpro:~ carlosrovira$ sudo npm i
> > >> @apache-royale/royale-js-swf@0.9.6-beta0 -g
> > >>
> > >> Password:
> > >>
> > >> /usr/local/bin/asjsc ->
> > >>
> > >>
> >
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/asjscnpm
> > >>
> > >> /usr/local/bin/asjscompc ->
> > >>
> > >>
> >
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/asjscompcnpm
> > >>
> > >> /usr/local/bin/mxmlc ->
> > >>
> > >>
> >
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/mxmlcnpm
> > >>
> > >> /usr/local/bin/asnodec ->
> > >>
> > >>
> >
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/asnodecnpm
> > >>
> > >> /usr/local/bin/compc ->
> > >>
> > >>
> >
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/compcnpm
> > >>
> > >> /usr/local/bin/externc ->
> > >>
> > >>
> >
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/externcnpm
> > >>
> > >>
> > >> > @apache-royale/royale-js-swf@0.9.6-beta0 postinstall
> > >> /usr/local/lib/node_modules/@apache-royale/royale-js-swf
> > >>
> > >> > node dependencies/download_dependencies.js
> > >>
> > >>
> > >> internal/modules/cjs/loader.js:582
> > >>
> > >> throw err;
> > >>
> > >> ^
> > >>
> > >>
> > >> Error: Cannot find module
> > >>
> > >>
> >
> '/usr/local/lib/node_modules/@apache-royale/royale-js-swf/dependencies/download_dependencies.js'
> > >>
> > >> at Function.Module._resolveFilename
> > >> (internal/modules/cjs/loader.js:580:15)
> > >>
> > >> at Function.Module._load
> (internal/modules/cjs/loader.js:506:25)
> > >>
> > >> at Function.Module.runMain
> > (internal/modules/cjs/loader.js:741:12)
> > >>
> > >> at startup (internal/bootstrap/node.js:285:19)
> > >>
> > >> at bootstrapNodeJSCore (internal/bootstrap/node.js:739:3)
> > >>
> > >> npm ERR! code ELIFECYCLE
> > >>
> > >> npm ERR! errno 1
> > >>
> > >> npm ERR! @apache-royale/royale-js-swf@0.9.6-beta0 postinstall:
> > `node
> > >> dependencies/download_dependencies.js`
> > >>
> > >> npm ERR! Exit status 1
> > >>
> > >> npm ERR!
> > >>
> > >> npm ERR! Failed at the @apache-royale/royale-js-swf@0.9.6-beta0
> > >> postinstall
> > >> script.
> > >>
> > >> npm ERR! This is probably not a problem with npm. There is likely
> > >> additional logging output above.
> > >>
> > >>
> > >> npm ERR! A complete log of this run can be found in:
> > >>
> > >> npm ERR!
> > >> /Users/carlosrovira/.npm/_logs/2019-09-05T09_39_50_359Z-debug.log
> > >>
> > >> macbookpro:~ carlosrovira$
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> El jue., 5 sept. 2019 a las 11:32, Harbs ( >)
> > >> escribió:
> > >>
> > >> > Try sudo.
> > >> >
> > >> > > On Sep 5, 2019, at 12:24 PM, Carlos Rovira <
> > carlosrov...@apache.org>
> > >> > 

Re: ${body} in index template

2019-09-06 Thread Carlos Rovira
Hi Greg,

so the proposal is to end with:

-body
-application (used for standard Royale apps)
-AppClassName (for Flex emulated apps that will have
"_mx_managers_SystemManager" as part of the string. so this is really
"{application}" + "_mx_managers_SystemManager")

right?

what do you think about

-body
-application
-flexapplication

?

(just trying to have the same style for names and simplifying to something
more human readable)

thanks!


El vie., 6 sept. 2019 a las 5:16, Greg Dove ()
escribió:

> This seems like an easy thing to fix (unless I missed something).
> So I think we just need to decide what the token should be.
>
> What does everyone think of:
> ${AppClassName}
>
> Input welcome...
>
>
>
> On Fri, Sep 6, 2019 at 3:05 PM Greg Dove  wrote:
>
> > It looks like that only works for debug builds because it gets '.min'
> > appended in the release build template.
> > And it seems that MXRoyale Application builds append the system manager
> > part as a variation.
> > So we need a new token probably just for the main class name.
> >
> > For now it is possible to do:
> > ${application}_mx_managers_SystemManager
> > for debug builds of mx apps.
> >
> >
> >
> > On Fri, Sep 6, 2019 at 1:17 PM Greg Dove  wrote:
> >
> >>
> >> Just to add to this thread:
> >>
> >> this type of thing also works if you need the name of the application
> >> injected (which seems quite helpful for injecting into customised
> >> javascript):
> >>
> >> 
> >> // the name of my app is:${application}
> >> 
> >>
> >>
> >> On Wed, Aug 28, 2019 at 8:02 PM Carlos Rovira 
> >> wrote:
> >>
> >>> Hi Chris,
> >>>
> >>> ua-parser-js seems very complete. I'll have into account for my own
> >>> projects :).
> >>> Thanks for sharing.
> >>>
> >>> El mié., 28 ago. 2019 a las 5:59, Chris Velevitch (<
> >>> chris.velevi...@gmail.com>) escribió:
> >>>
> >>> > On Tue, 27 Aug 2019 at 16:34, Carlos Rovira  >
> >>> > wrote:
> >>> >
> >>> > > maybe the actual way compiler deal with this is a bit restricted,
> >>> and we
> >>> > > can update that part including the 

Build failed in Jenkins: royale-asjs_MXTests #1126

2019-09-06 Thread Apache Royale CI Server
See 


--
[...truncated 967.68 KB...]
[mxmlc] scanning for overrides: ObjectUtil
[mxmlc] scanning for overrides: SolidBorderUtil
[mxmlc] scanning for overrides: StringTrimmer
[mxmlc] scanning for overrides: StringUtil
[mxmlc] scanning for overrides: Timer
[mxmlc] scanning for overrides: UIUtils
[mxmlc] scanning for overrides: Effect
[mxmlc] scanning for overrides: Transition
[mxmlc] scanning for overrides: IFill
[mxmlc] scanning for overrides: SolidColor
[mxmlc] scanning for overrides: IExternalizable
[mxmlc] scanning for overrides: Proxy
[mxmlc] scanning for overrides: CursorBookmark
[mxmlc] scanning for overrides: ICollectionView
[mxmlc] scanning for overrides: IList
[mxmlc] scanning for overrides: IViewCursor
[mxmlc] scanning for overrides: ListCollectionView
[mxmlc] scanning for overrides: ListCollectionViewCursor
[mxmlc] scanning for overrides: ListCollectionViewBookmark
[mxmlc] scanning for overrides: ArrayCollection
[mxmlc] scanning for overrides: ArrayList
[mxmlc] scanning for overrides: XMLListCollection
[mxmlc] scanning for overrides: CanvasLayout
[mxmlc] scanning for overrides: Flex
[mxmlc] scanning for overrides: BoxDirection
[mxmlc] scanning for overrides: HBox
[mxmlc] scanning for overrides: PanelTitleBar
[mxmlc] scanning for overrides: DataGridColumn
[mxmlc] scanning for overrides: Button
[mxmlc] scanning for overrides: ISelectable
[mxmlc] scanning for overrides: CheckBox
[mxmlc] scanning for overrides: IFocusManagerComponent
[mxmlc] scanning for overrides: ComboBase
[mxmlc] scanning for overrides: ComboBox
[mxmlc] scanning for overrides: ScrollControlBase
[mxmlc] scanning for overrides: ListBase
[mxmlc] scanning for overrides: DataGrid
[mxmlc] scanning for overrides: DateField
[mxmlc] scanning for overrides: Label
[mxmlc] scanning for overrides: List
[mxmlc] scanning for overrides: MenuBar
[mxmlc] scanning for overrides: NumericStepper
[mxmlc] scanning for overrides: RadioButton
[mxmlc] scanning for overrides: RadioButtonGroup
[mxmlc] scanning for overrides: TextArea
[mxmlc] scanning for overrides: ITextInput
[mxmlc] scanning for overrides: TextInput
[mxmlc] scanning for overrides: ITextFieldFactory
[mxmlc] scanning for overrides: Singleton
[mxmlc] scanning for overrides: ItemClickEvent
[mxmlc] scanning for overrides: ListEvent
[mxmlc] scanning for overrides: MenuEvent
[mxmlc] scanning for overrides: MouseEvent
[mxmlc] scanning for overrides: PropertyChangeEventKind
[mxmlc] scanning for overrides: Matrix
[mxmlc] scanning for overrides: Matrix
[mxmlc] scanning for overrides: IFocusManagerComplexComponent
[mxmlc] scanning for overrides: IFocusManagerGroup
[mxmlc] scanning for overrides: IResourceBundle
[mxmlc] scanning for overrides: ResourceManagerImpl
[mxmlc] scanning for overrides: ResourceModuleInfo
[mxmlc] scanning for overrides: ResourceEventDispatcher
[mxmlc] scanning for overrides: ResourceBundleProxy
[mxmlc] scanning for overrides: GroupBase
[mxmlc] scanning for overrides: SkinnableComponent
[mxmlc] scanning for overrides: ButtonBase
[mxmlc] scanning for overrides: Button
[mxmlc] scanning for overrides: ErrorArray
[mxmlc] scanning for overrides: RunCodeEvent
[mxmlc] scanning for overrides: PasswordInputBead
[mxmlc] scanning for overrides: ITileLayout
[mxmlc] scanning for overrides: TileLayout
[mxmlc] scanning for overrides: LocaleUtils
[mxmlc] scanning for overrides: StringPadder
[mxmlc] scanning for overrides: UIDUtil
[mxmlc] scanning for overrides: IStroke
[mxmlc] scanning for overrides: CursorError
[mxmlc] scanning for overrides: SortError
[mxmlc] scanning for overrides: ISort
[mxmlc] scanning for overrides: Sort
[mxmlc] scanning for overrides: IXMLNotifiable
[mxmlc] scanning for overrides: XMLListAdapter
[mxmlc] scanning for overrides: FlexChildInfo
[mxmlc] scanning for overrides: BaseListData
[mxmlc] scanning for overrides: IFactory
[mxmlc] scanning for overrides: IUITextField
[mxmlc] scanning for overrides: UITextField
[mxmlc] scanning for overrides: CollectionEvent
[mxmlc] scanning for overrides: CollectionEventKind
[mxmlc] scanning for overrides: LocaleSorter
[mxmlc] scanning for overrides: LocaleID
[mxmlc] scanning for overrides: LocaleRegistry
[mxmlc] scanning for overrides: ResourceBundle
[mxmlc] scanning for overrides: ArrayUtil
[mxmlc] scanning for overrides: StringUtil
[mxmlc] scanning for overrides: UIDUtil
[mxmlc] scanning for overrides: DataGroup
[mxmlc] scanning for overrides: LayoutBase
[mxmlc] scanning for overrides: BasicLayout