Build failed in Jenkins: royale-asjs_MXTests #1131

2019-09-07 Thread Apache Royale CI Server
See 


--
[...truncated 968.03 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

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

2019-09-07 Thread Apache Royale CI Server
See 




Re: [royale-compiler] branch develop updated: MemberAccessEmitter: fixed issue where fully-qualified names were emitted as dynamic access with -js-dynamic-access-unknown-members=true

2019-09-07 Thread Alex Harui
Josh,

What is the .factorypath file?  It is in the release package.  Should it even 
be in the repo?

-Alex

On 8/12/19, 11:12 AM, "joshtynj...@apache.org"  wrote:

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

joshtynjala pushed a commit to branch develop
in repository 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitbox.apache.org%2Frepos%2Fasf%2Froyale-compiler.gitdata=02%7C01%7Caharui%40adobe.com%7C8f2fb400e5d54f73082808d71f50a99b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637012303647260983sdata=W79nBsynNmvLQKY1tdcHgbR6K09oo%2FA%2F3z%2BRBb1Iq8E%3Dreserved=0


The following commit(s) were added to refs/heads/develop by this push:
 new f4f9898  MemberAccessEmitter: fixed issue where fully-qualified 
names were emitted as dynamic access with 
-js-dynamic-access-unknown-members=true
f4f9898 is described below

commit f4f9898ad6f94c903615db5bfae691bfaac4a5f3
Author: Josh Tynjala 
AuthorDate: Mon Aug 12 11:12:34 2019 -0700

MemberAccessEmitter: fixed issue where fully-qualified names were 
emitted as dynamic access with -js-dynamic-access-unknown-members=true

Now, if a definition is resolved, and its parent definition is a 
package, just outputs the fully-qualified name instead of walking the full 
chain of member access
---
 .../codegen/js/jx/MemberAccessEmitter.java |  13 ++-
 debugger/.factorypath  | 102 
+
 2 files changed, 111 insertions(+), 4 deletions(-)

diff --git 
a/compiler-jx/src/main/java/org/apache/royale/compiler/internal/codegen/js/jx/MemberAccessEmitter.java
 
b/compiler-jx/src/main/java/org/apache/royale/compiler/internal/codegen/js/jx/MemberAccessEmitter.java
index 741affb..cc0a892 100644
--- 
a/compiler-jx/src/main/java/org/apache/royale/compiler/internal/codegen/js/jx/MemberAccessEmitter.java
+++ 
b/compiler-jx/src/main/java/org/apache/royale/compiler/internal/codegen/js/jx/MemberAccessEmitter.java
@@ -23,6 +23,7 @@ import org.apache.royale.compiler.codegen.ISubEmitter;
 import org.apache.royale.compiler.codegen.js.IJSEmitter;
 import org.apache.royale.compiler.constants.IASLanguageConstants;
 import org.apache.royale.compiler.definitions.IDefinition;
+import org.apache.royale.compiler.definitions.IPackageDefinition;
 import org.apache.royale.compiler.internal.codegen.as.ASEmitterTokens;
 import org.apache.royale.compiler.internal.codegen.js.JSEmitterTokens;
 import org.apache.royale.compiler.internal.codegen.js.JSSubEmitter;
@@ -32,7 +33,6 @@ import 
org.apache.royale.compiler.internal.codegen.js.royale.JSRoyaleEmitterToke
 import 
org.apache.royale.compiler.internal.codegen.js.goog.JSGoogEmitterTokens;
 import 
org.apache.royale.compiler.internal.codegen.js.jx.BinaryOperatorEmitter.DatePropertiesGetters;
 import org.apache.royale.compiler.internal.definitions.AccessorDefinition;
-import 
org.apache.royale.compiler.internal.definitions.AppliedVectorDefinition;
 import org.apache.royale.compiler.internal.definitions.FunctionDefinition;
 import org.apache.royale.compiler.internal.projects.RoyaleJSProject;
 import org.apache.royale.compiler.internal.tree.as.*;
@@ -42,8 +42,6 @@ import org.apache.royale.compiler.tree.as.*;
 import org.apache.royale.compiler.tree.as.IOperatorNode.OperatorType;
 import org.apache.royale.compiler.utils.ASNodeUtils;
 
-import javax.sound.midi.SysexMessage;
-
 public class MemberAccessEmitter extends JSSubEmitter implements
 ISubEmitter
 {
@@ -177,6 +175,13 @@ public class MemberAccessEmitter extends JSSubEmitter 
implements
return;
}
 }
