Build failed in Jenkins: royale-asjs_MXTests #1052

[Apache Royale CI Server]

See 


--
[...truncated 984.19 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
[mxm

Build failed in Jenkins: royale-asjs_MXTests #1051

[Apache Royale CI Server]

See 


--
[...truncated 983.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
[mxm

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

[Apache Royale CI Server]

See 

Re: Discuss of release steps preparation

[Alex Harui]

There are a lot of intelligent things the Maven release plugin does.  One is to 
remove the "SNAPSHOT" from the dependencies in the poms.  So when builds are 
happening in the releases, it should not be using the SNAPSHOT version but 
rather, a release version from somewhere.  It might look in staging, I don't 
really know, but it does seem to find something without SNAPSHOT to use.

-Alex

On 8/13/19, 2:05 PM, "Piotr Zarzycki"  wrote:

Wow that is good point. I think if build of asjs is being done by Maven it
will be taken from 0.9.6-SNAPSHOT I think so. It definitely won't use
staged compiler - You need to point such stuff explicitly using settings.xml

On Tue, Aug 13, 2019, 10:20 PM Alex Harui  wrote:

> I'm not sure you should skip the uploading.  I'm not sure where typedefs
> and asjs will get its compiler artifacts if they haven't been uploaded.
>
> The output says that it is looking in the following folder for artifacts:
>
>
> 
d:\Work\royale-sources\royale-compiler\royale096\sources\royale096\artifacts\archive\target\checkout\release-dir
>
> For me, my temp folder is:
>
>   ~/temp/releasesteps
>
> And the artifacts are in:
>
>   artifacts/archive/target/checkout/release-dir
>
> There seems to be another level in there for you (sources\royale096).
>
> HTH,
> -Alex
>
> On 8/13/19, 11:31 AM, "Piotr Zarzycki"  wrote:
>
> Sorry about that. I was going trough the steps but I have left steps
> for
> signing artifacts and uploading them at the end.
>
> When for all 3 repos I had build, comparison and sign in works I tried
> upload it using provided instructions.
>
> If you are not seeing any suspicious in that log I need to understand
> more
> why actually upload wasn't triggered.
>
> Artifacts were definitely generated correctly.
>
> Thanks,
> Piotr
>
> On Tue, Aug 13, 2019, 5:33 PM Alex Harui 
> wrote:
>
> > I'm not sure what warnings you are referring to.
> >
> > If you look at releasesteps.xml, you can see that it is using 
Maven's
> > wagon:upload goal to upload from a particular folder.  Are there
> jars in
> > that folder (or its subfolders)?  Examine the output of the previous
> Ant
> > release steps for step 003 to see if the source package built
> correctly and
> > binary matched.  If the previous steps were successful then the
> upload
> > should be picking up those artifacts.
> >
> > I'm a bit confused that you got to step 11 according to email but
> now are
> > saying you never got past step 3.
> >
> > Also, I do not recommend using a temporary folder inside your 
working
> > copy.  It will be far safer to specify an absolute path to a folder
> outside
> > of your working copy.  Find a good place to add that to the wiki
> > instructions.
> >
> > HTH,
> > -Alex
> >
> > On 8/13/19, 2:02 AM, "Piotr Zarzycki" 
> wrote:
> >
> > Hi Alex,
> >
> > Thanks for information. I went today trough the steps again. I
> reached
> > point where I'm trying to upload artifacts, but script keep
> saying me
> > that
> > there is nothing to upload. Is it because of those warnings at
> the
> > beginnings ? [1]
> >
> > [1]
> >
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fzvxoi&data=02%7C01%7Caharui%40adobe.com%7C374a24bd51be4c55dbc908d72031fde1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637013271483828790&sdata=xw7LERONoJHq%2FflqQQMXwHTSZ6H9DuF5X1zigCeEygo%3D&reserved=0
> >
> > Thanks,
> > Piotr
> >
> > pon., 12 sie 2019 o 19:31 Alex Harui 
> > napisał(a):
> >
> > > Getting back to this.
> > >
> > > You can start a vote on the results.  If we get this process
> > working, it
> > > should be relatively easy for others to do releases as well so
> we
> > will
> > > hopefully do releases more often and it won't matter if
> someone's
> > recent
> > > changes made it into the RC or not.
> > >
> > > Also, the other committers should be aware that an RC is being
> > created
> > > because they see the emails being sent by the CI server and
> ask the
> > RM to
> > > agree to accept a commit to the release branch instead of the
> develop
> > > branch.
> > >
> > > The only build output I could find on the server for the 7/24
> both
> > show
> > 

Re: Discuss of release steps preparation

[Piotr Zarzycki]

Wow that is good point. I think if build of asjs is being done by Maven it
will be taken from 0.9.6-SNAPSHOT I think so. It definitely won't use
staged compiler - You need to point such stuff explicitly using settings.xml

On Tue, Aug 13, 2019, 10:20 PM Alex Harui  wrote:

> I'm not sure you should skip the uploading.  I'm not sure where typedefs
> and asjs will get its compiler artifacts if they haven't been uploaded.
>
> The output says that it is looking in the following folder for artifacts:
>
>
> d:\Work\royale-sources\royale-compiler\royale096\sources\royale096\artifacts\archive\target\checkout\release-dir
>
> For me, my temp folder is:
>
>   ~/temp/releasesteps
>
> And the artifacts are in:
>
>   artifacts/archive/target/checkout/release-dir
>
> There seems to be another level in there for you (sources\royale096).
>
> HTH,
> -Alex
>
> On 8/13/19, 11:31 AM, "Piotr Zarzycki"  wrote:
>
> Sorry about that. I was going trough the steps but I have left steps
> for
> signing artifacts and uploading them at the end.
>
> When for all 3 repos I had build, comparison and sign in works I tried
> upload it using provided instructions.
>
> If you are not seeing any suspicious in that log I need to understand
> more
> why actually upload wasn't triggered.
>
> Artifacts were definitely generated correctly.
>
> Thanks,
> Piotr
>
> On Tue, Aug 13, 2019, 5:33 PM Alex Harui 
> wrote:
>
> > I'm not sure what warnings you are referring to.
> >
> > If you look at releasesteps.xml, you can see that it is using Maven's
> > wagon:upload goal to upload from a particular folder.  Are there
> jars in
> > that folder (or its subfolders)?  Examine the output of the previous
> Ant
> > release steps for step 003 to see if the source package built
> correctly and
> > binary matched.  If the previous steps were successful then the
> upload
> > should be picking up those artifacts.
> >
> > I'm a bit confused that you got to step 11 according to email but
> now are
> > saying you never got past step 3.
> >
> > Also, I do not recommend using a temporary folder inside your working
> > copy.  It will be far safer to specify an absolute path to a folder
> outside
> > of your working copy.  Find a good place to add that to the wiki
> > instructions.
> >
> > HTH,
> > -Alex
> >
> > On 8/13/19, 2:02 AM, "Piotr Zarzycki" 
> wrote:
> >
> > Hi Alex,
> >
> > Thanks for information. I went today trough the steps again. I
> reached
> > point where I'm trying to upload artifacts, but script keep
> saying me
> > that
> > there is nothing to upload. Is it because of those warnings at
> the
> > beginnings ? [1]
> >
> > [1]
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fzvxoi&data=02%7C01%7Caharui%40adobe.com%7Cf5df4b604e16410f44a808d7201c803a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637013179110163174&sdata=4hzhaPPkBXhC4ACCdnZ1GEym6MRSVVsIhisRLT8vvjs%3D&reserved=0
> >
> > Thanks,
> > Piotr
> >
> > pon., 12 sie 2019 o 19:31 Alex Harui 
> > napisał(a):
> >
> > > Getting back to this.
> > >
> > > You can start a vote on the results.  If we get this process
> > working, it
> > > should be relatively easy for others to do releases as well so
> we
> > will
> > > hopefully do releases more often and it won't matter if
> someone's
> > recent
> > > changes made it into the RC or not.
> > >
> > > Also, the other committers should be aware that an RC is being
> > created
> > > because they see the emails being sent by the CI server and
> ask the
> > RM to
> > > agree to accept a commit to the release branch instead of the
> develop
> > > branch.
> > >
> > > The only build output I could find on the server for the 7/24
> both
> > show
> > > that the date/time given back in step 009 was invalid.  As you
> can
> > see from
> > > the exception, Java is parsing the string and the expectation
> is
> > that the
> > > string you enter conforms to the Java format of:
> > >
> > > MM/dd/yy HH:mm Z
> > >
> > > The documentation for this format is in the Java
> documentation.  As I
> > > explained in an earlier reply, "Z" stands for timezone and you
> must
> > supply
> > > one.  It shouldn't matter which one you supply, I use the one
> I'm
> > in, but
> > > again, the whole point of this exercise is to find bugs and
> improve
> > > documentation of the process.  In your most recent attempt,
> you did
> > not
> > > specify a timezone.  In the one prior, you did not supply a
> year or
> > a space
> > > between date and hour.  Please update the document

Re: Discuss of release steps preparation

[Alex Harui]

I'm not sure you should skip the uploading.  I'm not sure where typedefs and 
asjs will get its compiler artifacts if they haven't been uploaded.

The output says that it is looking in the following folder for artifacts:

d:\Work\royale-sources\royale-compiler\royale096\sources\royale096\artifacts\archive\target\checkout\release-dir

For me, my temp folder is:

  ~/temp/releasesteps

And the artifacts are in:

  artifacts/archive/target/checkout/release-dir

There seems to be another level in there for you (sources\royale096).

HTH,
-Alex

On 8/13/19, 11:31 AM, "Piotr Zarzycki"  wrote:

Sorry about that. I was going trough the steps but I have left steps for
signing artifacts and uploading them at the end.

When for all 3 repos I had build, comparison and sign in works I tried
upload it using provided instructions.

If you are not seeing any suspicious in that log I need to understand more
why actually upload wasn't triggered.

Artifacts were definitely generated correctly.

Thanks,
Piotr

On Tue, Aug 13, 2019, 5:33 PM Alex Harui  wrote:

> I'm not sure what warnings you are referring to.
>
> If you look at releasesteps.xml, you can see that it is using Maven's
> wagon:upload goal to upload from a particular folder.  Are there jars in
> that folder (or its subfolders)?  Examine the output of the previous Ant
> release steps for step 003 to see if the source package built correctly 
and
> binary matched.  If the previous steps were successful then the upload
> should be picking up those artifacts.
>
> I'm a bit confused that you got to step 11 according to email but now are
> saying you never got past step 3.
>
> Also, I do not recommend using a temporary folder inside your working
> copy.  It will be far safer to specify an absolute path to a folder 
outside
> of your working copy.  Find a good place to add that to the wiki
> instructions.
>
> HTH,
> -Alex
>
> On 8/13/19, 2:02 AM, "Piotr Zarzycki"  wrote:
>
> Hi Alex,
>
> Thanks for information. I went today trough the steps again. I reached
> point where I'm trying to upload artifacts, but script keep saying me
> that
> there is nothing to upload. Is it because of those warnings at the
> beginnings ? [1]
>
> [1]
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fzvxoi&data=02%7C01%7Caharui%40adobe.com%7Cf5df4b604e16410f44a808d7201c803a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637013179110163174&sdata=4hzhaPPkBXhC4ACCdnZ1GEym6MRSVVsIhisRLT8vvjs%3D&reserved=0
>
> Thanks,
> Piotr
>
> pon., 12 sie 2019 o 19:31 Alex Harui 
> napisał(a):
>
> > Getting back to this.
> >
> > You can start a vote on the results.  If we get this process
> working, it
> > should be relatively easy for others to do releases as well so we
> will
> > hopefully do releases more often and it won't matter if someone's
> recent
> > changes made it into the RC or not.
> >
> > Also, the other committers should be aware that an RC is being
> created
> > because they see the emails being sent by the CI server and ask the
> RM to
> > agree to accept a commit to the release branch instead of the 
develop
> > branch.
> >
> > The only build output I could find on the server for the 7/24 both
> show
> > that the date/time given back in step 009 was invalid.  As you can
> see from
> > the exception, Java is parsing the string and the expectation is
> that the
> > string you enter conforms to the Java format of:
> >
> > MM/dd/yy HH:mm Z
> >
> > The documentation for this format is in the Java documentation.  As 
I
> > explained in an earlier reply, "Z" stands for timezone and you must
> supply
> > one.  It shouldn't matter which one you supply, I use the one I'm
> in, but
> > again, the whole point of this exercise is to find bugs and improve
> > documentation of the process.  In your most recent attempt, you did
> not
> > specify a timezone.  In the one prior, you did not supply a year or
> a space
> > between date and hour.  Please update the documentation or the
> instructions
> > in the Jenkins jobs to make it more clear that you have to be
> accurate in
> > specifying the date.
> >
> > HTH,
> > -Alex
> >
> > On 7/24/19, 9:01 AM, "Piotr Zarzycki" 
> wrote:
> >
> > Btw. Once I finish steps - Can I publish artefacts and start RC1
> vote
> > on
> > dev ? Does anything I should know at the end which is not
> mention ?
> >
> >
 

Re: Discuss of release steps preparation

[Piotr Zarzycki]

Sorry about that. I was going trough the steps but I have left steps for
signing artifacts and uploading them at the end.

When for all 3 repos I had build, comparison and sign in works I tried
upload it using provided instructions.

If you are not seeing any suspicious in that log I need to understand more
why actually upload wasn't triggered.

Artifacts were definitely generated correctly.

Thanks,
Piotr

On Tue, Aug 13, 2019, 5:33 PM Alex Harui  wrote:

> I'm not sure what warnings you are referring to.
>
> If you look at releasesteps.xml, you can see that it is using Maven's
> wagon:upload goal to upload from a particular folder.  Are there jars in
> that folder (or its subfolders)?  Examine the output of the previous Ant
> release steps for step 003 to see if the source package built correctly and
> binary matched.  If the previous steps were successful then the upload
> should be picking up those artifacts.
>
> I'm a bit confused that you got to step 11 according to email but now are
> saying you never got past step 3.
>
> Also, I do not recommend using a temporary folder inside your working
> copy.  It will be far safer to specify an absolute path to a folder outside
> of your working copy.  Find a good place to add that to the wiki
> instructions.
>
> HTH,
> -Alex
>
> On 8/13/19, 2:02 AM, "Piotr Zarzycki"  wrote:
>
> Hi Alex,
>
> Thanks for information. I went today trough the steps again. I reached
> point where I'm trying to upload artifacts, but script keep saying me
> that
> there is nothing to upload. Is it because of those warnings at the
> beginnings ? [1]
>
> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fzvxoi&data=02%7C01%7Caharui%40adobe.com%7Cc75f329f79784d3203b108d71fcced83%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637012837434994244&sdata=tmu1%2ByeQjPG9mTY%2BnvW6S%2BtLFhFfdAinLqnxLgReKZE%3D&reserved=0
>
> Thanks,
> Piotr
>
> pon., 12 sie 2019 o 19:31 Alex Harui 
> napisał(a):
>
> > Getting back to this.
> >
> > You can start a vote on the results.  If we get this process
> working, it
> > should be relatively easy for others to do releases as well so we
> will
> > hopefully do releases more often and it won't matter if someone's
> recent
> > changes made it into the RC or not.
> >
> > Also, the other committers should be aware that an RC is being
> created
> > because they see the emails being sent by the CI server and ask the
> RM to
> > agree to accept a commit to the release branch instead of the develop
> > branch.
> >
> > The only build output I could find on the server for the 7/24 both
> show
> > that the date/time given back in step 009 was invalid.  As you can
> see from
> > the exception, Java is parsing the string and the expectation is
> that the
> > string you enter conforms to the Java format of:
> >
> > MM/dd/yy HH:mm Z
> >
> > The documentation for this format is in the Java documentation.  As I
> > explained in an earlier reply, "Z" stands for timezone and you must
> supply
> > one.  It shouldn't matter which one you supply, I use the one I'm
> in, but
> > again, the whole point of this exercise is to find bugs and improve
> > documentation of the process.  In your most recent attempt, you did
> not
> > specify a timezone.  In the one prior, you did not supply a year or
> a space
> > between date and hour.  Please update the documentation or the
> instructions
> > in the Jenkins jobs to make it more clear that you have to be
> accurate in
> > specifying the date.
> >
> > HTH,
> > -Alex
> >
> > On 7/24/19, 9:01 AM, "Piotr Zarzycki" 
> wrote:
> >
> > Btw. Once I finish steps - Can I publish artefacts and start RC1
> vote
> > on
> > dev ? Does anything I should know at the end which is not
> mention ?
> >
> >
> > śr., 24 lip 2019 o 17:59 Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> > napisał(a):
> >
> > > By compare to dypedefs step - do you mean that I should look
> into
> > Jenkins
> > > configuration of that steps or something else ?
> > >
> > > śr., 24 lip 2019 o 17:56 Alex Harui 
> > napisał(a):
> > >
> > >> Hi Piotr,
> > >>
> > >> You can compare the output from previous builds and also the
> > typedefs
> > >> build configuration because both successfully used the date
> > format.  The
> > >> Java documentation says that "Z" is for timezone.  It
> shouldn't
> > matter
> > >> which one you use, but in the typedefs you hadn't specified
> one at
> > all.
> > >>
> > >> It looks like in this case extra quotes are wrapped around
> the date.
> > >> You'll have to compare against the typedefs steps to see why
> that's
> > >> happening.
> > >>
> > >> 

Re: Discuss of release steps preparation

[Alex Harui]

I'm not sure what warnings you are referring to.

If you look at releasesteps.xml, you can see that it is using Maven's 
wagon:upload goal to upload from a particular folder.  Are there jars in that 
folder (or its subfolders)?  Examine the output of the previous Ant release 
steps for step 003 to see if the source package built correctly and binary 
matched.  If the previous steps were successful then the upload should be 
picking up those artifacts.

I'm a bit confused that you got to step 11 according to email but now are 
saying you never got past step 3.

Also, I do not recommend using a temporary folder inside your working copy.  It 
will be far safer to specify an absolute path to a folder outside of your 
working copy.  Find a good place to add that to the wiki instructions.

HTH,
-Alex

On 8/13/19, 2:02 AM, "Piotr Zarzycki"  wrote:

Hi Alex,

Thanks for information. I went today trough the steps again. I reached
point where I'm trying to upload artifacts, but script keep saying me that
there is nothing to upload. Is it because of those warnings at the
beginnings ? [1]

[1] 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fzvxoi&data=02%7C01%7Caharui%40adobe.com%7Cc75f329f79784d3203b108d71fcced83%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637012837434994244&sdata=tmu1%2ByeQjPG9mTY%2BnvW6S%2BtLFhFfdAinLqnxLgReKZE%3D&reserved=0

Thanks,
Piotr

pon., 12 sie 2019 o 19:31 Alex Harui  napisał(a):

> Getting back to this.
>
> You can start a vote on the results.  If we get this process working, it
> should be relatively easy for others to do releases as well so we will
> hopefully do releases more often and it won't matter if someone's recent
> changes made it into the RC or not.
>
> Also, the other committers should be aware that an RC is being created
> because they see the emails being sent by the CI server and ask the RM to
> agree to accept a commit to the release branch instead of the develop
> branch.
>
> The only build output I could find on the server for the 7/24 both show
> that the date/time given back in step 009 was invalid.  As you can see 
from
> the exception, Java is parsing the string and the expectation is that the
> string you enter conforms to the Java format of:
>
> MM/dd/yy HH:mm Z
>
> The documentation for this format is in the Java documentation.  As I
> explained in an earlier reply, "Z" stands for timezone and you must supply
> one.  It shouldn't matter which one you supply, I use the one I'm in, but
> again, the whole point of this exercise is to find bugs and improve
> documentation of the process.  In your most recent attempt, you did not
> specify a timezone.  In the one prior, you did not supply a year or a 
space
> between date and hour.  Please update the documentation or the 
instructions
> in the Jenkins jobs to make it more clear that you have to be accurate in
> specifying the date.
>
> HTH,
> -Alex
>
> On 7/24/19, 9:01 AM, "Piotr Zarzycki"  wrote:
>
> Btw. Once I finish steps - Can I publish artefacts and start RC1 vote
> on
> dev ? Does anything I should know at the end which is not mention ?
>
>
> śr., 24 lip 2019 o 17:59 Piotr Zarzycki 
> napisał(a):
>
> > By compare to dypedefs step - do you mean that I should look into
> Jenkins
> > configuration of that steps or something else ?
> >
> > śr., 24 lip 2019 o 17:56 Alex Harui 
> napisał(a):
> >
> >> Hi Piotr,
> >>
> >> You can compare the output from previous builds and also the
> typedefs
> >> build configuration because both successfully used the date
> format.  The
> >> Java documentation says that "Z" is for timezone.  It shouldn't
> matter
> >> which one you use, but in the typedefs you hadn't specified one at
> all.
> >>
> >> It looks like in this case extra quotes are wrapped around the 
date.
> >> You'll have to compare against the typedefs steps to see why that's
> >> happening.
> >>
> >> HTH,
> >> -Alex
> >>
> >> On 7/24/19, 3:53 AM, "Piotr Zarzycki" 
> wrote:
> >>
> >> Hi Alex,
> >>
> >> I was able to overcome issue with date for typedefs. 
Instruction
> >> there is
> >> saying:
> >>
> >> MM/dd/yy HH:mm Z
> >> > Where MM/dd/yy is the US-formatted date and HH:MM is a faked
> time to
> >> > encode the release version such as:
> >> > 2/10/19 9:06 -0800
> >>
> >>
> >> I have typed 7/24/2019 HH (I don't remember what was that) and
> -0800
> >> - This
> >> part I completely do not u

Build failed in Jenkins: royale-asjs_jsonly #3382

[Apache Royale CI Server]

See 


--
[...truncated 159.66 KB...]
   [delete] Deleting directory C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-externc\target

clean:
   [delete] Deleting directory C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler\target

wipe:
   [delete] Deleting directory C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler\lib

clean:

wipe:

thirdparty-clean:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\src\main\resources
 [echo] ROYALE_COMPILER_HOME is ${ROYALE_COMPILER_HOME}
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx

clean:
   [delete] Deleting directory C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\target

clean:

super-clean:

clean:
   [delete] Deleting directory C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\src\test\results

wipe:

clean:
   [delete] Deleting directory C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\flex-compiler-oem\target\classes

wipe:
   [delete] Deleting directory C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\flex-compiler-oem\target

clean:
   [delete] Deleting directory C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\swfutils\target\classes

wipe:
   [delete] Deleting directory C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\swfutils\target

clean:
   [delete] Deleting directory C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\royale-ant-tasks\target

wipe:

clean:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\royaleunit-ant-tasks
 [echo] ROYALE_COMPILER_HOME is ${ROYALE_COMPILER_HOME}
 [echo] ROYALE_COMPILER_HOME is C:\Program Files (x86)\compiler-jx

clean:
   [delete] Deleting directory C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\royaleunit-ant-tasks\target

wipe:

clean:
 [echo] Cleaning out dist dir: C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\debugger/../compiler/lib

clean:
 [echo] Cleaning out generated dir: target/generated-sources/jburg/
 [echo] Cleaning out output dir: C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\debugger/target

stage-source:

clean-temp:
[mkdir] Created dir: 

 [copy] Copying 43 files to 


stage-compiler:
 [copy] Copying 1831 files to 

 [copy] Copying 10 files to 

 [copy] Copying 9 files to 

 [copy] Copying 4 files to 

 [copy] Copying 253 files to 

 [copy] Copying 66 files to 


stage-fb-integration:
 [copy] Copying 243 files to 

 [copy] Copying 101 files to 

 [copy] Copying 152 files to 


stage-ant-tasks:
 [copy] Copying 31 files to 


stage-source-jx:
 [copy] Copying 1 file to 

 [copy] Copying 455 files to 


stage-all:

stage-typedefs:

wipe:
 [echo] swc-date is 08/13/19 12:32 +

wipe:
 [echo] swc-date is 08/13/19 12:32 +

clean:
   [delete] Deleting directory C:\Program Files 
(x86)\Jenkins\workspace\royale-typedefs\GCL\target

wipe:
 [echo] swc-date is 08/13/19 12:32 +

wipe:
 [echo] swc-date is 08/13/19 12:32 +

wipe:
   [delete] Deleting directory C:\Program Files 
(x86)\Jenkins\workspace\roy

Build failed in Jenkins: royale-asjs_MXTests #1050

[Apache Royale CI Server]

:
 [echo] PLAYERGLOBAL_HOME is C:\adobe\flash
 [echo] playerglobal.version is 11.7
 [echo] playerglobal.swc is C:\adobe\flash/11.7/playerglobal.swc

check-air-home:
 [echo] AIR_HOME is C:\adobe\air\4.0\AdobeAIRSDK

check-compiler-home:

check-compile-env:
 [echo] OS: Windows Server 2016 / 10.0 / amd64
 [echo] VM: Java HotSpot(TM) 64-Bit Server VM / 25.152-b16
 [echo] Java: 1.8.0_152
 [echo] Ant: Apache Ant(TM) version 1.9.9 compiled on February 2 2017 Ant 
Java Version: 1.8

thirdparty-downloads:

thirdparty-downloads:

create-description:
 [echo] build.number is 20190813

js-output-royale-description:

swf-js-output-royale-description:

create-config:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/frameworks>

tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/frameworks>

tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/frameworks>

tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/frameworks>

tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/frameworks>

tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/frameworks>

tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/frameworks>

tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/frameworks>

tweak-for-jsonly:

check-typedefs-home:

copy-externs:
 [copy] Copying 9 files to 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/js/libs>

check_jquery:

rename_jquery:

copy-compiler:
 [echo] Copying Compiler from C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler
 [copy] Copying 3 files to 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/lib>
 [echo] Copying Transpiler from C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler
 [copy] Copying 2 files to 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/js/lib>

prebuild:

check-runtime-env:

runtime-setup:

mustella-setup:

clean:
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/mustella.swc>

check-compiler-home:

check-compiler:

BUILD FAILED
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/build.xml>:1412:
 The following error occurred while executing this line:
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/build.xml>:87:
 java.io.FileNotFoundException: JAR entry flexTasks.tasks not found in 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/js/lib/compiler-royaleTasks.jar>
at 
sun.net.www.protocol.jar.JarURLConnection.connect(JarURLConnection.java:144)
at 
sun.net.www.protocol.jar.JarURLConnection.getInputStream(JarURLConnection.java:152)
at java.net.URL.openStream(URL.java:1045)
at 
org.apache.tools.ant.taskdefs.Definer.loadProperties(Definer.java:396)
at org.apache.tools.ant.taskdefs.Definer.execute(Definer.java:264)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:293)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:435)
at org.apache.tools.ant.Target.performTasks(Target.java:456)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1405)
at 
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
at org.apache.tools.ant.Project.executeTargets(Project.java:1260)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:441)
at org.apache.tools.ant.UnknownElement.execute(U

Jenkins build is back to normal : royale-typedefs #1537

[Apache Royale CI Server]

See 

Re: Discuss of release steps preparation

[Piotr Zarzycki]

Hi Alex,

Thanks for information. I went today trough the steps again. I reached
point where I'm trying to upload artifacts, but script keep saying me that
there is nothing to upload. Is it because of those warnings at the
beginnings ? [1]

[1] https://paste.apache.org/zvxoi

Thanks,
Piotr

pon., 12 sie 2019 o 19:31 Alex Harui  napisał(a):

> Getting back to this.
>
> You can start a vote on the results.  If we get this process working, it
> should be relatively easy for others to do releases as well so we will
> hopefully do releases more often and it won't matter if someone's recent
> changes made it into the RC or not.
>
> Also, the other committers should be aware that an RC is being created
> because they see the emails being sent by the CI server and ask the RM to
> agree to accept a commit to the release branch instead of the develop
> branch.
>
> The only build output I could find on the server for the 7/24 both show
> that the date/time given back in step 009 was invalid.  As you can see from
> the exception, Java is parsing the string and the expectation is that the
> string you enter conforms to the Java format of:
>
> MM/dd/yy HH:mm Z
>
> The documentation for this format is in the Java documentation.  As I
> explained in an earlier reply, "Z" stands for timezone and you must supply
> one.  It shouldn't matter which one you supply, I use the one I'm in, but
> again, the whole point of this exercise is to find bugs and improve
> documentation of the process.  In your most recent attempt, you did not
> specify a timezone.  In the one prior, you did not supply a year or a space
> between date and hour.  Please update the documentation or the instructions
> in the Jenkins jobs to make it more clear that you have to be accurate in
> specifying the date.
>
> HTH,
> -Alex
>
> On 7/24/19, 9:01 AM, "Piotr Zarzycki"  wrote:
>
> Btw. Once I finish steps - Can I publish artefacts and start RC1 vote
> on
> dev ? Does anything I should know at the end which is not mention ?
>
>
> śr., 24 lip 2019 o 17:59 Piotr Zarzycki 
> napisał(a):
>
> > By compare to dypedefs step - do you mean that I should look into
> Jenkins
> > configuration of that steps or something else ?
> >
> > śr., 24 lip 2019 o 17:56 Alex Harui 
> napisał(a):
> >
> >> Hi Piotr,
> >>
> >> You can compare the output from previous builds and also the
> typedefs
> >> build configuration because both successfully used the date
> format.  The
> >> Java documentation says that "Z" is for timezone.  It shouldn't
> matter
> >> which one you use, but in the typedefs you hadn't specified one at
> all.
> >>
> >> It looks like in this case extra quotes are wrapped around the date.
> >> You'll have to compare against the typedefs steps to see why that's
> >> happening.
> >>
> >> HTH,
> >> -Alex
> >>
> >> On 7/24/19, 3:53 AM, "Piotr Zarzycki" 
> wrote:
> >>
> >> Hi Alex,
> >>
> >> I was able to overcome issue with date for typedefs. Instruction
> >> there is
> >> saying:
> >>
> >> MM/dd/yy HH:mm Z
> >> > Where MM/dd/yy is the US-formatted date and HH:MM is a faked
> time to
> >> > encode the release version such as:
> >> > 2/10/19 9:06 -0800
> >>
> >>
> >> I have typed 7/24/2019 HH (I don't remember what was that) and
> -0800
> >> - This
> >> part I completely do not understand - what is for there minus ?
> Can
> >> you
> >> send exact example of what I should put there ?
> >>
> >> What's more I have went trough forward and in steps related to
> >> royale-asjs
> >> I see that typing either
> >>
> >> 7/24/19 9:06 -0800 or  just 7/24/19 9:06 causes an exception
> with
> >> following
> >> message:
> >>
> >>
> >> [INFO] COMPC
> >> [INFO] Loading configuration:
> >>
> >>
> C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\frameworks\themes\Jewel-Dark-NoFlat-Emphasized-Yellow-Theme\target\compile-swf-config.xml
> >> [INFO]
> >> [INFO] java.text.ParseException: Unparseable date: ""7/24/19
> 9:06""
> >> [INFO]  at java.text.DateFormat.parse(DateFormat.java:366)
> >> [INFO]  at
> >>
> org.apache.royale.compiler.internal.targets.SWCTarget.processFileEntry(SWCTarget.java:330)
> >> [INFO]  at
> >>
> org.apache.royale.compiler.internal.targets.SWCTarget.addFileEntriesToSWC(SWCTarget.java:291)
> >>
> >> It looks like there are some additional parentheses - Maybe
> it's an
> >> issue.
> >>
> >>
> >> Thanks,
> >>
> >> Piotr
> >>
> >>
> >> wt., 23 lip 2019 o 18:56 Alex Harui 
> >> napisał(a):
> >>
> >> > Hi Piotr,
> >> >
> >> > What differences did you see?  I downloaded the two SWCs and
> the
> >> only
> >> > difference

Build failed in Jenkins: royale-asjs_MXTests #1049

[Apache Royale CI Server]

See 


Changes:

[aharui] need ICollectionView support for selected item in ADG.  Fixes #442

[aharui] changes to support ADG column visibility.  Fixes #446

--
[...truncated 983.54 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 over