Build failed in Jenkins: royale-asjs_jsonly #3397

2019-08-15 Thread Apache Royale CI Server
See 


--
[...truncated 1.72 MB...]
 [java] 
 [java] public var scriptName:String;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public var testSWF:String;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public var startEvent:String = "applicationComplete";
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public var testCases:Array;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public var lastEvent:Event;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public static var excludedCount:int = 0;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public var valueChanged:Boolean;
 [java] ^
 [java] 
 [java] 3.5669668 seconds
 [java] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx1g 
 [java] Java Result: 2

main:

basictests-compile-java:
   [delete] Deleting directory 

[mkdir] Created dir: 

[javac] 
:1347:
 warning: 'includeantruntime' was not set, defaulting to 
build.sysclasspath=last; set to false for repeatable builds
[javac] Compiling 12 source files to 


basictests:

basictests-mustella:

basictests-compile-js:
 [echo] ROYALE_HOME: 

 [echo] ROYALE_COMPILER_HOME: 

 [echo] GOOG_HOME: 

[mxmlc] MXMLJSC
[mxmlc] 
-sdk-js-lib=
[mxmlc] -compiler.debug=true
[mxmlc] 
+royalelib=
[mxmlc] 
-closure-lib=
[mxmlc] -compiler.targets=JSRoyale
[mxmlc] 
-compiler.library-path=
[mxmlc] 
-compiler.js-external-library-path=
[mxmlc] 
-compiler.js-library-path=
[mxmlc] 
-compiler.js-library-path+=
[mxmlc] --
[mxmlc] 

[mxmlc] The project 'BasicTestsApp' has been successfully compiled.
[mxmlc] 6.7824967 seconds
[mxmlc] 

 Warning: The definition goog.events depended on by 
org.apache.royale.core.HTMLElementWrapper in the SWC 

Build failed in Jenkins: royale-asjs_jsonly #3396

2019-08-15 Thread Apache Royale CI Server
See 


--
[...truncated 1.72 MB...]
 [java] 
 [java] public var scriptName:String;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public var testSWF:String;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public var startEvent:String = "applicationComplete";
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public var testCases:Array;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public var lastEvent:Event;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public static var excludedCount:int = 0;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public var valueChanged:Boolean;
 [java] ^
 [java] 
 [java] 4.0964784 seconds
 [java] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx1g 
 [java] Java Result: 2

main:

basictests-compile-java:
   [delete] Deleting directory 

[mkdir] Created dir: 

[javac] 
:1347:
 warning: 'includeantruntime' was not set, defaulting to 
build.sysclasspath=last; set to false for repeatable builds
[javac] Compiling 12 source files to 


basictests:

basictests-mustella:

basictests-compile-js:
 [echo] ROYALE_HOME: 

 [echo] ROYALE_COMPILER_HOME: 

 [echo] GOOG_HOME: 

[mxmlc] MXMLJSC
[mxmlc] 
-sdk-js-lib=
[mxmlc] -compiler.debug=true
[mxmlc] 
+royalelib=
[mxmlc] 
-closure-lib=
[mxmlc] -compiler.targets=JSRoyale
[mxmlc] 
-compiler.library-path=
[mxmlc] 
-compiler.js-external-library-path=
[mxmlc] 
-compiler.js-library-path=
[mxmlc] 
-compiler.js-library-path+=
[mxmlc] --
[mxmlc] 

[mxmlc] The project 'BasicTestsApp' has been successfully compiled.
[mxmlc] 

 Warning: The definition goog.events depended on by 
org.apache.royale.core.HTMLElementWrapper in the SWC 

File Handling (was Re: inject_html in the framework via rawgit)

2019-08-15 Thread Alex Harui
Greg's email coincided with some other interesting file-handling issues that 
might be worth a discussion.

The issue I ran into was that the old MX RichTextEditor has some icon buttons.  
In Flex, those buttons are embedded.  We are not (yet) supporting embedding in 
Royale, so the question is how to deliver the icon files into the user's 
bin/js-debug and bin/js-release output folders?

IMO, this is related to the rawgit issue in that inject_html users may want to 
control the URL that gets injected and want to specify a file in the output 
folder.

IMO, the basic question is:  how can you specify to the compiler a file to be 
included in the output folder?

It seems easy enough to pack more files into SWCs.  The compiler already has a 
capability for JS output to copy ALL of the files in a theme swc (a swc 
specified as a theme) into the output folder.  The problem with that is that it 
is ALL when you probably just want the files for a particular component.  I 
don't think I want to see per-component theme asset SWCs.

Now some folks may argue that this is not the job of the compiler at all.  
Folks need to use build scripts/tools like Ant and Maven to grab files.  That 
is acceptable to me.  We could provide patterns to use in Ant and Maven to grab 
files from a SWC.

But if we decide to involve the compiler, then we have options.  The simplest 
is probably to allow -include-file COMPC syntax in MXMLC with some additional 
syntax to specify which SWC to look in.

More automated would be some metadata or css somewhere (even a @include_file 
directive like @inject_html) so the compiler will copy files needed by a class 
if a class is used in the output.

Thoughts?
-Alex

On 8/14/19, 6:47 PM, "Greg Dove"  wrote:

"RawGit is now in a sunset phase and will soon shut down" [1]

It just came to my attention today that some of the framework code uses
script tag injections for rawgit urls, and I checked that service... it
could be shut down as early as October 2019.
This looks to only be used in MXRoyale and AceEditor.

