Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-17 Thread Piotr Zarzycki
I'm going to push fixes for release steps script today and make RC2. If I
figure out how to export gpg KEY in a proper format as it is in KEYS file I
will update them as well - if not people can use Josh's way of getting my
key for now.

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

> I assume that wasn't the whole log.  I think we want to see the part where
> it builds Core, we only see the last bit of Core.  Core looks like it
> thought it was in js-only config and didn't build a swf swc and/or Binding
> thinks it is building swf swcs and is looking for Core's swf swc.
>
> FWIW, I am having a bunch of other build issues related to js-only for Ant
> for the ASDoc example.  It worked in the past because I still had
> PLAYERGLOBAL_HOME set in the environment, but when I took that away a bunch
> of new things cropped up.  Could be a  day or two of work.  We could still
> approve the release and folks who want js-only will have to not build ASDoc.
>
> -Alex
>
> On 9/17/19, 8:59 PM, "Piotr Zarzycki"  wrote:
>
> Hi Josh,
>
> Do you have in your Maven config setup link to Maven artifacts? Cause
> error
> is saying that it was attempt of downloading them from Snapshot.
> However
> Core build successfully, so I'm a bit confused.
>
> Thanks,
> Piotr
>
> On Tue, Sep 17, 2019, 11:47 PM Josh Tynjala  >
> wrote:
>
> > Unfortunately, I'm seeing that the Maven part of ApproveRoyale is
> failing
> > too. Here's the end of my console output:
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F83mivdata=02%7C01%7Caharui%40adobe.com%7C5418ae5d4cb94b454ab208d73beca2c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637043759850631985sdata=j%2FYDlKQ7Tx54p2PJfg2tEoGg2I5Mi19BMB5fFcZcKy4%3Dreserved=0
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7C5418ae5d4cb94b454ab208d73beca2c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637043759850631985sdata=%2BTdmGXZr5uiQaJ36dU8QeOQLGIpR8adX5ktk8%2FRo8ME%3Dreserved=0
> >
> >
> >
> > On Tue, Sep 17, 2019 at 2:22 PM Josh Tynjala <
> joshtynj...@bowlerhat.dev>
> > wrote:
> >
> > > Getting the following error when running the ApproveRoyale ant
> script...
> > >
> > > Error: unable to open
> > >
> >
> '/Users/joshtynjala/Desktop/royale/apache-royale-0.9.6-src/royale-asjs/examples/royale/CreditCardValidatorExample/src/main/royale/App.mxml'.
> > >
> > > Seems to be caused by this line in build.xml from
> > > CreditCardValidatorExample:
> > >
> > > 
> > >
> > > There is no App.mxml, but there is a
> CreditCardValidatorExample.mxml, so
> > I
> > > think that the value is supposed to be "CreditCardValidatorExample"
> > instead:
> > >
> > > 
> > >
> > > I just pushed a commit to develop to fix that for the next release.
> > >
> > > I will locally adjust ApproveRoyale to skip the examples and
> finish the
> > > rest of the approval process. Assuming that everything else
> completes
> > > successfully, a broken example build script is not enough to
> prevent me
> > > from approving this release candidate.
> > >
> > > --
> > > Josh Tynjala
> > > Bowler Hat LLC <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7C5418ae5d4cb94b454ab208d73beca2c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637043759850631985sdata=%2BTdmGXZr5uiQaJ36dU8QeOQLGIpR8adX5ktk8%2FRo8ME%3Dreserved=0
> >
> > >
> > >
> > > On Tue, Sep 17, 2019 at 6:43 AM Apache Royale CI Server <
> > > apacheroyal...@gmail.com> wrote:
> > >
> > >> This is the discussion thread.
> > >>
> > >> Thanks,
> > >> Piotr
> > >
> > >
> >
>
>
>

-- 

Piotr Zarzycki

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


Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-17 Thread Alex Harui
I assume that wasn't the whole log.  I think we want to see the part where it 
builds Core, we only see the last bit of Core.  Core looks like it thought it 
was in js-only config and didn't build a swf swc and/or Binding thinks it is 
building swf swcs and is looking for Core's swf swc.

FWIW, I am having a bunch of other build issues related to js-only for Ant for 
the ASDoc example.  It worked in the past because I still had PLAYERGLOBAL_HOME 
set in the environment, but when I took that away a bunch of new things cropped 
up.  Could be a  day or two of work.  We could still approve the release and 
folks who want js-only will have to not build ASDoc.

-Alex

On 9/17/19, 8:59 PM, "Piotr Zarzycki"  wrote:

Hi Josh,

Do you have in your Maven config setup link to Maven artifacts? Cause error
is saying that it was attempt of downloading them from Snapshot. However
Core build successfully, so I'm a bit confused.

Thanks,
Piotr

On Tue, Sep 17, 2019, 11:47 PM Josh Tynjala 
wrote:

> Unfortunately, I'm seeing that the Maven part of ApproveRoyale is failing
> too. Here's the end of my console output:
>
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F83mivdata=02%7C01%7Caharui%40adobe.com%7C5418ae5d4cb94b454ab208d73beca2c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637043759850631985sdata=j%2FYDlKQ7Tx54p2PJfg2tEoGg2I5Mi19BMB5fFcZcKy4%3Dreserved=0
>
> --
> Josh Tynjala
> Bowler Hat LLC 

>
>
> On Tue, Sep 17, 2019 at 2:22 PM Josh Tynjala 
> wrote:
>
> > Getting the following error when running the ApproveRoyale ant script...
> >
> > Error: unable to open
> >
> 
'/Users/joshtynjala/Desktop/royale/apache-royale-0.9.6-src/royale-asjs/examples/royale/CreditCardValidatorExample/src/main/royale/App.mxml'.
> >
> > Seems to be caused by this line in build.xml from
> > CreditCardValidatorExample:
> >
> > 
> >
> > There is no App.mxml, but there is a CreditCardValidatorExample.mxml, so
> I
> > think that the value is supposed to be "CreditCardValidatorExample"
> instead:
> >
> > 
> >
> > I just pushed a commit to develop to fix that for the next release.
> >
> > I will locally adjust ApproveRoyale to skip the examples and finish the
> > rest of the approval process. Assuming that everything else completes
> > successfully, a broken example build script is not enough to prevent me
> > from approving this release candidate.
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC 

> >
> >
> > On Tue, Sep 17, 2019 at 6:43 AM Apache Royale CI Server <
> > apacheroyal...@gmail.com> wrote:
> >
> >> This is the discussion thread.
> >>
> >> Thanks,
> >> Piotr
> >
> >
>




Build failed in Jenkins: royale-asjs_MXTests #1162

2019-09-17 Thread Apache Royale CI Server
See 


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

[DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-17 Thread Piotr Zarzycki
Hi Josh,

Do you have in your Maven config setup link to Maven artifacts? Cause error
is saying that it was attempt of downloading them from Snapshot. However
Core build successfully, so I'm a bit confused.

Thanks,
Piotr

On Tue, Sep 17, 2019, 11:47 PM Josh Tynjala 
wrote:

> Unfortunately, I'm seeing that the Maven part of ApproveRoyale is failing
> too. Here's the end of my console output:
>
> https://paste.apache.org/83miv
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>
>
> On Tue, Sep 17, 2019 at 2:22 PM Josh Tynjala 
> wrote:
>
> > Getting the following error when running the ApproveRoyale ant script...
> >
> > Error: unable to open
> >
> '/Users/joshtynjala/Desktop/royale/apache-royale-0.9.6-src/royale-asjs/examples/royale/CreditCardValidatorExample/src/main/royale/App.mxml'.
> >
> > Seems to be caused by this line in build.xml from
> > CreditCardValidatorExample:
> >
> > 
> >
> > There is no App.mxml, but there is a CreditCardValidatorExample.mxml, so
> I
> > think that the value is supposed to be "CreditCardValidatorExample"
> instead:
> >
> > 
> >
> > I just pushed a commit to develop to fix that for the next release.
> >
> > I will locally adjust ApproveRoyale to skip the examples and finish the
> > rest of the approval process. Assuming that everything else completes
> > successfully, a broken example build script is not enough to prevent me
> > from approving this release candidate.
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC 
> >
> >
> > On Tue, Sep 17, 2019 at 6:43 AM Apache Royale CI Server <
> > apacheroyal...@gmail.com> wrote:
> >
> >> This is the discussion thread.
> >>
> >> Thanks,
> >> Piotr
> >
> >
>


Build failed in Jenkins: royale-asjs_MXTests #1161

2019-09-17 Thread Apache Royale CI Server
See 


Changes:

[joshtynjala] CreditCardValidatorExample: fixed build script

--
[...truncated 1000.13 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] 

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

2019-09-17 Thread Apache Royale CI Server
See 




Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-17 Thread Josh Tynjala
Unfortunately, I'm seeing that the Maven part of ApproveRoyale is failing
too. Here's the end of my console output:

https://paste.apache.org/83miv

--
Josh Tynjala
Bowler Hat LLC 


On Tue, Sep 17, 2019 at 2:22 PM Josh Tynjala 
wrote:

> Getting the following error when running the ApproveRoyale ant script...
>
> Error: unable to open
> '/Users/joshtynjala/Desktop/royale/apache-royale-0.9.6-src/royale-asjs/examples/royale/CreditCardValidatorExample/src/main/royale/App.mxml'.
>
> Seems to be caused by this line in build.xml from
> CreditCardValidatorExample:
>
> 
>
> There is no App.mxml, but there is a CreditCardValidatorExample.mxml, so I
> think that the value is supposed to be "CreditCardValidatorExample" instead:
>
> 
>
> I just pushed a commit to develop to fix that for the next release.
>
> I will locally adjust ApproveRoyale to skip the examples and finish the
> rest of the approval process. Assuming that everything else completes
> successfully, a broken example build script is not enough to prevent me
> from approving this release candidate.
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>
>
> On Tue, Sep 17, 2019 at 6:43 AM Apache Royale CI Server <
> apacheroyal...@gmail.com> wrote:
>
>> This is the discussion thread.
>>
>> Thanks,
>> Piotr
>
>


Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-17 Thread Josh Tynjala
I'd rather not accidentally commit something to a release branch that
shouldn't go there, so to stay safe, I'll keep committing to develop first.
We can always cherry pick if needed.

--
Josh Tynjala
Bowler Hat LLC 


On Tue, Sep 17, 2019 at 2:29 PM Alex Harui  wrote:

> Hmm.  I thought I'd fixed that.  I swear I had all examples building.
>
> Anyway, fixes like these should be going in the release branch, not
> develop, IMO.
>
> Thanks,
> -Alex
>
> On 9/17/19, 2:22 PM, "Josh Tynjala"  wrote:
>
> Getting the following error when running the ApproveRoyale ant
> script...
>
> Error: unable to open
>
> '/Users/joshtynjala/Desktop/royale/apache-royale-0.9.6-src/royale-asjs/examples/royale/CreditCardValidatorExample/src/main/royale/App.mxml'.
>
> Seems to be caused by this line in build.xml from
> CreditCardValidatorExample:
>
> 
>
> There is no App.mxml, but there is a CreditCardValidatorExample.mxml,
> so I
> think that the value is supposed to be "CreditCardValidatorExample"
> instead:
>
> 
>
> I just pushed a commit to develop to fix that for the next release.
>
> I will locally adjust ApproveRoyale to skip the examples and finish the
> rest of the approval process. Assuming that everything else completes
> successfully, a broken example build script is not enough to prevent me
> from approving this release candidate.
>
> --
> Josh Tynjala
> Bowler Hat LLC <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7C3a8e9e313e9744a4706a08d73bb525db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637043521555610433sdata=z%2BrnbF8mRz%2Bh%2Fe54Ta9HaAvaqh2rLiMVQPpcx0VPRUc%3Dreserved=0
> >
>
>
> On Tue, Sep 17, 2019 at 6:43 AM Apache Royale CI Server <
> apacheroyal...@gmail.com> wrote:
>
> > This is the discussion thread.
> >
> > Thanks,
> > Piotr
>
>
>


Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-17 Thread Alex Harui
Hmm.  I thought I'd fixed that.  I swear I had all examples building.

Anyway, fixes like these should be going in the release branch, not develop, 
IMO.

Thanks,
-Alex

On 9/17/19, 2:22 PM, "Josh Tynjala"  wrote:

Getting the following error when running the ApproveRoyale ant script...

Error: unable to open

'/Users/joshtynjala/Desktop/royale/apache-royale-0.9.6-src/royale-asjs/examples/royale/CreditCardValidatorExample/src/main/royale/App.mxml'.

Seems to be caused by this line in build.xml from
CreditCardValidatorExample:



There is no App.mxml, but there is a CreditCardValidatorExample.mxml, so I
think that the value is supposed to be "CreditCardValidatorExample" instead:



I just pushed a commit to develop to fix that for the next release.

I will locally adjust ApproveRoyale to skip the examples and finish the
rest of the approval process. Assuming that everything else completes
successfully, a broken example build script is not enough to prevent me
from approving this release candidate.

--
Josh Tynjala
Bowler Hat LLC 



On Tue, Sep 17, 2019 at 6:43 AM Apache Royale CI Server <
apacheroyal...@gmail.com> wrote:

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




Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-17 Thread Josh Tynjala
Getting the following error when running the ApproveRoyale ant script...

Error: unable to open
'/Users/joshtynjala/Desktop/royale/apache-royale-0.9.6-src/royale-asjs/examples/royale/CreditCardValidatorExample/src/main/royale/App.mxml'.

Seems to be caused by this line in build.xml from
CreditCardValidatorExample:



There is no App.mxml, but there is a CreditCardValidatorExample.mxml, so I
think that the value is supposed to be "CreditCardValidatorExample" instead:



I just pushed a commit to develop to fix that for the next release.

I will locally adjust ApproveRoyale to skip the examples and finish the
rest of the approval process. Assuming that everything else completes
successfully, a broken example build script is not enough to prevent me
from approving this release candidate.

--
Josh Tynjala
Bowler Hat LLC 


On Tue, Sep 17, 2019 at 6:43 AM Apache Royale CI Server <
apacheroyal...@gmail.com> wrote:

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


Re: Release vote/discuss reply-to address

2019-09-17 Thread Josh Tynjala
Hmm... looking at the headers in Gmail seems to indicate that reply-to is
actually set to the dev list. I wonder why Gmail is ignoring it...

One thing that I see is that reply-to is showing up in the UI like this:

reply-to: dev@royale.apache.org, dev@royale.apache.org

Maybe Gmail is getting confused because it is set twice.

--
Josh Tynjala
Bowler Hat LLC 


On Tue, Sep 17, 2019 at 1:42 PM Josh Tynjala 
wrote:

> I just realized that several replies that I sent to the 0.9.6 discuss
> thread were lost because I was unexpectedly replying to
> apacheroyal...@gmail.com.
>
> When the server sends out vote/discuss threads, is it possible to set the
> reply-to address to dev@royale.apache.org?
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>


Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-17 Thread Josh Tynjala
I downloaded the KEYS file and imported it.

gpg --import KEYS

However, when I ran the ApproveRoyale.xml script after that, I got this
error:

gpg: Signature made 09/17/19 05:01:35 Pacific Daylight Time
gpg:using RSA key B0A9098B61A39B1E8D5B7C9976CF6A81D5C80F47
gpg: Can't check signature: No public key

Eventually, I figured out how to manually import Piotr's signature like
this, and then I could continue the approval script into later steps:

gpg --keyserver keys.gnupg.net --recv-keys D5C80F47

Not sure why it fails with the KEYS file, but maybe Piotr needs to update
his signature somewhere to fix the KEYS file?

--
Josh Tynjala
Bowler Hat LLC 


On Tue, Sep 17, 2019 at 6:43 AM Apache Royale CI Server <
apacheroyal...@gmail.com> wrote:

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


Release vote/discuss reply-to address

2019-09-17 Thread Josh Tynjala
I just realized that several replies that I sent to the 0.9.6 discuss
thread were lost because I was unexpectedly replying to
apacheroyal...@gmail.com.

When the server sends out vote/discuss threads, is it possible to set the
reply-to address to dev@royale.apache.org?

--
Josh Tynjala
Bowler Hat LLC 


Discuss of release steps preparation

2019-09-17 Thread Piotr Zarzycki
Alex,

I will fix those issues once we make current release. Both of them are not
a blockers in my opinion.

How issue in release steps script can influence sources ?

Thanks,
Piotr


On Tue, Sep 17, 2019, 7:29 PM Alex Harui  wrote:

> If you had to do that, how do you know the RC is still valid?  Sounds like
> there is a version number that isn't right in the source package.  One
> reason to have scripts is to detect things that are not right.  Yes there
> might be bugs in the scripts, but if you didn't have to do this before, it
> should imply that something changes in the source package.
>
> Please fix issues like the signing of RoyaleUnit.  Otherwise, who's job is
> it to fix it?  I could, but then we're back to the same problem of nobody
> else knowing how to fix the scripts.
>
> -Alex
>
> On 9/17/19, 3:58 AM, "Piotr Zarzycki"  wrote:
>
> Another small issue which I discovered is that I had to specify in Step
> 13 -Drelease.version=0.9.6 -Dreleaseversion=0.9.6 - With dot and
> without
> dot, cause script failed on compiler cloning.
>
> Thanks,
> Piotr
>
> wt., 17 wrz 2019 o 10:47 Piotr Zarzycki 
> napisał(a):
>
> > Hi Guys,
> >
> > I'm in a process of uploading Maven artifacts and after upload I got
> > following problem [1]. I will sign those artifacts manually, but
> this is
> > something what should be fixed in the script for the next release.
> >
> > [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fibb.co%2Fzh0r5nndata=02%7C01%7Caharui%40adobe.com%7C1fc0eda016c142c6749208d73b5df97a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637043147117439927sdata=ooR8yrRymFsNi6fa%2BZ3%2BUdMqWSoq0cPow8wUfaOw2mI%3Dreserved=0
> >
> > Thanks,
> > Piotr
> >
> > niedz., 15 wrz 2019 o 08:18 Alex Harui 
> > napisał(a):
> >
> >> Glad you are getting back to normal.  Please review what is in the
> >> release branch before the RC so we can fix things before Piotr
> spends a lot
> >> of time creating the RC.
> >>
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fblob%2Frelease%2F0.9.6%2FRELEASE_NOTES.mddata=02%7C01%7Caharui%40adobe.com%7C1fc0eda016c142c6749208d73b5df97a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637043147117439927sdata=9F0OmcoS2IPo6XKwtw7RWCSX0R3U5NLe1XX%2Fk10r%2Fms%3Dreserved=0
> >>
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fblob%2Frelease%2F0.9.6%2Freleasemgr%2FRELEASE_NOTESdata=02%7C01%7Caharui%40adobe.com%7C1fc0eda016c142c6749208d73b5df97a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637043147117449928sdata=b1gmeUkWeRBI0nuEplLMutT8tcWobwtbsvSOSuxtYOQ%3Dreserved=0
> >>
> >> Because of the way we package, the releasemgr/RELEASE_NOTES is the
> >> top-level release notes in the source package because the package
> contains
> >> all 3 repos and the releasemgr files are copied to the top.  The
> .MD file
> >> is for GitHub visitors to the repo.
> >>
> >> Thanks,
> >> -Alex
> >>
> >> On 9/14/19, 11:06 AM, "Andrew Wetmore"  wrote:
> >>
> >> We have power and internet again, at last. I guess I should
> wait to
> >> review
> >> texts until the next version of the release candidate.
> >>
> >> On Sat, Sep 14, 2019 at 3:01 PM Piotr Zarzycki <
> >> piotrzarzyck...@gmail.com>
> >> wrote:
> >>
> >> > Hi Carlos,
> >> >
> >> > I see you did commit to 0.9.6 branch, so we are good unless
> there is
> >> > something left in develop which should I pick. I will review
> all of
> >> that on
> >> > Monday.
> >> >
> >> > Thanks,
> >> > Piotr
> >> >
> >> > On Sat, Sep 14, 2019, 5:26 PM Carlos Rovira <
> >> carlosrov...@apache.org>
> >> > wrote:
> >> >
> >> > > Hi Piotr,
> >> > >
> >> > > seems there was a little confusion here and Greg and I did
> the
> >> changes in
> >> > > the release version of RELEASE_NOTES.
> >> > > Hope you can merge both in your process. I followed my
> changes
> >> since
> >> > > December to try to bring all relevant things done.
> >> > > Thanks
> >> > >
> >> > > El sáb., 14 sept. 2019 a las 15:39, Piotr Zarzycki (<
> >> > > piotrzarzyck...@gmail.com>) escribió:
> >> > >
> >> > > > Hi Greg,
> >> > > >
> >> > > > I'm sorry for a late response. I'm going to take what's
> develop
> >> has in
> >> > it
> >> > > > on Monday by cherry picking - to do not break release
> branch,
> >> so where
> >> > > you
> >> > > > commit it will be good and won't miss it.
> >> > > >
> >> > > > Thanks,
> >> > > > Piotr
> >> > > >
> >> > > > pt., 13 wrz 2019 o 19:24 Greg Dove 
>  

[DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-17 Thread Piotr Zarzycki
Carlos,

Could you also try to setup Maven artifacts and build your project - see if
all is ok?

It is the matter of setup links with artifacts in settings.xml. Set it as
active profile and maybe switch in pom to 0.9.6 non Snapshot.

If you will have time!

Thanks,
Piotr

On Tue, Sep 17, 2019, 6:34 PM Carlos Rovira  wrote:

> Hi Piotr, is ok is in royale-asjs README repo. All ok
>
> (about gmail mixing topics, good catch...although that's very strange gmail
> behavior :-? )
>
>
>
> El mar., 17 sept. 2019 a las 18:25, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > Are you checking README in sources? I think those information are in some
> > release notes file not readme.
> >
> > On Tue, Sep 17, 2019, 6:17 PM Carlos Rovira 
> > wrote:
> >
> > > Hi Piotr,
> > >
> > > I notice this thread is VOTE and not DISCUSS.
> > >
> > > About celebration, I think it deserves admiration, although we know we
> > > still could need a little final adjustment. But this process is about
> > 99%,
> > > so is good to celebrate all the hard work here by Alex, Om, you and
> > others
> > > involved :)
> > >
> > > Going to my checking of RC1: In README I think there are missing notes.
> > We
> > > provided a lot more. Don't know if is ok as is cause we couldn't add
> all
> > > latest notes (I though only Andrew's revision was left from this
> > release).
> > > I see just this (while final notes was about x3 more lines):
> > >
> > > Apache Royale 0.9.6
> > > ===
> > >
> > > - 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.
> > > - Dozens of bugs reported, investigated, and squashed. For details of
> > >   closed bug reports see
> > > https://github.com/apache/royale-asjs/issues?q=is%3Aissue+is%3Aclosed
> > >
> > > Thanks!
> > >
> > >
> > >
> > > El mar., 17 sept. 2019 a las 17:14, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>) escribió:
> > >
> > > > Hi Carlos,
> > > >
> > > > Thanks but I won't start celebrate till someone build stuff on his PC
> > > using
> > > > approval script or whatever other method.
> > > >
> > > > I did try script. I reached the point where SDK need to be build - I
> > left
> > > > it for now to try tomorrow maybe.
> > > >
> > > > wt., 17 wrz 2019 o 17:02 Carlos Rovira 
> > > > napisał(a):
> > > >
> > > > > Hi,
> > > > > congrats to reach this step! many work involved here so far! :)
> > > > >
> > > > > El mar., 17 sept. 2019 a las 15:45, Piotr Zarzycki (<
> > > > > piotrzarzyck...@gmail.com>) escribió:
> > > > >
> > > > > > Hi Guys,
> > > > > >
> > > > > > I believe we can officially start testing, providing feedback and
> > > > > hopefully
> > > > > > voting.
> > > > > >
> > > > > > Thanks,
> > > > > > Piotr
> > > > > >
> > > > > > wt., 17 wrz 2019 o 15:43 Apache Royale CI Server <
> > > > > apacheroyal...@gmail.com
> > > > > > >
> > > > > > napisał(a):
> > > > > >
> > > > > > > This is the discussion thread.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Piotr
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > >
> > > > > > Piotr Zarzycki
> > > > > >
> > > > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > > *
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Carlos Rovira
> > > > > http://about.me/carlosrovira
> > > > >
> > > >
> > > >
> > > > --
> > > >
> > > > Piotr Zarzycki
> > > >
> > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > *
> > > >
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


