date:20190912

Build failed in Jenkins: royale-asjs_MXTests #1148

2019-09-12 Thread Apache Royale CI Server

See 


--
[...truncated 1000.05 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 of release steps preparation

2019-09-12 Thread Alex Harui

I pushed changes to update the config.xml files.  It seemed to work for me.  
Try beta10 if you want to test it.

npm install  @apache-royale/royale-js-swf@0.9.6-beta10 -g

Thanks,
-Alex

On 9/12/19, 10:56 AM, "Alex Harui"  wrote:

I guess that’s expected.  I didn’t realize I had a PLAYERGLOBAL_HOME 
environment variable that was overriding.

The post install script would have to go replace the target-player in every 
-config.xml file (like royale-config.xml).  If you add -target-player=25.0, 
that will get you past it.

Another option is to have the install download 11.1 instead of 25.0.

Thoughts?
-Alex


On 9/12/19, 10:30 AM, "Carlos Rovira"  wrote:

Hi Alex,

I uninstall then install again. Commented all my paths (royale, flash
player, AIR,...) in my .bash_profile. Then open a new terminal window.

Results:

macbookpro:~ carlosrovira$ mxmlc

Using Royale Compiler codebase:

/usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/../..

Using Royale SDK:

/usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/../..

MXMLJSC


+royalelib=/usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/../../frameworks


-sdk-js-lib=/usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/../../frameworks/js/Royale/generated-sources


/usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/frameworks/royale-config.xml(74):
col: 0 Error: unable to open

'/usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/frameworks/libs/player/11.1/playerglobal.swc'.


/usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/frameworks/royale-config.xml
(line: 74)


  




/usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/frameworks/royale-config.xml(129):
col: 0 Error: unable to open

'/usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/frameworks/libs/player/11.1'.


/usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/frameworks/royale-config.xml
(line: 129)


  



0.68472554 seconds

macbookpro:~ carlosrovira$




Hope results are the expected ones :)


Best


Carlos

El jue., 12 sept. 2019 a las 18:46, Alex Harui 
()
escribió:

> Thanks for catching the places where FlexJS was still being used.
>
> Your output indicates that there is a ROYALE_HOME environment 
variable so
> it appears to be using your dev versions since I don't think NPM would
> store its stuff in /Users/carlosrovira/Dev.  Anyway, good to know 
that the
> environment variable can re-direct what the npm scripts do.  If you 
want to
> try without an environment variable that would be a better test of 
what new
> users would experience and the output should reference the npm 
node_modules
> folder.
>
> Thanks,
> -Alex
>
> On 9/12/19, 1:53 AM, "Carlos Rovira"  wrote:
>
> Hi,
>
> think al went fine :)
>
> this is my output:
>
>
> + @apache-royale/royale-js-swf@0.9.6-beta9
>
> added 146 packages from 108 contributors in 426.831s
>
>
>
>
> then I tried "mxmlc" just from command line:
>
>
> macbookpro:~ carlosrovira$ mxmlc
>
> Using Royale Compiler codebase:
> /Users/carlosrovira/Dev/Royale/Source/royale-compiler
>
> Using Royale SDK: 
/Users/carlosrovira/Dev/Royale/Source/royale-asjs
>
> MXMLJSC
>
> 
+royalelib=/Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks
>
>
> 
-sdk-js-lib=/Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/js/Royale/generated-sources
>
> Loading configuration:
>
> 
/Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/royale-config.xml
>
>
> Error: a target file must be specified.
>
>
>
>
> Error: a target file must be specified.
>
>
>
>
> 0.888219402 seconds
>
> macbookpro:~ carlosrovira$
>
>
>
>
> --
> Carlos Rovira
>
>

Re: Discuss of release steps preparation

2019-09-12 Thread Alex Harui

I guess that’s expected.  I didn’t realize I had a PLAYERGLOBAL_HOME 
environment variable that was overriding.

The post install script would have to go replace the target-player in every 
-config.xml file (like royale-config.xml).  If you add -target-player=25.0, 
that will get you past it.

Another option is to have the install download 11.1 instead of 25.0.

Thoughts?
-Alex