+   else if(def.getParent() instanceof IPackageDefinition)
+   {
+   //this is a fully qualified name, and we should output 
it directly
+   //because we don't want it to be treated as dynamic 
access
+   write(fjs.formatQualifiedName(def.getQualifiedName()));
+   return;
+   }
 else if (def.getParent() != null &&
def.getParent().getQualifiedName().equals("Array"))
 {
@@ -260,7 +265,7 @@ public class MemberAccessEmitter extends JSSubEmitter 
implements
getEmitter().emitClosureEnd(leftNode, def);
}
return;
-   }
+   }
 boolean isCustomNamespace = false;
 if (def instanceof FunctionDefinition && node.getOperator() == 
OperatorType.MEMBER_ACCESS)
isCustomNamespace = 
fjs.isCustomNamespace((FunctionDefinition)def);
diff --git a/debugger/.factorypath b/debugger/.factorypath
new file mode 100644
index 000..2103813
--- 

Re: Heads up on XML

2019-09-07 Thread Greg Dove
Yeah thanks Josh, Alex made a suggestion for that option too, it was the
one I thought I would try first. I hope to get there later today, so I will
see if I can figure that out.


On Sun, Sep 8, 2019 at 7:20 AM Josh Tynjala 
wrote:

> I think the DITA files generated by asdoc are pretty big too, so they're
> probably really useful for your testing.
>
> - Josh
>
> On Friday, September 6, 2019, Greg Dove  wrote:
> > '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.
> >>> >>

Re: Heads up on XML

2019-09-07 Thread Josh Tynjala
I think the DITA files generated by asdoc are pretty big too, so they're
probably really useful for your testing.

- Josh

On Friday, September 6, 2019, Greg Dove  wrote:
> '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 

Re: Discuss of release steps preparation

2019-09-07 Thread Andrew Wetmore
I think the release notes should definitely cover 0.9.6, at least at a high
level. Maybe points like this, if they are true:

   - Compiles faster
   - Many additional components available
   - Emulations of many other components available
   - For applications targeting JavaScript, you can now incorporate the
   vast resources available in existing, free, JavaScript libraries
   - Addition of familiar Flex features like modules
   - Dozens of bugs reported, investigated, and squashed. For details of
   closed bug reports see [link to GitHub bug list]

That would explain to most people why we are so happy to release 0.9.6 and,
in general, what they should be looking for.


On Sat, Sep 7, 2019 at 4:28 AM Piotr Zarzycki 
wrote:

> Hi Alex,
>
> That is only partially true what you are saying. Cause I'm definitely not
> the person, developer who when reaching some wall do not try to resolve it
> on it's own - Not that is not me.
>
> However in case of Royale release it's partially true, but let me explain
> why I asked first rather fix and ask:
>
> Building Royale framework on Windows is extremely long - and this is not
> limitation of my PC - I'm not the only one who experiencing such issue. You
> can definitely imagine that adding one line of echo and rebuild framework
> using releasesteps.xml can be challenge. - waiting 50 minutes. - Yeah I can
> do other stuff during that time, but it is not always possible.
>
> When I switched to Mac - all those problems simply gone. No hang on some
> files, building is two times faster, uploading working. - No problem at
> all.
>
> I simply wanted to count on people who are here, without hesitation ask for
> help even if I'm in a user mode - I'm doing that very rare.
>
> To all of you who are seeing now VOTE thread - please take some time and
> start voting, cause we finally have what we are trying to achieve for so
> many months.
>
> Thanks,
> Piotr
>
> sob., 7 wrz 2019 o 01:14 Alex Harui  napisał(a):
>
> > Those of you in favor of debugging the automation later must volunteer to
> > be the next RMs and do the debugging.
> >
> > Piotr, I'm sorry this effort took longer than expected, but IMO, that's
> > because I apparently could not convince you to take a developer instead
> of
> > user mindset.  By guessing at solutions and not providing console output
> > for others to help with or adding diagnostic output to the scripts,
> several
> > of your attempts failed which took a lot of your time.  I'm pretty sure I
> > said earlier that the release process is not a product developed and
> > maintained by me.  We need other people to be able to maintain and debug
> > Maven and Ant scripts.
> >
> > Similarly, I have not, nor has anyone else, tried a bunch of different
> > runtime configurations.  I don't know what would happen if you use a
> > different console window for each step.  I don't think the previous step
> > leaves environment variables for the next step, but I can't be sure of
> > that.  But the steps do set up files and folders to be used by the next
> > steps.  So if a working copy is not found at the folder specified, the
> > earlier step that tried to establish that working copy needs to be
> examined.
> >
> > Should this release get the votes to go out, the releasecandidate.xml
> > scripts have steps that merge branches and bump version numbers for Ant
> > (Maven should already be bumped).  Personally, I think we need to have
> some
> > sort of updated RELEASE_NOTES file.
> >
> > When I get done with migrating WebService, and fixing any issues with
> > virtual scrolling in ADG I will attempt to run the steps on Windows that
> > failed for Piotr.  But all of you who want to see more releases more
> often
> > need to try to find time to pitch in to improve the process.
> >
> > My 2 cents,
> > -Alex
> >
> > On 9/6/19, 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
> >
> >
> >
> > 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 

