Build failed in Jenkins: royale-asjs_jsonly #3084

2019-06-11 Thread Apache Royale CI Server 
See 


Changes:

[aharui] Revert "[maven-release-plugin] prepare for next development iteration"

[aharui] Revert "[maven-release-plugin] prepare branch release/0.9.6"

[aharui] fix poms.  The merge really screwed them up

--
[...truncated 4.47 MB...]
 [java] Compiling file: org.apache.royale.jewel.beads.views.SnackbarView
 [java] Writing file: 
js/out/org/apache/royale/jewel/beads/views/SnackbarView.js
 [java] Compiling file: 
org.apache.royale.jewel.itemRenderers.NavigationLinkItemRenderer
 [java] Writing file: 
js/out/org/apache/royale/jewel/itemRenderers/NavigationLinkItemRenderer.js
 [java] Compiling file: org.apache.royale.jewel.beads.views.DropDownListView
 [java] Writing file: 
js/out/org/apache/royale/jewel/beads/views/DropDownListView.js
 [java] Compiling file: 
org.apache.royale.jewel.beads.controls.datefield.DateFieldMaskedTextInput
 [java] Writing file: 
js/out/org/apache/royale/jewel/beads/controls/datefield/DateFieldMaskedTextInput.js
 [java] Compiling file: 
org.apache.royale.jewel.supportClasses.drawer.DrawerBase
 [java] Writing file: 
js/out/org/apache/royale/jewel/supportClasses/drawer/DrawerBase.js
 [java] Compiling file: org.apache.royale.jewel.supportClasses.bar.BarTitle
 [java] Writing file: 
js/out/org/apache/royale/jewel/supportClasses/bar/BarTitle.js
 [java] Compiling file: 
org.apache.royale.jewel.beads.models.SliderRangeModel
 [java] Writing file: 
js/out/org/apache/royale/jewel/beads/models/SliderRangeModel.js
 [java] Compiling file: 
org.apache.royale.jewel.itemRenderers.ListItemRenderer
 [java] Writing file: 
js/out/org/apache/royale/jewel/itemRenderers/ListItemRenderer.js
 [java] Compiling file: 
org.apache.royale.jewel.itemRenderers.TableItemRenderer
 [java] Writing file: 
js/out/org/apache/royale/jewel/itemRenderers/TableItemRenderer.js
 [java] Compiling file: org.apache.royale.jewel.Application
 [java] Writing file: js/out/org/apache/royale/jewel/Application.js
 [java] Compiling file: org.apache.royale.jewel.Snackbar
 [java] Writing file: js/out/org/apache/royale/jewel/Snackbar.js
 [java] Compiling file: 
org.apache.royale.jewel.beads.layouts.VerticalCenteredLayout
 [java] Writing file: 
js/out/org/apache/royale/jewel/beads/layouts/VerticalCenteredLayout.js
 [java] Compiling file: org.apache.royale.jewel.GridCell
 [java] Writing file: js/out/org/apache/royale/jewel/GridCell.js
 [java] Compiling file: 
org.apache.royale.jewel.beads.controls.textinput.LowerCase
 [java] Writing file: 
js/out/org/apache/royale/jewel/beads/controls/textinput/LowerCase.js
 [java] Compiling file: org.apache.royale.jewel.ImageButton
 [java] Writing file: js/out/org/apache/royale/jewel/ImageButton.js
 [java] Compiling file: org.apache.royale.jewel.beads.views.ComboBoxView
 [java] Writing file: 
js/out/org/apache/royale/jewel/beads/views/ComboBoxView.js
 [java] Compiling file: 
org.apache.royale.jewel.beads.controllers.DropDownListController
 [java] Writing file: 
js/out/org/apache/royale/jewel/beads/controllers/DropDownListController.js
 [java] Compiling file: org.apache.royale.jewel.FormItem
 [java] Writing file: js/out/org/apache/royale/jewel/FormItem.js
 [java] Compiling file: 
org.apache.royale.jewel.beads.itemRenderers.DataItemRendererFactoryForCollectionView
 [java] Writing file: 
js/out/org/apache/royale/jewel/beads/itemRenderers/DataItemRendererFactoryForCollectionView.js
 [java] Compiling file: 
org.apache.royale.jewel.itemRenderers.DateItemRenderer
 [java] Writing file: 
js/out/org/apache/royale/jewel/itemRenderers/DateItemRenderer.js
 [java] Compiling file: 
org.apache.royale.jewel.beads.itemRenderers.AddListItemRendererForArrayListData
 [java] Writing file: 
js/out/org/apache/royale/jewel/beads/itemRenderers/AddListItemRendererForArrayListData.js
 [java] Compiling file: 
org.apache.royale.jewel.beads.validators.StringValidator
 [java] Writing file: 
js/out/org/apache/royale/jewel/beads/validators/StringValidator.js
 [java] Compiling file: 
org.apache.royale.jewel.beads.controllers.SnackbarController
 [java] Writing file: 
js/out/org/apache/royale/jewel/beads/controllers/SnackbarController.js
 [java] Compiling file: 
org.apache.royale.jewel.supportClasses.popup.PopUpContent
 [java] Writing file: 
js/out/org/apache/royale/jewel/supportClasses/popup/PopUpContent.js
 [java] Compiling file: org.apache.royale.jewel.beads.controls.Disabled
 [java] Writing file: 
js/out/org/apache/royale/jewel/beads/controls/Disabled.js
 [java] Compiling file: 
org.apache.royale.jewel.beads.controls.datefield.DateFieldDisabled
 [java] Writing file: 