One of the uses seems to be for base64 encoding and decoding, which
(hopefully) can be replaced with native browser functions, I think [2]

For now, I am just highlighting this. I realize we are in release mode for
0.96, but we probably want to ensure another release before too long with
alternative script urls before that service drops out.

1. 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frawgit.com%2Fdata=02%7C01%7Caharui%40adobe.com%7Cd5b77fe779684f45eb5d08d721228dba%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637014304634757274sdata=PBow7tF5obtNnJZMEzXEOoVQ4A%2FYUBdj%2Fm8A73Zyf60%3Dreserved=0
2. 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcaniuse.com%2F%23feat%3Datob-btoadata=02%7C01%7Caharui%40adobe.com%7Cd5b77fe779684f45eb5d08d721228dba%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637014304634757274sdata=Z%2FlbQ%2B5bsnm8bgOdJEmcYZNek5XCdkWAKPXruGbHCUk%3Dreserved=0




Build failed in Jenkins: royale-asjs_jsonly #3395

2019-08-15 Thread Apache Royale CI Server
See 


Changes:

[aharui] well, if we're going to leverage explicitWidth/Height we also have to

[aharui] try to get DG columns to behave better

[aharui] need another pixel to keep label from wrapping on Safari

--
[...truncated 1.72 MB...]
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public var scriptName:String;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public var testSWF:String;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public var startEvent:String = "applicationComplete";
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public var testCases:Array;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public var lastEvent:Event;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public static var excludedCount:int = 0;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public var valueChanged:Boolean;
 [java] ^
 [java] 
 [java] 4.8611236 seconds
 [java] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx1g 
 [java] Java Result: 2

main:

basictests-compile-java:
   [delete] Deleting directory 

[mkdir] Created dir: 

[javac] 
:1347:
 warning: 'includeantruntime' was not set, defaulting to 
build.sysclasspath=last; set to false for repeatable builds
[javac] Compiling 12 source files to 


basictests:

basictests-mustella:

basictests-compile-js:
 [echo] ROYALE_HOME: 

 [echo] ROYALE_COMPILER_HOME: 

 [echo] GOOG_HOME: 

[mxmlc] MXMLJSC
[mxmlc] 
-sdk-js-lib=
[mxmlc] -compiler.debug=true
[mxmlc] 
+royalelib=
[mxmlc] 
-closure-lib=
[mxmlc] -compiler.targets=JSRoyale
[mxmlc] 
-compiler.library-path=
[mxmlc] 
-compiler.js-external-library-path=
[mxmlc] 
-compiler.js-library-path=
[mxmlc] 
-compiler.js-library-path+=
[mxmlc] --
[mxmlc] 

Re: Discuss of release steps preparation

2019-08-15 Thread Alex Harui
Sorry, that should be plural

-DskipTests=true

-Alex

On 8/15/19, 4:15 PM, "Alex Harui"  wrote:

Also, try adding -DskipTest=true to skip the mustella tests.

On 8/15/19, 1:37 PM, "Alex Harui"  wrote:

That's a possibility.  I only used absolute paths.

Piotr, it would nice to see the Windows console output including the 
paths you gave to help make this process more robust.

-Alex

On 8/15/19, 1:21 PM, "Josh Tynjala"  wrote:

If it started working correctly after changing the path to include 
../../,
perhaps ${artifactfolder} is being set to a relative path, but the 
script
expects the path to be absolute. I'm not familiar with the release 
steps
yet, so I'm just guessing, but does that make sense?

--
Josh Tynjala
Bowler Hat LLC 



On Wed, Aug 14, 2019 at 9:23 AM Alex Harui 
 wrote:

> Can you explain why that would be the right change?  Doesn't make 
sense to
> me.
>
> On 8/14/19, 3:36 AM, "Piotr Zarzycki"  
wrote:
>
> So far so good. I did tweak the script and was able to upload
> artifacts. I
> have changed in each script:
> Line from:
>
> 
> To
> 
>
> The very last thing was close repository, so I got some 
errors you can
> check here by logging your Apache handle [1] related to 
RoyaleUnit [2].
>
> Missing Signature:
>
> 
'/org/apache/royale/compiler/royaleunit-ant-tasks/0.9.6/royaleunit-ant-tasks-0.9.6.pom.asc'
> does not exist for 'royaleunit-ant-tasks-0.9.6.pom'.
>
> I will try to figure out what has happened, but if someone 
has any
> clue to
> that let me know.
>
> [1]
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2F%23stagingRepositoriesdata=02%7C01%7Caharui%40adobe.com%7Ccc8a8de0228e4130c1bd08d721d683b4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637015077547246264sdata=mEJ%2F67tHsQZoQ1ceAjbwySCgJ%2BlK1Uax7n6NOJWkjVM%3Dreserved=0
> [2]
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpasteboard.co%2FIsDKVTe.pngdata=02%7C01%7Caharui%40adobe.com%7Ccc8a8de0228e4130c1bd08d721d683b4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637015077547246264sdata=Yzt5WLNn1YYrxGcZWQVklEPTxSmdcoGFkGSRwP821RA%3Dreserved=0
>
> Thanks,
> Piotr
>
>
> śr., 14 sie 2019 o 10:58 Carlos Rovira 