On 9/12/19, 10:30 AM, "Carlos Rovira"  wrote:

Hi Alex,

I uninstall then install again. Commented all my paths (royale, flash
player, AIR,...) in my .bash_profile. Then open a new terminal window.

Results:

macbookpro:~ carlosrovira$ mxmlc

Using Royale Compiler codebase:

/usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/../..

Using Royale SDK:

/usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/../..

MXMLJSC


+royalelib=/usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/../../frameworks


-sdk-js-lib=/usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/../../frameworks/js/Royale/generated-sources


/usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/frameworks/royale-config.xml(74):
col: 0 Error: unable to open

'/usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/frameworks/libs/player/11.1/playerglobal.swc'.


/usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/frameworks/royale-config.xml
(line: 74)


  




/usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/frameworks/royale-config.xml(129):
col: 0 Error: unable to open

'/usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/frameworks/libs/player/11.1'.


/usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/frameworks/royale-config.xml
(line: 129)


  



0.68472554 seconds

macbookpro:~ carlosrovira$




Hope results are the expected ones :)


Best


Carlos

El jue., 12 sept. 2019 a las 18:46, Alex Harui ()
escribió:

> Thanks for catching the places where FlexJS was still being used.
>
> Your output indicates that there is a ROYALE_HOME environment variable so
> it appears to be using your dev versions since I don't think NPM would
> store its stuff in /Users/carlosrovira/Dev.  Anyway, good to know that the
> environment variable can re-direct what the npm scripts do.  If you want 
to
> try without an environment variable that would be a better test of what 
new
> users would experience and the output should reference the npm 
node_modules
> folder.
>
> Thanks,
> -Alex
>
> On 9/12/19, 1:53 AM, "Carlos Rovira"  wrote:
>
> Hi,
>
> think al went fine :)
>
> this is my output:
>
>
> + @apache-royale/royale-js-swf@0.9.6-beta9
>
> added 146 packages from 108 contributors in 426.831s
>
>
>
>
> then I tried "mxmlc" just from command line:
>
>
> macbookpro:~ carlosrovira$ mxmlc
>
> Using Royale Compiler codebase:
> /Users/carlosrovira/Dev/Royale/Source/royale-compiler
>
> Using Royale SDK: /Users/carlosrovira/Dev/Royale/Source/royale-asjs
>
> MXMLJSC
>
> 
+royalelib=/Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks
>
>
> 
-sdk-js-lib=/Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/js/Royale/generated-sources
>
> Loading configuration:
>
> 
/Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/royale-config.xml
>
>
> Error: a target file must be specified.
>
>
>
>
> Error: a target file must be specified.
>
>
>
>
> 0.888219402 seconds
>
> macbookpro:~ carlosrovira$
>
>
>
>
> --
> Carlos Rovira
>
> 
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C16ffc0d4285b4f46bd7408d737a6ddaa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637039062136780076sdata=2e1MR6QkJDdOXyF7ybO0dlNjVLjd51TfjmZQYiIk9EY%3Dreserved=0
>
>
>

-- 
Carlos Rovira

https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C16ffc0d4285b4f46bd7408d737a6ddaa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637039062136790069sdata=xUTrtQVQwlHqPbkS7qqRQ68ocgf9BAGi971HLwN0AdE%3Dreserved=0

Re: Discuss of release steps preparation

2019-09-12 Thread Carlos Rovira

Hi Alex,

I uninstall then install again. Commented all my paths (royale, flash
player, AIR,...) in my .bash_profile. Then open a new terminal window.

Results:

macbookpro:~ carlosrovira$ mxmlc

Using Royale Compiler codebase:
/usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/../..

Using Royale SDK:
/usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/../..

MXMLJSC

+royalelib=/usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/../../frameworks

-sdk-js-lib=/usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/../../frameworks/js/Royale/generated-sources

/usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/frameworks/royale-config.xml(74):
col: 0 Error: unable to open
'/usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/frameworks/libs/player/11.1/playerglobal.swc'.

/usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/frameworks/royale-config.xml
(line: 74)


  



/usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/frameworks/royale-config.xml(129):
col: 0 Error: unable to open
'/usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/frameworks/libs/player/11.1'.

/usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/frameworks/royale-config.xml
(line: 129)


  



0.68472554 seconds

macbookpro:~ carlosrovira$




Hope results are the expected ones :)


Best


Carlos

El jue., 12 sept. 2019 a las 18:46, Alex Harui ()
escribió:

> Thanks for catching the places where FlexJS was still being used.
>
> Your output indicates that there is a ROYALE_HOME environment variable so
> it appears to be using your dev versions since I don't think NPM would
> store its stuff in /Users/carlosrovira/Dev.  Anyway, good to know that the
> environment variable can re-direct what the npm scripts do.  If you want to
> try without an environment variable that would be a better test of what new
> users would experience and the output should reference the npm node_modules
> folder.
>
> Thanks,
> -Alex
>
> On 9/12/19, 1:53 AM, "Carlos Rovira"  wrote:
>
> Hi,
>
> think al went fine :)
>
> this is my output:
>
>
> + @apache-royale/royale-js-swf@0.9.6-beta9
>
> added 146 packages from 108 contributors in 426.831s
>
>
>
>
> then I tried "mxmlc" just from command line:
>
>
> macbookpro:~ carlosrovira$ mxmlc
>
> Using Royale Compiler codebase:
> /Users/carlosrovira/Dev/Royale/Source/royale-compiler
>
> Using Royale SDK: /Users/carlosrovira/Dev/Royale/Source/royale-asjs
>
> MXMLJSC
>
> +royalelib=/Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks
>
>
> -sdk-js-lib=/Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/js/Royale/generated-sources
>
> Loading configuration:
>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/royale-config.xml
>
>
> Error: a target file must be specified.
>
>
>
>
> Error: a target file must be specified.
>
>
>
>
> 0.888219402 seconds
>
> macbookpro:~ carlosrovira$
>
>
>
>
> --
> Carlos Rovira
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7Cb54fe685628942737caa08d7375eae53%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637038752101014050sdata=QnUwvb%2FB5tp42EKcRos6x8Qqipwzv5jR91HP6OgA0OE%3Dreserved=0
>
>
>

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

Re: Discuss of release steps preparation

2019-09-12 Thread Alex Harui

Thanks for catching the places where FlexJS was still being used.

Your output indicates that there is a ROYALE_HOME environment variable so it 
appears to be using your dev versions since I don't think NPM would store its 
stuff in /Users/carlosrovira/Dev.  Anyway, good to know that the environment 
variable can re-direct what the npm scripts do.  If you want to try without an 
environment variable that would be a better test of what new users would 
experience and the output should reference the npm node_modules folder.

Thanks,
-Alex

On 9/12/19, 1:53 AM, "Carlos Rovira"  wrote:

Hi,

think al went fine :)

this is my output:


+ @apache-royale/royale-js-swf@0.9.6-beta9

added 146 packages from 108 contributors in 426.831s




then I tried "mxmlc" just from command line:


macbookpro:~ carlosrovira$ mxmlc

Using Royale Compiler codebase:
/Users/carlosrovira/Dev/Royale/Source/royale-compiler

Using Royale SDK: /Users/carlosrovira/Dev/Royale/Source/royale-asjs

MXMLJSC

+royalelib=/Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks


-sdk-js-lib=/Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/js/Royale/generated-sources

Loading configuration:

/Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/royale-config.xml


Error: a target file must be specified.




Error: a target file must be specified.




0.888219402 seconds

macbookpro:~ carlosrovira$




-- 
Carlos Rovira

https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7Cb54fe685628942737caa08d7375eae53%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637038752101014050sdata=QnUwvb%2FB5tp42EKcRos6x8Qqipwzv5jR91HP6OgA0OE%3Dreserved=0

Re: Discuss of release steps preparation

2019-09-12 Thread Josh Tynjala

I installed the npm package on Windows 10 successfully, and I see that
mxmlc, compc, asjsc, asjscompc, and asnodec all seem to be available on my
path, and I can run them.


--
Josh Tynjala
Bowler Hat LLC 


On Thu, Sep 12, 2019 at 1:53 AM Carlos Rovira 
wrote:

> Hi,
>
> think al went fine :)
>
> this is my output:
>
>
> + @apache-royale/royale-js-swf@0.9.6-beta9
>
> added 146 packages from 108 contributors in 426.831s
>
>
>
>
> then I tried "mxmlc" just from command line:
>
>
> macbookpro:~ carlosrovira$ mxmlc
>
> Using Royale Compiler codebase:
> /Users/carlosrovira/Dev/Royale/Source/royale-compiler
>
> Using Royale SDK: /Users/carlosrovira/Dev/Royale/Source/royale-asjs
>
> MXMLJSC
>
> +royalelib=/Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks
>
>
> -sdk-js-lib=/Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/js/Royale/generated-sources
>
> Loading configuration:
>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/royale-config.xml
>
>
> Error: a target file must be specified.
>
>
>
>
> Error: a target file must be specified.
>
>
>
>
> 0.888219402 seconds
>
> macbookpro:~ carlosrovira$
>
>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>

Build failed in Jenkins: royale-asjs_MXTests #1147

2019-09-12 Thread Apache Royale CI Server

See 


--
[...truncated 1001.23 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 of release steps preparation

2019-09-12 Thread Carlos Rovira

Hi,

think al went fine :)

this is my output:


+ @apache-royale/royale-js-swf@0.9.6-beta9

added 146 packages from 108 contributors in 426.831s




then I tried "mxmlc" just from command line:


macbookpro:~ carlosrovira$ mxmlc

Using Royale Compiler codebase:
/Users/carlosrovira/Dev/Royale/Source/royale-compiler

Using Royale SDK: /Users/carlosrovira/Dev/Royale/Source/royale-asjs

MXMLJSC

+royalelib=/Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks

-sdk-js-lib=/Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/js/Royale/generated-sources

Loading configuration:
/Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/royale-config.xml


Error: a target file must be specified.




Error: a target file must be specified.




0.888219402 seconds

macbookpro:~ carlosrovira$




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

Re: Discuss of release steps preparation

2019-09-12 Thread Carlos Rovira

Hi Alex,

I'm trying it.

First thing I notice is the mention to FlexJS here:

prompt: Apache FlexJS includes an optional component set

that uses fonts from designmodo.com.  The font

files are subject to and governed by the

Creative Commons Attribution-NonCommercial-NoDerivs 3.0

Unported license: http://creativecommons.org/licenses/by-nc-nd/3.0/

This license is not compatible with the Apache v2 license.

Do you want to install the designmodo fonts?

This is an optional component (y/n):


I think is not important, but want to let you know so you can change it for
the future.

I continue with the process and report...

Thanks


El jue., 12 sept. 2019 a las 9:36, Alex Harui ()
escribió:

> FWIW, I was able to compile a test app on my Mac.  Testers, please use
> beta9
>
> npm install  @apache-royale/royale-js-swf@0.9.6-beta9 -g
>
> You can tell from the output that, for example, mxmlc is in the path (so
> you can just type 'mxmlc' and not some path to mxmlc in an SDK) and that
> mxmlc then uses the compiler, sdk and config files from wherever
> node_modules is on your computer.
>
> HTH,
> -Alex
>
> On 9/12/19, 12:19 AM, "Piotr Zarzycki"  wrote:
>
> Hi Om,
>
> Cool. I will wait for your sign.
>
> Thanks,
> Piotr
>
> czw., 12 wrz 2019 o 05:33 OmPrakash Muppirala 
> napisał(a):
>
> > Let me do some more testing of the npm flow pls.
> >
> > Thanks,
> > Om
> >
> > On Wed, Sep 11, 2019, 7:04 PM Alex Harui 
> wrote:
> >
> > > I may have fixed the NPM issues.  You can gamble and start the RC
> now or
> > > wait until folks do more testing.
> > >
> > > -Alex
> > >
> > > On 9/9/19, 10:23 PM, "Piotr Zarzycki" 
> > wrote:
> > >
> > > Ok I will wait, but I will at least try to revert changes
> which Maven
> > > did
> > > so I could perform steps properly.
> > >
> > > wt., 10 wrz 2019 o 07:21 Alex Harui 
> > > napisał(a):
> > >
> > > > I'm pretty sure you have to revert the changes made by Maven
> > > otherwise the
> > > > version numbers will be off.  And delete the tags as well.
> The
> > only
> > > thing
> > > > you don't want to do is delete and re-create the release
> branches.
> > > So make
> > > > sure you don't run those Jenkins steps.  I think you have to
> start
> > > with the
> > > > Maven Prepare steps so it creates a new tag for the Perform
> steps.
> > > >
> > > > I just tried Om's NPM changes on MacOS and am having the same
> > > problem as
> > > > Carlos.  IMO, we should hold off on another RC until that is
> > > resolved.
> > > >
> > > > My 2 cents,
> > > > -Alex
> > > >
> > > >
> > > > On 9/9/19, 10:16 PM, "Piotr Zarzycki" <
> piotrzarzyck...@gmail.com>
> > > wrote:
> > > >
> > > > What I understand now is that since I have updated
> release
> > > branches I
> > > > need
> > > > to perform maven artifacts builds, but not only - tag
> for RC1
> > > should be
> > > > changed as well. Probably I need to start perform for
> each
> > > repository
> > > > step
> > > > which creates for me tag, but before this is happening I
> need
> > to
> > > remove
> > > > existing one. Am I right?
> > > >
> > > > wt., 10 wrz 2019 o 07:00 Piotr Zarzycki <
> > > piotrzarzyck...@gmail.com>
> > > > napisał(a):
> > > >
> > > > > Hi Alex,
> > > > >
> > > > > Ok I have updated each branches with newest changes
> from
> > > develop by
> > > > cherry
> > > > > pickup. What actually now ? Should I perform without
> > reverting
> > > > anything ?
> > > > > [1] - I will try that today - it shouldn't break
> anything.
> > > > >
> > > > > [1]
> > > > >
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Steps-Jobs-On-Jenkins%23fail-and-revertdata=02%7C01%7Caharui%40adobe.com%7C3eba0e3d7d634a00e86008d737519189%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637038695797920813sdata=OXNEw1vCD9OAupTOKfs3jOq%2FDR59fmcQhvwGYqBYCno%3Dreserved=0
> > > > >
> > > > >
> > > > > Thanks,
> > > > > Piotr
> > > > >
> > > > > sob., 7 wrz 2019 o 17:51 Alex Harui
>  > >
> > > > napisał(a):
> > > > >
> > > > >> Hi Piotr,
> > > > >>
> > > > >> Sure, time limitations may affect how much
> "development" you
> > > can
> > > > do, but
> > > > >> consider that if everyone ends up taking the same
> approach,
> > > then
> > > > every
> > > > >> future RM is

Re: Discuss of release steps preparation

2019-09-12 Thread Alex Harui

FWIW, I was able to compile a test app on my Mac.  Testers, please use beta9

npm install  @apache-royale/royale-js-swf@0.9.6-beta9 -g

You can tell from the output that, for example, mxmlc is in the path (so you 
can just type 'mxmlc' and not some path to mxmlc in an SDK) and that mxmlc then 
uses the compiler, sdk and config files from wherever node_modules is on your 
computer.

HTH,
-Alex

On 9/12/19, 12:19 AM, "Piotr Zarzycki"  wrote:

Hi Om,

Cool. I will wait for your sign.

Thanks,
Piotr

czw., 12 wrz 2019 o 05:33 OmPrakash Muppirala 
napisał(a):