js/out/org/apache/royale/jewel/beads/controls/datefield/DateFieldDisabled.js
 [java] Compiling file: org

Jenkins build became unstable: royale-compiler #890

2019-06-11 Thread Apache Royale CI Server 
See

Build failed in Jenkins: royale-asjs_jsonly #3083

2019-06-11 Thread Apache Royale CI Server 
See 


Changes:

[aharui] add some properties for Jenkins release building

[aharui] propagate changes from typedefs pom to support CI release packaging

[aharui] [maven-release-plugin] prepare branch release/0.9.6

[aharui] [maven-release-plugin] prepare for next development iteration

[aharui] scripts for step 11

[aharui] forgot a few

[aharui] add first attempt at step 13

[aharui] fix ant script

[aharui] try to do some tasks in jenkins batch file

[aharui] step 13

[aharui] Revert "[maven-release-plugin] prepare for next development iteration"

[aharui] revert tag

[aharui] allow setting timestamps on swcs

[aharui] set swc-date

[aharui] http -> https

[aharui] validate most swcs

[aharui] [maven-release-plugin] prepare branch release/0.9.6

[aharui] [maven-release-plugin] prepare for next development iteration

[aharui] fix up validating bits

[aharui] Revert "[maven-release-plugin] prepare for next development iteration"

[aharui] Revert "[maven-release-plugin] prepare branch release/0.9.6"

[aharui] [maven-release-plugin] prepare branch release/0.9.6

[aharui] [maven-release-plugin] prepare for next development iteration

[aharui] need this profile

[aharui] Revert "[maven-release-plugin] prepare for next development iteration"

[aharui] Revert "[maven-release-plugin] prepare branch release/0.9.6"

[aharui] turn off sourcemaps in release artifacts as the sourceRoot won't match

[aharui] fix metadata and add debugfile alias

[aharui] debugfile alias for maven

[aharui] [maven-release-plugin] prepare branch release/0.9.6

[aharui] [maven-release-plugin] prepare for next development iteration

[aharui] Revert "[maven-release-plugin] prepare for next development iteration"

[aharui] Revert "[maven-release-plugin] prepare branch release/0.9.6"

[aharui] [maven-release-plugin] prepare branch release/0.9.6

[aharui] [maven-release-plugin] prepare for next development iteration

[aharui] Revert "[maven-release-plugin] prepare for next development iteration"

[aharui] Revert "[maven-release-plugin] prepare branch release/0.9.6"

[aharui] [maven-release-plugin] prepare branch release/0.9.6

[aharui] [maven-release-plugin] prepare for next development iteration

[aharui] diagnostics

[aharui] Revert "[maven-release-plugin] prepare for next development iteration"

[aharui] Revert "[maven-release-plugin] prepare branch release/0.9.6"

[aharui] [maven-release-plugin] prepare branch release/0.9.6

[aharui] [maven-release-plugin] prepare for next development iteration

[aharui] Revert "[maven-release-plugin] prepare for next development iteration"

[aharui] Revert "[maven-release-plugin] prepare branch release/0.9.6"

[aharui] some fixes to releasesteps

[aharui] use includeClasses instead of includeSource for XML so the swf version

[aharui] more fixes for release script

[aharui] [maven-release-plugin] prepare branch release/0.9.6

[aharui] [maven-release-plugin] prepare for next development iteration

[aharui] Revert "[maven-release-plugin] prepare for next development iteration"

[aharui] Revert "[maven-release-plugin] prepare branch release/0.9.6"

[aharui] [maven-release-plugin] prepare branch release/0.9.6

[aharui] [maven-release-plugin] prepare for next development iteration

[aharui] ensure AIR_HOME so build SWF artifacts and add swcs and jars to 
validate

[aharui] fix script

[aharui] more validation of ant artifacts

[aharui] add skipTests to checkintests

--
[...truncated 385.68 KB...]
[junit] environment property - AIR_HOME = null
[junit] environment property - FLASHPLAYER_DEBUGGER = null
[junit] environment property - ASJS_HOME = 