Re: Discuss of release steps preparation

2019-09-17 Thread Alex Harui
If you had to do that, how do you know the RC is still valid?  Sounds like 
there is a version number that isn't right in the source package.  One reason 
to have scripts is to detect things that are not right.  Yes there might be 
bugs in the scripts, but if you didn't have to do this before, it should imply 
that something changes in the source package.

Please fix issues like the signing of RoyaleUnit.  Otherwise, who's job is it 
to fix it?  I could, but then we're back to the same problem of nobody else 
knowing how to fix the scripts.

-Alex

On 9/17/19, 3:58 AM, "Piotr Zarzycki"  wrote:

Another small issue which I discovered is that I had to specify in Step
13 -Drelease.version=0.9.6 -Dreleaseversion=0.9.6 - With dot and without
dot, cause script failed on compiler cloning.

Thanks,
Piotr

wt., 17 wrz 2019 o 10:47 Piotr Zarzycki 
napisał(a):

> Hi Guys,
>
> I'm in a process of uploading Maven artifacts and after upload I got
> following problem [1]. I will sign those artifacts manually, but this is
> something what should be fixed in the script for the next release.
>
> [1] 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fibb.co%2Fzh0r5nndata=02%7C01%7Caharui%40adobe.com%7C1fc0eda016c142c6749208d73b5df97a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637043147117439927sdata=ooR8yrRymFsNi6fa%2BZ3%2BUdMqWSoq0cPow8wUfaOw2mI%3Dreserved=0
>
> Thanks,
> Piotr
>
> niedz., 15 wrz 2019 o 08:18 Alex Harui 
> napisał(a):
>
>> Glad you are getting back to normal.  Please review what is in the
>> release branch before the RC so we can fix things before Piotr spends a 
lot
>> of time creating the RC.
>>
>> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fblob%2Frelease%2F0.9.6%2FRELEASE_NOTES.mddata=02%7C01%7Caharui%40adobe.com%7C1fc0eda016c142c6749208d73b5df97a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637043147117439927sdata=9F0OmcoS2IPo6XKwtw7RWCSX0R3U5NLe1XX%2Fk10r%2Fms%3Dreserved=0
>>
>> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fblob%2Frelease%2F0.9.6%2Freleasemgr%2FRELEASE_NOTESdata=02%7C01%7Caharui%40adobe.com%7C1fc0eda016c142c6749208d73b5df97a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637043147117449928sdata=b1gmeUkWeRBI0nuEplLMutT8tcWobwtbsvSOSuxtYOQ%3Dreserved=0
>>
>> Because of the way we package, the releasemgr/RELEASE_NOTES is the
>> top-level release notes in the source package because the package 
contains
>> all 3 repos and the releasemgr files are copied to the top.  The .MD file
>> is for GitHub visitors to the repo.
>>
>> Thanks,
>> -Alex
>>
>> On 9/14/19, 11:06 AM, "Andrew Wetmore"  wrote:
>>
>> We have power and internet again, at last. I guess I should wait to
>> review
>> texts until the next version of the release candidate.
>>
>> On Sat, Sep 14, 2019 at 3:01 PM Piotr Zarzycki <
>> piotrzarzyck...@gmail.com>
>> wrote:
>>
>> > Hi Carlos,
>> >
>> > I see you did commit to 0.9.6 branch, so we are good unless there 
is
>> > something left in develop which should I pick. I will review all of
>> that on
>> > Monday.
>> >
>> > Thanks,
>> > Piotr
>> >
>> > On Sat, Sep 14, 2019, 5:26 PM Carlos Rovira <
>> carlosrov...@apache.org>
>> > wrote:
>> >
>> > > Hi Piotr,
>> > >
>> > > seems there was a little confusion here and Greg and I did the
>> changes in
>> > > the release version of RELEASE_NOTES.
>> > > Hope you can merge both in your process. I followed my changes
>> since
>> > > December to try to bring all relevant things done.
>> > > Thanks
>> > >
>> > > El sáb., 14 sept. 2019 a las 15:39, Piotr Zarzycki (<
>> > > piotrzarzyck...@gmail.com>) escribió:
>> > >
>> > > > Hi Greg,
>> > > >
>> > > > I'm sorry for a late response. I'm going to take what's develop
>> has in
>> > it
>> > > > on Monday by cherry picking - to do not break release branch,
>> so where
>> > > you
>> > > > commit it will be good and won't miss it.
>> > > >
>> > > > Thanks,
>> > > > Piotr
>> > > >
>> > > > pt., 13 wrz 2019 o 19:24 Greg Dove 
>> napisał(a):
>> > > >
>> > > > > Hi Piotr,
>> > > > >
>> > > > > I'm not so familiar with the release process. Do you want
>> additions
>> > to
>> > > go
>> > > > > directly into the release branch or should that be added to
>> develop
>> > > > > (assuming you would merge into release)?
>> > > > >
>> > > > > I see Josh added note about RoyalUnit in 

