Re: [royale-asjs] branch develop updated: Fixed #480

[Alex Harui]

Isn't that "just-in-case"?  If the fill does not change at runtime, each 
instance still called the updateView() function?

-Alex

On 9/23/19, 10:59 PM, "ha...@apache.org"  wrote:

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

harbs pushed a commit to branch develop
in repository 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitbox.apache.org%2Frepos%2Fasf%2Froyale-asjs.git&data=02%7C01%7Caharui%40adobe.com%7C73268a23c1b24e8ba02608d740b45db4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637049015762045896&sdata=xwfUPtLkxckotV3Z9qxLRsbIajGXsHbwMvUuLrfqTgo%3D&reserved=0


The following commit(s) were added to refs/heads/develop by this push:
 new 8cc19cd  Fixed #480
8cc19cd is described below

commit 8cc19cd55a6f1345fb60ca65cf3a2cdb4bf8d95f
Author: Harbs 
AuthorDate: Tue Sep 24 08:59:19 2019 +0300

Fixed #480
---
 .../royale/org/apache/royale/svg/GraphicShape.as   | 215 
+++--
 1 file changed, 112 insertions(+), 103 deletions(-)

diff --git 
a/frameworks/projects/Basic/src/main/royale/org/apache/royale/svg/GraphicShape.as
 
b/frameworks/projects/Basic/src/main/royale/org/apache/royale/svg/GraphicShape.as
index 35022f8..7c9590f 100644
--- 
a/frameworks/projects/Basic/src/main/royale/org/apache/royale/svg/GraphicShape.as
+++ 
b/frameworks/projects/Basic/src/main/royale/org/apache/royale/svg/GraphicShape.as
@@ -1,13 +1,13 @@
 /*
  *
- *  Licensed to the Apache Software Foundation (ASF) under one or more
- *  contributor license agreements.  See the NOTICE file distributed with
- *  this work for additional information regarding copyright ownership.
- *  The ASF licenses this file to You under the Apache License, Version 2.0
- *  (the "License"); you may not use this file except in compliance with
- *  the License.  You may obtain a copy of the License at
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.You may obtain a copy of the License at
  *
- * 
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache.org%2Flicenses%2FLICENSE-2.0&data=02%7C01%7Caharui%40adobe.com%7C73268a23c1b24e8ba02608d740b45db4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637049015762045896&sdata=dTjoDtE%2Bzu9qICpIB1tXi%2FlOHLanI0CEhITLYVu90A8%3D&reserved=0
+ *  
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache.org%2Flicenses%2FLICENSE-2.0&data=02%7C01%7Caharui%40adobe.com%7C73268a23c1b24e8ba02608d740b45db4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637049015762045896&sdata=dTjoDtE%2Bzu9qICpIB1tXi%2FlOHLanI0CEhITLYVu90A8%3D&reserved=0
  *
  * Unless required by applicable law or agreed to in writing, software
  * distributed under the License is distributed on an "AS IS" BASIS,
@@ -19,20 +19,20 @@
 package org.apache.royale.svg
 {
COMPILE::SWF
-{
+   {
import flash.display.Graphics;
import flash.display.Sprite;
import flash.geom.Point;
import flash.geom.Rectangle;
import org.apache.royale.core.WrappedSprite;
-}
-COMPILE::JS
-{
-import org.apache.royale.core.WrappedHTMLElement;
-import org.apache.royale.html.util.addSvgElementToWrapper;
-}
+   }
+   COMPILE::JS
+   {
+   import org.apache.royale.core.WrappedHTMLElement;
+   import org.apache.royale.html.util.addSvgElementToWrapper;
+   }
 
-import org.apache.royale.core.IRoyaleElement;
+   import org.apache.royale.core.IRoyaleElement;
import org.apache.royale.core.UIBase;
import org.apache.royale.graphics.IFill;
import org.apache.royale.graphics.IStroke;
@@ -50,16 +50,17 @@ package org.apache.royale.svg
}
 
/**
-*  A solid color fill.
+*  A solid color fill.
 *
-*  @langversion 3.0
-*  @playerversion Flash 9
-*  @playerversion AIR 1.1
-*  @productversion Royale 0.0
+*  @langversion 3.0
+*  @playerversion Flash 9
+*  @playerversion AIR 1.1
+*  @productversion Royale 0.0
 */
public function set stroke(value:IStroke):void
{
_stroke = value;
+   updateView();
}
 
public f

Build failed in Jenkins: royale-asjs_MXTests #1185

[Apache Royale CI Server]

See 


Changes:

[harbs] Fixed #480

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

Build failed in Jenkins: royale-asjs_MXTests #1184

[Apache Royale CI Server]

See 


--
[...truncated 1003.42 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
[mx

Re: [Discuss] Discuss Release Apache Royale 0.9.6 RC2

[Alex Harui]

OK, I think I saw Maven build with and without the Flash stuff.  I pushed the 
changes to the release branch.  The changes required reverting the version 
numbers on royale-compiler and royale-asjs but not royale-typedefs.

To build with the Adobe stuff with Maven, you will have to use system 
properties (as well as profiles):

  -Dgenerate.swf.swcs=true

Or for examples:

  -Dgenerate.swf=true

Thanks,
-Alex

On 9/23/19, 1:29 PM, "Alex Harui"  wrote:

The reason I am unsure about this release is that, in theory, we all agreed 
to be PMC members to make growing the community our primary goal.  To achieve 
that goal, we should be doing things to attract not just new users, but even 
more importantly, new committers.  We know we've got tons of bugs and features 
to work on, so we want someone to grab the release, try it, and when they find 
a problem, we want them to try to fix it.  And right now, they won't be able to 
build with Ant or Maven without the Adobe stuff.

I imagine you are quite frustrated by now, but I am also frustrated because 
I see people spending energy on guessing at workarounds instead of actually 
taking the time to analyze and propose solutions.  And then I end up putting 
off my other tasks to do the analysis, and IMO, that doesn't help the community 
nearly as much as having other committers/PMC members develop the skills to 
solve problems like this in the future.

My 2 cents,
-Alex

On 9/23/19, 8:59 AM, "Piotr Zarzycki"  wrote:

My point is that all those fixes are for SDK Developers, not for Users. 
I
would like to satisfy users not SDK developers, the first one are 
waiting
too long for release.

pon., 23 wrz 2019 o 17:53 Alex Harui  
napisał(a):

> Depends on your definition of small.  The .mvn/extensions.xml is 
missing
> from royale-compiler.  That's why it won't auto-download the Adobe 
stuff.
>
> Then almost every pom.xml needs to be changed to support js-only.
>
> -Alex
>
> On 9/23/19, 8:50 AM, "Piotr Zarzycki"  
wrote:
>
> Alex,
>
> Carlos is able to build framework by ANT so to me it's enough to 
go
> with
> release. I have pushed him to try cause I thought that with some 
small
> workarounds he will be able to build that as well.
>
> Thanks,
> Piotr
>
> pon., 23 wrz 2019 o 17:46 Alex Harui 
> napisał(a):
>
> > Update:  There is definitely a problem with the source package 
that
> > prevents building the source with Maven from a truly clean 
machine.
> I have
> > some changes pending.  This is going to be a pretty large 
commit as
> if
> > affects a lot of files.   I'm not sure why Piotr is have Carlos
> continue to
> > try things.  That seems like duplication of effort to me.  I 
will
> hopefully
> > have this working by end of my day today.
> >
> > -Alex
> >
> > On 9/21/19, 4:51 PM, "Alex Harui"  
wrote:
> >
> > I changed the subject to try to keep the threads separated.
> >
> > Please remember that the scripts and instructions are biased
> towards
> > js-only.  If you have PLAYERGLOBAL_HOME, AIR_HOME, and
> FLASHPLAYER_DEBUGGER
> > set then you will need different profiles.
> >
> > Looks like this failure is caused by change 228f4fbd1.  
There
> should
> > not be hard dependencies on Adobe stuff in order to support 
js-only.
> >
> > In testing a fix, I found out how to reproduce Josh's first
> issue with
> > the Maven build from a clean machine (remove all adobe and 
royale
> artifacts
> > from local repo) for js-only.  More changes to the poms are
> necessary.  I
> > will try to figure it out.
> >
> > And so, this means that a few more folks are likely to have
> trouble
> > building from source.  Again, most folks are going to just use 
the
> > binaries, but I'm worried about first impressions for those who 
do
> use the
> > source.
> >
> > -Alex
> >
> > On 9/21/19, 2:32 PM, "Carlos Rovira" 

> wrote:
> >
> > HI Piotr,
> >
> > since I have work to do on docs, I prefer to try with 
some
> > concrete info,
> > or I'll end going like chicken without head :)
> > I can test with and without vars on my .bash_profile 
too.
> >
> > 

New apache-royale questions for Sep 23 - Stack Exchange

[Stack Exchange]

***1 new question in [ApacheRoyale Tag Notifications 
filter]()
 on stackexchange.com***


[How to use graphic svg elements with apache 
royale?]()

Fan of Flex, I just discover apache Royale. I knew about FalconJS, I thought it 
was death, but no, after seeing Tour of jewel I'm very exited to use it. Thanks 
to all contributors. I play a little ...

Tagged: svg

by [user3183329]() on 






[Unsubscribe from this 
filter]()
 or change your email preferences by visitingyour [filter subscriptions page on 
stackexchange.com]().

If you no longer want to receive mail from Stack Exchange, unsubscribe from all 
stackexchange.com emails 

Questions? Comments? Let us know on our feedback site at 
.

Stack Exchange, Inc. 110 William St, 28th Floor, NY NY 10038

Re: [Discuss] Discuss Release Apache Royale 0.9.6 RC2

[Alex Harui]

The reason I am unsure about this release is that, in theory, we all agreed to 
be PMC members to make growing the community our primary goal.  To achieve that 
goal, we should be doing things to attract not just new users, but even more 
importantly, new committers.  We know we've got tons of bugs and features to 
work on, so we want someone to grab the release, try it, and when they find a 
problem, we want them to try to fix it.  And right now, they won't be able to 
build with Ant or Maven without the Adobe stuff.

I imagine you are quite frustrated by now, but I am also frustrated because I 
see people spending energy on guessing at workarounds instead of actually 
taking the time to analyze and propose solutions.  And then I end up putting 
off my other tasks to do the analysis, and IMO, that doesn't help the community 
nearly as much as having other committers/PMC members develop the skills to 
solve problems like this in the future.

My 2 cents,
-Alex

On 9/23/19, 8:59 AM, "Piotr Zarzycki"  wrote:

My point is that all those fixes are for SDK Developers, not for Users. I
would like to satisfy users not SDK developers, the first one are waiting
too long for release.

pon., 23 wrz 2019 o 17:53 Alex Harui  napisał(a):

> Depends on your definition of small.  The .mvn/extensions.xml is missing
> from royale-compiler.  That's why it won't auto-download the Adobe stuff.
>
> Then almost every pom.xml needs to be changed to support js-only.
>
> -Alex
>
> On 9/23/19, 8:50 AM, "Piotr Zarzycki"  wrote:
>
> Alex,
>
> Carlos is able to build framework by ANT so to me it's enough to go
> with
> release. I have pushed him to try cause I thought that with some small
> workarounds he will be able to build that as well.
>
> Thanks,
> Piotr
>
> pon., 23 wrz 2019 o 17:46 Alex Harui 
> napisał(a):
>
> > Update:  There is definitely a problem with the source package that
> > prevents building the source with Maven from a truly clean machine.
> I have
> > some changes pending.  This is going to be a pretty large commit as
> if
> > affects a lot of files.   I'm not sure why Piotr is have Carlos
> continue to
> > try things.  That seems like duplication of effort to me.  I will
> hopefully
> > have this working by end of my day today.
> >
> > -Alex
> >
> > On 9/21/19, 4:51 PM, "Alex Harui"  wrote:
> >
> > I changed the subject to try to keep the threads separated.
> >
> > Please remember that the scripts and instructions are biased
> towards
> > js-only.  If you have PLAYERGLOBAL_HOME, AIR_HOME, and
> FLASHPLAYER_DEBUGGER
> > set then you will need different profiles.
> >
> > Looks like this failure is caused by change 228f4fbd1.  There
> should
> > not be hard dependencies on Adobe stuff in order to support js-only.
> >
> > In testing a fix, I found out how to reproduce Josh's first
> issue with
> > the Maven build from a clean machine (remove all adobe and royale
> artifacts
> > from local repo) for js-only.  More changes to the poms are
> necessary.  I
> > will try to figure it out.
> >
> > And so, this means that a few more folks are likely to have
> trouble
> > building from source.  Again, most folks are going to just use the
> > binaries, but I'm worried about first impressions for those who do
> use the
> > source.
> >
> > -Alex
> >
> > On 9/21/19, 2:32 PM, "Carlos Rovira" 
> wrote:
> >
> > HI Piotr,
> >
> > since I have work to do on docs, I prefer to try with some
> > concrete info,
> > or I'll end going like chicken without head :)
> > I can test with and without vars on my .bash_profile too.
> >
> > Even we can release 0.9.6 and left this issues for 0.9.7
> >
> > thanks
> >
> > Carlos
> >
> >
> >
> >
> > El sáb., 21 sept. 2019 a las 22:44, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>) escribió:
> >
> > > You have example of such file in repository. Just based on
> that
> > setup
> > > staging link repository. Currently in that file you have
> > Snapshot links and
> > > release. Based on this you can setup staging.
> > >
> > > Apart of that I have shared such file some time ago in the
> > previous
> > > releases.
> > >
> > > I'm not sure even if that i

Re: [DISCUSS] Release Apache Royale 0.9.6 RC2

[Alex Harui]

The value is different for each individual's computer.  It is meant as an 
acceptance of a LICENSE, not a workaround to avoid acceptance of a LICENSE.

-Alex

On 9/23/19, 9:40 AM, "Piotr Zarzycki"  wrote:

Do you have this env. setup
systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted ? You need
to have with value I think  6d2bc022.

pon., 23 wrz 2019 o 18:33 Carlos Rovira 
napisał(a):

> Hi Piotr,
>
> For this hour my laptop was running the build again, and now the script
> seems to end in an endless loop repeating this in console all the time:
>
>
> 
"Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=6d2bc022
> )
>
> Do you accept (Yes/No) ? Your System-Id: 6d2bc022
>
> The Adobe SDK license agreement applies to the Adobe AIR SDK. Do you want
> to install the Adobe AIR SDK? Adobe AIR SDK License:
> http://www.adobe.com/products/air/sdk-eula.html
>
> (In a non-interactive build such as a CI server build, alternatively to
> typing y or yes you can also set a system property containing your system
> which is interpreted as equivalent to accepting by typing y or yes: -"
>
> I can launch it again to see what happens...
>
>
>
>
> El lun., 23 sept. 2019 a las 17:16, Carlos Rovira (<
> carlosrov...@apache.org>)
> escribió:
>
> > Hi Piotr,
> >
> > sorry, ignore my latest emails. Since I forgot to switch .m2
> repositories.
> > In the real one there's no such layout
> > Going to rerun again.
> >
> >
> >
> >
> > El lun., 23 sept. 2019 a las 17:13, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>) escribió:
> >
> >> Ok so what is the output of your build now ?
> >>
> >> pon., 23 wrz 2019 o 17:11 Carlos Rovira 
> >> napisał(a):
> >>
> >> > Hi Piotr,
> >> > since finally layouts are the same, I think is not worth it to do the
> >> > sending.
> >> > The only difference is the file exposed in my last email
> >> >
> >> > El lun., 23 sept. 2019 a las 16:47, Piotr Zarzycki (<
> >> > piotrzarzyck...@gmail.com>) escribió:
> >> >
> >> > > Carlos,
> >> > >
> >> > > Mailing list won't allow post screenshot. Upload them somewhere and
> >> post
> >> > > links.
> >> > >
> >> > > pon., 23 wrz 2019 o 16:27 Carlos Rovira 
> >> > > napisał(a):
> >> > >
> >> > > > Hi all,
> >> > > >
> >> > > > Piotr and I discover off list the following:
> >> > > >
> >> > > > this is what I have in my .m2
> >> > > > [image: Captura de pantalla 2019-09-23 a las 16.11.04.png]
> >> > > >
> >> > > >
> >> > > > and this the Pitro's package layout that sent me off list:
> >> > > >
> >> > > > [image: Captura de pantalla 2019-09-23 a las 16.12.19.png]
> >> > > >
> >> > > > how is possible Piotr and I get different layouts?
> >> > > >
> >> > > > I'll try to build now with his layout
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > > El lun., 23 sept. 2019 a las 16:04, Piotr Zarzycki (<
> >> > > > piotrzarzyck...@gmail.com>) escribió:
> >> > > >
> >> > > >> Carlos,
> >> > > >>
> >> > > >> It's not exactly the same, cause my settings eliminate one issue
> >> from
> >> > > your
> >> > > >> log. I have send you player global off list - just put it
> manually
> >> > into
> >> > > >> Maven folder and try again.
> >> > > >>
> >> > > >> Thanks,
> >> > > >> Piotr
> >> > > >>
> >> > > >> pon., 23 wrz 2019 o 13:50 Carlos Rovira  >
> >> > > >> napisał(a):
> >> > > >>
> >> > > >> > Hi,
> >> > > >> >
> >> > > >> > sorry to say that build failed. Here's the final log. Mostly
> the
> >> > same
> >> > > >> > problem with flash player as always:
> >> > > >> >
> >> > > >> > 0 MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress
> (1):
> >> > > >> 1.0/1.0
> >> > > >> > MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress 
(1):
> >> > > 1.0/1.0
> >> > > >> > MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress 
(1):
> >> > > 1.0/1.0
> >> > > >> > MBProgress (1): 1.0 MBDownloaded from
> >> > central:
> >> > > >> >
> >> > > >>
> >> > >
> >> >
> >>
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepo.maven.apache.org%2Fmaven2%2Fde%2Fjflex%2Fjflex%2F1.6.0%2Fjflex-1.6.0.jar&data=02%7C01%7Caharui%40adobe.com%7C003d6d99b4834f7bdf8a08d74044c278%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637048536383335101&sdata=6qsq1FXxf6UnlEpHIYN1JVURpQsdV99PwD9kpipbQlc%3D&reserved=0
> >> > > >> > (1.0 MB at 3.7 MB/s)[INFO]
> >> > > >> >
> >> > >
> >> 