Discuss of release steps preparation

2019-09-07 Thread Piotr Zarzycki
Hi Alex,

That is only partially true what you are saying. Cause I'm definitely not
the person, developer who when reaching some wall do not try to resolve it
on it's own - Not that is not me.

However in case of Royale release it's partially true, but let me explain
why I asked first rather fix and ask:

Building Royale framework on Windows is extremely long - and this is not
limitation of my PC - I'm not the only one who experiencing such issue. You
can definitely imagine that adding one line of echo and rebuild framework
using releasesteps.xml can be challenge. - waiting 50 minutes. - Yeah I can
do other stuff during that time, but it is not always possible.

When I switched to Mac - all those problems simply gone. No hang on some
files, building is two times faster, uploading working. - No problem at
all.

I simply wanted to count on people who are here, without hesitation ask for
help even if I'm in a user mode - I'm doing that very rare.

To all of you who are seeing now VOTE thread - please take some time and
start voting, cause we finally have what we are trying to achieve for so
many months.

Thanks,
Piotr

sob., 7 wrz 2019 o 01:14 Alex Harui  napisał(a):

> Those of you in favor of debugging the automation later must volunteer to
> be the next RMs and do the debugging.
>
> Piotr, I'm sorry this effort took longer than expected, but IMO, that's
> because I apparently could not convince you to take a developer instead of
> user mindset.  By guessing at solutions and not providing console output
> for others to help with or adding diagnostic output to the scripts, several
> of your attempts failed which took a lot of your time.  I'm pretty sure I
> said earlier that the release process is not a product developed and
> maintained by me.  We need other people to be able to maintain and debug
> Maven and Ant scripts.
>
> Similarly, I have not, nor has anyone else, tried a bunch of different
> runtime configurations.  I don't know what would happen if you use a
> different console window for each step.  I don't think the previous step
> leaves environment variables for the next step, but I can't be sure of
> that.  But the steps do set up files and folders to be used by the next
> steps.  So if a working copy is not found at the folder specified, the
> earlier step that tried to establish that working copy needs to be examined.
>
> Should this release get the votes to go out, the releasecandidate.xml
> scripts have steps that merge branches and bump version numbers for Ant
> (Maven should already be bumped).  Personally, I think we need to have some
> sort of updated RELEASE_NOTES file.
>
> When I get done with migrating WebService, and fixing any issues with
> virtual scrolling in ADG I will attempt to run the steps on Windows that
> failed for Piotr.  But all of you who want to see more releases more often
> need to try to find time to pitch in to improve the process.
>
> My 2 cents,
> -Alex
>
> On 9/6/19, 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
>
>
>
> 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 

Build failed in Jenkins: royale-asjs_MXTests #1130

2019-09-07 Thread Apache Royale CI Server
See 


--
[...truncated 967.37 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