Re: [VOTE] Release Apache Royale 0.9.6 RC1

2019-09-17 Thread Carlos Rovira
Hi,

+1

Package
https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc1/apache-royale-0.9.6-src.tar.gz
Java 1.8.0_181
OS: Mac OS X x86_64 10.14.6
Source kit signatures match: Y
Source kit builds: Y
README is ok: Y
RELEASE_NOTES is ok: Y
NOTICE is ok: Y
LICENSE is ok: Y
No unapproved licenses or archives: Y
No unapproved binaries: Y

Package
https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc1/binaries/apache-royale-0.9.6-bin-js-swf.tar.gz
Binary kit signatures match: Y
README is ok: Y
RELEASE_NOTES is ok: Y
NOTICE is ok: Y
LICENSE is ok: Y
No unapproved licenses or archives in binary package: Y
No unapproved binaries in binary package: Y




El mar., 17 sept. 2019 a las 15:43, Apache Royale CI Server (<
apacheroyal...@gmail.com>) escribió:

> Hi,
>
> This is the vote for the 0.9.6 release of Apache Royale.
>
> The release candidate can be found here;
> https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc1/
>
> Before voting please review the section,'What are the ASF requirements on
> approving a release?', at:
> http://www.apache.org/dev/release.html#approving-a-release
>
> At a minimum you would be expected to check that:
> - SHA and signed packages are correct
> - README, RELEASE_NOTES, NOTICE and LICENSE files are all fine
> - That the build script completes successfully
> - That you can compile and cross-compile a simple example using the SDK.
>
> The KEYS file is at https://dist.apache.org/repos/dist/release/royale/KEYS
>
> The source package is a combination of the 3 main Royale repos.
>
> To use the binary package, unzip it into a folder.  The -js package is
> ready-to-use in an IDE or command-line.  If you need SWF output, use the
> -js-swf package and use Apache Ant to run the InstallAdobeSDKs script via:
>   ant -f InstallAdobeSDKs.xml
>
> You may also get the binary packages via NPM.  The -js package can be
> installed via:
>
> npm install
> https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc1/binaries/apache-royale-0.9.6-bin-js.tar.gz
> -g
>
> The full package with SWF support can be installed via:
>
> npm install
> https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc1/binaries/apache-royale-0.9.6-bin-js-swf.tar.gz
> -g
>
> Maven artifacts are staged here:
> https://repository.apache.org/content/repositories/orgapacheroyale-1056
>
> Please vote to approve this release:
> +1 Approve the release
> -1 Disapprove the release (please provide specific comments to why)
>
> This vote will be open for 72 hours or until a result can be called.
>
> The vote passes if there is:
> - At least 3 +1 votes from the PMC
> - More positive votes than negative votes
>
> Remember that this is a 'beta-quality' release so expect there
> will be many bugs found.  IMO the goal is not to try to find and fix bugs
> in the RC, but to make sure we have the packaging right, and enough
> functionality that folks will have some success trying to use it.
>
> People who are not in PMC are also encouraged to test out the release and
> vote, although their votes will not be binding, they can influence how the
> PMC votes.
>
> When voting please indicate what OS, IDE, Flash Player version and AIR
> version you tested with.
>
> For your convenience, there is an ant script that automates the common
> steps to validate a release.  Instead of individually downloading the
> package and signature files, unzipping, etc, you can instead:
> 1) create an empty folder,
> 2) download into that folder this file:
> https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc1/ApproveRoyale.xml
> 3) run the script:
>ant -e -f ApproveRoyale.xml -Drelease.version=0.9.6 -Drc=1
>If you want to test SWF support during the approval, use:
>ant -e -f ApproveRoyale.xml -Drelease.version=0.9.6 -Drc=1
> -Duse-flash=true
>
> You are not required to use this script, and more testing of the packages
> and build results are always encouraged.
>
> Please put all discussion about this release in the DISCUSSION thread not
> this VOTE thread.
>
> Thanks,
> Piotr



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


Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-17 Thread Carlos Rovira
Hi Piotr, is ok is in royale-asjs README repo. All ok