> >> > > >> >
> >> > > >> > [I

[DISCUSS] Release Apache Royale 0.9.6 RC2

[Piotr Zarzycki]

Anyone know what should Carlos setup in that environment variable to pass
farther?

On Mon, Sep 23, 2019, 7:18 PM Carlos Rovira  wrote:

> Hi,
> process did the same endless loop.
>
> @Piotr Zarzycki  do you mean to add to may
> .bash_profile "export
> systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted= 6d2bc022" ?
>
>
>
> El lun., 23 sept. 2019 a las 18:40, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > Do you have this env. setup
> > systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted ? You need
> > to have with value I think  6d2bc022.
> >
> > pon., 23 wrz 2019 o 18:33 Carlos Rovira 
> > napisał(a):
> >
> > > Hi Piotr,
> > >
> > > For this hour my laptop was running the build again, and now the script
> > > seems to end in an endless loop repeating this in console all the time:
> > >
> > >
> > >
> >
> "Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=6d2bc022
> > > )
> > >
> > > Do you accept (Yes/No) ? Your System-Id: 6d2bc022
> > >
> > > The Adobe SDK license agreement applies to the Adobe AIR SDK. Do you
> want
> > > to install the Adobe AIR SDK? Adobe AIR SDK License:
> > > http://www.adobe.com/products/air/sdk-eula.html
> > >
> > > (In a non-interactive build such as a CI server build, alternatively to
> > > typing y or yes you can also set a system property containing your
> system
> > > which is interpreted as equivalent to accepting by typing y or yes: -"
> > >
> > > I can launch it again to see what happens...
> > >
> > >
> > >
> > >
> > > El lun., 23 sept. 2019 a las 17:16, Carlos Rovira (<
> > > carlosrov...@apache.org>)
> > > escribió:
> > >
> > > > Hi Piotr,
> > > >
> > > > sorry, ignore my latest emails. Since I forgot to switch .m2
> > > repositories.
> > > > In the real one there's no such layout
> > > > Going to rerun again.
> > > >
> > > >
> > > >
> > > >
> > > > El lun., 23 sept. 2019 a las 17:13, Piotr Zarzycki (<
> > > > piotrzarzyck...@gmail.com>) escribió:
> > > >
> > > >> Ok so what is the output of your build now ?
> > > >>
> > > >> pon., 23 wrz 2019 o 17:11 Carlos Rovira 
> > > >> napisał(a):
> > > >>
> > > >> > Hi Piotr,
> > > >> > since finally layouts are the same, I think is not worth it to do
> > the
> > > >> > sending.
> > > >> > The only difference is the file exposed in my last email
> > > >> >
> > > >> > El lun., 23 sept. 2019 a las 16:47, Piotr Zarzycki (<
> > > >> > piotrzarzyck...@gmail.com>) escribió:
> > > >> >
> > > >> > > Carlos,
> > > >> > >
> > > >> > > Mailing list won't allow post screenshot. Upload them somewhere
> > and
> > > >> post
> > > >> > > links.
> > > >> > >
> > > >> > > pon., 23 wrz 2019 o 16:27 Carlos Rovira <
> carlosrov...@apache.org>
> > > >> > > napisał(a):
> > > >> > >
> > > >> > > > Hi all,
> > > >> > > >
> > > >> > > > Piotr and I discover off list the following:
> > > >> > > >
> > > >> > > > this is what I have in my .m2
> > > >> > > > [image: Captura de pantalla 2019-09-23 a las 16.11.04.png]
> > > >> > > >
> > > >> > > >
> > > >> > > > and this the Pitro's package layout that sent me off list:
> > > >> > > >
> > > >> > > > [image: Captura de pantalla 2019-09-23 a las 16.12.19.png]
> > > >> > > >
> > > >> > > > how is possible Piotr and I get different layouts?
> > > >> > > >
> > > >> > > > I'll try to build now with his layout
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > > >> > > > El lun., 23 sept. 2019 a las 16:04, Piotr Zarzycki (<
> > > >> > > > piotrzarzyck...@gmail.com>) escribió:
> > > >> > > >
> > > >> > > >> Carlos,
> > > >> > > >>
> > > >> > > >> It's not exactly the same, cause my settings eliminate one
> > issue
> > > >> from
> > > >> > > your
> > > >> > > >> log. I have send you player global off list - just put it
> > > manually
> > > >> > into
> > > >> > > >> Maven folder and try again.
> > > >> > > >>
> > > >> > > >> Thanks,
> > > >> > > >> Piotr
> > > >> > > >>
> > > >> > > >> pon., 23 wrz 2019 o 13:50 Carlos Rovira <
> > carlosrov...@apache.org
> > > >
> > > >> > > >> napisał(a):
> > > >> > > >>
> > > >> > > >> > Hi,
> > > >> > > >> >
> > > >> > > >> > sorry to say that build failed. Here's the final log.
> Mostly
> > > the
> > > >> > same
> > > >> > > >> > problem with flash player as always:
> > > >> > > >> >
> > > >> > > >> > 0 MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0
> MBProgress
> > > (1):
> > > >> > > >> 1.0/1.0
> > > >> > > >> > MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress
> > (1):
> > > >> > > 1.0/1.0
> > > >> > > >> > MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress
> > (1):
> > > >> > > 1.0/1.0
> > > >> > > >> > MBProgress (1): 1.0 MBDownloaded
> from
> > > >> > central:
> > > >> > > >> >
> > > >> > > >>
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> https://repo.maven.apache.org/maven2/de/jflex/jflex/1.6.0/jflex-1.6.0.jar
> > > >> > > >> > (1.0 MB at 3.7 MB/s)[INFO]
> > > >> > > >> >
> > > >> > >
> > > >>
> > --

[Discuss] Discuss Release Apache Royale 0.9.6 RC2

[Piotr Zarzycki]

Carlos,

Well I don't see importance from user perspective to that changes at all.
It means that you are not going to vote?

Thanks,
Piotr

On Mon, Sep 23, 2019, 7:22 PM Carlos Rovira  wrote:

> Hi,
>
> I will stop for today, want to work a bit on royale-docs mobile layout that
> I have near finish, so I'll wait for Alex changes and try tomorrow. IMHO
> this stuff is important, so it's worth the waiting time of a day or two.
>
> Thanks
>
>
>
>
>
> El lun., 23 sept. 201. 9 a las 17:59, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > My point is that all those fixes are for SDK Developers, not for Users. I
> > would like to satisfy users not SDK developers, the first one are waiting
> > too long for release.
> >
> > pon., 23 wrz 2019 o 17:53 Alex Harui 
> > napisał(a):
> >
> > > Depends on your definition of small.  The .mvn/extensions.xml is
> missing
> > > from royale-compiler.  That's why it won't auto-download the Adobe
> stuff.
> > >
> > > Then almost every pom.xml needs to be changed to support js-only.
> > >
> > > -Alex
> > >
> > > On 9/23/19, 8:50 AM, "Piotr Zarzycki" 
> > wrote:
> > >
> > > Alex,
> > >
> > > Carlos is able to build framework by ANT so to me it's enough to go
> > > with
> > > release. I have pushed him to try cause I thought that with some
> > small
> > > workarounds he will be able to build that as well.
> > >
> > > Thanks,
> > > Piotr
> > >
> > > pon., 23 wrz 2019 o 17:46 Alex Harui 
> > > napisał(a):
> > >
> > > > Update:  There is definitely a problem with the source package
> that
> > > > prevents building the source with Maven from a truly clean
> machine.
> > > I have
> > > > some changes pending.  This is going to be a pretty large commit
> as
> > > if
> > > > affects a lot of files.   I'm not sure why Piotr is have Carlos
> > > continue to
> > > > try things.  That seems like duplication of effort to me.  I will
> > > hopefully
> > > > have this working by end of my day today.
> > > >
> > > > -Alex
> > > >
> > > > On 9/21/19, 4:51 PM, "Alex Harui" 
> > wrote:
> > > >
> > > > I changed the subject to try to keep the threads separated.
> > > >
> > > > Please remember that the scripts and instructions are biased
> > > towards
> > > > js-only.  If you have PLAYERGLOBAL_HOME, AIR_HOME, and
> > > FLASHPLAYER_DEBUGGER
> > > > set then you will need different profiles.
> > > >
> > > > Looks like this failure is caused by change 228f4fbd1.  There
> > > should
> > > > not be hard dependencies on Adobe stuff in order to support
> > js-only.
> > > >
> > > > In testing a fix, I found out how to reproduce Josh's first
> > > issue with
> > > > the Maven build from a clean machine (remove all adobe and royale
> > > artifacts
> > > > from local repo) for js-only.  More changes to the poms are
> > > necessary.  I
> > > > will try to figure it out.
> > > >
> > > > And so, this means that a few more folks are likely to have
> > > trouble
> > > > building from source.  Again, most folks are going to just use
> the
> > > > binaries, but I'm worried about first impressions for those who
> do
> > > use the
> > > > source.
> > > >
> > > > -Alex
> > > >
> > > > On 9/21/19, 2:32 PM, "Carlos Rovira" <
> carlosrov...@apache.org>
> > > wrote:
> > > >
> > > > HI Piotr,
> > > >
> > > > since I have work to do on docs, I prefer to try with
> some
> > > > concrete info,
> > > > or I'll end going like chicken without head :)
> > > > I can test with and without vars on my .bash_profile too.
> > > >
> > > > Even we can release 0.9.6 and left this issues for 0.9.7
> > > >
> > > > thanks
> > > >
> > > > Carlos
> > > >
> > > >
> > > >
> > > >
> > > > El sáb., 21 sept. 2019 a las 22:44, Piotr Zarzycki (<
> > > > piotrzarzyck...@gmail.com>) escribió:
> > > >
> > > > > You have example of such file in repository. Just based
> > on
> > > that
> > > > setup
> > > > > staging link repository. Currently in that file you
> have
> > > > Snapshot links and
> > > > > release. Based on this you can setup staging.
> > > > >
> > > > > Apart of that I have shared such file some time ago in
> > the
> > > > previous
> > > > > releases.
> > > > >
> > > > > I'm not sure even if that is needed it's just I wanted
> to
> > > > confirm that is
> > > > > really not needed.
> > > > >
> > > > > Do you have player global setup env variable?
> > > > >
> > > > > If you won't figure out stuff I will share it on
> Monday.
> > > > >
> > > > > Thanks,
> > > > > Piotr
> > > > >
> >

Re: [Discuss] Discuss Release Apache Royale 0.9.6 RC2

[Carlos Rovira]

Hi,

I will stop for today, want to work a bit on royale-docs mobile layout that
I have near finish, so I'll wait for Alex changes and try tomorrow. IMHO
this stuff is important, so it's worth the waiting time of a day or two.

Thanks





El lun., 23 sept. 201. 9 a las 17:59, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> My point is that all those fixes are for SDK Developers, not for Users. I
> would like to satisfy users not SDK developers, the first one are waiting
> too long for release.
>
> pon., 23 wrz 2019 o 17:53 Alex Harui 
> napisał(a):
>
> > Depends on your definition of small.  The .mvn/extensions.xml is missing
> > from royale-compiler.  That's why it won't auto-download the Adobe stuff.
> >
> > Then almost every pom.xml needs to be changed to support js-only.
> >
> > -Alex
> >
> > On 9/23/19, 8:50 AM, "Piotr Zarzycki" 
> wrote:
> >
> > Alex,
> >
> > Carlos is able to build framework by ANT so to me it's enough to go
> > with
> > release. I have pushed him to try cause I thought that with some
> small
> > workarounds he will be able to build that as well.
> >
> > Thanks,
> > Piotr
> >
> > pon., 23 wrz 2019 o 17:46 Alex Harui 
> > napisał(a):
> >
> > > Update:  There is definitely a problem with the source package that
> > > prevents building the source with Maven from a truly clean machine.
> > I have
> > > some changes pending.  This is going to be a pretty large commit as
> > if
> > > affects a lot of files.   I'm not sure why Piotr is have Carlos
> > continue to
> > > try things.  That seems like duplication of effort to me.  I will
> > hopefully
> > > have this working by end of my day today.
> > >
> > > -Alex
> > >
> > > On 9/21/19, 4:51 PM, "Alex Harui" 
> wrote:
> > >
> > > I changed the subject to try to keep the threads separated.
> > >
> > > Please remember that the scripts and instructions are biased
> > towards
> > > js-only.  If you have PLAYERGLOBAL_HOME, AIR_HOME, and
> > FLASHPLAYER_DEBUGGER
> > > set then you will need different profiles.
> > >
> > > Looks like this failure is caused by change 228f4fbd1.  There
> > should
> > > not be hard dependencies on Adobe stuff in order to support
> js-only.
> > >
> > > In testing a fix, I found out how to reproduce Josh's first
> > issue with
> > > the Maven build from a clean machine (remove all adobe and royale
> > artifacts
> > > from local repo) for js-only.  More changes to the poms are
> > necessary.  I
> > > will try to figure it out.
> > >
> > > And so, this means that a few more folks are likely to have
> > trouble
> > > building from source.  Again, most folks are going to just use the
> > > binaries, but I'm worried about first impressions for those who do
> > use the
> > > source.
> > >
> > > -Alex
> > >
> > > On 9/21/19, 2:32 PM, "Carlos Rovira" 
> > wrote:
> > >
> > > HI Piotr,
> > >
> > > since I have work to do on docs, I prefer to try with some
> > > concrete info,
> > > or I'll end going like chicken without head :)
> > > I can test with and without vars on my .bash_profile too.
> > >
> > > Even we can release 0.9.6 and left this issues for 0.9.7
> > >
> > > thanks
> > >
> > > Carlos
> > >
> > >
> > >
> > >
> > > El sáb., 21 sept. 2019 a las 22:44, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>) escribió:
> > >
> > > > You have example of such file in repository. Just based
> on
> > that
> > > setup
> > > > staging link repository. Currently in that file you have
> > > Snapshot links and
> > > > release. Based on this you can setup staging.
> > > >
> > > > Apart of that I have shared such file some time ago in
> the
> > > previous
> > > > releases.
> > > >
> > > > I'm not sure even if that is needed it's just I wanted to
> > > confirm that is
> > > > really not needed.
> > > >
> > > > Do you have player global setup env variable?
> > > >
> > > > If you won't figure out stuff I will share it on Monday.
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > On Sat, Sep 21, 2019, 8:06 PM Carlos Rovira <
> > > carlosrov...@apache.org>
> > > > wrote:
> > > >
> > > > > Hi Piort,
> > > > >
> > > > > can you share here the set of links to add to my
> > > .m2/settings.xml?
> > > > >
> > > > > thanks
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > El sáb., 21 sept. 2019 a las 19:02, Piotr Zarzycki (

Re: [DISCUSS] Release Apache Royale 0.9.6 RC2

[Carlos Rovira]

Hi,
process did the same endless loop.

@Piotr Zarzycki  do you mean to add to may
.bash_profile "export
systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted= 6d2bc022" ?



El lun., 23 sept. 2019 a las 18:40, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> Do you have this env. setup
> systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted ? You need
> to have with value I think  6d2bc022.
>
> pon., 23 wrz 2019 o 18:33 Carlos Rovira 
> napisał(a):
>
> > Hi Piotr,
> >
> > For this hour my laptop was running the build again, and now the script
> > seems to end in an endless loop repeating this in console all the time:
> >
> >
> >
> "Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=6d2bc022
> > )
> >
> > Do you accept (Yes/No) ? Your System-Id: 6d2bc022
> >
> > The Adobe SDK license agreement applies to the Adobe AIR SDK. Do you want
> > to install the Adobe AIR SDK? Adobe AIR SDK License:
> > http://www.adobe.com/products/air/sdk-eula.html
> >
> > (In a non-interactive build such as a CI server build, alternatively to
> > typing y or yes you can also set a system property containing your system
> > which is interpreted as equivalent to accepting by typing y or yes: -"
> >
> > I can launch it again to see what happens...
> >
> >
> >
> >
> > El lun., 23 sept. 2019 a las 17:16, Carlos Rovira (<
> > carlosrov...@apache.org>)
> > escribió:
> >
> > > Hi Piotr,
> > >
> > > sorry, ignore my latest emails. Since I forgot to switch .m2
> > repositories.
> > > In the real one there's no such layout
> > > Going to rerun again.
> > >
> > >
> > >
> > >
> > > El lun., 23 sept. 2019 a las 17:13, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>) escribió:
> > >
> > >> Ok so what is the output of your build now ?
> > >>
> > >> pon., 23 wrz 2019 o 17:11 Carlos Rovira 
> > >> napisał(a):
> > >>
> > >> > Hi Piotr,
> > >> > since finally layouts are the same, I think is not worth it to do
> the
> > >> > sending.
> > >> > The only difference is the file exposed in my last email
> > >> >
> > >> > El lun., 23 sept. 2019 a las 16:47, Piotr Zarzycki (<
> > >> > piotrzarzyck...@gmail.com>) escribió:
> > >> >
> > >> > > Carlos,
> > >> > >
> > >> > > Mailing list won't allow post screenshot. Upload them somewhere
> and
> > >> post
> > >> > > links.
> > >> > >
> > >> > > pon., 23 wrz 2019 o 16:27 Carlos Rovira 
> > >> > > napisał(a):
> > >> > >
> > >> > > > Hi all,
> > >> > > >
> > >> > > > Piotr and I discover off list the following:
> > >> > > >
> > >> > > > this is what I have in my .m2
> > >> > > > [image: Captura de pantalla 2019-09-23 a las 16.11.04.png]
> > >> > > >
> > >> > > >
> > >> > > > and this the Pitro's package layout that sent me off list:
> > >> > > >
> > >> > > > [image: Captura de pantalla 2019-09-23 a las 16.12.19.png]
> > >> > > >
> > >> > > > how is possible Piotr and I get different layouts?
> > >> > > >
> > >> > > > I'll try to build now with his layout
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > > El lun., 23 sept. 2019 a las 16:04, Piotr Zarzycki (<
> > >> > > > piotrzarzyck...@gmail.com>) escribió:
> > >> > > >
> > >> > > >> Carlos,
> > >> > > >>
> > >> > > >> It's not exactly the same, cause my settings eliminate one
> issue
> > >> from
> > >> > > your
> > >> > > >> log. I have send you player global off list - just put it
> > manually
> > >> > into
> > >> > > >> Maven folder and try again.
> > >> > > >>
> > >> > > >> Thanks,
> > >> > > >> Piotr
> > >> > > >>
> > >> > > >> pon., 23 wrz 2019 o 13:50 Carlos Rovira <
> carlosrov...@apache.org
> > >
> > >> > > >> napisał(a):
> > >> > > >>
> > >> > > >> > Hi,
> > >> > > >> >
> > >> > > >> > sorry to say that build failed. Here's the final log. Mostly
> > the
> > >> > same
> > >> > > >> > problem with flash player as always:
> > >> > > >> >
> > >> > > >> > 0 MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress
> > (1):
> > >> > > >> 1.0/1.0
> > >> > > >> > MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress
> (1):
> > >> > > 1.0/1.0
> > >> > > >> > MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress
> (1):
> > >> > > 1.0/1.0
> > >> > > >> > MBProgress (1): 1.0 MBDownloaded from
> > >> > central:
> > >> > > >> >
> > >> > > >>
> > >> > >
> > >> >
> > >>
> >
> https://repo.maven.apache.org/maven2/de/jflex/jflex/1.6.0/jflex-1.6.0.jar
> > >> > > >> > (1.0 MB at 3.7 MB/s)[INFO]
> > >> > > >> >
> > >> > >
> > >>
> 
> > >> > > >> >
> > >> > > >> > [INFO] Reactor Summary for Apache Royale: Compiler: Parent
> > 0.9.6:
> > >> > > >> >
> > >> > > >> > [INFO]
> > >> > > >> >
> > >> > > >> > [INFO] Apache Royale: Compiler: Parent 
> > >> SUCCESS
> > >> > [
> > >> > > >> > 6.206 s]
> > >> > > >> >
> > >> > > >> > [INFO] Apache Royale: Compiler: Compiler-Common ...
> > >> SUCCESS
> > >> > > >> [01:24
> > >> > > >> > min]
> > >> > > >> >
> > >> > > >> > 