> Let me do some more testing of the npm flow pls.
>
> Thanks,
> Om
>
> On Wed, Sep 11, 2019, 7:04 PM Alex Harui  wrote:
>
> > I may have fixed the NPM issues.  You can gamble and start the RC now or
> > wait until folks do more testing.
> >
> > -Alex
> >
> > On 9/9/19, 10:23 PM, "Piotr Zarzycki" 
> wrote:
> >
> > Ok I will wait, but I will at least try to revert changes which 
Maven
> > did
> > so I could perform steps properly.
> >
> > wt., 10 wrz 2019 o 07:21 Alex Harui 
> > napisał(a):
> >
> > > I'm pretty sure you have to revert the changes made by Maven
> > otherwise the
> > > version numbers will be off.  And delete the tags as well.  The
> only
> > thing
> > > you don't want to do is delete and re-create the release branches.
> > So make
> > > sure you don't run those Jenkins steps.  I think you have to start
> > with the
> > > Maven Prepare steps so it creates a new tag for the Perform steps.
> > >
> > > I just tried Om's NPM changes on MacOS and am having the same
> > problem as
> > > Carlos.  IMO, we should hold off on another RC until that is
> > resolved.
> > >
> > > My 2 cents,
> > > -Alex
> > >
> > >
> > > On 9/9/19, 10:16 PM, "Piotr Zarzycki" 
> > wrote:
> > >
> > > What I understand now is that since I have updated release
> > branches I
> > > need
> > > to perform maven artifacts builds, but not only - tag for RC1
> > should be
> > > changed as well. Probably I need to start perform for each
> > repository
> > > step
> > > which creates for me tag, but before this is happening I need
> to
> > remove
> > > existing one. Am I right?
> > >
> > > wt., 10 wrz 2019 o 07:00 Piotr Zarzycki <
> > piotrzarzyck...@gmail.com>
> > > napisał(a):
> > >
> > > > Hi Alex,
> > > >
> > > > Ok I have updated each branches with newest changes from
> > develop by
> > > cherry
> > > > pickup. What actually now ? Should I perform without
> reverting
> > > anything ?
> > > > [1] - I will try that today - it shouldn't break anything.
> > > >
> > > > [1]
> > > >
> > >
> >
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Steps-Jobs-On-Jenkins%23fail-and-revertdata=02%7C01%7Caharui%40adobe.com%7C3eba0e3d7d634a00e86008d737519189%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637038695797920813sdata=OXNEw1vCD9OAupTOKfs3jOq%2FDR59fmcQhvwGYqBYCno%3Dreserved=0
> > > >
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > sob., 7 wrz 2019 o 17:51 Alex Harui 
 >
> > > napisał(a):
> > > >
> > > >> Hi Piotr,
> > > >>
> > > >> Sure, time limitations may affect how much "development" 
you
> > can
> > > do, but
> > > >> consider that if everyone ends up taking the same approach,
> > then
> > > every
> > > >> future RM is going to spend time running into these issues,
> > or make
> > > >> mistakes manually uploading the artifacts and cause people
> to
> > spend
> > > time
> > > >> examining more than one release candidate.  This is the key
> > > difference that
> > > >> I am pointing out.  I've definitely seen you work through
> > tough
> > > problems,
> > > >> but most coding issues don't have as much impact on the
> > others on
> > > the team.
> > > >>
> > > >> There is no one right answer to how much sacrifice you
> should
> > make
> > > for
> > > >> the project, but I asked several times for console output
> and
> > never
> > > got
> > > >> it.  It might have been nice for you to report how long
> these
> > steps
> > > took on
> > > >> your Windows computer so future RM's

Re: Discuss of release steps preparation

2019-09-12 Thread Piotr Zarzycki

Hi Om,

Cool. I will wait for your sign.

Thanks,
Piotr

czw., 12 wrz 2019 o 05:33 OmPrakash Muppirala 
napisał(a):