(about gmail mixing topics, good catch...although that's very strange gmail
behavior :-? )



El mar., 17 sept. 2019 a las 18:25, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> Are you checking README in sources? I think those information are in some
> release notes file not readme.
>
> On Tue, Sep 17, 2019, 6:17 PM Carlos Rovira 
> wrote:
>
> > Hi Piotr,
> >
> > I notice this thread is VOTE and not DISCUSS.
> >
> > About celebration, I think it deserves admiration, although we know we
> > still could need a little final adjustment. But this process is about
> 99%,
> > so is good to celebrate all the hard work here by Alex, Om, you and
> others
> > involved :)
> >
> > Going to my checking of RC1: In README I think there are missing notes.
> We
> > provided a lot more. Don't know if is ok as is cause we couldn't add all
> > latest notes (I though only Andrew's revision was left from this
> release).
> > I see just this (while final notes was about x3 more lines):
> >
> > Apache Royale 0.9.6
> > ===
> >
> > - 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.
> > - Dozens of bugs reported, investigated, and squashed. For details of
> >   closed bug reports see
> > https://github.com/apache/royale-asjs/issues?q=is%3Aissue+is%3Aclosed
> >
> > Thanks!
> >
> >
> >
> > El mar., 17 sept. 2019 a las 17:14, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>) escribió:
> >
> > > Hi Carlos,
> > >
> > > Thanks but I won't start celebrate till someone build stuff on his PC
> > using
> > > approval script or whatever other method.
> > >
> > > I did try script. I reached the point where SDK need to be build - I
> left
> > > it for now to try tomorrow maybe.
> > >
> > > wt., 17 wrz 2019 o 17:02 Carlos Rovira 
> > > napisał(a):
> > >
> > > > Hi,
> > > > congrats to reach this step! many work involved here so far! :)
> > > >
> > > > El mar., 17 sept. 2019 a las 15:45, Piotr Zarzycki (<
> > > > piotrzarzyck...@gmail.com>) escribió:
> > > >
> > > > > Hi Guys,
> > > > >
> > > > > I believe we can officially start testing, providing feedback and
> > > > hopefully
> > > > > voting.
> > > > >
> > > > > Thanks,
> > > > > Piotr
> > > > >
> > > > > wt., 17 wrz 2019 o 15:43 Apache Royale CI Server <
> > > > apacheroyal...@gmail.com
> > > > > >
> > > > > napisał(a):
> > > > >
> > > > > > This is the discussion thread.
> > > > > >
> > > > > > Thanks,
> > > > > > Piotr
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > Piotr Zarzycki
> > > > >
> > > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > *
> > > > >
> > > >
> > > >
> > > > --
> > > > Carlos Rovira
> > > > http://about.me/carlosrovira
> > > >
> > >
> > >
> > > --
> > >
> > > Piotr Zarzycki
> > >
> > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > *
> > >
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>


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


[DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-17 Thread Piotr Zarzycki
Are you checking README in sources? I think those information are in some
release notes file not readme.

On Tue, Sep 17, 2019, 6:17 PM Carlos Rovira  wrote:

> Hi Piotr,
>
> I notice this thread is VOTE and not DISCUSS.
>
> About celebration, I think it deserves admiration, although we know we
> still could need a little final adjustment. But this process is about 99%,
> so is good to celebrate all the hard work here by Alex, Om, you and others
> involved :)
>
> Going to my checking of RC1: In README I think there are missing notes. We
> provided a lot more. Don't know if is ok as is cause we couldn't add all
> latest notes (I though only Andrew's revision was left from this release).
> I see just this (while final notes was about x3 more lines):
>
> Apache Royale 0.9.6
> ===
>
> - 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.
> - Dozens of bugs reported, investigated, and squashed. For details of
>   closed bug reports see
> https://github.com/apache/royale-asjs/issues?q=is%3Aissue+is%3Aclosed
>
> Thanks!
>
>
>
> El mar., 17 sept. 2019 a las 17:14, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > Hi Carlos,
> >
> > Thanks but I won't start celebrate till someone build stuff on his PC
> using
> > approval script or whatever other method.
> >
> > I did try script. I reached the point where SDK need to be build - I left
> > it for now to try tomorrow maybe.
> >
> > wt., 17 wrz 2019 o 17:02 Carlos Rovira 
> > napisał(a):
> >
> > > Hi,
> > > congrats to reach this step! many work involved here so far! :)
> > >
> > > El mar., 17 sept. 2019 a las 15:45, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>) escribió:
> > >
> > > > Hi Guys,
> > > >
> > > > I believe we can officially start testing, providing feedback and
> > > hopefully
> > > > voting.
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > wt., 17 wrz 2019 o 15:43 Apache Royale CI Server <
> > > apacheroyal...@gmail.com
> > > > >
> > > > napisał(a):
> > > >
> > > > > This is the discussion thread.
> > > > >
> > > > > Thanks,
> > > > > Piotr
> > > >
> > > >
> > > >
> > > > --
> > > >
> > > > Piotr Zarzycki
> > > >
> > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > *
> > > >
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > *
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


[DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-17 Thread Piotr Zarzycki
Carlos,

Gmail merge both topics, but if you hit Reply All and check Edit Title you
can make sure that your replaying in a good subject. Check before reply.

Thanks,
Piotr

On Tue, Sep 17, 2019, 6:17 PM Carlos Rovira  wrote:

> Hi Piotr,
>
> I notice this thread is VOTE and not DISCUSS.
>
> About celebration, I think it deserves admiration, although we know we
> still could need a little final adjustment. But this process is about 99%,
> so is good to celebrate all the hard work here by Alex, Om, you and others
> involved :)
>
> Going to my checking of RC1: In README I think there are missing notes. We
> provided a lot more. Don't know if is ok as is cause we couldn't add all
> latest notes (I though only Andrew's revision was left from this release).
> I see just this (while final notes was about x3 more lines):
>
> Apache Royale 0.9.6
> ===
>
> - 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.
> - Dozens of bugs reported, investigated, and squashed. For details of
>   closed bug reports see
> https://github.com/apache/royale-asjs/issues?q=is%3Aissue+is%3Aclosed
>
> Thanks!
>
>
>
> El mar., 17 sept. 2019 a las 17:14, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > Hi Carlos,
> >
> > Thanks but I won't start celebrate till someone build stuff on his PC
> using
> > approval script or whatever other method.
> >
> > I did try script. I reached the point where SDK need to be build - I left
> > it for now to try tomorrow maybe.
> >
> > wt., 17 wrz 2019 o 17:02 Carlos Rovira 
> > napisał(a):
> >
> > > Hi,
> > > congrats to reach this step! many work involved here so far! :)
> > >
> > > El mar., 17 sept. 2019 a las 15:45, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>) escribió:
> > >
> > > > Hi Guys,
> > > >
> > > > I believe we can officially start testing, providing feedback and
> > > hopefully
> > > > voting.
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > wt., 17 wrz 2019 o 15:43 Apache Royale CI Server <
> > > apacheroyal...@gmail.com
> > > > >
> > > > napisał(a):
> > > >
> > > > > This is the discussion thread.
> > > > >
> > > > > Thanks,
> > > > > Piotr
> > > >
> > > >
> > > >
> > > > --
> > > >
> > > > Piotr Zarzycki
> > > >
> > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > *
> > > >
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > *
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-17 Thread Carlos Rovira
Hi Piotr,

I notice this thread is VOTE and not DISCUSS.

About celebration, I think it deserves admiration, although we know we
still could need a little final adjustment. But this process is about 99%,
so is good to celebrate all the hard work here by Alex, Om, you and others
involved :)