> napisał(a):
>
> > Hi Alex,
> >
> > El lun., 12 ago. 2019 a las 19:30, Alex Harui
> ()
> > escribió:
> >
> > > Also, the other committers should be aware that an RC is 
being
> created
> > > because they see the emails being sent by the CI server 
and ask
> the RM to
> > > agree to accept a commit to the release branch instead of 
the
> develop
> > > branch.
> >
> >
> > AFAIK, we should always commit to dev branch and not to 
release
> branch.
> > Releases are cut from develop. Only hot-fixes use to be 
branches
> that have
> > commits that fix something important in the release and 
then use to
> be
> > merged back to develop and master. Making commits to release
> branches could
> > bring some confusion and problems.
> >
> > At least from is what I always learnt and used [1]
> >
> > [1]
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fnvie.com%2Fposts%2Fa-successful-git-branching-model%2Fdata=02%7C01%7Caharui%40adobe.com%7Ccc8a8de0228e4130c1bd08d721d683b4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637015077547246264sdata=dz7TzbwghcsjbT0yTvoeI1gGon4bW7dgf6kI27%2BBmEk%3Dreserved=0
> >
> > --
> > Carlos Rovira
> >
> 

Re: Discuss of release steps preparation

2019-08-15 Thread Alex Harui
Also, try adding -DskipTest=true to skip the mustella tests.

On 8/15/19, 1:37 PM, "Alex Harui"  wrote:

That's a possibility.  I only used absolute paths.

Piotr, it would nice to see the Windows console output including the paths 
you gave to help make this process more robust.

-Alex

On 8/15/19, 1:21 PM, "Josh Tynjala"  wrote:

If it started working correctly after changing the path to include 
../../,
perhaps ${artifactfolder} is being set to a relative path, but the 
script
expects the path to be absolute. I'm not familiar with the release steps
yet, so I'm just guessing, but does that make sense?

--
Josh Tynjala
Bowler Hat LLC 



On Wed, Aug 14, 2019 at 9:23 AM Alex Harui  
wrote:

> Can you explain why that would be the right change?  Doesn't make 
sense to
> me.
>
> On 8/14/19, 3:36 AM, "Piotr Zarzycki"  
wrote:
>
> So far so good. I did tweak the script and was able to upload
> artifacts. I
> have changed in each script:
> Line from:
>
> 
> To
> 
>
> The very last thing was close repository, so I got some errors 
you can
> check here by logging your Apache handle [1] related to 
RoyaleUnit [2].
>
> Missing Signature:
>
> 
'/org/apache/royale/compiler/royaleunit-ant-tasks/0.9.6/royaleunit-ant-tasks-0.9.6.pom.asc'
> does not exist for 'royaleunit-ant-tasks-0.9.6.pom'.
>
> I will try to figure out what has happened, but if someone has any
> clue to
> that let me know.
>
> [1]
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2F%23stagingRepositoriesdata=02%7C01%7Caharui%40adobe.com%7C55095d2b96154c8314f708d721c05868%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637014982310625679sdata=ASZf31h7UYZsvlj2LbOsIPE8jOHf2mgeG0uSQlv5pcY%3Dreserved=0
> [2]
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpasteboard.co%2FIsDKVTe.pngdata=02%7C01%7Caharui%40adobe.com%7C55095d2b96154c8314f708d721c05868%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637014982310625679sdata=S%2Fx9lL3WQIbAlX4War36xAmoEuLer387HFK7UUon%2BBg%3Dreserved=0
>
> Thanks,
> Piotr
>
>
> śr., 14 sie 2019 o 10:58 Carlos Rovira 
> napisał(a):
>
> > Hi Alex,
> >
> > El lun., 12 ago. 2019 a las 19:30, Alex Harui
> ()
> > escribió:
> >
> > > Also, the other committers should be aware that an RC is being
> created
> > > because they see the emails being sent by the CI server and 
ask
> the RM to
> > > agree to accept a commit to the release branch instead of the
> develop
> > > branch.
> >
> >
> > AFAIK, we should always commit to dev branch and not to release
> branch.
> > Releases are cut from develop. Only hot-fixes use to be branches
> that have
> > commits that fix something important in the release and then 
use to
> be
> > merged back to develop and master. Making commits to release
> branches could
> > bring some confusion and problems.
> >
> > At least from is what I always learnt and used [1]
> >
> > [1]
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fnvie.com%2Fposts%2Fa-successful-git-branching-model%2Fdata=02%7C01%7Caharui%40adobe.com%7C55095d2b96154c8314f708d721c05868%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637014982310625679sdata=X41udM3mLBSC3UE6fCiHhNrBf%2F7GcuaylOHaEa9CDz0%3Dreserved=0
> >
> > --
> > Carlos Rovira
> >
> 
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C55095d2b96154c8314f708d721c05868%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637014982310625679sdata=DgzewAQj2wKxm6Rn1eKVntWEsByKNqzMDNyxF%2Bah8zY%3Dreserved=0
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *
> 

Re: Discuss of release steps preparation

2019-08-15 Thread Alex Harui
That's a possibility.  I only used absolute paths.

Piotr, it would nice to see the Windows console output including the paths you 
gave to help make this process more robust.

-Alex

On 8/15/19, 1:21 PM, "Josh Tynjala"  wrote:

If it started working correctly after changing the path to include ../../,
perhaps ${artifactfolder} is being set to a relative path, but the script
expects the path to be absolute. I'm not familiar with the release steps
yet, so I'm just guessing, but does that make sense?

--
Josh Tynjala
Bowler Hat LLC 



On Wed, Aug 14, 2019 at 9:23 AM Alex Harui  wrote:

> Can you explain why that would be the right change?  Doesn't make sense to
> me.
>
> On 8/14/19, 3:36 AM, "Piotr Zarzycki"  wrote:
>
> So far so good. I did tweak the script and was able to upload
> artifacts. I
> have changed in each script:
> Line from:
>
> 
> To
> 
>
> The very last thing was close repository, so I got some errors you can
> check here by logging your Apache handle [1] related to RoyaleUnit 
[2].
>
> Missing Signature:
>
> 
'/org/apache/royale/compiler/royaleunit-ant-tasks/0.9.6/royaleunit-ant-tasks-0.9.6.pom.asc'
> does not exist for 'royaleunit-ant-tasks-0.9.6.pom'.
>
> I will try to figure out what has happened, but if someone has any
> clue to
> that let me know.
>
> [1]
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2F%23stagingRepositoriesdata=02%7C01%7Caharui%40adobe.com%7Cd73a421dee514ae4c93e08d721be3546%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637014973132264344sdata=1F5rtHiDdAlRTVQjaF2RfI%2B5HXGy6tD71XE3HHuR7Hw%3Dreserved=0
> [2]
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpasteboard.co%2FIsDKVTe.pngdata=02%7C01%7Caharui%40adobe.com%7Cd73a421dee514ae4c93e08d721be3546%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637014973132274346sdata=H6H7V6ukhQ50ZCVXOuM0jtmmiyshBFnMWuqnNW87s%2B8%3Dreserved=0
>
> Thanks,
> Piotr
>
>
> śr., 14 sie 2019 o 10:58 Carlos Rovira 
> napisał(a):
>
> > Hi Alex,
> >
> > El lun., 12 ago. 2019 a las 19:30, Alex Harui
> ()
> > escribió:
> >
> > > Also, the other committers should be aware that an RC is being
> created
> > > because they see the emails being sent by the CI server and ask
> the RM to
> > > agree to accept a commit to the release branch instead of the
> develop
> > > branch.
> >
> >
> > AFAIK, we should always commit to dev branch and not to release
> branch.
> > Releases are cut from develop. Only hot-fixes use to be branches
> that have
> > commits that fix something important in the release and then use to
> be
> > merged back to develop and master. Making commits to release
> branches could
> > bring some confusion and problems.
> >
> > At least from is what I always learnt and used [1]
> >
> > [1]
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fnvie.com%2Fposts%2Fa-successful-git-branching-model%2Fdata=02%7C01%7Caharui%40adobe.com%7Cd73a421dee514ae4c93e08d721be3546%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637014973132274346sdata=WOwGWqyt3o5I3PqBYsvyti1Qvh2r9aLwDnRHRP8mY%2FI%3Dreserved=0
> >
> > --
> > Carlos Rovira
> >
> 
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7Cd73a421dee514ae4c93e08d721be3546%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637014973132274346sdata=MgE%2BH8qIszjbsLf%2FzeHjGVnzvQFwYrKJmLAUQ6dRc74%3Dreserved=0
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Cd73a421dee514ae4c93e08d721be3546%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637014973132274346sdata=Z98GvacfeJc8YGvOtAYfBqSou6MadzZtbt%2BjRZ%2BOln4%3Dreserved=0
> <
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Cd73a421dee514ae4c93e08d721be3546%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637014973132274346sdata=Z98GvacfeJc8YGvOtAYfBqSou6MadzZtbt%2BjRZ%2BOln4%3Dreserved=0
> >*
>
>
>




Re: Discuss of release steps preparation

2019-08-15 Thread Josh Tynjala
If it started working correctly after changing the path to include ../../,
perhaps ${artifactfolder} is being set to a relative path, but the script
expects the path to be absolute. I'm not familiar with the release steps
yet, so I'm just guessing, but does that make sense?

--
Josh Tynjala
Bowler Hat LLC 


On Wed, Aug 14, 2019 at 9:23 AM Alex Harui  wrote:

> Can you explain why that would be the right change?  Doesn't make sense to
> me.
>
> On 8/14/19, 3:36 AM, "Piotr Zarzycki"  wrote:
>
> So far so good. I did tweak the script and was able to upload
> artifacts. I
> have changed in each script:
> Line from:
>
> 
> To
> 
>
> The very last thing was close repository, so I got some errors you can
> check here by logging your Apache handle [1] related to RoyaleUnit [2].
>
> Missing Signature:
>
> '/org/apache/royale/compiler/royaleunit-ant-tasks/0.9.6/royaleunit-ant-tasks-0.9.6.pom.asc'
> does not exist for 'royaleunit-ant-tasks-0.9.6.pom'.
>
> I will try to figure out what has happened, but if someone has any
> clue to
> that let me know.
>
> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2F%23stagingRepositoriesdata=02%7C01%7Caharui%40adobe.com%7Ccc49916dedd948ec37a408d720a330e8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637013757624763085sdata=MBN%2FVae7WMZ6YWOD8fQumGivlLwaxfFNwmNE59%2F61Rc%3Dreserved=0
> [2]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpasteboard.co%2FIsDKVTe.pngdata=02%7C01%7Caharui%40adobe.com%7Ccc49916dedd948ec37a408d720a330e8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637013757624763085sdata=wiTOzckxfuKk9whMWtP1ZbBQ8nPygJb7ORnT0yvLKiM%3Dreserved=0
>
> Thanks,
> Piotr
>
>
> śr., 14 sie 2019 o 10:58 Carlos Rovira 
> napisał(a):
>
> > Hi Alex,
> >
> > El lun., 12 ago. 2019 a las 19:30, Alex Harui
> ()
> > escribió:
> >
> > > Also, the other committers should be aware that an RC is being
> created
> > > because they see the emails being sent by the CI server and ask
> the RM to
> > > agree to accept a commit to the release branch instead of the
> develop
> > > branch.
> >
> >
> > AFAIK, we should always commit to dev branch and not to release
> branch.
> > Releases are cut from develop. Only hot-fixes use to be branches
> that have
> > commits that fix something important in the release and then use to
> be
> > merged back to develop and master. Making commits to release
> branches could
> > bring some confusion and problems.
> >
> > At least from is what I always learnt and used [1]
> >
> > [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fnvie.com%2Fposts%2Fa-successful-git-branching-model%2Fdata=02%7C01%7Caharui%40adobe.com%7Ccc49916dedd948ec37a408d720a330e8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637013757624763085sdata=wH%2B2sM0uBA8CdSRbaaniZdqaHrRk6hnIwdYZPJHTVLA%3Dreserved=0
> >
> > --
> > Carlos Rovira
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7Ccc49916dedd948ec37a408d720a330e8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637013757624763085sdata=ncu5xXT3rnbQG%2BKTZBO6sX61T5gWfOiicgAIXQy8%2F8Y%3Dreserved=0
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Ccc49916dedd948ec37a408d720a330e8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637013757624773080sdata=CY1fo%2FqTgW%2B8Jtx32I7bw%2B0k7ys3iNJ2zxjT3p7P1cU%3Dreserved=0
> <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Ccc49916dedd948ec37a408d720a330e8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637013757624773080sdata=CY1fo%2FqTgW%2B8Jtx32I7bw%2B0k7ys3iNJ2zxjT3p7P1cU%3Dreserved=0
> >*
>
>
>


Discuss of release steps preparation

2019-08-15 Thread Piotr Zarzycki
Nope Maven didn't provide such feature or at least I didn't get any
questions on console.

I was today on a last step which takes lot's of time - build on machine
whole framework by ant, but if failed on mustella tests. I will try
tomorrow and see whether it happen again. If that very last step will be
successful I will post vote thread.

BTW. I had to still use in releasesteps.xml Mac that path ../../folder
which I have mention In previous emails.

On Thu, Aug 15, 2019, 8:36 PM Alex Harui  wrote:

> Good to know.  When it failed on Windows, did Maven offer command-line
> options to continue from the point of failure?  Unless all future RMs have
> Macs, we still need to find a way for Windows-only RMs to be successful.
>
> -Alex
>
> On 8/15/19, 5:12 AM, "Piotr Zarzycki"  wrote:
>
> Good news. I tried today again upload artifacts from my Windows
> machine -
> it failed again. I copied my signed artifacts to my Mac machine which
> is
> using different internet connection. I'm not sure how it influences
> all the
> process but I have uploaded artifacts without any problem. I'm moving
> forward with all of that.
>
> śr., 14 sie 2019 o 18:40 Alex Harui 
> napisał(a):
>
> > Carlos,
> >
> > In [1] that you referenced it says about release branches:
> >
> > "During that time, bug fixes may be applied in this branch (rather
> than on
> > the develop branch)."
> >
> > To me, that means that new unstable changes should go into develop,
> but
> > changes to make the release better should be discussed with the RM
> and
> > committed to the release branch if agreed.  We want to avoid
> cherry-picking
> > the develop branch to the release branch if at all possible.
> >
> > -Alex
> >
> > On 8/14/19, 1:58 AM, "Carlos Rovira" 
> wrote:
> >
> > Hi Alex,
> >
> > El lun., 12 ago. 2019 a las 19:30, Alex Harui
> > ()
> > escribió:
> >
> > > Also, the other committers should be aware that an RC is being
> > created
> > > because they see the emails being sent by the CI server and
> ask the
> > RM to
> > > agree to accept a commit to the release branch instead of the
> develop
> > > branch.
> >
> >
> > AFAIK, we should always commit to dev branch and not to release
> branch.
> > Releases are cut from develop. Only hot-fixes use to be branches
> that
> > have
> > commits that fix something important in the release and then use
> to be
> > merged back to develop and master. Making commits to release
> branches
> > could
> > bring some confusion and problems.
> >
> > At least from is what I always learnt and used [1]
> >
> > [1]
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fnvie.com%2Fposts%2Fa-successful-git-branching-model%2Fdata=02%7C01%7Caharui%40adobe.com%7C86e1e58dae864a33809708d72179c053%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637014679195903060sdata=bjUheSRli9gqZ7mGNo77rHSJULBlChoR9wpJevToGak%3Dreserved=0
> >
> > --
> > Carlos Rovira
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C86e1e58dae864a33809708d72179c053%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637014679195903060sdata=rA2ejTyLa08eWmDaDAQsMpAgdeNklbIuOMYLJWMVj4E%3Dreserved=0
> >
> >
> >
>
> --
>
> Piotr Zarzycki
>
> Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7C86e1e58dae864a33809708d72179c053%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637014679195903060sdata=zyWAUHptRYTuNyIzrlLhV4a3CCCQTRX%2F%2FDT3XoxKK4Y%3Dreserved=0
> <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7C86e1e58dae864a33809708d72179c053%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637014679195903060sdata=zyWAUHptRYTuNyIzrlLhV4a3CCCQTRX%2F%2FDT3XoxKK4Y%3Dreserved=0
> >*
>
>
>


Build failed in Jenkins: royale-asjs_jsonly #3394