[junit] environment property - GOOG_HOME = null
[junit] Running 
org.apache.royale.compiler.internal.codegen.typedefs.TestAnnotationEnum
[junit] foo parameters not found!  0
[junit] bar parameters not found!  0
[junit] baz parameters not found!  0
[junit] foo parameters not found!  0
[junit] bar parameters not found!  0
[junit] baz parameters not found!  0
[junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
2.226 sec
[junit] Running 
org.apache.royale.compiler.internal.codegen.typedefs.TestCollectImports
[junit] BASE parameters not found!  0
[junit] foo parameters not found!  0
[junit] foo parameters not found!  0
[junit] API parameters not found!  0
[junit] foo parameters not found!  0
[junit] BASE parameters not found!  0
[junit] foo parameters not found!  0
[junit] foo parameters not found!  0
[junit] API parameters not found!  0
[junit] foo parameters not found!  0
[junit] Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.585 sec
[junit] Running 
org.apache.royale.compiler.internal.codegen.typedefs

Build failed in Jenkins: royale-asjs #2330

2019-06-11 Thread Apache Royale CI Server 
See 


--
[...truncated 1.16 MB...]
 [java] 
 [java] Jun 12, 2019 4:36:13 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [os]:113: WARNING - name module is not defined in the 
externs.
 [java] module.exports = os;
 [java] ^^
 [java] 
 [java] Jun 12, 2019 4:36:13 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [path]:97: WARNING - name module is not defined in the 
externs.
 [java] module.exports = path;
 [java] ^^
 [java] 
 [java] Jun 12, 2019 4:36:13 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [punycode]:74: WARNING - name module is not defined in the 
externs.
 [java] module.exports = punycode;
 [java] ^^
 [java] 
 [java] Jun 12, 2019 4:36:13 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [querystring]:66: WARNING - name module is not defined in 
the externs.
 [java] module.exports = querystring;
 [java] ^^
 [java] 
 [java] Jun 12, 2019 4:36:13 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [readline]:22: WARNING - accessing name require in externs 
has no effect. Perhaps you forgot to add a var keyword?
 [java] var events = require('events');
 [java]  ^^^
 [java] 
 [java] Jun 12, 2019 4:36:13 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [readline]:23: WARNING - accessing name require in externs 
has no effect. Perhaps you forgot to add a var keyword?
 [java] var stream = require('stream');
 [java]  ^^^
 [java] 
 [java] Jun 12, 2019 4:36:13 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [readline]:84: WARNING - name module is not defined in the 
externs.
 [java] module.exports = readline;
 [java] ^^
 [java] 
 [java] Jun 12, 2019 4:36:13 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [repl]:23: WARNING - accessing name require in externs has 
no effect. Perhaps you forgot to add a var keyword?
 [java] var events = require('events');
 [java]  ^^^
 [java] 
 [java] Jun 12, 2019 4:36:13 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [repl]:24: WARNING - accessing name require in externs has 
no effect. Perhaps you forgot to add a var keyword?
 [java] var stream = require('stream');
 [java]  ^^^
 [java] 
 [java] Jun 12, 2019 4:36:13 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [repl]:48: WARNING - name module is not defined in the 
externs.
 [java] module.exports = repl;
 [java] ^^
 [java] 
 [java] Jun 12, 2019 4:36:13 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [stream]:23: WARNING - accessing name require in externs 
has no effect. Perhaps you forgot to add a var keyword?
 [java] var events = require('events');
 [java]  ^^^
 [java] 
 [java] Jun 12, 2019 4:36:13 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [stream]:254: WARNING - name module is not defined in the 
externs.
 [java] module.exports = stream;
 [java] ^^
 [java] 
 [java] Jun 12, 2019 4:36:13 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [string_decoder]:52: WARNING - name module is not defined 
in the externs.
 [java] module.exports = StringDecoder;
 [java] ^^
 [java] 
 [java] Jun 12, 2019 4:36:13 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [tls]:23: WARNING - accessing name require in externs has 
no effect. Perhaps you forgot to add a var keyword?
 [java] var crypto = require('crypto');
 [java]  ^^^
 [java] 
 [java] Jun 12, 2019 4:36:13 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [tls]:24: WARNING - accessing name require in externs has 
no effect. Perhaps you forgot to add a var keyword?
 [java] var events = require('events');
 [java]  ^^^
 [java] 
 [java] Jun 12, 2019 4:36:13 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [tls]:25: WARNING - accessing name require in externs has 
no effect. Perhaps you forgot to add a var keyword?
 [java] var net = require('net');
 [java]   ^^^
 [java] 
 [java] Jun 12, 2019 4:36:13 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [tls]:26: WARNING - accessing name require in externs has 
no effect. Perhaps you forgot to add a var keyword?
 [java] var stream = require('stream');

Re: Problem with Vectors

2019-06-11 Thread Greg Dove 
Hi Harbs - just in reply to your specific questions:
As I mentioned elsewhere it is easy to have full speed index access and
also full speed pop() and unshift() methods
If you switch off the first 3 settings I outlined in the post titled
'Language/Reflection improvements details' you will have that. Those
settings are switchable locally with doc directives as well. I will do a
full write-up this coming weekend for docs. Hopefully I can harvest a lot
of what I already wrote elsewhere for that.
BTW I switched TLF to use the legacy Vector-as-Array approach by default, I
am not sure what you want there, you could undo that if you prefer.

Beyond the above mentioned approaches for (mainly index level)
optimization, I have a preference for two more approaches, but I'd rather
limit the overall number of options to be what people definitely need
instead of adding too many options (which could create confusion). I think
your other proposal with Josh for the typed Arrays and their greater
compile-time safety will be a better fit for many cases as well, so I hope
that happens. If I have time to help out in any way with that, I would be
happy to do so as well, because it sounds like something I would use a lot.
Anyhow, I do want to support more optimizations with this implementation.
Can you say what your main concerns would be for optimization? Is it mainly
for 'push'  (and unshift) ? Those would be mine...

I would personally like to see the following:

1. A global optimization setting that affects all instances in all code
including pre-built library code. This would avoid certain runtime checks
and would also result in a lighter implementation. This is something the
final application developer decides, not anything dictated by a library
developer (but a library developer could advertise their public swc as
being compatible/safe with this type of optimization). This approach could
include perhaps 2 levels: one to remove any code paths related to fixed
length Vectors (which I think you said you never used) for example. Then
another possibly removing all element level type-checking as another level.
Adding this should not be too difficult I think and would be determined via
a goog define (which might be driven by a compiler setting, I did not look
at how easy this is yet). The thing I like about this approach is that it
is not 'baked-in' to any instance and the application developer makes the
ultimate decision and owns the associated risk (as opposed to having it
imposed on them by a library developer, for example). I think the removal
of support for 'fixed' Vectors could probably be made to generate
(debug-only) errors if there is code that runs that sets fixed to true on
any Vector instance  - to provide some reassurance of no side effects when
choosing this option.

2. Compilation scoped optimizations.
By 'compilation-scoped' I mean configurable in the same way as the
vector-index-check suppression: An over-arching config setting for the
current compilation that can be overridden locally with doc comment
directives. This affects code sites (or all current compilation scope if
set in the config) and not specific instances. I would hope this might be
the only other 'Vector' specific config option like this, simply to avoid
confusion with too many options.
So I personally think the important things here are the push and unshift
methods, because they're the ones that are also most often used in loops
when index level access or assignment is not being used (in the loop). But
I'm keen to hear more about what people want in case it's different to how
I think. And I will add support for what best represents the needs of the
community. While index level access is best for large loops (just as it is
for 'Array'), push could be preferred in small loops because it does not
require a 'get' for length to establish the upper bound of the loop or the
next acceptable index to set (for non-fixed Vectors). The optimization for
push in this case would be to bypass runtime typechecking and just do a
regular Array.push into the underlying Vector representation, which is
still actually an Array in terms of how javascript sees it. Adding this
option is easy also, but rather than just forging ahead with it, I am keen
to get input from others first.

I consider that specific instance level optimizations (in general) are
'dangerous' because even if the code is 'safe' when it is originally
written, subsequent changes to the overall codebase (possibly by different
developers) can mean that an instance ends up elsewhere in code where it
behaves differently from other instances of the same type.  Code-site
optimizations could also create an unusual internal state for an instance,
but most often they should not, because the code site where the
optimization is used should be validated in terms of the optimization by
its original developer (e.g. no runtime type checking at a particular usage
site because it is never needed in the context of that c

Build failed in Jenkins: royale-asjs_MXTests #834

2019-06-11 Thread Apache Royale CI Server 
See 


--
[...truncated 2.10 MB...]
[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source

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

2019-06-11 Thread Apache Royale CI Server 
See

Build failed in Jenkins: royale-asjs_MXTests #833

2019-06-11 Thread Apache Royale CI Server 
See 


--
[...truncated 2.10 MB...]
[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source

Build failed in Jenkins: royale-asjs_MXTests #832

2019-06-11 Thread Apache Royale CI Server 
See 


Changes:

[carlosrovira] BE0013: preparing a new blog example about modules

--
[...truncated 2.10 MB...]
[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file:

Build failed in Jenkins: royale-typedefs #1367

2019-06-11 Thread Apache Royale CI Server 
See 


--
[...truncated 55.30 KB...]
 [echo] ${env.ROYALE_DOWNLOAD_CACHE}
 [echo] Need file: ${still_no_file}

get-from-cache-if-needed:

fail-if-not-found:

getfile:
  [get] Getting: 
https://raw.githubusercontent.com/royale-extras/closure-compiler/royale/contrib/nodejs/globals.js
  [get] To: 


double-check-file:
 [echo] ${env.ROYALE_DOWNLOAD_CACHE}
 [echo] Need file: ${still_no_file}

get-from-cache-if-needed:

fail-if-not-found:

getfile:
  [get] Getting: 
https://raw.githubusercontent.com/royale-extras/closure-compiler/royale/contrib/nodejs/http.js
  [get] To: 


double-check-file:
 [echo] ${env.ROYALE_DOWNLOAD_CACHE}
 [echo] Need file: ${still_no_file}

get-from-cache-if-needed:

fail-if-not-found:

getfile:
  [get] Getting: 
https://raw.githubusercontent.com/royale-extras/closure-compiler/royale/contrib/nodejs/https.js
  [get] To: 


double-check-file:
 [echo] ${env.ROYALE_DOWNLOAD_CACHE}
 [echo] Need file: ${still_no_file}

get-from-cache-if-needed:

fail-if-not-found:

getfile:
  [get] Getting: 
https://raw.githubusercontent.com/royale-extras/closure-compiler/royale/contrib/nodejs/net.js
  [get] To: 


double-check-file:
 [echo] ${env.ROYALE_DOWNLOAD_CACHE}
 [echo] Need file: ${still_no_file}

get-from-cache-if-needed:

fail-if-not-found:

getfile:
  [get] Getting: 
https://raw.githubusercontent.com/royale-extras/closure-compiler/royale/contrib/nodejs/os.js
  [get] To: 


double-check-file:
 [echo] ${env.ROYALE_DOWNLOAD_CACHE}
 [echo] Need file: ${still_no_file}

get-from-cache-if-needed:

fail-if-not-found:

getfile:
  [get] Getting: 
https://raw.githubusercontent.com/royale-extras/closure-compiler/royale/contrib/nodejs/path.js
  [get] To: 


double-check-file:
 [echo] ${env.ROYALE_DOWNLOAD_CACHE}
 [echo] Need file: ${still_no_file}

get-from-cache-if-needed:

fail-if-not-found:

getfile:
  [get] Getting: 
https://raw.githubusercontent.com/royale-extras/closure-compiler/royale/contrib/nodejs/punycode.js
  [get] To: 


double-check-file:
 [echo] ${env.ROYALE_DOWNLOAD_CACHE}
 [echo] Need file: ${still_no_file}

get-from-cache-if-needed:

fail-if-not-found:

getfile:
  [get] Getting: 
https://raw.githubusercontent.com/royale-extras/closure-compiler/royale/contrib/nodejs/querystring.js
  [get] To: 


double-check-file:
 [echo] ${env.ROYALE_DOWNLOAD_CACHE}
 [echo] Need file: ${still_no_file}

get-from-cache-if-needed:

fail-if-not-found:

getfile:
  [get] Getting: 
https://raw.githubusercontent.com/royale-extras/closure-compiler/royale/contrib/nodejs/readline.js
  [get] To: 


double-check-file:
 [echo] ${env.ROYALE_DOWNLOAD_CACHE}
 [echo] Need file: ${still_no_file}

get-from-cache-if-needed:

fail-if-not-found:

getfile:
  [get] Getting: 
https://raw.githubusercontent.com/royale-extras/closure-compiler/royale/contrib/nodejs/repl.js
  [get] To: 


double-check-file:
 [echo] ${env.ROYALE_DOWNLOAD_CACHE}
 [echo] Need file: ${still_no_file}

get-from-cache-if-needed:

fail-if-not-found:

getfile:
  [get] Getting: 
https://raw.githubusercontent.com/royale-extras/closure-compiler/royale/contrib/nodejs/stream.js
  [get] To:

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

2019-06-11 Thread Apache Royale CI Server 
See

Re: Problem with Vectors

2019-06-11 Thread Carlos Rovira 
ok,

btw I think Greg put all info in the thread: Language/Reflection
improvements details

El mar., 11 jun. 2019 a las 16:22, Yishay Weiss ()
escribió:

> This is my mistake, I was using a library that was compiled with an older
> compiler. Sorry for the noise.
>
> 
> From: Yishay Weiss
> Sent: Tuesday, June 11, 2019 2:07:36 PM
> To: dev@royale.apache.org
> Subject: Problem with Vectors
>
> Hi Greg,
>
> I just updated Royale and I’m seeing that in our class FontLoader
>
> private var _fonts:Vector. = new Vector.();
>
> gets transpiled to
>
> this.com_printui_text_engine_FontLoader__fonts =
> org.apache.royale.utils.Language.Vector();
>
> Notice how the type isn’t given in Vector’s constructor. This results in a
> runtime error [1]. Any ideas?
>
> [1]
>
> TypeError: Cannot read property 'indexOf' of null
> Watch
> Call Stack
> org.apache.royale.utils.Language.VectorSupport.vectorElementCoercion
> Language.js:868
> org.apache.royale.utils.Language.synthVector
> Language.js:642
> org.apache.royale.utils.Language.Vector
> Language.js:685
> com.printui.text.engine.FontLoader
> FontLoader.js:24
>
>

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

RE: Problem with Vectors

2019-06-11 Thread Yishay Weiss 
This is my mistake, I was using a library that was compiled with an older 
compiler. Sorry for the noise.


From: Yishay Weiss
Sent: Tuesday, June 11, 2019 2:07:36 PM
To: dev@royale.apache.org
Subject: Problem with Vectors

Hi Greg,

I just updated Royale and I’m seeing that in our class FontLoader

private var _fonts:Vector. = new Vector.();

gets transpiled to

this.com_printui_text_engine_FontLoader__fonts = 
org.apache.royale.utils.Language.Vector();

Notice how the type isn’t given in Vector’s constructor. This results in a 
runtime error [1]. Any ideas?

[1]

TypeError: Cannot read property 'indexOf' of null
Watch
Call Stack
org.apache.royale.utils.Language.VectorSupport.vectorElementCoercion
Language.js:868
org.apache.royale.utils.Language.synthVector
Language.js:642
org.apache.royale.utils.Language.Vector
Language.js:685
com.printui.text.engine.FontLoader
FontLoader.js:24

Re: Problem with Vectors

2019-06-11 Thread Harbs 
Practical question for me is: How do we disable to Vector runtime checking? I 
was having trouble following the full discussion. My understanding was that 
there’s a compiler flag, but I’m not sure what it is.

> On Jun 11, 2019, at 7:10 AM, Yishay Weiss  wrote:
> 
> Language.js:868 [1] is
> 
>if (elementType.indexOf('Vector.<') == 0) {
> 
> 
> 
> 
> From: Yishay Weiss 
> Sent: Tuesday, June 11, 2019 2:07:36 PM
> To: dev@royale.apache.org
> Subject: Problem with Vectors
> 
> Hi Greg,
> 
> I just updated Royale and I’m seeing that in our class FontLoader
> 
> private var _fonts:Vector. = new Vector.();
> 
> gets transpiled to
> 
> this.com_printui_text_engine_FontLoader__fonts = 
> org.apache.royale.utils.Language.Vector();
> 
> Notice how the type isn’t given in Vector’s constructor. This results in a 
> runtime error [1]. Any ideas?
> 
> [1]
> 
> TypeError: Cannot read property 'indexOf' of null
> Watch
> Call Stack
> org.apache.royale.utils.Language.VectorSupport.vectorElementCoercion
> Language.js:868
> org.apache.royale.utils.Language.synthVector
> Language.js:642
> org.apache.royale.utils.Language.Vector
> Language.js:685
> com.printui.text.engine.FontLoader
> FontLoader.js:24
>

Re: 0.9.6 Release

2019-06-11 Thread Carlos Rovira 
Hi Alex!

Congrats for this milestone! In doing we'll be doing an important step! :)

Now is time for the rest of us to don't stop on docs to make 1.0 be
available soon! :))

Thanks!



El mar., 11 jun. 2019 a las 8:35, Piotr Zarzycki ()
escribió:

> Greg,
>
> It looks like Ant compiler build is working fine. I'm waiting now for JS
> only build of framework to be finished.
>
> Thanks,
> Piotr
>
> On Tue, Jun 11, 2019, 8:31 AM Greg Dove  wrote:
>
> > Thanks for clarifying Piotr. That one at least worked it seems.
> > I saw the problem elsewhere and first time it was because the compiler
> > build had required changes and did not complete before the framework.
> > The others have some issues, but I don't think it is related to my latest
> > changes , because it seems to be the same issue as previous fails. I will
> > try to figure those out tomorrow some time if I can.
> >
> > On Tue, Jun 11, 2019 at 5:08 PM Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> > wrote:
> >
> > > Greg,
> > >
> > > I was thinking about ant build on Jenkins [1]. I didn't check Maven
> build
> > > in a while.
> > >
> > > [1]
> > >
> > >
> >
> http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/changes
> > >
> > > Thanks,
> > > Piotr
> > >
> > >
> > > On Tue, Jun 11, 2019, 6:48 AM Greg Dove  wrote:
> > >
> > > > Piotr, I hope I addressed the issue, but waiting to see...
> > > > It looks like it has been unstable for last 7 days , am I reading
> that
> > > > right? https://builds.apache.org/job/Royale-asjs/
> > > >
> > > >
> > > > On Tue, Jun 11, 2019 at 4:30 PM Greg Dove 
> wrote:
> > > >
> > > > > Working on it!
> > > > >
> > > > >
> > > > > On Tue, Jun 11, 2019 at 4:29 PM Piotr Zarzycki <
> > > > piotrzarzyck...@gmail.com>
> > > > > wrote:
> > > > >
> > > > >> Hi Greg,
> > > > >>
> > > > >> After your merge the goal should be that build on Jenkins is
> working
> > > > fine.
> > > > >> Please make sure that is happen.
> > > > >>
> > > > >> Thanks,
> > > > >> Piotr
> > > > >>
> > > > >> On Tue, Jun 11, 2019, 5:32 AM Greg Dove 
> > wrote:
> > > > >>
> > > > >> > I will stick with the plan of single commit, I think it should
> be
> > > > easier
> > > > >> > for you if there are any conflicts.
> > > > >> > Last build testing is running now in local develop. I will push
> > > after
> > > > >> > that...
> > > > >> >
> > > > >> > On Tue, Jun 11, 2019 at 3:15 PM Greg Dove 
> > > > wrote:
> > > > >> >
> > > > >> > >
> > > > >> > > Thanks Alex, I was planning to merge this as a single squashed
> > > > commit,
> > > > >> > > because it isolates all the changes to a single commit (but
> this
> > > > will
> > > > >> > mean
> > > > >> > > there are many changes in one hit).
> > > > >> > > Do you have a preference in terms of how easy it will make
> > things
> > > > for
> > > > >> > you?
> > > > >> > >
> > > > >> > >
> > > > >> > > On Tue, Jun 11, 2019 at 3:07 PM Alex Harui
> > >  > > > >
> > > > >> > > wrote:
> > > > >> > >
> > > > >> > >> OK, I will wait to see your commit emails.  I will do some
> > other
> > > > >> things
> > > > >> > >> like the wiki doc.
> > > > >> > >>
> > > > >> > >> -Alex
> > > > >> > >>
> > > > >> > >> On 6/10/19, 8:06 PM, "Greg Dove" 
> wrote:
> > > > >> > >>
> > > > >> > >> Hi Alex, I guess you might be back on Royale about now.
> > Just
> > > a
> > > > >> heads
> > > > >> > >> up: I
> > > > >> > >> am about 20-30 mins max from merging in what I have. Hope
> > > > that's
> > > > >> > still
> > > > >> > >> ok... please let me know if not.
> > > > >> > >> Thanks,
> > > > >> > >> -Greg
> > > > >> > >>
> > > > >> > >>
> > > > >> > >> On Tue, Jun 11, 2019 at 7:51 AM Greg Dove <
> > > greg.d...@gmail.com
> > > > >
> > > > >> > >> wrote:
> > > > >> > >>
> > > > >> > >> >
> > > > >> > >> > Thanks Alex - I'll try to hit the window, much
> > appreciated!
> > > > >> > >> >
> > > > >> > >> >
> > > > >> > >> > On Tue, Jun 11, 2019 at 6:57 AM Alex Harui
> > > > >> >  > > > >> > >> >
> > > > >> > >> > wrote:
> > > > >> > >> >
> > > > >> > >> >> Hi Greg,
> > > > >> > >> >>
> > > > >> > >> >> It turns out I have a "split shift" today.  I'm
> stopping
> > > > work
> > > > >> for
> > > > >> > >> the
> > > > >> > >> >> next 7 or 8 hours then will get around to the merge.
> So
> > > if
> > > > >> you
> > > > >> > >> can get
> > > > >> > >> >> your changes merged in that amount of time, then I
> will
> > > wait
> > > > >> for
> > > > >> > >> you and
> > > > >> > >> >> deal with any merge conflicts (there are almost
> certain
> > to
> > > > be
> > > > >> > >> some).
> > > > >> > >> >>
> > > > >> > >> >> -Alex
> > > > >> > >> >>
> > > > >> > >> >> On 6/10/19, 11:46 AM, "Greg Dove" <
> greg.d...@gmail.com>
> > > > >> wrote:
> > > > >> > >> >>
> > > > >> > >> >> Alex, slightly OT, but in terms of coordination:
> > fyi I
> > > > am
> > > > >> > also
> > > > >> > >> very
> > > > >> > >> >> close
> > > > >> > >>

Re: Language/Reflection improvements details

2019-06-11 Thread Carlos Rovira 
Hi,

congrats Greg for get this one complete! I shared this in twitter, Linkedin
and facebook Royale social media accounts:

https://twitter.com/ApacheRoyale/status/1138438001971871744

@all: please share so we can spread the word! :)

Best

Carlos



El mar., 11 jun. 2019 a las 8:24, Greg Dove ()
escribió:

> Hi all,
>
> Just a quick summary of things merged in via recent commit.  See below for
> "How do I get things 'how they were' ?" if you want to switch off any of
> the new stuff.
>
> More reliable actionscript support.
> The new settings provide greater compatibility. But they can also be tuned
> out (Hello world is a good example, and it is smaller now in gzipped format
> for release build, than it was before)
> -More things will 'just work' when porting from older actionscript libs.
> Vector behaviour is virtually identical to swf, other types of implicit
> type coercions are generated by default (but avoidable by config), and
> certain uses of int, uint and Class are more reliable and avoid compiler or
> runtime errors compared to before.
> Reflection now has PAYG/opt-in support for including top level as3 types
> (Array, Number, int, Vector etc). These roughly match the results you see
> with reflection in swf (actually reflection info for these swf items quite
> light). This is via a plugin style setup that is only included in release
> build if you use it. See here:
>
> https://github.com/apache/royale-asjs/blob/c6379b85d8aa9d164d49b09402a23f30cb4aee3a/frameworks/projects/Reflection/src/main/royale/org/apache/royale/reflection/ExtraData.as#L127
> This same approach could be used with externs reflection data if it could
> be generated in a similar format, e.g. to provide possible reflection pack
> support for sets of javascript native classes.
> I plan to use the same ExtraData class to add support for Vector to
> AMFBinaryData, Vector is a low level type that has its own serialization
> rules. In this way there will also be no hard dependency on vector support
> in AMFBinaryData and it is therefore opt-in/PAYG via the ExtraData class.
>
> How do I get things 'how they were' ?
> maven (via additionalCompilerOptions):
> -js-complex-implicit-coercions=false;
> -js-vector-index-checks=false;
> -js-resolve-uncertain=false;
> -js-vector-emulation-class=Array;
> (note that you should also now be able to have these on separate lines in
> the pom - I find this much easier to read)
>
> ant:
> in compile-js-config.xml example
> [js-complex-implicit-coercions]false[/js-complex-implicit-coercions]
> [js-resolve-uncertain]false[/js-resolve-uncertain]
> [js-vector-index-checks]false[/js-vector-index-checks]
> [js-vector-emulation-class]Array[/js-vector-emulation-class]
> (angle brackets are substituted here with square brackets above in case
> they mess with some email clients)
>
> The first 3 options above have doc comment directives (@royalesuppress... )
> so they can be tuned off or on inside method definitions also.
>
> Fixes
> Vector-as-Array emulation now supports insertAt/removeAt (same as Array)
> vectorEmulationClass receives the fully qualified name as the string
> parameter for the elementType
>
>
> Other
> -Added a lot of compiler tests for the vector emulation options and default
> vector implementation
> -RoyaleUnit: I ported a start of the manualtest unit tests to RoyaleUnit.
> @josh... these are actually language tests, but I thought they could not
> run in the Language project because it does not have all dependencies to
> run the tests themselves, perhaps I am wrong about that? I put them in Core
> for now, and they do run correctly in both swf and JS. But please tell me
> what you prefer for these (maybe they do need to go in Language...). Also I
> made some small changes in the js ant scripts for tests to correctly clean
> the test folder.
> -Added more reflection unit tests (manualtests)
> -Started to collate unit tests for XML and updated code to fix some
> observed issues (compiler and framework).
> -Hello world is approx 600 bytes smaller after gzip compression than it was
> before
>
> I might have forgotten some things, I will add extra info tomorrow if I
> recall more. Please ask questions if you have them.
>


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

RE: Problem with Vectors

2019-06-11 Thread Yishay Weiss 
Language.js:868 [1] is

if (elementType.indexOf('Vector.<') == 0) {




From: Yishay Weiss 
Sent: Tuesday, June 11, 2019 2:07:36 PM
To: dev@royale.apache.org
Subject: Problem with Vectors

Hi Greg,

I just updated Royale and I’m seeing that in our class FontLoader

private var _fonts:Vector. = new Vector.();

gets transpiled to

this.com_printui_text_engine_FontLoader__fonts = 
org.apache.royale.utils.Language.Vector();

Notice how the type isn’t given in Vector’s constructor. This results in a 
runtime error [1]. Any ideas?

[1]

TypeError: Cannot read property 'indexOf' of null
Watch
Call Stack
org.apache.royale.utils.Language.VectorSupport.vectorElementCoercion
Language.js:868
org.apache.royale.utils.Language.synthVector
Language.js:642
org.apache.royale.utils.Language.Vector
Language.js:685
com.printui.text.engine.FontLoader
FontLoader.js:24

Problem with Vectors

2019-06-11 Thread Yishay Weiss 
Hi Greg,

I just updated Royale and I’m seeing that in our class FontLoader

private var _fonts:Vector. = new Vector.();

gets transpiled to

this.com_printui_text_engine_FontLoader__fonts = 
org.apache.royale.utils.Language.Vector();

Notice how the type isn’t given in Vector’s constructor. This results in a 
runtime error [1]. Any ideas?

[1]

TypeError: Cannot read property 'indexOf' of null
Watch
Call Stack
org.apache.royale.utils.Language.VectorSupport.vectorElementCoercion
Language.js:868
org.apache.royale.utils.Language.synthVector
Language.js:642
org.apache.royale.utils.Language.Vector
Language.js:685
com.printui.text.engine.FontLoader
FontLoader.js:24

Facebook promotion

2019-06-11 Thread Carlos Rovira 
Hi,

just let you know that yesterday I applied to a Facebook promotion of 10€
to promote Apache Royale.
I distribute a basic announce about Apache Royale for 2€ /day, so it will
be 5 days.
I'll report when this 5 days finished and share what significant data this
ad generates.

Best regards

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

RE: Compiler Build Failing on Windows

2019-06-11 Thread Shiffy 
Setting my FLASHPLAYER_DEBUGGER environment variable to 
\..\..\Documents\github\adobe\flash\flashplayer_32_sa_debug.exe aided the 
situation.
BUILD SUCCESSFUL,finally 😊 

Shiffy




From: Shiffy
Sent: Monday, June 10, 2019 11:04 PM
To: dev@royale.apache.org
Subject: RE: Compiler Build Failing on Windows

I’m going to check this out.
Thanks Alex and Yishay

Shiffy

From: Alex Harui
Sent: Friday, June 7, 2019 6:48 PM
To: dev@royale.apache.org
Subject: Re: Compiler Build Failing on Windows

IIRC, FLASHPLAYER_DEBUGGER has to point to an actual .exe file, not just a 
folder.

If our documentation need to be more clear, please suggest changes.

Thanks,
-Alex

On 6/7/19, 2:20 AM, "Shiffy"  wrote:

Its PLAYERGLOBAL_HOME


From: Harbs
Sent: Friday, June 7, 2019 12:17 PM
To: dev@royale.apache.org
Subject: Re: Compiler Build Failing on Windows

Is it PLAYERGLOBAL or PLAYERGLOBAL_HOME?

> On Jun 7, 2019, at 11:50 AM, Shiffy  wrote:
> 
> Thanks everyone for helping me out here.
> 
> These are my environment variables.
> 
> AIR_HOME ..\github\adobe\frameworks\AIRSDK_Compiler
> PLAYERGLOBAL ..\github\adobe\frameworks\libs\player
> FLASHPLAYER_DEBUGGER ..\github\adobe\flash
> 
> 
> From: Yishay Weiss
> Sent: Friday, June 7, 2019 8:45 AM
> To: dev@royale.apache.org
> Subject: RE: Compiler Build Failing on Windows
> 
> I haven’t had problems building the compiler with Ant. Shiffy, can you 
share the values of the env vars Alex wrote down?
> 
> 
> 
> AIR_HOME
> PLAYERGLOBAL_HOME
> FLASHPLAYER_DEBUGGER
> 
> 
> 
> 
> 
> From: Piotr Zarzycki 
> Sent: Thursday, June 6, 2019 1:40:17 PM
> To: dev@royale.apache.org
> Subject: Re: Compiler Build Failing on Windows
> 
> I believe the most important thing right now is to getting back our 
nightly
> build and see whether there it doesn't occur. If it doesn't you may have
> your answer to the issue without doing anything on your local machine.
> 
> czw., 6 cze 2019 o 12:36 Carlos Rovira  
napisał(a):
> 
>> I have pendent to check build with Env vars, although can't say where I
>> could try since that requieres some hours to pursue that task.
>> I think we should all try to do this, since in doing that we can finally
>> refine the process of build that is the biggest problem in Royale along
>> with releases.
>> Getting Royale to build without any issue for any new comers is the most
>> important thing along with getting releases monthly without much effort.
>> (And of course continue with documentation)
>> 
>> 
>> 
>> El mié., 5 jun. 2019 a las 17:53, Alex Harui ()
>> escribió:
>> 
>>> As discussed recently on some other thread, environment variables matter
>>> and the documentation may not be up-to-date.
>>> 
>>> We build both SWF&JS or JS-Only packages based on environment variables.
>>> Either you have the Adobe stuff for SWF and environment variables
>> pointing
>>> to them or not.  If you only have some of the Adobe environment 
variables
>>> but not others, you'll probably confuse the builds.
>>> 
>>> AIR_HOME
>>> PLAYERGLOBAL_HOME
>>> FLASHPLAYER_DEBUGGER
>>> 
>>> Either set all 3 or don't set any of the 3.
>>> 
>>> HTH,
>>> -Alex
>>> 
>>> On 6/5/19, 7:27 AM, "Piotr Zarzycki"  wrote:
>>> 
>>>Carlos,
>>> 
>>>I think it is ANT build. Yesterday I tried locally and had the same
>>> issue.
>>>I was going to report it here as well.
>>> 
>>>Thanks,
>>>Piotr
>>> 
>>>śr., 5 cze 2019 o 16:00 Carlos Rovira 
>>> napisał(a):
>>> 
 Hi
 
 can you provide more info about what method are you using to build?
>>> ANT?
 Maven? and provide the steps you use, also if you have set up some
>>> env
 vars?
 thanks
 
 El mié., 5 jun. 2019 a las 12:43, Shiffy ()
>>> escribió:
 
> I’m trying to build the compiler on Windows and it keeps failing
>>> in the
> tests.
> 
> Here’s one example of a failed test that I’m getting:
> 
>>> 
>> https://pastebin.com/TpQynEmF
> 
> The test results are hard to read, but one difference I see
>>> between the
> expected results and the actual results is that it expects
>> extends
>>> Object
> and it’s extending flash.display::Sprite.
> 
> Any ideas on what’s wrong?
> 
 
 
 --
 Carlos Rovira
 
>>> 
>> http://about.me/carlosrovira
 
>>> 
>>> 
>>>--
>>> 
>>>Piotr Zarzycki
>>> 
>>>Patreon: *
>>> 
>> https://www.patreon.com/piotrzarzycki
>>><

Build failed in Jenkins: royale-asjs_MXTests #831

2019-06-11 Thread Apache Royale CI Server 
See 


--
[...truncated 2.10 MB...]
[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source