Going to my checking of RC1: In README I think there are missing notes. We
provided a lot more. Don't know if is ok as is cause we couldn't add all
latest notes (I though only Andrew's revision was left from this release).
I see just this (while final notes was about x3 more lines):

Apache Royale 0.9.6
===

- 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.
- Dozens of bugs reported, investigated, and squashed. For details of
  closed bug reports see
https://github.com/apache/royale-asjs/issues?q=is%3Aissue+is%3Aclosed

Thanks!



El mar., 17 sept. 2019 a las 17:14, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> Hi Carlos,
>
> Thanks but I won't start celebrate till someone build stuff on his PC using
> approval script or whatever other method.
>
> I did try script. I reached the point where SDK need to be build - I left
> it for now to try tomorrow maybe.
>
> wt., 17 wrz 2019 o 17:02 Carlos Rovira 
> napisał(a):
>
> > Hi,
> > congrats to reach this step! many work involved here so far! :)
> >
> > El mar., 17 sept. 2019 a las 15:45, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>) escribió:
> >
> > > Hi Guys,
> > >
> > > I believe we can officially start testing, providing feedback and
> > hopefully
> > > voting.
> > >
> > > Thanks,
> > > Piotr
> > >
> > > wt., 17 wrz 2019 o 15:43 Apache Royale CI Server <
> > apacheroyal...@gmail.com
> > > >
> > > napisał(a):
> > >
> > > > This is the discussion thread.
> > > >
> > > > Thanks,
> > > > Piotr
> > >
> > >
> > >
> > > --
> > >
> > > Piotr Zarzycki
> > >
> > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > *
> > >
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>


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


[DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-17 Thread Piotr Zarzycki
Hi Carlos,

Thanks but I won't start celebrate till someone build stuff on his PC using
approval script or whatever other method.

I did try script. I reached the point where SDK need to be build - I left
it for now to try tomorrow maybe.

wt., 17 wrz 2019 o 17:02 Carlos Rovira  napisał(a):

> Hi,
> congrats to reach this step! many work involved here so far! :)
>
> El mar., 17 sept. 2019 a las 15:45, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > Hi Guys,
> >
> > I believe we can officially start testing, providing feedback and
> hopefully
> > voting.
> >
> > Thanks,
> > Piotr
> >
> > wt., 17 wrz 2019 o 15:43 Apache Royale CI Server <
> apacheroyal...@gmail.com
> > >
> > napisał(a):
> >
> > > This is the discussion thread.
> > >
> > > Thanks,
> > > Piotr
> >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > *
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 

Piotr Zarzycki

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


Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-17 Thread Carlos Rovira
Hi,
congrats to reach this step! many work involved here so far! :)

El mar., 17 sept. 2019 a las 15:45, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> Hi Guys,
>
> I believe we can officially start testing, providing feedback and hopefully
> voting.
>
> Thanks,
> Piotr
>
> wt., 17 wrz 2019 o 15:43 Apache Royale CI Server  >
> napisał(a):
>
> > This is the discussion thread.
> >
> > Thanks,
> > Piotr
>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>


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


[DISCUSS] Release Apache Royale 0.9.6 RC1

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

Thanks,
Piotr

[VOTE] Release Apache Royale 0.9.6 RC1

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

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

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

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

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

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

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

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

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

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

The full package with SWF support can be installed via:

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

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

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

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

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

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

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

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

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

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

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

Thanks,
Piotr

[DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-17 Thread Piotr Zarzycki
Hi Guys,

I believe we can officially start testing, providing feedback and hopefully
voting.

Thanks,
Piotr

wt., 17 wrz 2019 o 15:43 Apache Royale CI Server 
napisał(a):

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



-- 

Piotr Zarzycki

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


Build failed in Jenkins: royale-asjs_jsonly #3552

2019-09-17 Thread Apache Royale CI Server
See 


--
[...truncated 159.64 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 254 files to 

 [copy] Copying 66 files to 


stage-fb-integration:
 [copy] Copying 242 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 09/17/19 12:17 +

wipe:
 [echo] swc-date is 09/17/19 12:17 +

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

wipe:
 [echo] swc-date is 09/17/19 12:17 +

wipe:
 [echo] swc-date is 09/17/19 12:17 +

wipe:
   [delete] Deleting directory C:\Program Files 

Re: Discuss of release steps preparation

2019-09-17 Thread Piotr Zarzycki
Another small issue which I discovered is that I had to specify in Step
13 -Drelease.version=0.9.6 -Dreleaseversion=0.9.6 - With dot and without
dot, cause script failed on compiler cloning.

Thanks,
Piotr

wt., 17 wrz 2019 o 10:47 Piotr Zarzycki 
napisał(a):

> Hi Guys,
>
> I'm in a process of uploading Maven artifacts and after upload I got
> following problem [1]. I will sign those artifacts manually, but this is
> something what should be fixed in the script for the next release.
>
> [1] https://ibb.co/zh0r5nn
>
> Thanks,
> Piotr
>
> niedz., 15 wrz 2019 o 08:18 Alex Harui 
> napisał(a):
>
>> Glad you are getting back to normal.  Please review what is in the
>> release branch before the RC so we can fix things before Piotr spends a lot
>> of time creating the RC.
>>
>> https://github.com/apache/royale-asjs/blob/release/0.9.6/RELEASE_NOTES.md
>>
>> https://github.com/apache/royale-asjs/blob/release/0.9.6/releasemgr/RELEASE_NOTES
>>
>> Because of the way we package, the releasemgr/RELEASE_NOTES is the
>> top-level release notes in the source package because the package contains
>> all 3 repos and the releasemgr files are copied to the top.  The .MD file
>> is for GitHub visitors to the repo.
>>
>> Thanks,
>> -Alex
>>
>> On 9/14/19, 11:06 AM, "Andrew Wetmore"  wrote:
>>
>> We have power and internet again, at last. I guess I should wait to
>> review
>> texts until the next version of the release candidate.
>>
>> On Sat, Sep 14, 2019 at 3:01 PM Piotr Zarzycki <
>> piotrzarzyck...@gmail.com>
>> wrote:
>>
>> > Hi Carlos,
>> >
>> > I see you did commit to 0.9.6 branch, so we are good unless there is
>> > something left in develop which should I pick. I will review all of
>> that on
>> > Monday.
>> >
>> > Thanks,
>> > Piotr
>> >
>> > On Sat, Sep 14, 2019, 5:26 PM Carlos Rovira <
>> carlosrov...@apache.org>
>> > wrote:
>> >
>> > > Hi Piotr,
>> > >
>> > > seems there was a little confusion here and Greg and I did the
>> changes in
>> > > the release version of RELEASE_NOTES.
>> > > Hope you can merge both in your process. I followed my changes
>> since
>> > > December to try to bring all relevant things done.
>> > > Thanks
>> > >
>> > > El sáb., 14 sept. 2019 a las 15:39, Piotr Zarzycki (<
>> > > piotrzarzyck...@gmail.com>) escribió:
>> > >
>> > > > Hi Greg,
>> > > >
>> > > > I'm sorry for a late response. I'm going to take what's develop
>> has in
>> > it
>> > > > on Monday by cherry picking - to do not break release branch,
>> so where
>> > > you
>> > > > commit it will be good and won't miss it.
>> > > >
>> > > > Thanks,
>> > > > Piotr
>> > > >
>> > > > pt., 13 wrz 2019 o 19:24 Greg Dove 
>> napisał(a):
>> > > >
>> > > > > Hi Piotr,
>> > > > >
>> > > > > I'm not so familiar with the release process. Do you want
>> additions
>> > to
>> > > go
>> > > > > directly into the release branch or should that be added to
>> develop
>> > > > > (assuming you would merge into release)?
>> > > > >
>> > > > > I see Josh added note about RoyalUnit in develop [1], which
>> is not
>> > yet
>> > > in
>> > > > > release.[2] . So perhaps you will merge from develop? I'm not
>> sure
>> > how
>> > > > this
>> > > > > all needs to work.
>> > > > >
>> > > > > I'm thinking to add the following to 0.9.6 release notes
>> (changes
>> > since
>> > > > > 0.9.4) for some of the things I worked on:
>> > > > >
>> > > > > -Improvements to AMF / RemoteObject Support
>> > > > > -AMFBinaryData api now matches flash.utils.ByteArray, (the
>> missing
>> > > > feature
>> > > > > is non-UTF String encoding support). It therefore now works
>> for deep
>> > > > > cloning via readObject/writeObject and registerClassAlias.
>> > > > > -Updates to Royale collections library with support for
>> sorting and
>> > > > > filtering via ArrayListView. Simple example added to Tour de
>> Jewel
>> > > > > -A conforming runtime implementation of AS3 Vector (typed
>> Arrays) was
>> > > > added
>> > > > > for javascript output, with options for avoiding certain
>> runtime
>> > > checks.
>> > > > > -int, uint, Class are now represented as simple, distinct
>> types
>> > (Class
>> > > is
>> > > > > now not 'Object', int is now not 'Number' for example), and
>> these
>> > > support
>> > > > > indirect 'as' or 'is' type checking and instantiation,
>> matching swf
>> > > > > behavior.
>> > > > > -General Improvements and additions in Reflection library
>> > > > > -New Apache Royale Crux MVC/DI/IOC application architecture
>> library
>> > > > (based
>> > > > > on Swiz Framework) was added, with some simple examples
>> > > > >
>> > > > > If it's too late to add those, no worries, I can add that to
>> the
>> > > 'Updates
>> > > > > to the 

Release Step 013 Succeeded

2019-09-17 Thread Apache Royale CI Server
>From the royale-asjs repo
1. Run ant -f releasesteps.xml Release_Step_013 -Drelease.version=0.9.6 
-Droyale.swc-date="9/17/19 9:06 -0800" -Dplayerglobal.version=11.7 
-Dflat.donot.ask=true -Drc=1 -DskipTests=true
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f releasesteps.xml Release_Step_013_Sign 
-Drelease.version=0.9.6
This will PGP sign the source and convenience binary packages
4. Then run ant -f releasesteps.xml Release_Step_013_Upload 
-Drelease.version=0.9.6 -Drc=1
This will upload the signed artifacts to dist.apache.org.

Re: Could @nocollapse be a solution to the -warn-public-vars issue?

2019-09-17 Thread Harbs
Rather than having to specify a whole slew of compiler options, I’d like to see 
2 or 3 compiler configurations that would set the defaults on a group of 
options to get the best default behavior for a use case.
Maybe something like this:

js-config=compatible (for maximum, compatibility with Flash behavior)
js-config=optimized (for minimum code size)
js-config=safe (for best type safety but not necessarily Flash compatible)

Obviously, you could override the defaults on any one of these, but I hope we 
could give predefined sets of defaults which cover the vast majority of use 
cases out of the box.

It’s hard learning all the compiler options, but being able to specify a few 
sets of defaults seems reasonable.

Harbs

> On Sep 17, 2019, at 11:02 AM, Greg Dove  wrote:
> 
> I personally would use a non-default setting to keep things as they are
> right now, but I agree with Josh in that as it is, I don't think it's a
> good hurdle to present to new users, or people in general that simply want
> things to 'work' out of the box, based on what they should reasonably
> expect to work. The language layer is the foundation for building
> everything else. People have serious doubts when things don't work right at
> that level. I have had to reassure people about this recently (XML - still
> working on it - soon!).
> 
> We have only touched the surface of what we could do with GCC for tuning
> the output. There are ways to have all the default stuff in there but
> selectively remove it from release builds without having to recompile
> library code, for example. So I think it is possible that we could provide
> flexible solutions that match whatever we consider people want.
> But in terms of defaults, is it not obvious that it we should be guided by
> actionscript 3 language itself and the reference implementation we already
> have? We can't always match things, but I think the onus is on us to get as
> close as we can by default.
> 
> 
> On Tue, Sep 17, 2019 at 5:59 PM Alex Harui  wrote:
> 
>> Some folks want us to get smarter and not automatically export all public
>> methods and getter/setters.  There are a lot of just-in-case strings in
>> Royale apps.  That's not good.  So better control over things even after
>> compiling without being painful to use is the goal.
>> 
>> My 2 cents,
>> -Alex
>> 
>> On 9/16/19, 12:39 PM, "Josh Tynjala"  wrote:
>> 
>>I was thinking about this some more, and is there anything else that's
>>public that also we allow to be renamed? I'm not aware of anything, but
>>maybe I've missed something. If it's true, it seems inconsistent to
>> allow
>>public variables to be the one exception that should be renamed. If
>> public
>>methods, properties, and other things can't be renamed, public
>> variables
>>shouldn't be either.
>> 
>>Looking into the configuration classes, I see that we have the
>>export-public-symbols compiler option. That seems like it's the one
>> that is
>>meant to control whether public things should be renamed or not. It's
>> true
>>by default. I have no issue with public variables being renamed when
>> it's
>>false. Again, that would be consistent with how the compiler handles
>> other
>>public things.
>> 
>>--
>>Josh Tynjala
>>Bowler Hat LLC <
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7C384429ef197b497fff9408d73add9c25%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637042595795496907sdata=ii0taRMhu0bD0Ea577FNZ9CzDn%2B60MAdu7VsVIA92W4%3Dreserved=0
>>> 
>> 
>> 
>>On Mon, Sep 16, 2019 at 11:13 AM Josh Tynjala <
>> joshtynj...@bowlerhat.dev>
>>wrote:
>> 
>>> Unfortunately, people actively avoid using public vars because we
>> warn
>>> about them. Our warnings are too aggressive if it doesn't actually
>> matter
>>> most of the time. Plus, this warning leaves a bad impression because
>> it's
>>> such a basic feature of the language that pretty much everyone uses.
>>> 
>>> What can we do to provide a more sensible default behavior, while
>> also
>>> giving someone the ability to tell the compiler that everything can
>> be
>>> renamed (or selective renaming)?
>>> 
>>> We could add an option that doesn't rename public things by default,
>> but
>>> can also be toggled to rename everything. I guess we could have some
>>> @royalewhatever annotations to give someone selective control over
>> which
>>> things are renamed or not, if someone needs that. Thoughts?
>>> 
>>> --
>>> Josh Tynjala
>>> Bowler Hat LLC <
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7C384429ef197b497fff9408d73add9c25%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637042595795496907sdata=ii0taRMhu0bD0Ea577FNZ9CzDn%2B60MAdu7VsVIA92W4%3Dreserved=0
>>> 
>>> 
>>> 
>>> On Mon, Sep 16, 2019 at 10:50 AM Alex Harui >> 
>>> wrote:
>>> 
 I'm not sure I understand your proposal.  Are you proposing that all
 

Release Step 012 Succeeded

2019-09-17 Thread Apache Royale CI Server
Folder 0.9.6 already exists.  Continue to next step

Re: Discuss of release steps preparation

2019-09-17 Thread Piotr Zarzycki
Hi Guys,

I'm in a process of uploading Maven artifacts and after upload I got
following problem [1]. I will sign those artifacts manually, but this is
something what should be fixed in the script for the next release.

[1] https://ibb.co/zh0r5nn

Thanks,
Piotr

niedz., 15 wrz 2019 o 08:18 Alex Harui 
napisał(a):

> Glad you are getting back to normal.  Please review what is in the release
> branch before the RC so we can fix things before Piotr spends a lot of time
> creating the RC.
>
> https://github.com/apache/royale-asjs/blob/release/0.9.6/RELEASE_NOTES.md
>
> https://github.com/apache/royale-asjs/blob/release/0.9.6/releasemgr/RELEASE_NOTES
>
> Because of the way we package, the releasemgr/RELEASE_NOTES is the
> top-level release notes in the source package because the package contains
> all 3 repos and the releasemgr files are copied to the top.  The .MD file
> is for GitHub visitors to the repo.
>
> Thanks,
> -Alex
>
> On 9/14/19, 11:06 AM, "Andrew Wetmore"  wrote:
>
> We have power and internet again, at last. I guess I should wait to
> review
> texts until the next version of the release candidate.
>
> On Sat, Sep 14, 2019 at 3:01 PM Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> wrote:
>
> > Hi Carlos,
> >
> > I see you did commit to 0.9.6 branch, so we are good unless there is
> > something left in develop which should I pick. I will review all of
> that on
> > Monday.
> >
> > Thanks,
> > Piotr
> >
> > On Sat, Sep 14, 2019, 5:26 PM Carlos Rovira  >
> > wrote:
> >
> > > Hi Piotr,
> > >
> > > seems there was a little confusion here and Greg and I did the
> changes in
> > > the release version of RELEASE_NOTES.
> > > Hope you can merge both in your process. I followed my changes
> since
> > > December to try to bring all relevant things done.
> > > Thanks
> > >
> > > El sáb., 14 sept. 2019 a las 15:39, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>) escribió:
> > >
> > > > Hi Greg,
> > > >
> > > > I'm sorry for a late response. I'm going to take what's develop
> has in
> > it
> > > > on Monday by cherry picking - to do not break release branch, so
> where
> > > you
> > > > commit it will be good and won't miss it.
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > pt., 13 wrz 2019 o 19:24 Greg Dove 
> napisał(a):
> > > >
> > > > > Hi Piotr,
> > > > >
> > > > > I'm not so familiar with the release process. Do you want
> additions
> > to
> > > go
> > > > > directly into the release branch or should that be added to
> develop
> > > > > (assuming you would merge into release)?
> > > > >
> > > > > I see Josh added note about RoyalUnit in develop [1], which is
> not
> > yet
> > > in
> > > > > release.[2] . So perhaps you will merge from develop? I'm not
> sure
> > how
> > > > this
> > > > > all needs to work.
> > > > >
> > > > > I'm thinking to add the following to 0.9.6 release notes
> (changes
> > since
> > > > > 0.9.4) for some of the things I worked on:
> > > > >
> > > > > -Improvements to AMF / RemoteObject Support
> > > > > -AMFBinaryData api now matches flash.utils.ByteArray, (the
> missing
> > > > feature
> > > > > is non-UTF String encoding support). It therefore now works
> for deep
> > > > > cloning via readObject/writeObject and registerClassAlias.
> > > > > -Updates to Royale collections library with support for
> sorting and
> > > > > filtering via ArrayListView. Simple example added to Tour de
> Jewel
> > > > > -A conforming runtime implementation of AS3 Vector (typed
> Arrays) was
> > > > added
> > > > > for javascript output, with options for avoiding certain
> runtime
> > > checks.
> > > > > -int, uint, Class are now represented as simple, distinct types
> > (Class
> > > is
> > > > > now not 'Object', int is now not 'Number' for example), and
> these
> > > support
> > > > > indirect 'as' or 'is' type checking and instantiation,
> matching swf
> > > > > behavior.
> > > > > -General Improvements and additions in Reflection library
> > > > > -New Apache Royale Crux MVC/DI/IOC application architecture
> library
> > > > (based
> > > > > on Swiz Framework) was added, with some simple examples
> > > > >
> > > > > If it's too late to add those, no worries, I can add that to
> the
> > > 'Updates
> > > > > to the RELEASE_NOTES discovered after this file was packaged'
> wiki
> > > > >
> > > > > 1.
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fblob%2Fdevelop%2FRELEASE_NOTES.mddata=02%7C01%7Caharui%40adobe.com%7C64f7cf65c8fb4a7faf1d08d7393e4df4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637040812074543911sdata=YCHetkEVkKAvvid7MAOETcPBuV7P%2BaMB4Ajr1UsyH%2Fg%3Dreserved=0
> > 

Re: Could @nocollapse be a solution to the -warn-public-vars issue?

2019-09-17 Thread Greg Dove
I personally would use a non-default setting to keep things as they are
right now, but I agree with Josh in that as it is, I don't think it's a
good hurdle to present to new users, or people in general that simply want
things to 'work' out of the box, based on what they should reasonably
expect to work. The language layer is the foundation for building
everything else. People have serious doubts when things don't work right at
that level. I have had to reassure people about this recently (XML - still
working on it - soon!).

We have only touched the surface of what we could do with GCC for tuning
the output. There are ways to have all the default stuff in there but
selectively remove it from release builds without having to recompile
library code, for example. So I think it is possible that we could provide
flexible solutions that match whatever we consider people want.
But in terms of defaults, is it not obvious that it we should be guided by
actionscript 3 language itself and the reference implementation we already
have? We can't always match things, but I think the onus is on us to get as
close as we can by default.


On Tue, Sep 17, 2019 at 5:59 PM Alex Harui  wrote:

> Some folks want us to get smarter and not automatically export all public
> methods and getter/setters.  There are a lot of just-in-case strings in
> Royale apps.  That's not good.  So better control over things even after
> compiling without being painful to use is the goal.
>
> My 2 cents,
> -Alex
>
> On 9/16/19, 12:39 PM, "Josh Tynjala"  wrote:
>
> I was thinking about this some more, and is there anything else that's
> public that also we allow to be renamed? I'm not aware of anything, but
> maybe I've missed something. If it's true, it seems inconsistent to
> allow
> public variables to be the one exception that should be renamed. If
> public
> methods, properties, and other things can't be renamed, public
> variables
> shouldn't be either.
>
> Looking into the configuration classes, I see that we have the
> export-public-symbols compiler option. That seems like it's the one
> that is
> meant to control whether public things should be renamed or not. It's
> true
> by default. I have no issue with public variables being renamed when
> it's
> false. Again, that would be consistent with how the compiler handles
> other
> public things.
>
> --
> Josh Tynjala
> Bowler Hat LLC <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7C384429ef197b497fff9408d73add9c25%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637042595795496907sdata=ii0taRMhu0bD0Ea577FNZ9CzDn%2B60MAdu7VsVIA92W4%3Dreserved=0
> >
>
>
> On Mon, Sep 16, 2019 at 11:13 AM Josh Tynjala <
> joshtynj...@bowlerhat.dev>
> wrote:
>
> > Unfortunately, people actively avoid using public vars because we
> warn
> > about them. Our warnings are too aggressive if it doesn't actually
> matter
> > most of the time. Plus, this warning leaves a bad impression because
> it's
> > such a basic feature of the language that pretty much everyone uses.
> >
> > What can we do to provide a more sensible default behavior, while
> also
> > giving someone the ability to tell the compiler that everything can
> be
> > renamed (or selective renaming)?
> >
> > We could add an option that doesn't rename public things by default,
> but
> > can also be toggled to rename everything. I guess we could have some
> > @royalewhatever annotations to give someone selective control over
> which
> > things are renamed or not, if someone needs that. Thoughts?
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7C384429ef197b497fff9408d73add9c25%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637042595795496907sdata=ii0taRMhu0bD0Ea577FNZ9CzDn%2B60MAdu7VsVIA92W4%3Dreserved=0
> >
> >
> >
> > On Mon, Sep 16, 2019 at 10:50 AM Alex Harui  >
> > wrote:
> >
> >> I'm not sure I understand your proposal.  Are you proposing that all
> >> public variables will be quoted and thus not renamed so we never
> warn
> >> again?  I am not in favor of that.  IMO, the vast majority of
> public vars
> >> can be renamed without penalty.  It is only certain classes that
> will be
> >> mapped to external code that matter.
> >>
> >> My 2 cents,
> >> -Alex
> >>
> >> On 9/16/19, 10:46 AM, "Josh Tynjala" 
> wrote:
> >>
> >> You're right. After a number of tests, I cannot find any
> annotation
> >> (or
> >> combination of them) that will prevent the renaming of variables
> >> defined on
> >> a prototype. All of the official advice that I see from Google
> >> suggests
> >> quoting the properties (or using externs). So, from a Royale
> >> 

RE: Async RoyaleUnit Tests

2019-09-17 Thread Yishay Weiss
Ok, thanks for making it clear. We ended up implementing sync xhr requests.




From: Josh Tynjala 
Sent: Monday, September 16, 2019 12:33:45 AM
To: Apache Royale Development 
Subject: Re: Async RoyaleUnit Tests

Async tests are not yet supported by RoyaleUnit. It's something that I hope
to add when time allows.

--
Josh Tynjala
Bowler Hat LLC 


On Sun, Sep 15, 2019 at 2:15 AM Yishay Weiss  wrote:

> Hi,
>
> We’re trying to create a test suite for out application using RoyaleUnit.
> Some of these tests require loading fonts before running the test. Does
> RoyaleUnit currently support async operations similar to FlexUnit [1].
>
> Or, as a work around, can anyone think of a way to load fonts
> synchronously?
>
> Thanks,
> Yishay
>
> [1] https://flex.apache.org/flexunit/tutorial/flexunit/Unit-13.html
>
>