2019-08-15 Thread Apache Royale CI Server
See 


Changes:

[yishayjobs] Fixes #445

[yishayjobs] bad comment

[yishayjobs] Fixes #445 again

--
[...truncated 1.72 MB...]
 [java] 
 [java] public var scriptName:String;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public var testSWF:String;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public var startEvent:String = "applicationComplete";
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public var testCases:Array;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public var lastEvent:Event;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public static var excludedCount:int = 0;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public var valueChanged:Boolean;
 [java] ^
 [java] 
 [java] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx1g 
 [java] 4.1604024 seconds
 [java] Java Result: 2

main:

basictests-compile-java:
   [delete] Deleting directory 

[mkdir] Created dir: 

[javac] 
:1347:
 warning: 'includeantruntime' was not set, defaulting to 
build.sysclasspath=last; set to false for repeatable builds
[javac] Compiling 12 source files to 


basictests:

basictests-mustella:

basictests-compile-js:
 [echo] ROYALE_HOME: 

 [echo] ROYALE_COMPILER_HOME: 

 [echo] GOOG_HOME: 

[mxmlc] MXMLJSC
[mxmlc] 
-sdk-js-lib=
[mxmlc] -compiler.debug=true
[mxmlc] 
+royalelib=
[mxmlc] 
-closure-lib=
[mxmlc] -compiler.targets=JSRoyale
[mxmlc] 
-compiler.library-path=
[mxmlc] 
-compiler.js-external-library-path=
[mxmlc] 
-compiler.js-library-path=
[mxmlc] 
-compiler.js-library-path+=
[mxmlc] --
[mxmlc] 

[mxmlc] The project 'BasicTestsApp' has been successfully compiled.
[mxmlc] 6.9825587 seconds
[mxmlc] 

 Warning: The definition 

Re: Discuss of release steps preparation

2019-08-15 Thread Alex Harui
Good to know.  When it failed on Windows, did Maven offer command-line options 
to continue from the point of failure?  Unless all future RMs have Macs, we 
still need to find a way for Windows-only RMs to be successful.

-Alex

On 8/15/19, 5:12 AM, "Piotr Zarzycki"  wrote:

Good news. I tried today again upload artifacts from my Windows machine -
it failed again. I copied my signed artifacts to my Mac machine which is
using different internet connection. I'm not sure how it influences all the
process but I have uploaded artifacts without any problem. I'm moving
forward with all of that.

śr., 14 sie 2019 o 18:40 Alex Harui  napisał(a):

> Carlos,
>
> In [1] that you referenced it says about release branches:
>
> "During that time, bug fixes may be applied in this branch (rather than on
> the develop branch)."
>
> To me, that means that new unstable changes should go into develop, but
> changes to make the release better should be discussed with the RM and
> committed to the release branch if agreed.  We want to avoid 
cherry-picking
> the develop branch to the release branch if at all possible.
>
> -Alex
>
> On 8/14/19, 1:58 AM, "Carlos Rovira"  wrote:
>
> Hi Alex,
>
> El lun., 12 ago. 2019 a las 19:30, Alex Harui
> ()
> escribió:
>
> > Also, the other committers should be aware that an RC is being
> created
> > because they see the emails being sent by the CI server and ask the
> RM to
> > agree to accept a commit to the release branch instead of the 
develop
> > branch.
>
>
> AFAIK, we should always commit to dev branch and not to release 
branch.
> Releases are cut from develop. Only hot-fixes use to be branches that
> have
> commits that fix something important in the release and then use to be
> merged back to develop and master. Making commits to release branches
> could
> bring some confusion and problems.
>
> At least from is what I always learnt and used [1]
>
> [1]
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fnvie.com%2Fposts%2Fa-successful-git-branching-model%2Fdata=02%7C01%7Caharui%40adobe.com%7C86e1e58dae864a33809708d72179c053%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637014679195903060sdata=bjUheSRli9gqZ7mGNo77rHSJULBlChoR9wpJevToGak%3Dreserved=0
>
> --
> Carlos Rovira
>
> 
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C86e1e58dae864a33809708d72179c053%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637014679195903060sdata=rA2ejTyLa08eWmDaDAQsMpAgdeNklbIuOMYLJWMVj4E%3Dreserved=0
>
>
>

-- 

Piotr Zarzycki

Patreon: 
*https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7C86e1e58dae864a33809708d72179c053%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637014679195903060sdata=zyWAUHptRYTuNyIzrlLhV4a3CCCQTRX%2F%2FDT3XoxKK4Y%3Dreserved=0

*




Build failed in Jenkins: royale-asjs_MXTests #1061

2019-08-15 Thread Apache Royale CI Server
See 


--
[...truncated 897.25 KB...]
[mxmlc] 
-compiler.library-path+=
[mxmlc] 
-compiler.js-external-library-path=
[mxmlc] 
-compiler.js-library-path=
[mxmlc] 
-compiler.js-library-path+=
[mxmlc] --
[mxmlc] 

[mxmlc] Loading configuration: 

[mxmlc] Loading configuration: 