Re: [DISCUSS] Release Apache Royale 0.9.6 RC2

[Piotr Zarzycki]

Do you have this env. setup
systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted ? You need
to have with value I think  6d2bc022.

pon., 23 wrz 2019 o 18:33 Carlos Rovira 
napisał(a):

> Hi Piotr,
>
> For this hour my laptop was running the build again, and now the script
> seems to end in an endless loop repeating this in console all the time:
>
>
> "Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=6d2bc022
> )
>
> Do you accept (Yes/No) ? Your System-Id: 6d2bc022
>
> The Adobe SDK license agreement applies to the Adobe AIR SDK. Do you want
> to install the Adobe AIR SDK? Adobe AIR SDK License:
> http://www.adobe.com/products/air/sdk-eula.html
>
> (In a non-interactive build such as a CI server build, alternatively to
> typing y or yes you can also set a system property containing your system
> which is interpreted as equivalent to accepting by typing y or yes: -"
>
> I can launch it again to see what happens...
>
>
>
>
> El lun., 23 sept. 2019 a las 17:16, Carlos Rovira (<
> carlosrov...@apache.org>)
> escribió:
>
> > Hi Piotr,
> >
> > sorry, ignore my latest emails. Since I forgot to switch .m2
> repositories.
> > In the real one there's no such layout
> > Going to rerun again.
> >
> >
> >
> >
> > El lun., 23 sept. 2019 a las 17:13, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>) escribió:
> >
> >> Ok so what is the output of your build now ?
> >>
> >> pon., 23 wrz 2019 o 17:11 Carlos Rovira 
> >> napisał(a):
> >>
> >> > Hi Piotr,
> >> > since finally layouts are the same, I think is not worth it to do the
> >> > sending.
> >> > The only difference is the file exposed in my last email
> >> >
> >> > El lun., 23 sept. 2019 a las 16:47, Piotr Zarzycki (<
> >> > piotrzarzyck...@gmail.com>) escribió:
> >> >
> >> > > Carlos,
> >> > >
> >> > > Mailing list won't allow post screenshot. Upload them somewhere and
> >> post
> >> > > links.
> >> > >
> >> > > pon., 23 wrz 2019 o 16:27 Carlos Rovira 
> >> > > napisał(a):
> >> > >
> >> > > > Hi all,
> >> > > >
> >> > > > Piotr and I discover off list the following:
> >> > > >
> >> > > > this is what I have in my .m2
> >> > > > [image: Captura de pantalla 2019-09-23 a las 16.11.04.png]
> >> > > >
> >> > > >
> >> > > > and this the Pitro's package layout that sent me off list:
> >> > > >
> >> > > > [image: Captura de pantalla 2019-09-23 a las 16.12.19.png]
> >> > > >
> >> > > > how is possible Piotr and I get different layouts?
> >> > > >
> >> > > > I'll try to build now with his layout
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > > El lun., 23 sept. 2019 a las 16:04, Piotr Zarzycki (<
> >> > > > piotrzarzyck...@gmail.com>) escribió:
> >> > > >
> >> > > >> Carlos,
> >> > > >>
> >> > > >> It's not exactly the same, cause my settings eliminate one issue
> >> from
> >> > > your
> >> > > >> log. I have send you player global off list - just put it
> manually
> >> > into
> >> > > >> Maven folder and try again.
> >> > > >>
> >> > > >> Thanks,
> >> > > >> Piotr
> >> > > >>
> >> > > >> pon., 23 wrz 2019 o 13:50 Carlos Rovira  >
> >> > > >> napisał(a):
> >> > > >>
> >> > > >> > Hi,
> >> > > >> >
> >> > > >> > sorry to say that build failed. Here's the final log. Mostly
> the
> >> > same
> >> > > >> > problem with flash player as always:
> >> > > >> >
> >> > > >> > 0 MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress
> (1):
> >> > > >> 1.0/1.0
> >> > > >> > MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1):
> >> > > 1.0/1.0
> >> > > >> > MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1):
> >> > > 1.0/1.0
> >> > > >> > MBProgress (1): 1.0 MBDownloaded from
> >> > central:
> >> > > >> >
> >> > > >>
> >> > >
> >> >
> >>
> https://repo.maven.apache.org/maven2/de/jflex/jflex/1.6.0/jflex-1.6.0.jar
> >> > > >> > (1.0 MB at 3.7 MB/s)[INFO]
> >> > > >> >
> >> > >
> >> 
> >> > > >> >
> >> > > >> > [INFO] Reactor Summary for Apache Royale: Compiler: Parent
> 0.9.6:
> >> > > >> >
> >> > > >> > [INFO]
> >> > > >> >
> >> > > >> > [INFO] Apache Royale: Compiler: Parent 
> >> SUCCESS
> >> > [
> >> > > >> > 6.206 s]
> >> > > >> >
> >> > > >> > [INFO] Apache Royale: Compiler: Compiler-Common ...
> >> SUCCESS
> >> > > >> [01:24
> >> > > >> > min]
> >> > > >> >
> >> > > >> > [INFO] Apache Royale: Compiler: Test Utils 
> >> SUCCESS
> >> > [
> >> > > >> > 3.174 s]
> >> > > >> >
> >> > > >> > [INFO] Apache Royale: Compiler: Externc ...
> >> SUCCESS
> >> > [
> >> > > >> > 58.423 s]
> >> > > >> >
> >> > > >> > [INFO] Apache Royale: Compiler: Compiler ..
> >> FAILURE
> >> > [
> >> > > >> > 8.802 s]
> >> > > >> >
> >> > > >> > [INFO] Apache Royale: Compiler: Compiler-JX ...
> >> SKIPPED
> >> > > >> >
> >> > > >> > [INFO] Apache Royale: Compiler: SWFUtils ..
> >> SKIPPED
> >> > > >> >
> >> > > >> > [INFO] Apache Royale: Co

Re: [DISCUSS] Release Apache Royale 0.9.6 RC2

[Carlos Rovira]

Hi Piotr,

For this hour my laptop was running the build again, and now the script
seems to end in an endless loop repeating this in console all the time:

"Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=6d2bc022
)

Do you accept (Yes/No) ? Your System-Id: 6d2bc022

The Adobe SDK license agreement applies to the Adobe AIR SDK. Do you want
to install the Adobe AIR SDK? Adobe AIR SDK License:
http://www.adobe.com/products/air/sdk-eula.html

(In a non-interactive build such as a CI server build, alternatively to
typing y or yes you can also set a system property containing your system
which is interpreted as equivalent to accepting by typing y or yes: -"

I can launch it again to see what happens...




El lun., 23 sept. 2019 a las 17:16, Carlos Rovira ()
escribió:

> Hi Piotr,
>
> sorry, ignore my latest emails. Since I forgot to switch .m2 repositories.
> In the real one there's no such layout
> Going to rerun again.
>
>
>
>
> El lun., 23 sept. 2019 a las 17:13, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
>> Ok so what is the output of your build now ?
>>
>> pon., 23 wrz 2019 o 17:11 Carlos Rovira 
>> napisał(a):
>>
>> > Hi Piotr,
>> > since finally layouts are the same, I think is not worth it to do the
>> > sending.
>> > The only difference is the file exposed in my last email
>> >
>> > El lun., 23 sept. 2019 a las 16:47, Piotr Zarzycki (<
>> > piotrzarzyck...@gmail.com>) escribió:
>> >
>> > > Carlos,
>> > >
>> > > Mailing list won't allow post screenshot. Upload them somewhere and
>> post
>> > > links.
>> > >
>> > > pon., 23 wrz 2019 o 16:27 Carlos Rovira 
>> > > napisał(a):
>> > >
>> > > > Hi all,
>> > > >
>> > > > Piotr and I discover off list the following:
>> > > >
>> > > > this is what I have in my .m2
>> > > > [image: Captura de pantalla 2019-09-23 a las 16.11.04.png]
>> > > >
>> > > >
>> > > > and this the Pitro's package layout that sent me off list:
>> > > >
>> > > > [image: Captura de pantalla 2019-09-23 a las 16.12.19.png]
>> > > >
>> > > > how is possible Piotr and I get different layouts?
>> > > >
>> > > > I'll try to build now with his layout
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > > El lun., 23 sept. 2019 a las 16:04, Piotr Zarzycki (<
>> > > > piotrzarzyck...@gmail.com>) escribió:
>> > > >
>> > > >> Carlos,
>> > > >>
>> > > >> It's not exactly the same, cause my settings eliminate one issue
>> from
>> > > your
>> > > >> log. I have send you player global off list - just put it manually
>> > into
>> > > >> Maven folder and try again.
>> > > >>
>> > > >> Thanks,
>> > > >> Piotr
>> > > >>
>> > > >> pon., 23 wrz 2019 o 13:50 Carlos Rovira 
>> > > >> napisał(a):
>> > > >>
>> > > >> > Hi,
>> > > >> >
>> > > >> > sorry to say that build failed. Here's the final log. Mostly the
>> > same
>> > > >> > problem with flash player as always:
>> > > >> >
>> > > >> > 0 MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1):
>> > > >> 1.0/1.0
>> > > >> > MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1):
>> > > 1.0/1.0
>> > > >> > MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1):
>> > > 1.0/1.0
>> > > >> > MBProgress (1): 1.0 MBDownloaded from
>> > central:
>> > > >> >
>> > > >>
>> > >
>> >
>> https://repo.maven.apache.org/maven2/de/jflex/jflex/1.6.0/jflex-1.6.0.jar
>> > > >> > (1.0 MB at 3.7 MB/s)[INFO]
>> > > >> >
>> > >
>> 
>> > > >> >
>> > > >> > [INFO] Reactor Summary for Apache Royale: Compiler: Parent 0.9.6:
>> > > >> >
>> > > >> > [INFO]
>> > > >> >
>> > > >> > [INFO] Apache Royale: Compiler: Parent 
>> SUCCESS
>> > [
>> > > >> > 6.206 s]
>> > > >> >
>> > > >> > [INFO] Apache Royale: Compiler: Compiler-Common ...
>> SUCCESS
>> > > >> [01:24
>> > > >> > min]
>> > > >> >
>> > > >> > [INFO] Apache Royale: Compiler: Test Utils 
>> SUCCESS
>> > [
>> > > >> > 3.174 s]
>> > > >> >
>> > > >> > [INFO] Apache Royale: Compiler: Externc ...
>> SUCCESS
>> > [
>> > > >> > 58.423 s]
>> > > >> >
>> > > >> > [INFO] Apache Royale: Compiler: Compiler ..
>> FAILURE
>> > [
>> > > >> > 8.802 s]
>> > > >> >
>> > > >> > [INFO] Apache Royale: Compiler: Compiler-JX ...
>> SKIPPED
>> > > >> >
>> > > >> > [INFO] Apache Royale: Compiler: SWFUtils ..
>> SKIPPED
>> > > >> >
>> > > >> > [INFO] Apache Royale: Compiler: Debugger ..
>> SKIPPED
>> > > >> >
>> > > >> > [INFO] Apache Royale: Compiler: OEM Layer .
>> SKIPPED
>> > > >> >
>> > > >> > [INFO] Apache Royale: Royale Ant Tasks 
>> SKIPPED
>> > > >> >
>> > > >> > [INFO] Apache Royale: RoyaleUnit Ant Tasks 
>> SKIPPED
>> > > >> >
>> > > >> > [INFO] Apache Royale: Royale Maven Plugin .
>> SKIPPED
>> > > >> >
>> > > >> > [INFO]
>> > > >> >
>> > >
>> 

Re: [Discuss] Discuss Release Apache Royale 0.9.6 RC2

[Piotr Zarzycki]

My point is that all those fixes are for SDK Developers, not for Users. I
would like to satisfy users not SDK developers, the first one are waiting
too long for release.

pon., 23 wrz 2019 o 17:53 Alex Harui  napisał(a):

> Depends on your definition of small.  The .mvn/extensions.xml is missing
> from royale-compiler.  That's why it won't auto-download the Adobe stuff.
>
> Then almost every pom.xml needs to be changed to support js-only.
>
> -Alex
>
> On 9/23/19, 8:50 AM, "Piotr Zarzycki"  wrote:
>
> Alex,
>
> Carlos is able to build framework by ANT so to me it's enough to go
> with
> release. I have pushed him to try cause I thought that with some small
> workarounds he will be able to build that as well.
>
> Thanks,
> Piotr
>
> pon., 23 wrz 2019 o 17:46 Alex Harui 
> napisał(a):
>
> > Update:  There is definitely a problem with the source package that
> > prevents building the source with Maven from a truly clean machine.
> I have
> > some changes pending.  This is going to be a pretty large commit as
> if
> > affects a lot of files.   I'm not sure why Piotr is have Carlos
> continue to
> > try things.  That seems like duplication of effort to me.  I will
> hopefully
> > have this working by end of my day today.
> >
> > -Alex
> >
> > On 9/21/19, 4:51 PM, "Alex Harui"  wrote:
> >
> > I changed the subject to try to keep the threads separated.
> >
> > Please remember that the scripts and instructions are biased
> towards
> > js-only.  If you have PLAYERGLOBAL_HOME, AIR_HOME, and
> FLASHPLAYER_DEBUGGER
> > set then you will need different profiles.
> >
> > Looks like this failure is caused by change 228f4fbd1.  There
> should
> > not be hard dependencies on Adobe stuff in order to support js-only.
> >
> > In testing a fix, I found out how to reproduce Josh's first
> issue with
> > the Maven build from a clean machine (remove all adobe and royale
> artifacts
> > from local repo) for js-only.  More changes to the poms are
> necessary.  I
> > will try to figure it out.
> >
> > And so, this means that a few more folks are likely to have
> trouble
> > building from source.  Again, most folks are going to just use the
> > binaries, but I'm worried about first impressions for those who do
> use the
> > source.
> >
> > -Alex
> >
> > On 9/21/19, 2:32 PM, "Carlos Rovira" 
> wrote:
> >
> > HI Piotr,
> >
> > since I have work to do on docs, I prefer to try with some
> > concrete info,
> > or I'll end going like chicken without head :)
> > I can test with and without vars on my .bash_profile too.
> >
> > Even we can release 0.9.6 and left this issues for 0.9.7
> >
> > thanks
> >
> > Carlos
> >
> >
> >
> >
> > El sáb., 21 sept. 2019 a las 22:44, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>) escribió:
> >
> > > You have example of such file in repository. Just based on
> that
> > setup
> > > staging link repository. Currently in that file you have
> > Snapshot links and
> > > release. Based on this you can setup staging.
> > >
> > > Apart of that I have shared such file some time ago in the
> > previous
> > > releases.
> > >
> > > I'm not sure even if that is needed it's just I wanted to
> > confirm that is
> > > really not needed.
> > >
> > > Do you have player global setup env variable?
> > >
> > > If you won't figure out stuff I will share it on Monday.
> > >
> > > Thanks,
> > > Piotr
> > >
> > > On Sat, Sep 21, 2019, 8:06 PM Carlos Rovira <
> > carlosrov...@apache.org>
> > > wrote:
> > >
> > > > Hi Piort,
> > > >
> > > > can you share here the set of links to add to my
> > .m2/settings.xml?
> > > >
> > > > thanks
> > > >
> > > >
> > > >
> > > >
> > > > El sáb., 21 sept. 2019 a las 19:02, Piotr Zarzycki (<
> > > > piotrzarzyck...@gmail.com>) escribió:
> > > >
> > > > > Switching subject to discuss.
> > > > >
> > > > > Carlos can you put in your settings link toavem staging
> > artifacts? And
> > > > run
> > > > > approve script again.
> > > > >
> > > > > Thanks,
> > > > > Piotr
> > > > >
> > > > > On Sat, Sep 21, 2019, 6:49 PM Carlos Rovira <
> > carlosrov...@apache.org>
> > > > > wrote:
> > > > >
> > > > > > Curious 

Re: [Discuss] Discuss Release Apache Royale 0.9.6 RC2

[Alex Harui]

Depends on your definition of small.  The .mvn/extensions.xml is missing from 
royale-compiler.  That's why it won't auto-download the Adobe stuff.

Then almost every pom.xml needs to be changed to support js-only.

-Alex

On 9/23/19, 8:50 AM, "Piotr Zarzycki"  wrote:

Alex,

Carlos is able to build framework by ANT so to me it's enough to go with
release. I have pushed him to try cause I thought that with some small
workarounds he will be able to build that as well.

Thanks,
Piotr

pon., 23 wrz 2019 o 17:46 Alex Harui  napisał(a):