> Let me do some more testing of the npm flow pls.
>
> Thanks,
> Om
>
> On Wed, Sep 11, 2019, 7:04 PM Alex Harui  wrote:
>
> > I may have fixed the NPM issues.  You can gamble and start the RC now or
> > wait until folks do more testing.
> >
> > -Alex
> >
> > On 9/9/19, 10:23 PM, "Piotr Zarzycki" 
> wrote:
> >
> > Ok I will wait, but I will at least try to revert changes which Maven
> > did
> > so I could perform steps properly.
> >
> > wt., 10 wrz 2019 o 07:21 Alex Harui 
> > napisał(a):
> >
> > > I'm pretty sure you have to revert the changes made by Maven
> > otherwise the
> > > version numbers will be off.  And delete the tags as well.  The
> only
> > thing
> > > you don't want to do is delete and re-create the release branches.
> > So make
> > > sure you don't run those Jenkins steps.  I think you have to start
> > with the
> > > Maven Prepare steps so it creates a new tag for the Perform steps.
> > >
> > > I just tried Om's NPM changes on MacOS and am having the same
> > problem as
> > > Carlos.  IMO, we should hold off on another RC until that is
> > resolved.
> > >
> > > My 2 cents,
> > > -Alex
> > >
> > >
> > > On 9/9/19, 10:16 PM, "Piotr Zarzycki" 
> > wrote:
> > >
> > > What I understand now is that since I have updated release
> > branches I
> > > need
> > > to perform maven artifacts builds, but not only - tag for RC1
> > should be
> > > changed as well. Probably I need to start perform for each
> > repository
> > > step
> > > which creates for me tag, but before this is happening I need
> to
> > remove
> > > existing one. Am I right?
> > >
> > > wt., 10 wrz 2019 o 07:00 Piotr Zarzycki <
> > piotrzarzyck...@gmail.com>
> > > napisał(a):
> > >
> > > > Hi Alex,
> > > >
> > > > Ok I have updated each branches with newest changes from
> > develop by
> > > cherry
> > > > pickup. What actually now ? Should I perform without
> reverting
> > > anything ?
> > > > [1] - I will try that today - it shouldn't break anything.
> > > >
> > > > [1]
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Steps-Jobs-On-Jenkins%23fail-and-revertdata=02%7C01%7Caharui%40adobe.com%7Ca3ef8d389f7e4f6ff40508d735af0d80%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637036898328967212sdata=6mHpIj33OvwPYqn2NZKEj8Gn2nUHpx0Nt3dOZKRqAGU%3Dreserved=0
> > > >
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > sob., 7 wrz 2019 o 17:51 Alex Harui  >
> > > napisał(a):
> > > >
> > > >> Hi Piotr,
> > > >>
> > > >> Sure, time limitations may affect how much "development" you
> > can
> > > do, but
> > > >> consider that if everyone ends up taking the same approach,
> > then
> > > every
> > > >> future RM is going to spend time running into these issues,
> > or make
> > > >> mistakes manually uploading the artifacts and cause people
> to
> > spend
> > > time
> > > >> examining more than one release candidate.  This is the key
> > > difference that
> > > >> I am pointing out.  I've definitely seen you work through
> > tough
> > > problems,
> > > >> but most coding issues don't have as much impact on the
> > others on
> > > the team.
> > > >>
> > > >> There is no one right answer to how much sacrifice you
> should
> > make
> > > for
> > > >> the project, but I asked several times for console output
> and
> > never
> > > got
> > > >> it.  It might have been nice for you to report how long
> these
> > steps
> > > took on
> > > >> your Windows computer so future RM's could plan ahead or we
> > could
> > > >> investigate optimizations or breaking steps into other
> > pieces.  Now
> > > the
> > > >> next RM will have the responsibility for experiencing these
> > long
> > > builds and
> > > >> sharing that information.
> > > >>
> > > >> Regarding the current RC, I will try it later today, but I
> > agree
> > > with
> > > >> Andrew Wetmore that we need to have current RELEASE_NOTES,
> so
> > this
> > > RC
> > > >> should not be the one released, but I will run other checks
> > on it
> > > to see if
> > > >> there are other issues.  Andrew's proposal for the release
> > notes
> > > sounds
> > > >> good to me so he or you should commit it to the release
> branch
> > > along with
> > > >> the link I used in prior release notes that point to our
> wiki.
> > > That way we
> > > >> can note other things later.
> >

Build failed in Jenkins: royale-asjs_MXTests #1146

2019-09-12 Thread Apache Royale CI Server

See 


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

Build failed in Jenkins: royale-asjs_MXTests #1148

Re: Discuss of release steps preparation

Re: Discuss of release steps preparation

Re: Discuss of release steps preparation

Re: Discuss of release steps preparation

Re: Discuss of release steps preparation

Build failed in Jenkins: royale-asjs_MXTests #1147

Re: Discuss of release steps preparation

Re: Discuss of release steps preparation

Re: Discuss of release steps preparation

Re: Discuss of release steps preparation

Build failed in Jenkins: royale-asjs_MXTests #1146

12 matches

Site Navigation

Mail list logo

Footer information