[mxmlc] 
[mxmlc] scanning for overrides: IFlexInfo
[mxmlc] scanning for overrides: ApplicationBase
[mxmlc] scanning for overrides: IEventDispatcher
[mxmlc] scanning for overrides: IInitialViewApplication
[mxmlc] scanning for overrides: IParent
[mxmlc] scanning for overrides: IPopUpHost
[mxmlc] scanning for overrides: IPopUpHostParent
[mxmlc] scanning for overrides: IRenderedObject
[mxmlc] scanning for overrides: IStrand
[mxmlc] scanning for overrides: Application
[mxmlc] scanning for overrides: BasicTestsApp
[mxmlc] scanning for overrides: DontSendScriptComplete
[mxmlc] scanning for overrides: ExitWhenDone
[mxmlc] scanning for overrides: SendFormattedResultsToLog
[mxmlc] scanning for overrides: RoyaleContext
[mxmlc] scanning for overrides: UnitTester
[mxmlc] scanning for overrides: ButtonTestScript
[mxmlc] scanning for overrides: CheckBoxTestScript
[mxmlc] scanning for overrides: HTMLElementWrapper
[mxmlc] scanning for overrides: IId
[mxmlc] scanning for overrides: IChild
[mxmlc] scanning for overrides: IUIBase
[mxmlc] scanning for overrides: ILayoutChild
[mxmlc] scanning for overrides: IParentIUIBase
[mxmlc] scanning for overrides: IRoyaleElement
[mxmlc] scanning for overrides: IStrandWithModel
[mxmlc] scanning for overrides: IStrandWithModelView
[mxmlc] scanning for overrides: IStyleableObject
[mxmlc] scanning for overrides: UIBase
[mxmlc] scanning for overrides: IContainer
[mxmlc] scanning for overrides: IContentViewHost
[mxmlc] scanning for overrides: ILayoutParent
[mxmlc] scanning for overrides: ILayoutView
[mxmlc] scanning for overrides: IStatesObject
[mxmlc] scanning for overrides: GroupBase
[mxmlc] scanning for overrides: IApplicationView
[mxmlc] scanning for overrides: ViewBase
[mxmlc] scanning for overrides: IMXMLDocument
[mxmlc] scanning for overrides: View
[mxmlc] scanning for overrides: BasicTests
[mxmlc] scanning for overrides: IBead
[mxmlc] scanning for overrides: IBeadLayout
[mxmlc] scanning for overrides: LayoutBase
[mxmlc] scanning for overrides: BasicLayout
[mxmlc] scanning for overrides: IBeadModel
[mxmlc] scanning for overrides: ITextModel
[mxmlc] scanning for overrides: EventDispatcher
[mxmlc] scanning for overrides: TextModel
[mxmlc] scanning for overrides: IToggleButtonModel
[mxmlc] scanning for overrides: ToggleButtonModel
[mxmlc] scanning for overrides: IViewportModel
[mxmlc] scanning for overrides: ViewportModel
[mxmlc] scanning for overrides: IBeadView
[mxmlc] scanning for overrides: BeadViewBase
[mxmlc] scanning for overrides: CSSButtonView
[mxmlc] scanning for overrides: CSSTextButtonView
[mxmlc] scanning for overrides: CheckBoxView
[mxmlc] scanning for overrides: ILayoutHost
[mxmlc] scanning for overrides: GroupView
[mxmlc] scanning for overrides: ContainerView
[mxmlc] scanning for overrides: IGraphicsDrawing
[mxmlc] scanning for overrides: IBorderBead
[mxmlc] scanning for overrides: SingleLineBorderBead
[mxmlc] scanning for overrides: IBackgroundBead
[mxmlc] scanning for overrides: SolidBackgroundBead
[mxmlc] scanning for overrides: IMeasurementBead
[mxmlc] scanning for overrides: TextButtonMeasurementBead
[mxmlc] scanning for overrides: TextFieldLabelMeasurementBead
[mxmlc] scanning for overrides: ITextFieldView
[mxmlc] scanning for overrides: TextFieldViewBase
[mxmlc] scanning for overrides: TextFieldView
[mxmlc] scanning for overrides: ContainerContentArea
[mxmlc] scanning for overrides: IViewport
[mxmlc] scanning for overrides: Viewport
[mxmlc] scanning for overrides: 

Release Step 013 Succeeded

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

Re: Discuss of release steps preparation

2019-08-15 Thread Piotr Zarzycki
If we would use for release process develop it would impossible for me
finish that process. I'm volunteer - even if current tasks is being paid
job. - It means that I could do first 5 steps first day and in couple of
days another 2 steps. If there would be some commit between those days - I
will have to start from scratch again everything again.

śr., 14 sie 2019 o 18:40 Alex Harui  napisał(a):

> Carlos,
>
> In [1] that you referenced it says about release branches:
>
> "During that time, bug fixes may be applied in this branch (rather than on
> the develop branch)."
>
> To me, that means that new unstable changes should go into develop, but
> changes to make the release better should be discussed with the RM and
> committed to the release branch if agreed.  We want to avoid cherry-picking
> the develop branch to the release branch if at all possible.
>
> -Alex
>
> On 8/14/19, 1:58 AM, "Carlos Rovira"  wrote:
>
> Hi Alex,
>
> El lun., 12 ago. 2019 a las 19:30, Alex Harui
> ()
> escribió:
>
> > Also, the other committers should be aware that an RC is being
> created
> > because they see the emails being sent by the CI server and ask the
> RM to
> > agree to accept a commit to the release branch instead of the develop
> > branch.
>
>
> AFAIK, we should always commit to dev branch and not to release branch.
> Releases are cut from develop. Only hot-fixes use to be branches that
> have
> commits that fix something important in the release and then use to be
> merged back to develop and master. Making commits to release branches
> could
> bring some confusion and problems.
>
> At least from is what I always learnt and used [1]
>
> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fnvie.com%2Fposts%2Fa-successful-git-branching-model%2Fdata=02%7C01%7Caharui%40adobe.com%7C84d6c89c5d284a001ddf08d72095850a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637013698867612965sdata=yGlrwnkreBblWjBtMMmpWJD4Cwk7q2tx62B97kn2F5o%3Dreserved=0
>
> --
> Carlos Rovira
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C84d6c89c5d284a001ddf08d72095850a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637013698867622965sdata=dgVvkG6rNkPhYuSJ6FkuHgXFKzUJi2Qxuknk5iuPYS0%3Dreserved=0
>
>
>