> Update:  There is definitely a problem with the source package that
> prevents building the source with Maven from a truly clean machine.  I 
have
> some changes pending.  This is going to be a pretty large commit as if
> affects a lot of files.   I'm not sure why Piotr is have Carlos continue 
to
> try things.  That seems like duplication of effort to me.  I will 
hopefully
> have this working by end of my day today.
>
> -Alex
>
> On 9/21/19, 4:51 PM, "Alex Harui"  wrote:
>
> I changed the subject to try to keep the threads separated.
>
> Please remember that the scripts and instructions are biased towards
> js-only.  If you have PLAYERGLOBAL_HOME, AIR_HOME, and 
FLASHPLAYER_DEBUGGER
> set then you will need different profiles.
>
> Looks like this failure is caused by change 228f4fbd1.  There should
> not be hard dependencies on Adobe stuff in order to support js-only.
>
> In testing a fix, I found out how to reproduce Josh's first issue with
> the Maven build from a clean machine (remove all adobe and royale 
artifacts
> from local repo) for js-only.  More changes to the poms are necessary.  I
> will try to figure it out.
>
> And so, this means that a few more folks are likely to have trouble
> building from source.  Again, most folks are going to just use the
> binaries, but I'm worried about first impressions for those who do use the
> source.
>
> -Alex
>
> On 9/21/19, 2:32 PM, "Carlos Rovira"  wrote:
>
> HI Piotr,
>
> since I have work to do on docs, I prefer to try with some
> concrete info,
> or I'll end going like chicken without head :)
> I can test with and without vars on my .bash_profile too.
>
> Even we can release 0.9.6 and left this issues for 0.9.7
>
> thanks
>
> Carlos
>
>
>
>
> El sáb., 21 sept. 2019 a las 22:44, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > You have example of such file in repository. Just based on that
> setup
> > staging link repository. Currently in that file you have
> Snapshot links and
> > release. Based on this you can setup staging.
> >
> > Apart of that I have shared such file some time ago in the
> previous
> > releases.
> >
> > I'm not sure even if that is needed it's just I wanted to
> confirm that is
> > really not needed.
> >
> > Do you have player global setup env variable?
> >
> > If you won't figure out stuff I will share it on Monday.
> >
> > Thanks,
> > Piotr
> >
> > On Sat, Sep 21, 2019, 8:06 PM Carlos Rovira <
> carlosrov...@apache.org>
> > wrote:
> >
> > > Hi Piort,
> > >
> > > can you share here the set of links to add to my
> .m2/settings.xml?
> > >
> > > thanks
> > >
> > >
> > >
> > >
> > > El sáb., 21 sept. 2019 a las 19:02, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>) escribió:
> > >
> > > > Switching subject to discuss.
> > > >
> > > > Carlos can you put in your settings link toavem staging
> artifacts? And
> > > run
> > > > approve script again.
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > On Sat, Sep 21, 2019, 6:49 PM Carlos Rovira <
> carlosrov...@apache.org>
> > > > wrote:
> > > >
> > > > > Curious thing is:
> > > > >
> > > > > if I run in my source tree royale-compiler folder this:
> > > > >
> > > > > mvn -s settings-template.xml -DskipTests clean install
> > > > >
> > > > >
> > > > > with clean .m2 all ends properly.
> > > > >
> > > > >
> > > > > if I run it in the downloaded RC2 folder it fails:
> > > > >
> > > > >
>

Re: [Discuss] Discuss Release Apache Royale 0.9.6 RC2

[Piotr Zarzycki]

Alex,

Carlos is able to build framework by ANT so to me it's enough to go with
release. I have pushed him to try cause I thought that with some small
workarounds he will be able to build that as well.

Thanks,
Piotr

pon., 23 wrz 2019 o 17:46 Alex Harui  napisał(a):

> Update:  There is definitely a problem with the source package that
> prevents building the source with Maven from a truly clean machine.  I have
> some changes pending.  This is going to be a pretty large commit as if
> affects a lot of files.   I'm not sure why Piotr is have Carlos continue to
> try things.  That seems like duplication of effort to me.  I will hopefully
> have this working by end of my day today.
>
> -Alex
>
> On 9/21/19, 4:51 PM, "Alex Harui"  wrote:
>
> I changed the subject to try to keep the threads separated.
>
> Please remember that the scripts and instructions are biased towards
> js-only.  If you have PLAYERGLOBAL_HOME, AIR_HOME, and FLASHPLAYER_DEBUGGER
> set then you will need different profiles.
>
> Looks like this failure is caused by change 228f4fbd1.  There should
> not be hard dependencies on Adobe stuff in order to support js-only.
>
> In testing a fix, I found out how to reproduce Josh's first issue with
> the Maven build from a clean machine (remove all adobe and royale artifacts
> from local repo) for js-only.  More changes to the poms are necessary.  I
> will try to figure it out.
>
> And so, this means that a few more folks are likely to have trouble
> building from source.  Again, most folks are going to just use the
> binaries, but I'm worried about first impressions for those who do use the
> source.
>
> -Alex
>
> On 9/21/19, 2:32 PM, "Carlos Rovira"  wrote:
>
> HI Piotr,
>
> since I have work to do on docs, I prefer to try with some
> concrete info,
> or I'll end going like chicken without head :)
> I can test with and without vars on my .bash_profile too.
>
> Even we can release 0.9.6 and left this issues for 0.9.7
>
> thanks
>
> Carlos
>
>
>
>
> El sáb., 21 sept. 2019 a las 22:44, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > You have example of such file in repository. Just based on that
> setup
> > staging link repository. Currently in that file you have
> Snapshot links and
> > release. Based on this you can setup staging.
> >
> > Apart of that I have shared such file some time ago in the
> previous
> > releases.
> >
> > I'm not sure even if that is needed it's just I wanted to
> confirm that is
> > really not needed.
> >
> > Do you have player global setup env variable?
> >
> > If you won't figure out stuff I will share it on Monday.
> >
> > Thanks,
> > Piotr
> >
> > On Sat, Sep 21, 2019, 8:06 PM Carlos Rovira <
> carlosrov...@apache.org>
> > wrote:
> >
> > > Hi Piort,
> > >
> > > can you share here the set of links to add to my
> .m2/settings.xml?
> > >
> > > thanks
> > >
> > >
> > >
> > >
> > > El sáb., 21 sept. 2019 a las 19:02, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>) escribió:
> > >
> > > > Switching subject to discuss.
> > > >
> > > > Carlos can you put in your settings link toavem staging
> artifacts? And
> > > run
> > > > approve script again.
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > On Sat, Sep 21, 2019, 6:49 PM Carlos Rovira <
> carlosrov...@apache.org>
> > > > wrote:
> > > >
> > > > > Curious thing is:
> > > > >
> > > > > if I run in my source tree royale-compiler folder this:
> > > > >
> > > > > mvn -s settings-template.xml -DskipTests clean install
> > > > >
> > > > >
> > > > > with clean .m2 all ends properly.
> > > > >
> > > > >
> > > > > if I run it in the downloaded RC2 folder it fails:
> > > > >
> > > > >
> > > > > Downloaded from central:
> > > > >
> > > > >
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepo.maven.apache.org%2Fmaven2%2Forg%2Fcodehaus%2Fplexus%2Fplexus-container-default%2F1.0-alpha-9-stable-1%2Fplexus-container-default-1.0-alpha-9-stable-1.jar&data=02%7C01%7Caharui%40adobe.com%7C102bbce2a6b94f47599408d73eeea986%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637047067078793068&sdata=QhbpGC%2BtKlQ4dxLvri%2FmYdSerlKFUTjqXkGfDeBE0c0%3D&reserved=0
> > > > > (194 kB at 290 kB/s)
> > > > >
> > > > > Downloaded from central:
> > > > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepo.maven.apache.org%2Fmaven2%2Forg%2Fantlr%2FST

Re: [Discuss] Discuss Release Apache Royale 0.9.6 RC2

[Alex Harui]

Update:  There is definitely a problem with the source package that prevents 
building the source with Maven from a truly clean machine.  I have some changes 
pending.  This is going to be a pretty large commit as if affects a lot of 
files.   I'm not sure why Piotr is have Carlos continue to try things.  That 
seems like duplication of effort to me.  I will hopefully have this working by 
end of my day today.

-Alex

On 9/21/19, 4:51 PM, "Alex Harui"  wrote:

I changed the subject to try to keep the threads separated.

Please remember that the scripts and instructions are biased towards 
js-only.  If you have PLAYERGLOBAL_HOME, AIR_HOME, and FLASHPLAYER_DEBUGGER set 
then you will need different profiles.

Looks like this failure is caused by change 228f4fbd1.  There should not be 
hard dependencies on Adobe stuff in order to support js-only.

In testing a fix, I found out how to reproduce Josh's first issue with the 
Maven build from a clean machine (remove all adobe and royale artifacts from 
local repo) for js-only.  More changes to the poms are necessary.  I will try 
to figure it out.

And so, this means that a few more folks are likely to have trouble 
building from source.  Again, most folks are going to just use the binaries, 
but I'm worried about first impressions for those who do use the source.

-Alex

On 9/21/19, 2:32 PM, "Carlos Rovira"  wrote:

HI Piotr,

since I have work to do on docs, I prefer to try with some concrete 
info,
or I'll end going like chicken without head :)
I can test with and without vars on my .bash_profile too.

Even we can release 0.9.6 and left this issues for 0.9.7

thanks

Carlos




El sáb., 21 sept. 2019 a las 22:44, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> You have example of such file in repository. Just based on that setup
> staging link repository. Currently in that file you have Snapshot 
links and
> release. Based on this you can setup staging.
>
> Apart of that I have shared such file some time ago in the previous
> releases.
>
> I'm not sure even if that is needed it's just I wanted to confirm 
that is
> really not needed.
>
> Do you have player global setup env variable?
>
> If you won't figure out stuff I will share it on Monday.
>
> Thanks,
> Piotr
>
> On Sat, Sep 21, 2019, 8:06 PM Carlos Rovira 
> wrote:
>
> > Hi Piort,
> >
> > can you share here the set of links to add to my .m2/settings.xml?
> >
> > thanks
> >
> >
> >
> >
> > El sáb., 21 sept. 2019 a las 19:02, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>) escribió:
> >
> > > Switching subject to discuss.
> > >
> > > Carlos can you put in your settings link toavem staging 
artifacts? And
> > run
> > > approve script again.
> > >
> > > Thanks,
> > > Piotr
> > >
> > > On Sat, Sep 21, 2019, 6:49 PM Carlos Rovira 

> > > wrote:
> > >
> > > > Curious thing is:
> > > >
> > > > if I run in my source tree royale-compiler folder this:
> > > >
> > > > mvn -s settings-template.xml -DskipTests clean install
> > > >
> > > >
> > > > with clean .m2 all ends properly.
> > > >
> > > >
> > > > if I run it in the downloaded RC2 folder it fails:
> > > >
> > > >
> > > > Downloaded from central:
> > > >
> > > >
> > >
> >
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepo.maven.apache.org%2Fmaven2%2Forg%2Fcodehaus%2Fplexus%2Fplexus-container-default%2F1.0-alpha-9-stable-1%2Fplexus-container-default-1.0-alpha-9-stable-1.jar&data=02%7C01%7Caharui%40adobe.com%7C102bbce2a6b94f47599408d73eeea986%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637047067078793068&sdata=QhbpGC%2BtKlQ4dxLvri%2FmYdSerlKFUTjqXkGfDeBE0c0%3D&reserved=0
> > > > (194 kB at 290 kB/s)
> > > >
> > > > Downloaded from central:
> > > >
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepo.maven.apache.org%2Fmaven2%2Forg%2Fantlr%2FST4%2F4.0.4%2FST4-4.0.4.jar&data=02%7C01%7Caharui%40adobe.com%7C102bbce2a6b94f47599408d73eeea986%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637047067078793068&sdata=C%2BMVzWH3QNeEH42YUkHU4Mrx64sXvaPbfwjWcbSlOnA%3D&reserved=0
> > > > (237
> > > > kB at 345 kB/s)
> > > >
> > > > [*ERROR*] [ERROR] Some problems were encountered while 
processing the
> > > POMs:
> > > >
> > > > [ERROR] Unr

Re: [DISCUSS] Release Apache Royale 0.9.6 RC2

[Carlos Rovira]

Hi Piotr,

sorry, ignore my latest emails. Since I forgot to switch .m2 repositories.
In the real one there's no such layout
Going to rerun again.




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

> Ok so what is the output of your build now ?
>
> pon., 23 wrz 2019 o 17:11 Carlos Rovira 
> napisał(a):
>
> > Hi Piotr,
> > since finally layouts are the same, I think is not worth it to do the
> > sending.
> > The only difference is the file exposed in my last email
> >
> > El lun., 23 sept. 2019 a las 16:47, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>) escribió:
> >
> > > Carlos,
> > >
> > > Mailing list won't allow post screenshot. Upload them somewhere and
> post
> > > links.
> > >
> > > pon., 23 wrz 2019 o 16:27 Carlos Rovira 
> > > napisał(a):
> > >
> > > > Hi all,
> > > >
> > > > Piotr and I discover off list the following:
> > > >
> > > > this is what I have in my .m2
> > > > [image: Captura de pantalla 2019-09-23 a las 16.11.04.png]
> > > >
> > > >
> > > > and this the Pitro's package layout that sent me off list:
> > > >
> > > > [image: Captura de pantalla 2019-09-23 a las 16.12.19.png]
> > > >
> > > > how is possible Piotr and I get different layouts?
> > > >
> > > > I'll try to build now with his layout
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > El lun., 23 sept. 2019 a las 16:04, Piotr Zarzycki (<
> > > > piotrzarzyck...@gmail.com>) escribió:
> > > >
> > > >> Carlos,
> > > >>
> > > >> It's not exactly the same, cause my settings eliminate one issue
> from
> > > your
> > > >> log. I have send you player global off list - just put it manually
> > into
> > > >> Maven folder and try again.
> > > >>
> > > >> Thanks,
> > > >> Piotr
> > > >>
> > > >> pon., 23 wrz 2019 o 13:50 Carlos Rovira 
> > > >> napisał(a):
> > > >>
> > > >> > Hi,
> > > >> >
> > > >> > sorry to say that build failed. Here's the final log. Mostly the
> > same
> > > >> > problem with flash player as always:
> > > >> >
> > > >> > 0 MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1):
> > > >> 1.0/1.0
> > > >> > MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1):
> > > 1.0/1.0
> > > >> > MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1):
> > > 1.0/1.0
> > > >> > MBProgress (1): 1.0 MBDownloaded from
> > central:
> > > >> >
> > > >>
> > >
> >
> https://repo.maven.apache.org/maven2/de/jflex/jflex/1.6.0/jflex-1.6.0.jar
> > > >> > (1.0 MB at 3.7 MB/s)[INFO]
> > > >> >
> > >
> 
> > > >> >
> > > >> > [INFO] Reactor Summary for Apache Royale: Compiler: Parent 0.9.6:
> > > >> >
> > > >> > [INFO]
> > > >> >
> > > >> > [INFO] Apache Royale: Compiler: Parent 
> SUCCESS
> > [
> > > >> > 6.206 s]
> > > >> >
> > > >> > [INFO] Apache Royale: Compiler: Compiler-Common ...
> SUCCESS
> > > >> [01:24
> > > >> > min]
> > > >> >
> > > >> > [INFO] Apache Royale: Compiler: Test Utils 
> SUCCESS
> > [
> > > >> > 3.174 s]
> > > >> >
> > > >> > [INFO] Apache Royale: Compiler: Externc ...
> SUCCESS
> > [
> > > >> > 58.423 s]
> > > >> >
> > > >> > [INFO] Apache Royale: Compiler: Compiler ..
> FAILURE
> > [
> > > >> > 8.802 s]
> > > >> >
> > > >> > [INFO] Apache Royale: Compiler: Compiler-JX ...
> SKIPPED
> > > >> >
> > > >> > [INFO] Apache Royale: Compiler: SWFUtils ..
> SKIPPED
> > > >> >
> > > >> > [INFO] Apache Royale: Compiler: Debugger ..
> SKIPPED
> > > >> >
> > > >> > [INFO] Apache Royale: Compiler: OEM Layer .
> SKIPPED
> > > >> >
> > > >> > [INFO] Apache Royale: Royale Ant Tasks 
> SKIPPED
> > > >> >
> > > >> > [INFO] Apache Royale: RoyaleUnit Ant Tasks 
> SKIPPED
> > > >> >
> > > >> > [INFO] Apache Royale: Royale Maven Plugin .
> SKIPPED
> > > >> >
> > > >> > [INFO]
> > > >> >
> > >
> 
> > > >> >
> > > >> > [INFO] BUILD FAILURE
> > > >> >
> > > >> > [INFO]
> > > >> >
> > >
> 
> > > >> >
> > > >> > [INFO] Total time:  02:51 min
> > > >> >
> > > >> > [INFO] Finished at: 2019-09-23T13:40:46+02:00
> > > >> >
> > > >> > [INFO]
> > > >> >
> > >
> 
> > > >> >
> > > >> > [ERROR] Failed to execute goal on project compiler: Could not
> > resolve
> > > >> > dependencies for project
> > > org.apache.royale.compiler:compiler:jar:0.9.6:
> > > >> > Could not find artifact
> > > com.adobe.flash.framework:playerglobal:swc:20.0
> > > >> in
> > > >> > apache-release (
> > > >> > https://repository.apache.org/content/repositories/releases)
> > > >> > -> [Help 1]
> > > >> >
> > > >> > [ERROR]
> > > >> >
> > > >> > [ERROR] To see the full stack trace of the errors, re-run Maven
> with
> > > >> th

Re: [DISCUSS] Release Apache Royale 0.9.6 RC2

[Piotr Zarzycki]

Ok so what is the output of your build now ?

pon., 23 wrz 2019 o 17:11 Carlos Rovira 
napisał(a):

> Hi Piotr,
> since finally layouts are the same, I think is not worth it to do the
> sending.
> The only difference is the file exposed in my last email
>
> El lun., 23 sept. 2019 a las 16:47, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > Carlos,
> >
> > Mailing list won't allow post screenshot. Upload them somewhere and post
> > links.
> >
> > pon., 23 wrz 2019 o 16:27 Carlos Rovira 
> > napisał(a):
> >
> > > Hi all,
> > >
> > > Piotr and I discover off list the following:
> > >
> > > this is what I have in my .m2
> > > [image: Captura de pantalla 2019-09-23 a las 16.11.04.png]
> > >
> > >
> > > and this the Pitro's package layout that sent me off list:
> > >
> > > [image: Captura de pantalla 2019-09-23 a las 16.12.19.png]
> > >
> > > how is possible Piotr and I get different layouts?
> > >
> > > I'll try to build now with his layout
> > >
> > >
> > >
> > >
> > >
> > > El lun., 23 sept. 2019 a las 16:04, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>) escribió:
> > >
> > >> Carlos,
> > >>
> > >> It's not exactly the same, cause my settings eliminate one issue from
> > your
> > >> log. I have send you player global off list - just put it manually
> into
> > >> Maven folder and try again.
> > >>
> > >> Thanks,
> > >> Piotr
> > >>
> > >> pon., 23 wrz 2019 o 13:50 Carlos Rovira 
> > >> napisał(a):
> > >>
> > >> > Hi,
> > >> >
> > >> > sorry to say that build failed. Here's the final log. Mostly the
> same
> > >> > problem with flash player as always:
> > >> >
> > >> > 0 MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1):
> > >> 1.0/1.0
> > >> > MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1):
> > 1.0/1.0
> > >> > MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1):
> > 1.0/1.0
> > >> > MBProgress (1): 1.0 MBDownloaded from
> central:
> > >> >
> > >>
> >
> https://repo.maven.apache.org/maven2/de/jflex/jflex/1.6.0/jflex-1.6.0.jar
> > >> > (1.0 MB at 3.7 MB/s)[INFO]
> > >> >
> > 
> > >> >
> > >> > [INFO] Reactor Summary for Apache Royale: Compiler: Parent 0.9.6:
> > >> >
> > >> > [INFO]
> > >> >
> > >> > [INFO] Apache Royale: Compiler: Parent  SUCCESS
> [
> > >> > 6.206 s]
> > >> >
> > >> > [INFO] Apache Royale: Compiler: Compiler-Common ... SUCCESS
> > >> [01:24
> > >> > min]
> > >> >
> > >> > [INFO] Apache Royale: Compiler: Test Utils  SUCCESS
> [
> > >> > 3.174 s]
> > >> >
> > >> > [INFO] Apache Royale: Compiler: Externc ... SUCCESS
> [
> > >> > 58.423 s]
> > >> >
> > >> > [INFO] Apache Royale: Compiler: Compiler .. FAILURE
> [
> > >> > 8.802 s]
> > >> >
> > >> > [INFO] Apache Royale: Compiler: Compiler-JX ... SKIPPED
> > >> >
> > >> > [INFO] Apache Royale: Compiler: SWFUtils .. SKIPPED
> > >> >
> > >> > [INFO] Apache Royale: Compiler: Debugger .. SKIPPED
> > >> >
> > >> > [INFO] Apache Royale: Compiler: OEM Layer . SKIPPED
> > >> >
> > >> > [INFO] Apache Royale: Royale Ant Tasks  SKIPPED
> > >> >
> > >> > [INFO] Apache Royale: RoyaleUnit Ant Tasks  SKIPPED
> > >> >
> > >> > [INFO] Apache Royale: Royale Maven Plugin . SKIPPED
> > >> >
> > >> > [INFO]
> > >> >
> > 
> > >> >
> > >> > [INFO] BUILD FAILURE
> > >> >
> > >> > [INFO]
> > >> >
> > 
> > >> >
> > >> > [INFO] Total time:  02:51 min
> > >> >
> > >> > [INFO] Finished at: 2019-09-23T13:40:46+02:00
> > >> >
> > >> > [INFO]
> > >> >
> > 
> > >> >
> > >> > [ERROR] Failed to execute goal on project compiler: Could not
> resolve
> > >> > dependencies for project
> > org.apache.royale.compiler:compiler:jar:0.9.6:
> > >> > Could not find artifact
> > com.adobe.flash.framework:playerglobal:swc:20.0
> > >> in
> > >> > apache-release (
> > >> > https://repository.apache.org/content/repositories/releases)
> > >> > -> [Help 1]
> > >> >
> > >> > [ERROR]
> > >> >
> > >> > [ERROR] To see the full stack trace of the errors, re-run Maven with
> > >> the -e
> > >> > switch.
> > >> >
> > >> > [ERROR] Re-run Maven using the -X switch to enable full debug
> logging.
> > >> >
> > >> > [ERROR]
> > >> >
> > >> > [ERROR] For more information about the errors and possible
> solutions,
> > >> > please read the following articles:
> > >> >
> > >> > [ERROR] [Help 1]
> > >> >
> > >> >
> > >>
> >
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
> > >> >
> > >> > [ERROR]
> > >> >
> > >> > [ERROR] After correcting the problems, you can resume the build with
> > the
> > >> > command
> > >> >
> > >> > [ERROR]  

Re: [DISCUSS] Release Apache Royale 0.9.6 RC2

[Carlos Rovira]

Hi Piotr,
since finally layouts are the same, I think is not worth it to do the
sending.
The only difference is the file exposed in my last email

El lun., 23 sept. 2019 a las 16:47, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> Carlos,
>
> Mailing list won't allow post screenshot. Upload them somewhere and post
> links.
>
> pon., 23 wrz 2019 o 16:27 Carlos Rovira 
> napisał(a):
>
> > Hi all,
> >
> > Piotr and I discover off list the following:
> >
> > this is what I have in my .m2
> > [image: Captura de pantalla 2019-09-23 a las 16.11.04.png]
> >
> >
> > and this the Pitro's package layout that sent me off list:
> >
> > [image: Captura de pantalla 2019-09-23 a las 16.12.19.png]
> >
> > how is possible Piotr and I get different layouts?
> >
> > I'll try to build now with his layout
> >
> >
> >
> >
> >
> > El lun., 23 sept. 2019 a las 16:04, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>) escribió:
> >
> >> Carlos,
> >>
> >> It's not exactly the same, cause my settings eliminate one issue from
> your
> >> log. I have send you player global off list - just put it manually into
> >> Maven folder and try again.
> >>
> >> Thanks,
> >> Piotr
> >>
> >> pon., 23 wrz 2019 o 13:50 Carlos Rovira 
> >> napisał(a):
> >>
> >> > Hi,
> >> >
> >> > sorry to say that build failed. Here's the final log. Mostly the same
> >> > problem with flash player as always:
> >> >
> >> > 0 MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1):
> >> 1.0/1.0
> >> > MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1):
> 1.0/1.0
> >> > MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1):
> 1.0/1.0
> >> > MBProgress (1): 1.0 MBDownloaded from central:
> >> >
> >>
> https://repo.maven.apache.org/maven2/de/jflex/jflex/1.6.0/jflex-1.6.0.jar
> >> > (1.0 MB at 3.7 MB/s)[INFO]
> >> >
> 
> >> >
> >> > [INFO] Reactor Summary for Apache Royale: Compiler: Parent 0.9.6:
> >> >
> >> > [INFO]
> >> >
> >> > [INFO] Apache Royale: Compiler: Parent  SUCCESS [
> >> > 6.206 s]
> >> >
> >> > [INFO] Apache Royale: Compiler: Compiler-Common ... SUCCESS
> >> [01:24
> >> > min]
> >> >
> >> > [INFO] Apache Royale: Compiler: Test Utils  SUCCESS [
> >> > 3.174 s]
> >> >
> >> > [INFO] Apache Royale: Compiler: Externc ... SUCCESS [
> >> > 58.423 s]
> >> >
> >> > [INFO] Apache Royale: Compiler: Compiler .. FAILURE [
> >> > 8.802 s]
> >> >
> >> > [INFO] Apache Royale: Compiler: Compiler-JX ... SKIPPED
> >> >
> >> > [INFO] Apache Royale: Compiler: SWFUtils .. SKIPPED
> >> >
> >> > [INFO] Apache Royale: Compiler: Debugger .. SKIPPED
> >> >
> >> > [INFO] Apache Royale: Compiler: OEM Layer . SKIPPED
> >> >
> >> > [INFO] Apache Royale: Royale Ant Tasks  SKIPPED
> >> >
> >> > [INFO] Apache Royale: RoyaleUnit Ant Tasks  SKIPPED
> >> >
> >> > [INFO] Apache Royale: Royale Maven Plugin . SKIPPED
> >> >
> >> > [INFO]
> >> >
> 
> >> >
> >> > [INFO] BUILD FAILURE
> >> >
> >> > [INFO]
> >> >
> 
> >> >
> >> > [INFO] Total time:  02:51 min
> >> >
> >> > [INFO] Finished at: 2019-09-23T13:40:46+02:00
> >> >
> >> > [INFO]
> >> >
> 
> >> >
> >> > [ERROR] Failed to execute goal on project compiler: Could not resolve
> >> > dependencies for project
> org.apache.royale.compiler:compiler:jar:0.9.6:
> >> > Could not find artifact
> com.adobe.flash.framework:playerglobal:swc:20.0
> >> in
> >> > apache-release (
> >> > https://repository.apache.org/content/repositories/releases)
> >> > -> [Help 1]
> >> >
> >> > [ERROR]
> >> >
> >> > [ERROR] To see the full stack trace of the errors, re-run Maven with
> >> the -e
> >> > switch.
> >> >
> >> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> >> >
> >> > [ERROR]
> >> >
> >> > [ERROR] For more information about the errors and possible solutions,
> >> > please read the following articles:
> >> >
> >> > [ERROR] [Help 1]
> >> >
> >> >
> >>
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
> >> >
> >> > [ERROR]
> >> >
> >> > [ERROR] After correcting the problems, you can resume the build with
> the
> >> > command
> >> >
> >> > [ERROR]   mvn  -rf :compiler
> >> >
> >> >
> >> > BUILD FAILED
> >> >
> >> > /Users/carlosrovira/Downloads/testrc2/ApproveRoyale.xml:778: The
> >> following
> >> > error occurred while executing this line:
> >> >
> >> > /Users/carlosrovira/Downloads/testrc2/ApproveRoyale.xml:789: exec
> >> returned:
> >> > 1
> >> >
> >> >
> >> > Total time: 40 minutes 58 seconds
> >> >
> >> > macbookpro:testrc2 carlosrovira$
> >> >
> >> >
> >> >
> >> >
> >> > El

Re: [DISCUSS] Release Apache Royale 0.9.6 RC2

[Piotr Zarzycki]

Carlos,

Mailing list won't allow post screenshot. Upload them somewhere and post
links.

pon., 23 wrz 2019 o 16:27 Carlos Rovira 
napisał(a):

> Hi all,
>
> Piotr and I discover off list the following:
>
> this is what I have in my .m2
> [image: Captura de pantalla 2019-09-23 a las 16.11.04.png]
>
>
> and this the Pitro's package layout that sent me off list:
>
> [image: Captura de pantalla 2019-09-23 a las 16.12.19.png]
>
> how is possible Piotr and I get different layouts?
>
> I'll try to build now with his layout
>
>
>
>
>
> El lun., 23 sept. 2019 a las 16:04, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
>> Carlos,
>>
>> It's not exactly the same, cause my settings eliminate one issue from your
>> log. I have send you player global off list - just put it manually into
>> Maven folder and try again.
>>
>> Thanks,
>> Piotr
>>
>> pon., 23 wrz 2019 o 13:50 Carlos Rovira 
>> napisał(a):
>>
>> > Hi,
>> >
>> > sorry to say that build failed. Here's the final log. Mostly the same
>> > problem with flash player as always:
>> >
>> > 0 MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1):
>> 1.0/1.0
>> > MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0
>> > MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0
>> > MBProgress (1): 1.0 MBDownloaded from central:
>> >
>> https://repo.maven.apache.org/maven2/de/jflex/jflex/1.6.0/jflex-1.6.0.jar
>> > (1.0 MB at 3.7 MB/s)[INFO]
>> > 
>> >
>> > [INFO] Reactor Summary for Apache Royale: Compiler: Parent 0.9.6:
>> >
>> > [INFO]
>> >
>> > [INFO] Apache Royale: Compiler: Parent  SUCCESS [
>> > 6.206 s]
>> >
>> > [INFO] Apache Royale: Compiler: Compiler-Common ... SUCCESS
>> [01:24
>> > min]
>> >
>> > [INFO] Apache Royale: Compiler: Test Utils  SUCCESS [
>> > 3.174 s]
>> >
>> > [INFO] Apache Royale: Compiler: Externc ... SUCCESS [
>> > 58.423 s]
>> >
>> > [INFO] Apache Royale: Compiler: Compiler .. FAILURE [
>> > 8.802 s]
>> >
>> > [INFO] Apache Royale: Compiler: Compiler-JX ... SKIPPED
>> >
>> > [INFO] Apache Royale: Compiler: SWFUtils .. SKIPPED
>> >
>> > [INFO] Apache Royale: Compiler: Debugger .. SKIPPED
>> >
>> > [INFO] Apache Royale: Compiler: OEM Layer . SKIPPED
>> >
>> > [INFO] Apache Royale: Royale Ant Tasks  SKIPPED
>> >
>> > [INFO] Apache Royale: RoyaleUnit Ant Tasks  SKIPPED
>> >
>> > [INFO] Apache Royale: Royale Maven Plugin . SKIPPED
>> >
>> > [INFO]
>> > 
>> >
>> > [INFO] BUILD FAILURE
>> >
>> > [INFO]
>> > 
>> >
>> > [INFO] Total time:  02:51 min
>> >
>> > [INFO] Finished at: 2019-09-23T13:40:46+02:00
>> >
>> > [INFO]
>> > 
>> >
>> > [ERROR] Failed to execute goal on project compiler: Could not resolve
>> > dependencies for project org.apache.royale.compiler:compiler:jar:0.9.6:
>> > Could not find artifact com.adobe.flash.framework:playerglobal:swc:20.0
>> in
>> > apache-release (
>> > https://repository.apache.org/content/repositories/releases)
>> > -> [Help 1]
>> >
>> > [ERROR]
>> >
>> > [ERROR] To see the full stack trace of the errors, re-run Maven with
>> the -e
>> > switch.
>> >
>> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> >
>> > [ERROR]
>> >
>> > [ERROR] For more information about the errors and possible solutions,
>> > please read the following articles:
>> >
>> > [ERROR] [Help 1]
>> >
>> >
>> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
>> >
>> > [ERROR]
>> >
>> > [ERROR] After correcting the problems, you can resume the build with the
>> > command
>> >
>> > [ERROR]   mvn  -rf :compiler
>> >
>> >
>> > BUILD FAILED
>> >
>> > /Users/carlosrovira/Downloads/testrc2/ApproveRoyale.xml:778: The
>> following
>> > error occurred while executing this line:
>> >
>> > /Users/carlosrovira/Downloads/testrc2/ApproveRoyale.xml:789: exec
>> returned:
>> > 1
>> >
>> >
>> > Total time: 40 minutes 58 seconds
>> >
>> > macbookpro:testrc2 carlosrovira$
>> >
>> >
>> >
>> >
>> > El lun., 23 sept. 2019 a las 12:39, Piotr Zarzycki (<
>> > piotrzarzyck...@gmail.com>) escribió:
>> >
>> > > Hey Carlos,
>> > >
>> > > Answers inline.
>> > >
>> > > pon., 23 wrz 2019 o 12:34 Carlos Rovira 
>> > > napisał(a):
>> > >
>> > > > Hi Piotr,
>> > > >
>> > > > I want to try now. To try this xml with Approve xml workflow:
>> > > >
>> > > > 1.- should I put it in my .m2 folder (and remove mine)? or there's
>> > > another
>> > > > way?
>> > > >
>> > > Yes. You can also try to modify maven target and add to each exec run
>> -s
>> > > "path to your settings"
>> > >
>> > >
>

Re: [DISCUSS] Release Apache Royale 0.9.6 RC2

[Carlos Rovira]

Hi,

sorry, but just notice that both layouts are exactly the same :?
The only change is in

playerglobal-20.0.pom.lastUpdated

Piotrs is:

#NOTE: This is an Aether internal implementation file, its format can be
changed without prior notice.
#Tue Aug 13 05:59:44 CEST 2019
https\://repository.apache.org/content/repositories/releases/.error=
https\://repo.maven.apache.org/maven2/.lastUpdated=1565668784011
https\://
repository.apache.org/content/repositories/releases/.lastUpdated=1565668783757
https\://repo.maven.apache.org/maven2/.error=


and mine is:


#NOTE: This is a Maven Resolver internal implementation file, its format
can be changed without prior notice.
#Wed May 22 20:31:44 CEST 2019
https\://repo.maven.apache.org/maven2/.lastUpdated=1558549904792
https\://repo.maven.apache.org/maven2/.error=









El lun., 23 sept. 2019 a las 16:27, Carlos Rovira ()
escribió:

> Hi all,
>
> Piotr and I discover off list the following:
>
> this is what I have in my .m2
> [image: Captura de pantalla 2019-09-23 a las 16.11.04.png]
>
>
> and this the Pitro's package layout that sent me off list:
>
> [image: Captura de pantalla 2019-09-23 a las 16.12.19.png]
>
> how is possible Piotr and I get different layouts?
>
> I'll try to build now with his layout
>
>
>
>
>
> El lun., 23 sept. 2019 a las 16:04, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
>> Carlos,
>>
>> It's not exactly the same, cause my settings eliminate one issue from your
>> log. I have send you player global off list - just put it manually into
>> Maven folder and try again.
>>
>> Thanks,
>> Piotr
>>
>> pon., 23 wrz 2019 o 13:50 Carlos Rovira 
>> napisał(a):
>>
>> > Hi,
>> >
>> > sorry to say that build failed. Here's the final log. Mostly the same
>> > problem with flash player as always:
>> >
>> > 0 MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1):
>> 1.0/1.0
>> > MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0
>> > MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0
>> > MBProgress (1): 1.0 MBDownloaded from central:
>> >
>> https://repo.maven.apache.org/maven2/de/jflex/jflex/1.6.0/jflex-1.6.0.jar
>> > (1.0 MB at 3.7 MB/s)[INFO]
>> > 
>> >
>> > [INFO] Reactor Summary for Apache Royale: Compiler: Parent 0.9.6:
>> >
>> > [INFO]
>> >
>> > [INFO] Apache Royale: Compiler: Parent  SUCCESS [
>> > 6.206 s]
>> >
>> > [INFO] Apache Royale: Compiler: Compiler-Common ... SUCCESS
>> [01:24
>> > min]
>> >
>> > [INFO] Apache Royale: Compiler: Test Utils  SUCCESS [
>> > 3.174 s]
>> >
>> > [INFO] Apache Royale: Compiler: Externc ... SUCCESS [
>> > 58.423 s]
>> >
>> > [INFO] Apache Royale: Compiler: Compiler .. FAILURE [
>> > 8.802 s]
>> >
>> > [INFO] Apache Royale: Compiler: Compiler-JX ... SKIPPED
>> >
>> > [INFO] Apache Royale: Compiler: SWFUtils .. SKIPPED
>> >
>> > [INFO] Apache Royale: Compiler: Debugger .. SKIPPED
>> >
>> > [INFO] Apache Royale: Compiler: OEM Layer . SKIPPED
>> >
>> > [INFO] Apache Royale: Royale Ant Tasks  SKIPPED
>> >
>> > [INFO] Apache Royale: RoyaleUnit Ant Tasks  SKIPPED
>> >
>> > [INFO] Apache Royale: Royale Maven Plugin . SKIPPED
>> >
>> > [INFO]
>> > 
>> >
>> > [INFO] BUILD FAILURE
>> >
>> > [INFO]
>> > 
>> >
>> > [INFO] Total time:  02:51 min
>> >
>> > [INFO] Finished at: 2019-09-23T13:40:46+02:00
>> >
>> > [INFO]
>> > 
>> >
>> > [ERROR] Failed to execute goal on project compiler: Could not resolve
>> > dependencies for project org.apache.royale.compiler:compiler:jar:0.9.6:
>> > Could not find artifact com.adobe.flash.framework:playerglobal:swc:20.0
>> in
>> > apache-release (
>> > https://repository.apache.org/content/repositories/releases)
>> > -> [Help 1]
>> >
>> > [ERROR]
>> >
>> > [ERROR] To see the full stack trace of the errors, re-run Maven with
>> the -e
>> > switch.
>> >
>> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> >
>> > [ERROR]
>> >
>> > [ERROR] For more information about the errors and possible solutions,
>> > please read the following articles:
>> >
>> > [ERROR] [Help 1]
>> >
>> >
>> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
>> >
>> > [ERROR]
>> >
>> > [ERROR] After correcting the problems, you can resume the build with the
>> > command
>> >
>> > [ERROR]   mvn  -rf :compiler
>> >
>> >
>> > BUILD FAILED
>> >
>> > /Users/carlosrovira/Downloads/testrc2/ApproveRoyale.xml:778: The
>> following
>> > error occurred while executing this line:
>> >
>> > /Users/carlosrovira/Downloads/testrc2/Approve

Re: [DISCUSS] Release Apache Royale 0.9.6 RC2

[Carlos Rovira]

Hi all,

Piotr and I discover off list the following:

this is what I have in my .m2
[image: Captura de pantalla 2019-09-23 a las 16.11.04.png]


and this the Pitro's package layout that sent me off list:

[image: Captura de pantalla 2019-09-23 a las 16.12.19.png]

how is possible Piotr and I get different layouts?

I'll try to build now with his layout





El lun., 23 sept. 2019 a las 16:04, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> Carlos,
>
> It's not exactly the same, cause my settings eliminate one issue from your
> log. I have send you player global off list - just put it manually into
> Maven folder and try again.
>
> Thanks,
> Piotr
>
> pon., 23 wrz 2019 o 13:50 Carlos Rovira 
> napisał(a):
>
> > Hi,
> >
> > sorry to say that build failed. Here's the final log. Mostly the same
> > problem with flash player as always:
> >
> > 0 MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0
> > MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0
> > MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0
> > MBProgress (1): 1.0 MBDownloaded from central:
> >
> https://repo.maven.apache.org/maven2/de/jflex/jflex/1.6.0/jflex-1.6.0.jar
> > (1.0 MB at 3.7 MB/s)[INFO]
> > 
> >
> > [INFO] Reactor Summary for Apache Royale: Compiler: Parent 0.9.6:
> >
> > [INFO]
> >
> > [INFO] Apache Royale: Compiler: Parent  SUCCESS [
> > 6.206 s]
> >
> > [INFO] Apache Royale: Compiler: Compiler-Common ... SUCCESS
> [01:24
> > min]
> >
> > [INFO] Apache Royale: Compiler: Test Utils  SUCCESS [
> > 3.174 s]
> >
> > [INFO] Apache Royale: Compiler: Externc ... SUCCESS [
> > 58.423 s]
> >
> > [INFO] Apache Royale: Compiler: Compiler .. FAILURE [
> > 8.802 s]
> >
> > [INFO] Apache Royale: Compiler: Compiler-JX ... SKIPPED
> >
> > [INFO] Apache Royale: Compiler: SWFUtils .. SKIPPED
> >
> > [INFO] Apache Royale: Compiler: Debugger .. SKIPPED
> >
> > [INFO] Apache Royale: Compiler: OEM Layer . SKIPPED
> >
> > [INFO] Apache Royale: Royale Ant Tasks  SKIPPED
> >
> > [INFO] Apache Royale: RoyaleUnit Ant Tasks  SKIPPED
> >
> > [INFO] Apache Royale: Royale Maven Plugin . SKIPPED
> >
> > [INFO]
> > 
> >
> > [INFO] BUILD FAILURE
> >
> > [INFO]
> > 
> >
> > [INFO] Total time:  02:51 min
> >
> > [INFO] Finished at: 2019-09-23T13:40:46+02:00
> >
> > [INFO]
> > 
> >
> > [ERROR] Failed to execute goal on project compiler: Could not resolve
> > dependencies for project org.apache.royale.compiler:compiler:jar:0.9.6:
> > Could not find artifact com.adobe.flash.framework:playerglobal:swc:20.0
> in
> > apache-release (
> > https://repository.apache.org/content/repositories/releases)
> > -> [Help 1]
> >
> > [ERROR]
> >
> > [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e
> > switch.
> >
> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> >
> > [ERROR]
> >
> > [ERROR] For more information about the errors and possible solutions,
> > please read the following articles:
> >
> > [ERROR] [Help 1]
> >
> >
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
> >
> > [ERROR]
> >
> > [ERROR] After correcting the problems, you can resume the build with the
> > command
> >
> > [ERROR]   mvn  -rf :compiler
> >
> >
> > BUILD FAILED
> >
> > /Users/carlosrovira/Downloads/testrc2/ApproveRoyale.xml:778: The
> following
> > error occurred while executing this line:
> >
> > /Users/carlosrovira/Downloads/testrc2/ApproveRoyale.xml:789: exec
> returned:
> > 1
> >
> >
> > Total time: 40 minutes 58 seconds
> >
> > macbookpro:testrc2 carlosrovira$
> >
> >
> >
> >
> > El lun., 23 sept. 2019 a las 12:39, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>) escribió:
> >
> > > Hey Carlos,
> > >
> > > Answers inline.
> > >
> > > pon., 23 wrz 2019 o 12:34 Carlos Rovira 
> > > napisał(a):
> > >
> > > > Hi Piotr,
> > > >
> > > > I want to try now. To try this xml with Approve xml workflow:
> > > >
> > > > 1.- should I put it in my .m2 folder (and remove mine)? or there's
> > > another
> > > > way?
> > > >
> > > Yes. You can also try to modify maven target and add to each exec run
> -s
> > > "path to your settings"
> > >
> > >
> > > > 2.- should I remove all my env vars in my .bash_profile?
> > > >
> > > Don't touch it.
> > >
> > >
> > > > 3.- I assume I must run the command: "ant -e -f ApproveRoyale.xml
> > > > -Drelease.version=0.9.6 -Drc=2" inside the folder I created with the
> > > > Approve xml file in it.
> > > >
> > >
> > > Yes. I'm running it w

Re: [royale-asjs] branch release/0.9.6 updated: fix ASDoc js-only

[Carlos Rovira]

I hope the few people building from sources would try with actual
instructions and if they have problems come to the list and try to solve it
with our help, so we can improve scripts and build process learning from
that kind of experiences.

El lun., 23 sept. 2019 a las 14:05, Andrew Wetmore ()
escribió:

> Yes: the PERFECT would be clear and simple instructions that work and do
> not scare people away. We do not seem to have those. I thought the
> discussion was whether to go forward with the release anyhow, since the
> number of users who build from source is smaller than the number who use
> the compiled binaries, or delay the release until we get the instructions
> right.
>
> My suggestion related to the first option, to make sure that, if we go
> ahead with the release including insufficient build instructions, that we
> warn people about that. That way we show that we know it's an issue, rather
> than looking like we don't know or, worse, don't care.
>
> a
>
> On Mon, Sep 23, 2019 at 8:28 AM Carlos Rovira 
> wrote:
>
> > Hi Andrew,
> >
> > ok I understand.
> >
> > IMHO, instructions should be as easy as possible. People that see steps
> > depending on things that are not clear will be mostly lost and with high
> > probability of never come back. Royale SDK is a complex technology with
> > many pieces involved, we should make the install process as simple as
> > possible hidding all that complexity if we want to succeed. The main
> point
> > that is running against us is that complexity.
> >
> > just my 2...
> >
> >
> >
> >
> >
>


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

Re: [DISCUSS] Release Apache Royale 0.9.6 RC2

[Piotr Zarzycki]

Carlos,

It's not exactly the same, cause my settings eliminate one issue from your
log. I have send you player global off list - just put it manually into
Maven folder and try again.

Thanks,
Piotr

pon., 23 wrz 2019 o 13:50 Carlos Rovira 
napisał(a):

> Hi,
>
> sorry to say that build failed. Here's the final log. Mostly the same
> problem with flash player as always:
>
> 0 MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0
> MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0
> MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0
> MBProgress (1): 1.0 MBDownloaded from central:
> https://repo.maven.apache.org/maven2/de/jflex/jflex/1.6.0/jflex-1.6.0.jar
> (1.0 MB at 3.7 MB/s)[INFO]
> 
>
> [INFO] Reactor Summary for Apache Royale: Compiler: Parent 0.9.6:
>
> [INFO]
>
> [INFO] Apache Royale: Compiler: Parent  SUCCESS [
> 6.206 s]
>
> [INFO] Apache Royale: Compiler: Compiler-Common ... SUCCESS [01:24
> min]
>
> [INFO] Apache Royale: Compiler: Test Utils  SUCCESS [
> 3.174 s]
>
> [INFO] Apache Royale: Compiler: Externc ... SUCCESS [
> 58.423 s]
>
> [INFO] Apache Royale: Compiler: Compiler .. FAILURE [
> 8.802 s]
>
> [INFO] Apache Royale: Compiler: Compiler-JX ... SKIPPED
>
> [INFO] Apache Royale: Compiler: SWFUtils .. SKIPPED
>
> [INFO] Apache Royale: Compiler: Debugger .. SKIPPED
>
> [INFO] Apache Royale: Compiler: OEM Layer . SKIPPED
>
> [INFO] Apache Royale: Royale Ant Tasks  SKIPPED
>
> [INFO] Apache Royale: RoyaleUnit Ant Tasks  SKIPPED
>
> [INFO] Apache Royale: Royale Maven Plugin . SKIPPED
>
> [INFO]
> 
>
> [INFO] BUILD FAILURE
>
> [INFO]
> 
>
> [INFO] Total time:  02:51 min
>
> [INFO] Finished at: 2019-09-23T13:40:46+02:00
>
> [INFO]
> 
>
> [ERROR] Failed to execute goal on project compiler: Could not resolve
> dependencies for project org.apache.royale.compiler:compiler:jar:0.9.6:
> Could not find artifact com.adobe.flash.framework:playerglobal:swc:20.0 in
> apache-release (
> https://repository.apache.org/content/repositories/releases)
> -> [Help 1]
>
> [ERROR]
>
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
>
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>
> [ERROR]
>
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
>
> [ERROR] [Help 1]
>
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
>
> [ERROR]
>
> [ERROR] After correcting the problems, you can resume the build with the
> command
>
> [ERROR]   mvn  -rf :compiler
>
>
> BUILD FAILED
>
> /Users/carlosrovira/Downloads/testrc2/ApproveRoyale.xml:778: The following
> error occurred while executing this line:
>
> /Users/carlosrovira/Downloads/testrc2/ApproveRoyale.xml:789: exec returned:
> 1
>
>
> Total time: 40 minutes 58 seconds
>
> macbookpro:testrc2 carlosrovira$
>
>
>
>
> El lun., 23 sept. 2019 a las 12:39, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > Hey Carlos,
> >
> > Answers inline.
> >
> > pon., 23 wrz 2019 o 12:34 Carlos Rovira 
> > napisał(a):
> >
> > > Hi Piotr,
> > >
> > > I want to try now. To try this xml with Approve xml workflow:
> > >
> > > 1.- should I put it in my .m2 folder (and remove mine)? or there's
> > another
> > > way?
> > >
> > Yes. You can also try to modify maven target and add to each exec run -s
> > "path to your settings"
> >
> >
> > > 2.- should I remove all my env vars in my .bash_profile?
> > >
> > Don't touch it.
> >
> >
> > > 3.- I assume I must run the command: "ant -e -f ApproveRoyale.xml
> > > -Drelease.version=0.9.6 -Drc=2" inside the folder I created with the
> > > Approve xml file in it.
> > >
> >
> > Yes. I'm running it with -DskipTests=true
> >
> >
> > >
> > > thanks
> > >
> > >
> > > El lun., 23 sept. 2019 a las 10:20, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>) escribió:
> > >
> > > > Hi Carlos,
> > > >
> > > > Here you have settings.xml which I'm using. Please try this one with
> > > > Approve script [1]. Pay attention in it that I have put there staging
> > > > artifacts link, so you know what I'm talking about in the next
> release.
> > > > According to what Josh is saying this settings with staging artifacts
> > > > shouldn't be required, but still I would like to try that idea.
> > > >
> > > > Don't forget in approve script modify target build_maven and change
> > exec
> > > > which is starting royale-asjs build to:
> > > >
> > > >  > > > dir="${basedir}/${maven.

Build failed in Jenkins: royale-asjs_MXTests #1183

[Apache Royale CI Server]

See 


--
[...truncated 1003.99 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
[mx

Re: [royale-asjs] branch release/0.9.6 updated: fix ASDoc js-only

[Andrew Wetmore]

Yes: the PERFECT would be clear and simple instructions that work and do
not scare people away. We do not seem to have those. I thought the
discussion was whether to go forward with the release anyhow, since the
number of users who build from source is smaller than the number who use
the compiled binaries, or delay the release until we get the instructions
right.

My suggestion related to the first option, to make sure that, if we go
ahead with the release including insufficient build instructions, that we
warn people about that. That way we show that we know it's an issue, rather
than looking like we don't know or, worse, don't care.

a

On Mon, Sep 23, 2019 at 8:28 AM Carlos Rovira 
wrote:

> Hi Andrew,
>
> ok I understand.
>
> IMHO, instructions should be as easy as possible. People that see steps
> depending on things that are not clear will be mostly lost and with high
> probability of never come back. Royale SDK is a complex technology with
> many pieces involved, we should make the install process as simple as
> possible hidding all that complexity if we want to succeed. The main point
> that is running against us is that complexity.
>
> just my 2...
>
>
>
>
>

Re: [DISCUSS] Release Apache Royale 0.9.6 RC2

[Carlos Rovira]

Hi,

sorry to say that build failed. Here's the final log. Mostly the same
problem with flash player as always:

0 MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0
MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0
MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0 MBProgress (1): 1.0/1.0
MBProgress (1): 1.0 MBDownloaded from central:
https://repo.maven.apache.org/maven2/de/jflex/jflex/1.6.0/jflex-1.6.0.jar
(1.0 MB at 3.7 MB/s)[INFO]


[INFO] Reactor Summary for Apache Royale: Compiler: Parent 0.9.6:

[INFO]

[INFO] Apache Royale: Compiler: Parent  SUCCESS [
6.206 s]

[INFO] Apache Royale: Compiler: Compiler-Common ... SUCCESS [01:24
min]

[INFO] Apache Royale: Compiler: Test Utils  SUCCESS [
3.174 s]

[INFO] Apache Royale: Compiler: Externc ... SUCCESS [
58.423 s]

[INFO] Apache Royale: Compiler: Compiler .. FAILURE [
8.802 s]

[INFO] Apache Royale: Compiler: Compiler-JX ... SKIPPED

[INFO] Apache Royale: Compiler: SWFUtils .. SKIPPED

[INFO] Apache Royale: Compiler: Debugger .. SKIPPED

[INFO] Apache Royale: Compiler: OEM Layer . SKIPPED

[INFO] Apache Royale: Royale Ant Tasks  SKIPPED

[INFO] Apache Royale: RoyaleUnit Ant Tasks  SKIPPED

[INFO] Apache Royale: Royale Maven Plugin . SKIPPED

[INFO]


[INFO] BUILD FAILURE

[INFO]


[INFO] Total time:  02:51 min

[INFO] Finished at: 2019-09-23T13:40:46+02:00

[INFO]


[ERROR] Failed to execute goal on project compiler: Could not resolve
dependencies for project org.apache.royale.compiler:compiler:jar:0.9.6:
Could not find artifact com.adobe.flash.framework:playerglobal:swc:20.0 in
apache-release (https://repository.apache.org/content/repositories/releases)
-> [Help 1]

[ERROR]

[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.

[ERROR] Re-run Maven using the -X switch to enable full debug logging.

[ERROR]

[ERROR] For more information about the errors and possible solutions,
please read the following articles:

[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException

[ERROR]

[ERROR] After correcting the problems, you can resume the build with the
command

[ERROR]   mvn  -rf :compiler


BUILD FAILED

/Users/carlosrovira/Downloads/testrc2/ApproveRoyale.xml:778: The following
error occurred while executing this line:

/Users/carlosrovira/Downloads/testrc2/ApproveRoyale.xml:789: exec returned:
1


Total time: 40 minutes 58 seconds

macbookpro:testrc2 carlosrovira$




El lun., 23 sept. 2019 a las 12:39, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> Hey Carlos,
>
> Answers inline.
>
> pon., 23 wrz 2019 o 12:34 Carlos Rovira 
> napisał(a):
>
> > Hi Piotr,
> >
> > I want to try now. To try this xml with Approve xml workflow:
> >
> > 1.- should I put it in my .m2 folder (and remove mine)? or there's
> another
> > way?
> >
> Yes. You can also try to modify maven target and add to each exec run -s
> "path to your settings"
>
>
> > 2.- should I remove all my env vars in my .bash_profile?
> >
> Don't touch it.
>
>
> > 3.- I assume I must run the command: "ant -e -f ApproveRoyale.xml
> > -Drelease.version=0.9.6 -Drc=2" inside the folder I created with the
> > Approve xml file in it.
> >
>
> Yes. I'm running it with -DskipTests=true
>
>
> >
> > thanks
> >
> >
> > El lun., 23 sept. 2019 a las 10:20, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>) escribió:
> >
> > > Hi Carlos,
> > >
> > > Here you have settings.xml which I'm using. Please try this one with
> > > Approve script [1]. Pay attention in it that I have put there staging
> > > artifacts link, so you know what I'm talking about in the next release.
> > > According to what Josh is saying this settings with staging artifacts
> > > shouldn't be required, but still I would like to try that idea.
> > >
> > > Don't forget in approve script modify target build_maven and change
> exec
> > > which is starting royale-asjs build to:
> > >
> > >  > > dir="${basedir}/${maven.package.url.name}/royale-asjs"
> > > failonerror="true" >
> > > 
> > > 
> > > 
> > > 
> > > 
> > >
> > > Let me know if it helps.
> > >
> > > [1] https://paste.apache.org/gfift
> > >
> > > Thanks,
> > > Piotr
> > >
> > > niedz., 22 wrz 2019 o 19:24 Carlos Rovira 
> > > napisał(a):
> > >
> > > > Hi,
> > > >
> > > > yes, I was not able to build even using -s settings-template.xml.
> > > > I tried adding it in the Approve xml workflow code and trying to
> build
> > > > directly with maven with a clean .m2
> > > > I

Re: [royale-asjs] branch release/0.9.6 updated: fix ASDoc js-only

[Carlos Rovira]

Hi Andrew,

ok I understand.

IMHO, instructions should be as easy as possible. People that see steps
depending on things that are not clear will be mostly lost and with high
probability of never come back. Royale SDK is a complex technology with
many pieces involved, we should make the install process as simple as
possible hidding all that complexity if we want to succeed. The main point
that is running against us is that complexity.

just my 2...




El lun., 23 sept. 2019 a las 13:01, Andrew Wetmore ()
escribió:

> Oops: edited my proposed text and did not check it afterwards. What I meant
> was this for the release page for 0.9.6::
>
> "The current version of Apache Royale is 0.9.6, released in MONTH YEAR. It
> is beta-quality. This means that Royale may not work entirely as you or we
> want it to, and that certain standard components and functions are not yet
> available. However, you can create and compile applications in Royale and
> run them either in a browser window or on the Flash and AIR platforms.
> Further: please note that the instructions for compiling Royale from the
> source code may not work for you as they are written. You may need to set
> additional environment variables, depending on your operating system. Send
> an email to EMAIL ADDRESS if you run into difficulties and need further
> instructions. You can, of course, use the compiled binaries of Royale and
> get to work immediately."
>
> On Mon, Sep 23, 2019 at 7:57 AM Andrew Wetmore 
> wrote:
>
> > The question is whether we release 0.9.6 when the instructions for
> > compiling from source are incomplete and/or inaccurate.
> >
> > For 0.9.4 the page says "The current version of *Apache Royale* is
> *0.9.4*,
> > released in *Diciembre, 2018*. It is *beta-quality*. This means that
> > Royale may not work entirely as you or we want it to, and that certain
> > “standard” components or functions are not yet available. However, you
> can
> > create applications in Royale and compile them to run either in a browser
> > window or on the Flash/AIR platforms."
> >
> > For 0.9.6, why can we not say, "The current version of Apache Royale is
> > 0.9.6, release in MONTH YEAR. It is beta-quality. This means that Royale
> > may not work entirely as you or we want it to, and that certain
> "standard"
> > components or functions are not yet available. However, you can create
> > applications and compile applications in Royale and run them either in a
> > browser window or on the Flash and AIR platforms.
> > Further: please note that the instructions for compiling Royale from the
> > source code may not work for you as they are written. You may need to set
> > additional environment variables, depending on your operating system.
> Send
> > an email to EMAIL ADDRESS if you run into difficulties and need further
> > instructions. You can, of course, use the compiled binaries of Royale and
> > get to work immediately."
> >
> > Andrew
> >
> > On Mon, Sep 23, 2019 at 6:57 AM Carlos Rovira 
> > wrote:
> >
> >> Hi Andrew,
> >>
> >> can you specify what you mean? Here's the download page with all
> download
> >> links: https://royale.apache.org/download/
> >>
> >> El dom., 22 sept. 2019 a las 20:11, Andrew Wetmore (<
> cottag...@gmail.com
> >> >)
> >> escribió:
> >>
> >> > Could it not also be posted on the website, where the link for
> >> downloading
> >> > the release is?
> >> >
> >> > On Sat, Sep 21, 2019 at 8:53 PM Alex Harui 
> >> > wrote:
> >> >
> >> > > The only place to include it without altering the release artifacts
> >> is in
> >> > > the RELEASE_NOTES addendum in our wiki.
> >> > >
> >> > > We could do that, but folks probably won't look there until after
> they
> >> > > have a problem.
> >> > >
> >> > > -Alex
> >> > >
> >> > > On 9/21/19, 4:44 AM, "Andrew Wetmore"  wrote:
> >> > >
> >> > > Would it be acceptable to include some sort of explanation that
> >> > > compiling
> >> > > from source will require setting a number of environment
> >> variables,
> >> > not
> >> > > just ANT_HOME, and that, if you really want to compile 0.9.6
> from
> >> > > source,
> >> > > you should contact [LIST EMAIL] for instructions on what to do?
> It
> >> > > sort of
> >> > > dodges the issue, but permits moving forward with the release
> with
> >> > the
> >> > > presumption that, as Alex says, most people will want and use
> the
> >> > > compiled
> >> > > binaries.
> >> > >
> >> > > I guess I would rather acknowledge the problem than look like we
> >> > don't
> >> > > realize there is a problem.
> >> > >
> >> > > Andrew
> >> > >
> >> > > On Fri, Sep 20, 2019 at 2:10 AM Alex Harui
> >>  >> > >
> >> > > wrote:
> >> > >
> >> > > > I think we all want to get a release out.
> >> > > >
> >> > > > My user experience was the equivalent of taking the source
> >> package
> >> > > and
> >> > > > trying to build it without setting any environment variables
> >> other
> >> > > than
> >> > > > ANT_HOME as specif

Re: [royale-asjs] branch release/0.9.6 updated: fix ASDoc js-only

[Andrew Wetmore]

Oops: edited my proposed text and did not check it afterwards. What I meant
was this for the release page for 0.9.6::

"The current version of Apache Royale is 0.9.6, released in MONTH YEAR. It
is beta-quality. This means that Royale may not work entirely as you or we
want it to, and that certain standard components and functions are not yet
available. However, you can create and compile applications in Royale and
run them either in a browser window or on the Flash and AIR platforms.
Further: please note that the instructions for compiling Royale from the
source code may not work for you as they are written. You may need to set
additional environment variables, depending on your operating system. Send
an email to EMAIL ADDRESS if you run into difficulties and need further
instructions. You can, of course, use the compiled binaries of Royale and
get to work immediately."

On Mon, Sep 23, 2019 at 7:57 AM Andrew Wetmore  wrote:

> The question is whether we release 0.9.6 when the instructions for
> compiling from source are incomplete and/or inaccurate.
>
> For 0.9.4 the page says "The current version of *Apache Royale* is *0.9.4*,
> released in *Diciembre, 2018*. It is *beta-quality*. This means that
> Royale may not work entirely as you or we want it to, and that certain
> “standard” components or functions are not yet available. However, you can
> create applications in Royale and compile them to run either in a browser
> window or on the Flash/AIR platforms."
>
> For 0.9.6, why can we not say, "The current version of Apache Royale is
> 0.9.6, release in MONTH YEAR. It is beta-quality. This means that Royale
> may not work entirely as you or we want it to, and that certain "standard"
> components or functions are not yet available. However, you can create
> applications and compile applications in Royale and run them either in a
> browser window or on the Flash and AIR platforms.
> Further: please note that the instructions for compiling Royale from the
> source code may not work for you as they are written. You may need to set
> additional environment variables, depending on your operating system. Send
> an email to EMAIL ADDRESS if you run into difficulties and need further
> instructions. You can, of course, use the compiled binaries of Royale and
> get to work immediately."
>
> Andrew
>
> On Mon, Sep 23, 2019 at 6:57 AM Carlos Rovira 
> wrote:
>
>> Hi Andrew,
>>
>> can you specify what you mean? Here's the download page with all download
>> links: https://royale.apache.org/download/
>>
>> El dom., 22 sept. 2019 a las 20:11, Andrew Wetmore (> >)
>> escribió:
>>
>> > Could it not also be posted on the website, where the link for
>> downloading
>> > the release is?
>> >
>> > On Sat, Sep 21, 2019 at 8:53 PM Alex Harui 
>> > wrote:
>> >
>> > > The only place to include it without altering the release artifacts
>> is in
>> > > the RELEASE_NOTES addendum in our wiki.
>> > >
>> > > We could do that, but folks probably won't look there until after they
>> > > have a problem.
>> > >
>> > > -Alex
>> > >
>> > > On 9/21/19, 4:44 AM, "Andrew Wetmore"  wrote:
>> > >
>> > > Would it be acceptable to include some sort of explanation that
>> > > compiling
>> > > from source will require setting a number of environment
>> variables,
>> > not
>> > > just ANT_HOME, and that, if you really want to compile 0.9.6 from
>> > > source,
>> > > you should contact [LIST EMAIL] for instructions on what to do? It
>> > > sort of
>> > > dodges the issue, but permits moving forward with the release with
>> > the
>> > > presumption that, as Alex says, most people will want and use the
>> > > compiled
>> > > binaries.
>> > >
>> > > I guess I would rather acknowledge the problem than look like we
>> > don't
>> > > realize there is a problem.
>> > >
>> > > Andrew
>> > >
>> > > On Fri, Sep 20, 2019 at 2:10 AM Alex Harui
>> > > >
>> > > wrote:
>> > >
>> > > > I think we all want to get a release out.
>> > > >
>> > > > My user experience was the equivalent of taking the source
>> package
>> > > and
>> > > > trying to build it without setting any environment variables
>> other
>> > > than
>> > > > ANT_HOME as specified in the README.  It did not work for me.
>> > > >
>> > > > The question is:  how many of our users are going to try to
>> build
>> > the
>> > > > source package?  And when it fails and the ask about it, will it
>> > > bother
>> > > > them to be told to go get the Adobe stuff and set environment
>> > > variables?  I
>> > > > think it is a small number of people, almost everyone else is
>> going
>> > > to grab
>> > > > binaries.  However, it is bothering me because we are an open
>> > source
>> > > > project and our minimum configuration should work but doesn't.
>> > > >
>> > > > -Alex
>> > > >
>> > > > On 9/19/19, 9:20 PM, "Piotr Zarzycki" <
>> piotrzarzyck...@gmail.com>
>> > > wrote:
>> > > >
>> > > > I'm in fav

Re: [royale-asjs] branch release/0.9.6 updated: fix ASDoc js-only

[Andrew Wetmore]

The question is whether we release 0.9.6 when the instructions for
compiling from source are incomplete and/or inaccurate.

For 0.9.4 the page says "The current version of *Apache Royale* is *0.9.4*,
released in *Diciembre, 2018*. It is *beta-quality*. This means that Royale
may not work entirely as you or we want it to, and that certain “standard”
components or functions are not yet available. However, you can create
applications in Royale and compile them to run either in a browser window
or on the Flash/AIR platforms."

For 0.9.6, why can we not say, "The current version of Apache Royale is
0.9.6, release in MONTH YEAR. It is beta-quality. This means that Royale
may not work entirely as you or we want it to, and that certain "standard"
components or functions are not yet available. However, you can create
applications and compile applications in Royale and run them either in a
browser window or on the Flash and AIR platforms.
Further: please note that the instructions for compiling Royale from the
source code may not work for you as they are written. You may need to set
additional environment variables, depending on your operating system. Send
an email to EMAIL ADDRESS if you run into difficulties and need further
instructions. You can, of course, use the compiled binaries of Royale and
get to work immediately."

Andrew

On Mon, Sep 23, 2019 at 6:57 AM Carlos Rovira 
wrote:

> Hi Andrew,
>
> can you specify what you mean? Here's the download page with all download
> links: https://royale.apache.org/download/
>
> El dom., 22 sept. 2019 a las 20:11, Andrew Wetmore ()
> escribió:
>
> > Could it not also be posted on the website, where the link for
> downloading
> > the release is?
> >
> > On Sat, Sep 21, 2019 at 8:53 PM Alex Harui 
> > wrote:
> >
> > > The only place to include it without altering the release artifacts is
> in
> > > the RELEASE_NOTES addendum in our wiki.
> > >
> > > We could do that, but folks probably won't look there until after they
> > > have a problem.
> > >
> > > -Alex
> > >
> > > On 9/21/19, 4:44 AM, "Andrew Wetmore"  wrote:
> > >
> > > Would it be acceptable to include some sort of explanation that
> > > compiling
> > > from source will require setting a number of environment variables,
> > not
> > > just ANT_HOME, and that, if you really want to compile 0.9.6 from
> > > source,
> > > you should contact [LIST EMAIL] for instructions on what to do? It
> > > sort of
> > > dodges the issue, but permits moving forward with the release with
> > the
> > > presumption that, as Alex says, most people will want and use the
> > > compiled
> > > binaries.
> > >
> > > I guess I would rather acknowledge the problem than look like we
> > don't
> > > realize there is a problem.
> > >
> > > Andrew
> > >
> > > On Fri, Sep 20, 2019 at 2:10 AM Alex Harui
>  > >
> > > wrote:
> > >
> > > > I think we all want to get a release out.
> > > >
> > > > My user experience was the equivalent of taking the source
> package
> > > and
> > > > trying to build it without setting any environment variables
> other
> > > than
> > > > ANT_HOME as specified in the README.  It did not work for me.
> > > >
> > > > The question is:  how many of our users are going to try to build
> > the
> > > > source package?  And when it fails and the ask about it, will it
> > > bother
> > > > them to be told to go get the Adobe stuff and set environment
> > > variables?  I
> > > > think it is a small number of people, almost everyone else is
> going
> > > to grab
> > > > binaries.  However, it is bothering me because we are an open
> > source
> > > > project and our minimum configuration should work but doesn't.
> > > >
> > > > -Alex
> > > >
> > > > On 9/19/19, 9:20 PM, "Piotr Zarzycki"  >
> > > wrote:
> > > >
> > > > I'm in favor of moving forward. I would like to finally
> release
> > > stuff.
> > > >
> > > > I can live with setting up env. Variables. I'm concern by the
> > > user
> > > > experience than mine.
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > On Thu, Sep 19, 2019, 10:36 PM Alex Harui
> > > 
> > > > wrote:
> > > >
> > > > > Don't know.  Judgement call.
> > > > >
> > > > > We've done a bunch of work since 0.9.4 to allow folks to be
> > > able to
> > > > > compile without the Adobe Flash and AIR SDKs.  I've run
> into
> > a
> > > > couple of
> > > > > problems.  ASDoc's JSON generator was failing if you didn't
> > > have
> > > > Flash
> > > > > SDK.  I mentioned it in the RC1 discuss thread.  I think
> > > because it
> > > > is only
> > > > > this one example it is probably ok.
> > > > >
> > > > > What is less ok is another commit I have pending which is
> > that
> > > the
> > > > main
> > > > > SWC build fails if you don't have Flash and AIR 

Re: [DISCUSS] Release Apache Royale 0.9.6 RC2

[Piotr Zarzycki]

Hey Carlos,

Answers inline.

pon., 23 wrz 2019 o 12:34 Carlos Rovira 
napisał(a):

> Hi Piotr,
>
> I want to try now. To try this xml with Approve xml workflow:
>
> 1.- should I put it in my .m2 folder (and remove mine)? or there's another
> way?
>
Yes. You can also try to modify maven target and add to each exec run -s
"path to your settings"


> 2.- should I remove all my env vars in my .bash_profile?
>
Don't touch it.


> 3.- I assume I must run the command: "ant -e -f ApproveRoyale.xml
> -Drelease.version=0.9.6 -Drc=2" inside the folder I created with the
> Approve xml file in it.
>

Yes. I'm running it with -DskipTests=true


>
> thanks
>
>
> El lun., 23 sept. 2019 a las 10:20, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > Hi Carlos,
> >
> > Here you have settings.xml which I'm using. Please try this one with
> > Approve script [1]. Pay attention in it that I have put there staging
> > artifacts link, so you know what I'm talking about in the next release.
> > According to what Josh is saying this settings with staging artifacts
> > shouldn't be required, but still I would like to try that idea.
> >
> > Don't forget in approve script modify target build_maven and change exec
> > which is starting royale-asjs build to:
> >
> >  > dir="${basedir}/${maven.package.url.name}/royale-asjs"
> > failonerror="true" >
> > 
> > 
> > 
> > 
> > 
> >
> > Let me know if it helps.
> >
> > [1] https://paste.apache.org/gfift
> >
> > Thanks,
> > Piotr
> >
> > niedz., 22 wrz 2019 o 19:24 Carlos Rovira 
> > napisał(a):
> >
> > > Hi,
> > >
> > > yes, I was not able to build even using -s settings-template.xml.
> > > I tried adding it in the Approve xml workflow code and trying to build
> > > directly with maven with a clean .m2
> > > In exchange, If I try to build in my usual royale repo folder as usual
> > from
> > > clean, it works all ok
> > > As well I tried commenting/uncommenting environment vars in my
> > > .bash_profile
> > >
> > > thanks
> > >
> > >
> > >
> > >
> > > El dom., 22 sept. 2019 a las 16:10, Josh Tynjala (<
> > > joshtynj...@bowlerhat.dev>)
> > > escribió:
> > >
> > > > That was my original assumption, but it sounds like Carlos had issues
> > > > trying that.
> > > >
> > > > - Josh
> > > >
> > > > On Sunday, September 22, 2019, Piotr Zarzycki <
> > piotrzarzyck...@gmail.com
> > > >
> > > > wrote:
> > > > > Josh,
> > > > >
> > > > > Are you saying that settings-template from repository should be
> > enough
> > > to
> > > > > get stuff working for Carlos? I'm confused right now.
> > > > >
> > > > > Thanks,
> > > > > Piotr
> > > > >
> > > > > On Sun, Sep 22, 2019, 1:43 AM Josh Tynjala <
> > joshtynj...@bowlerhat.dev>
> > > > > wrote:
> > > > >
> > > > >> I'm guessing that the settings template isn't supposed to be
> > required
> > > > for
> > > > >> JS-only builds, similar to the other things discussed in this
> thread
> > > (or
> > > > >> the previous RC thread).
> > > > >>
> > > > >> I know that this file is needed to download the proprietary Adobe
> > bits
> > > > >> (since Maven doesn't know where to find them by default), and that
> > > > seemed
> > > > >> to be where your build failed.
> > > > >>
> > > > >> - Josh
> > > > >>
> > > > >> On Saturday, September 21, 2019, Carlos Rovira <
> > > carlosrov...@apache.org
> > > > >
> > > > >> wrote:
> > > > >> > Thanks Josh,
> > > > >> >
> > > > >> > I just tried with Approve xml and get similar results (I copy
> > here)
> > > > >> > I'll try using the setting, I forgot completely about it.. But
> > this
> > > > means
> > > > >> > the instructions to build are wrong right?
> > > > >> >
> > > > >> >
> > > > >> > Here's my console output after try with the Approve xml script
> > > (mostly
> > > > >> the
> > > > >> > same as trying to build with maven):
> > > > >> >
> > > > >> > [INFO] --- maven-install-plugin:2.5.2:install (default-install)
> @
> > > > >> > compiler-externc ---
> > > > >> >
> > > > >> > [INFO] Installing
> > > > >> >
> > > > >>
> > > > >>
> > > >
> > > >
> > >
> >
> /Users/carlosrovira/Downloads/testrc2/apache-royale-0.9.6-maven-src/royale-compiler/compiler-externc/target/compiler-externc-0.9.6.jar
> > > > >> > to
> > > > >> >
> > > > >>
> > > > >>
> > > >
> > > >
> > >
> >
> /Users/carlosrovira/.m2/repository/org/apache/royale/compiler/compiler-externc/0.9.6/compiler-externc-0.9.6.jar
> > > > >> >
> > > > >> > [INFO] Installing
> > > > >> >
> > > > >>
> > > > >>
> > > >
> > > >
> > >
> >
> /Users/carlosrovira/Downloads/testrc2/apache-royale-0.9.6-maven-src/royale-compiler/compiler-externc/pom.xml
> > > > >> > to
> > > > >> >
> > > > >>
> > > > >>
> > > >
> > > >
> > >
> >
> /Users/carlosrovira/.m2/repository/org/apache/royale/compiler/compiler-externc/0.9.6/compiler-externc-0.9.6.pom
> > > > >> >
> > > > >> > [INFO] Installing
> > > > >> >
> > > > >>
> > > > >>
> > > >
> > > >
> > >
> >
> /Users/carlosrovira/Downloads/testrc2/apache-royale-0.9.6-maven-src/royale-compiler/compiler-externc/target/compile

Re: [DISCUSS] Release Apache Royale 0.9.6 RC2

[Carlos Rovira]

Hi Piotr,

I want to try now. To try this xml with Approve xml workflow:

1.- should I put it in my .m2 folder (and remove mine)? or there's another
way?
2.- should I remove all my env vars in my .bash_profile?
3.- I assume I must run the command: "ant -e -f ApproveRoyale.xml
-Drelease.version=0.9.6 -Drc=2" inside the folder I created with the
Approve xml file in it.

thanks


El lun., 23 sept. 2019 a las 10:20, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> Hi Carlos,
>
> Here you have settings.xml which I'm using. Please try this one with
> Approve script [1]. Pay attention in it that I have put there staging
> artifacts link, so you know what I'm talking about in the next release.
> According to what Josh is saying this settings with staging artifacts
> shouldn't be required, but still I would like to try that idea.
>
> Don't forget in approve script modify target build_maven and change exec
> which is starting royale-asjs build to:
>
>  dir="${basedir}/${maven.package.url.name}/royale-asjs"
> failonerror="true" >
> 
> 
> 
> 
> 
>
> Let me know if it helps.
>
> [1] https://paste.apache.org/gfift
>
> Thanks,
> Piotr
>
> niedz., 22 wrz 2019 o 19:24 Carlos Rovira 
> napisał(a):
>
> > Hi,
> >
> > yes, I was not able to build even using -s settings-template.xml.
> > I tried adding it in the Approve xml workflow code and trying to build
> > directly with maven with a clean .m2
> > In exchange, If I try to build in my usual royale repo folder as usual
> from
> > clean, it works all ok
> > As well I tried commenting/uncommenting environment vars in my
> > .bash_profile
> >
> > thanks
> >
> >
> >
> >
> > El dom., 22 sept. 2019 a las 16:10, Josh Tynjala (<
> > joshtynj...@bowlerhat.dev>)
> > escribió:
> >
> > > That was my original assumption, but it sounds like Carlos had issues
> > > trying that.
> > >
> > > - Josh
> > >
> > > On Sunday, September 22, 2019, Piotr Zarzycki <
> piotrzarzyck...@gmail.com
> > >
> > > wrote:
> > > > Josh,
> > > >
> > > > Are you saying that settings-template from repository should be
> enough
> > to
> > > > get stuff working for Carlos? I'm confused right now.
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > On Sun, Sep 22, 2019, 1:43 AM Josh Tynjala <
> joshtynj...@bowlerhat.dev>
> > > > wrote:
> > > >
> > > >> I'm guessing that the settings template isn't supposed to be
> required
> > > for
> > > >> JS-only builds, similar to the other things discussed in this thread
> > (or
> > > >> the previous RC thread).
> > > >>
> > > >> I know that this file is needed to download the proprietary Adobe
> bits
> > > >> (since Maven doesn't know where to find them by default), and that
> > > seemed
> > > >> to be where your build failed.
> > > >>
> > > >> - Josh
> > > >>
> > > >> On Saturday, September 21, 2019, Carlos Rovira <
> > carlosrov...@apache.org
> > > >
> > > >> wrote:
> > > >> > Thanks Josh,
> > > >> >
> > > >> > I just tried with Approve xml and get similar results (I copy
> here)
> > > >> > I'll try using the setting, I forgot completely about it.. But
> this
> > > means
> > > >> > the instructions to build are wrong right?
> > > >> >
> > > >> >
> > > >> > Here's my console output after try with the Approve xml script
> > (mostly
> > > >> the
> > > >> > same as trying to build with maven):
> > > >> >
> > > >> > [INFO] --- maven-install-plugin:2.5.2:install (default-install) @
> > > >> > compiler-externc ---
> > > >> >
> > > >> > [INFO] Installing
> > > >> >
> > > >>
> > > >>
> > >
> > >
> >
> /Users/carlosrovira/Downloads/testrc2/apache-royale-0.9.6-maven-src/royale-compiler/compiler-externc/target/compiler-externc-0.9.6.jar
> > > >> > to
> > > >> >
> > > >>
> > > >>
> > >
> > >
> >
> /Users/carlosrovira/.m2/repository/org/apache/royale/compiler/compiler-externc/0.9.6/compiler-externc-0.9.6.jar
> > > >> >
> > > >> > [INFO] Installing
> > > >> >
> > > >>
> > > >>
> > >
> > >
> >
> /Users/carlosrovira/Downloads/testrc2/apache-royale-0.9.6-maven-src/royale-compiler/compiler-externc/pom.xml
> > > >> > to
> > > >> >
> > > >>
> > > >>
> > >
> > >
> >
> /Users/carlosrovira/.m2/repository/org/apache/royale/compiler/compiler-externc/0.9.6/compiler-externc-0.9.6.pom
> > > >> >
> > > >> > [INFO] Installing
> > > >> >
> > > >>
> > > >>
> > >
> > >
> >
> /Users/carlosrovira/Downloads/testrc2/apache-royale-0.9.6-maven-src/royale-compiler/compiler-externc/target/compiler-externc-0.9.6-tests.jar
> > > >> > to
> > > >> >
> > > >>
> > > >>
> > >
> > >
> >
> /Users/carlosrovira/.m2/repository/org/apache/royale/compiler/compiler-externc/0.9.6/compiler-externc-0.9.6-tests.jar
> > > >> >
> > > >> > [INFO]
> > > >> >
> > > >> > [INFO] < org.apache.royale.compiler:compiler
> > > >> >>-
> > > >> >
> > > >> > [INFO] Building Apache Royale: Compiler: Compiler 0.9.6
> > > >> > [5/12]
> > > >> >
> > > >> > [INFO] [ jar
> > > >> > ]-
> > > >> >
> > > >> > [WARNING] The POM for

Build failed in Jenkins: royale-asjs_MXTests #1182

[Apache Royale CI Server]

See 


Changes:

[carlosrovira] update all jewel themes with collapsible styles

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

Re: [royale-asjs] branch release/0.9.6 updated: fix ASDoc js-only

[Carlos Rovira]

Hi Andrew,

can you specify what you mean? Here's the download page with all download
links: https://royale.apache.org/download/

El dom., 22 sept. 2019 a las 20:11, Andrew Wetmore ()
escribió:

> Could it not also be posted on the website, where the link for downloading
> the release is?
>
> On Sat, Sep 21, 2019 at 8:53 PM Alex Harui 
> wrote:
>
> > The only place to include it without altering the release artifacts is in
> > the RELEASE_NOTES addendum in our wiki.
> >
> > We could do that, but folks probably won't look there until after they
> > have a problem.
> >
> > -Alex
> >
> > On 9/21/19, 4:44 AM, "Andrew Wetmore"  wrote:
> >
> > Would it be acceptable to include some sort of explanation that
> > compiling
> > from source will require setting a number of environment variables,
> not
> > just ANT_HOME, and that, if you really want to compile 0.9.6 from
> > source,
> > you should contact [LIST EMAIL] for instructions on what to do? It
> > sort of
> > dodges the issue, but permits moving forward with the release with
> the
> > presumption that, as Alex says, most people will want and use the
> > compiled
> > binaries.
> >
> > I guess I would rather acknowledge the problem than look like we
> don't
> > realize there is a problem.
> >
> > Andrew
> >
> > On Fri, Sep 20, 2019 at 2:10 AM Alex Harui  >
> > wrote:
> >
> > > I think we all want to get a release out.
> > >
> > > My user experience was the equivalent of taking the source package
> > and
> > > trying to build it without setting any environment variables other
> > than
> > > ANT_HOME as specified in the README.  It did not work for me.
> > >
> > > The question is:  how many of our users are going to try to build
> the
> > > source package?  And when it fails and the ask about it, will it
> > bother
> > > them to be told to go get the Adobe stuff and set environment
> > variables?  I
> > > think it is a small number of people, almost everyone else is going
> > to grab
> > > binaries.  However, it is bothering me because we are an open
> source
> > > project and our minimum configuration should work but doesn't.
> > >
> > > -Alex
> > >
> > > On 9/19/19, 9:20 PM, "Piotr Zarzycki" 
> > wrote:
> > >
> > > I'm in favor of moving forward. I would like to finally release
> > stuff.
> > >
> > > I can live with setting up env. Variables. I'm concern by the
> > user
> > > experience than mine.
> > >
> > > Thanks,
> > > Piotr
> > >
> > > On Thu, Sep 19, 2019, 10:36 PM Alex Harui
> > 
> > > wrote:
> > >
> > > > Don't know.  Judgement call.
> > > >
> > > > We've done a bunch of work since 0.9.4 to allow folks to be
> > able to
> > > > compile without the Adobe Flash and AIR SDKs.  I've run into
> a
> > > couple of
> > > > problems.  ASDoc's JSON generator was failing if you didn't
> > have
> > > Flash
> > > > SDK.  I mentioned it in the RC1 discuss thread.  I think
> > because it
> > > is only
> > > > this one example it is probably ok.
> > > >
> > > > What is less ok is another commit I have pending which is
> that
> > the
> > > main
> > > > SWC build fails if you don't have Flash and AIR SDKs.  In
> > theory,
> > > none of
> > > > you should have been able to get the build to work without
> > > environment
> > > > variables for the Adobe stuff.  So it depends a bit on how
> > important
> > > we
> > > > think building from sources without the Adobe stuff is for
> this
> > > release.
> > > > If you did get the build to work without the Adobe stuff,
> > check your
> > > > environment and post the console output.  I was fooled by
> > having a
> > > > PLAYERGLOBAL_HOME still set.  When I took it away, more
> things
> > broke.
> > > >
> > > > I'm testing building with Flash/AIR now to try to make sure
> my
> > > js-only
> > > > changes didn't affect js-swf.
> > > >
> > > > -Alex
> > > >
> > > > On 9/19/19, 1:19 PM, "Piotr Zarzycki" <
> > piotrzarzyck...@gmail.com>
> > > wrote:
> > > >
> > > > Hi Alex,
> > > >
> > > > We need to have it in 0.9.6?
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > On Thu, Sep 19, 2019, 9:49 PM  wrote:
> > > >
> > > > > This is an automated email from the ASF dual-hosted git
> > > repository.
> > > > >
> > > > > aharui pushed a commit to branch release/0.9.6
> > > > > in repository
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitbox.apache.org%2Frepos%2Fasf%2Froyale-asjs.git&data=02%7C01%7Caharui%40adobe.com%7Cdde0aae4a55a4671118c08

Re: [DISCUSS] Release Apache Royale 0.9.6 RC2

[Piotr Zarzycki]

Hi Carlos,

Here you have settings.xml which I'm using. Please try this one with
Approve script [1]. Pay attention in it that I have put there staging
artifacts link, so you know what I'm talking about in the next release.
According to what Josh is saying this settings with staging artifacts
shouldn't be required, but still I would like to try that idea.

Don't forget in approve script modify target build_maven and change exec
which is starting royale-asjs build to:








Let me know if it helps.

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

Thanks,
Piotr

niedz., 22 wrz 2019 o 19:24 Carlos Rovira 
napisał(a):

> Hi,
>
> yes, I was not able to build even using -s settings-template.xml.
> I tried adding it in the Approve xml workflow code and trying to build
> directly with maven with a clean .m2
> In exchange, If I try to build in my usual royale repo folder as usual from
> clean, it works all ok
> As well I tried commenting/uncommenting environment vars in my
> .bash_profile
>
> thanks
>
>
>
>
> El dom., 22 sept. 2019 a las 16:10, Josh Tynjala (<
> joshtynj...@bowlerhat.dev>)
> escribió:
>
> > That was my original assumption, but it sounds like Carlos had issues
> > trying that.
> >
> > - Josh
> >
> > On Sunday, September 22, 2019, Piotr Zarzycki  >
> > wrote:
> > > Josh,
> > >
> > > Are you saying that settings-template from repository should be enough
> to
> > > get stuff working for Carlos? I'm confused right now.
> > >
> > > Thanks,
> > > Piotr
> > >
> > > On Sun, Sep 22, 2019, 1:43 AM Josh Tynjala 
> > > wrote:
> > >
> > >> I'm guessing that the settings template isn't supposed to be required
> > for
> > >> JS-only builds, similar to the other things discussed in this thread
> (or
> > >> the previous RC thread).
> > >>
> > >> I know that this file is needed to download the proprietary Adobe bits
> > >> (since Maven doesn't know where to find them by default), and that
> > seemed
> > >> to be where your build failed.
> > >>
> > >> - Josh
> > >>
> > >> On Saturday, September 21, 2019, Carlos Rovira <
> carlosrov...@apache.org
> > >
> > >> wrote:
> > >> > Thanks Josh,
> > >> >
> > >> > I just tried with Approve xml and get similar results (I copy here)
> > >> > I'll try using the setting, I forgot completely about it.. But this
> > means
> > >> > the instructions to build are wrong right?
> > >> >
> > >> >
> > >> > Here's my console output after try with the Approve xml script
> (mostly
> > >> the
> > >> > same as trying to build with maven):
> > >> >
> > >> > [INFO] --- maven-install-plugin:2.5.2:install (default-install) @
> > >> > compiler-externc ---
> > >> >
> > >> > [INFO] Installing
> > >> >
> > >>
> > >>
> >
> >
> /Users/carlosrovira/Downloads/testrc2/apache-royale-0.9.6-maven-src/royale-compiler/compiler-externc/target/compiler-externc-0.9.6.jar
> > >> > to
> > >> >
> > >>
> > >>
> >
> >
> /Users/carlosrovira/.m2/repository/org/apache/royale/compiler/compiler-externc/0.9.6/compiler-externc-0.9.6.jar
> > >> >
> > >> > [INFO] Installing
> > >> >
> > >>
> > >>
> >
> >
> /Users/carlosrovira/Downloads/testrc2/apache-royale-0.9.6-maven-src/royale-compiler/compiler-externc/pom.xml
> > >> > to
> > >> >
> > >>
> > >>
> >
> >
> /Users/carlosrovira/.m2/repository/org/apache/royale/compiler/compiler-externc/0.9.6/compiler-externc-0.9.6.pom
> > >> >
> > >> > [INFO] Installing
> > >> >
> > >>
> > >>
> >
> >
> /Users/carlosrovira/Downloads/testrc2/apache-royale-0.9.6-maven-src/royale-compiler/compiler-externc/target/compiler-externc-0.9.6-tests.jar
> > >> > to
> > >> >
> > >>
> > >>
> >
> >
> /Users/carlosrovira/.m2/repository/org/apache/royale/compiler/compiler-externc/0.9.6/compiler-externc-0.9.6-tests.jar
> > >> >
> > >> > [INFO]
> > >> >
> > >> > [INFO] < org.apache.royale.compiler:compiler
> > >> >>-
> > >> >
> > >> > [INFO] Building Apache Royale: Compiler: Compiler 0.9.6
> > >> > [5/12]
> > >> >
> > >> > [INFO] [ jar
> > >> > ]-
> > >> >
> > >> > [WARNING] The POM for
> com.adobe.flash.framework:playerglobal:swc:20.0
> > is
> > >> > missing, no dependency information available
> > >> >
> > >> > [INFO]
> > >> >
> > 
> > >> >
> > >> > [INFO] Reactor Summary for Apache Royale: Compiler: Parent 0.9.6:
> > >> >
> > >> > [INFO]
> > >> >
> > >> > [INFO] Apache Royale: Compiler: Parent  SUCCESS
> [
> > >> > 2.102 s]
> > >> >
> > >> > [INFO] Apache Royale: Compiler: Compiler-Common ... SUCCESS
> [
> > >> > 4.555 s]
> > >> >
> > >> > [INFO] Apache Royale: Compiler: Test Utils  SUCCESS
> [
> > >> > 0.431 s]
> > >> >
> > >> > [INFO] Apache Royale: Compiler: Externc ... SUCCESS
> [
> > >> > 9.225 s]
> > >> >
> > >> > [INFO] Apache Royale: Compiler: Compiler .. FAILURE
> [
> > >> > 0.052 s]
> > >> >
> > >> > [INFO] Apache Royale: Compiler: Compiler-JX