-- 

Piotr Zarzycki

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


Re: Discuss of release steps preparation

2019-08-15 Thread Piotr Zarzycki
Good news. I tried today again upload artifacts from my Windows machine -
it failed again. I copied my signed artifacts to my Mac machine which is
using different internet connection. I'm not sure how it influences all the
process but I have uploaded artifacts without any problem. I'm moving
forward with all of that.

śr., 14 sie 2019 o 18:40 Alex Harui  napisał(a):

> Carlos,
>
> In [1] that you referenced it says about release branches:
>
> "During that time, bug fixes may be applied in this branch (rather than on
> the develop branch)."
>
> To me, that means that new unstable changes should go into develop, but
> changes to make the release better should be discussed with the RM and
> committed to the release branch if agreed.  We want to avoid cherry-picking
> the develop branch to the release branch if at all possible.
>
> -Alex
>
> On 8/14/19, 1:58 AM, "Carlos Rovira"  wrote:
>
> Hi Alex,
>
> El lun., 12 ago. 2019 a las 19:30, Alex Harui
> ()
> escribió:
>
> > Also, the other committers should be aware that an RC is being
> created
> > because they see the emails being sent by the CI server and ask the
> RM to
> > agree to accept a commit to the release branch instead of the develop
> > branch.
>
>
> AFAIK, we should always commit to dev branch and not to release branch.
> Releases are cut from develop. Only hot-fixes use to be branches that
> have
> commits that fix something important in the release and then use to be
> merged back to develop and master. Making commits to release branches
> could
> bring some confusion and problems.
>
> At least from is what I always learnt and used [1]
>
> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fnvie.com%2Fposts%2Fa-successful-git-branching-model%2Fdata=02%7C01%7Caharui%40adobe.com%7C84d6c89c5d284a001ddf08d72095850a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637013698867612965sdata=yGlrwnkreBblWjBtMMmpWJD4Cwk7q2tx62B97kn2F5o%3Dreserved=0
>
> --
> Carlos Rovira
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C84d6c89c5d284a001ddf08d72095850a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637013698867622965sdata=dgVvkG6rNkPhYuSJ6FkuHgXFKzUJi2Qxuknk5iuPYS0%3Dreserved=0
>
>
>

-- 

Piotr Zarzycki

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


Release Step 012 Succeeded

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

Build failed in Jenkins: royale-asjs_MXTests #1060

2019-08-15 Thread Apache Royale CI Server
See 


--
[...truncated 982.95 KB...]
[mxmlc] scanning for overrides: CustomEvent
[mxmlc] scanning for overrides: ItemAddedEvent
[mxmlc] scanning for overrides: ItemClickedEvent
[mxmlc] scanning for overrides: ItemRemovedEvent
[mxmlc] scanning for overrides: ItemRendererEvent
[mxmlc] scanning for overrides: Size
[mxmlc] scanning for overrides: ItemAndDescriptor
[mxmlc] scanning for overrides: SetEventHandler
[mxmlc] scanning for overrides: SetProperty
[mxmlc] scanning for overrides: CSSBorderUtils
[mxmlc] scanning for overrides: CSSUtils
[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: 

Build failed in Jenkins: royale-asjs_MXTests #1059

2019-08-15 Thread Apache Royale CI Server
See 


Changes:

[aharui] handle left/right and top/bottom sizing

--
[...truncated 984.24 KB...]
[mxmlc] scanning for overrides: CustomEvent
[mxmlc] scanning for overrides: ItemAddedEvent
[mxmlc] scanning for overrides: ItemClickedEvent
[mxmlc] scanning for overrides: ItemRemovedEvent
[mxmlc] scanning for overrides: ItemRendererEvent
[mxmlc] scanning for overrides: Size
[mxmlc] scanning for overrides: ItemAndDescriptor
[mxmlc] scanning for overrides: SetEventHandler
[mxmlc] scanning for overrides: SetProperty
[mxmlc] scanning for overrides: CSSBorderUtils
[mxmlc] scanning for overrides: CSSUtils
[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] 

Build failed in Jenkins: royale-asjs_MXTests #1058

2019-08-15 Thread Apache Royale CI Server
See 


--
[...truncated 983.60 KB...]
[mxmlc] scanning for overrides: CustomEvent
[mxmlc] scanning for overrides: ItemAddedEvent
[mxmlc] scanning for overrides: ItemClickedEvent
[mxmlc] scanning for overrides: ItemRemovedEvent
[mxmlc] scanning for overrides: ItemRendererEvent
[mxmlc] scanning for overrides: Size
[mxmlc] scanning for overrides: ItemAndDescriptor
[mxmlc] scanning for overrides: SetEventHandler
[mxmlc] scanning for overrides: SetProperty
[mxmlc] scanning for overrides: CSSBorderUtils
[mxmlc] scanning for overrides: CSSUtils
[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: