Build failed in Jenkins: royale-asjs_jsonly #3650

2019-10-06 Thread Apache Royale CI Server
See 


--
[...truncated 103.67 KB...]
   [delete] Deleting: 


check-for-tests:

clean-tests:
 [echo] swc-date is 10/07/19 04:05 +
   [delete] Deleting: 


clean:
 [echo] swc-date is 10/07/19 04:05 +
   [delete] Deleting: 


check-for-tests:

clean-tests:
 [echo] swc-date is 10/07/19 04:05 +
   [delete] Deleting: 


clean:
 [echo] swc-date is 10/07/19 04:05 +
   [delete] Deleting: 


check-for-tests:

clean-tests:
 [echo] swc-date is 10/07/19 04:05 +
   [delete] Deleting: 


clean:
 [echo] swc-date is 10/07/19 04:05 +
   [delete] Deleting: 


check-for-tests:

clean-tests:
 [echo] swc-date is 10/07/19 04:05 +
   [delete] Deleting: 


clean:
 [echo] swc-date is 10/07/19 04:05 +
   [delete] Deleting: 


check-for-tests:

clean-tests:
 [echo] swc-date is 10/07/19 04:05 +
   [delete] Deleting: 


clean:
 [echo] swc-date is 10/07/19 04:05 +
   [delete] Deleting: 


check-for-tests:

clean-tests:
 [echo] swc-date is 10/07/19 04:05 +
   [delete] Deleting: 


clean:
 [echo] swc-date is 10/07/19 04:05 +
   [delete] Deleting: 


check-for-tests:

clean-tests:

clean:
 [echo] swc-date is 10/07/19 04:05 +
   [delete] Deleting: 


clean:
 [echo] swc-date is 10/07/19 04:05 +
   [delete] Deleting: 


check-for-tests:

clean-tests:

clean:
 [echo] swc-date is 10/07/19 04:05 +
   [delete] Deleting: 


clean:
 [echo] swc-date is 10/07/19 04:05 +
   [delete] Deleting: 


check-for-tests:

clean-tests:

clean:
 [echo] swc-date is 10/07/19 04:05 +
   [delete] Deleting: 


clean:
 [echo] swc-date is 10/07/19 04:05 +
   [delete] Deleting: 


check-for-tests:

clean-tests:
 [echo] swc-date is 10/07/19 04:05 +
   [delete] Deleting: 


clean:
 [echo] swc-date is 10/07/19 04:05 +
   [delete] Deleting: 


check-for-tests:

clean-tests:

Re: Heads up on XML

2019-10-06 Thread Greg Dove
Ok, thanks Alex, I will do that tomorrow.


On Mon, Oct 7, 2019 at 4:02 PM Alex Harui  wrote:

> Improvements to the Maven builds and Ant builds are always welcome.  Just
> make sure they work from a truly clean machine (empty the local Maven repo,
> build without access to the snapshots repo, etc).
>
> There are some issues with profile inheritance in Maven, but I don't
> understand your proposal enough to know if there is some hole in it.  Try
> it and find out.
>
> -Alex
>
> On 10/6/19, 4:49 PM, "Greg Dove"  wrote:
>
> Hi Piotr, just a quick follow-up to let you know that was all good, I
> had
> already tested the merge and conflict resolution myself and was ready
> to
> step in and help with that if that was necessary, but you already did
> it
> before I got a chance to send my email about that. :)
>
> I have to say: well done for getting through the release process. I
> could
> sense your frustration at times, and I know it must have seemed like it
> took far too long, but I am sure you have made a huge difference for
> the
> future in terms of that process.
>
>
> also fyi, I had to use -Dgenerate.swf.swcs=true in my local maven build
> today, and I was vaguely aware of discussions about this during release
> prep.
> But I wonder if this is necessary. Can't we just use the top level
> profiles
> at the lower levels instead of creating new profiles? There's probably
> a
> gap in my understanding of why this was necessary, but I would have
> expected that we could simply use something like:
>
> 
> generate-swcs-for-swf
> 
> 
> org.apache.royale.framework
> Core
> 0.9.7-SNAPSHOT
> swc
> swf
> 
> 
> 
>
> in the framework modules, instead of:
>
>   
>   swf-dependencies
>   
>   
>   generate.swf.swcs
>   
>   
>   
>   
>   org.apache.royale.framework
>   Core
>   0.9.7-SNAPSHOT
>   swc
>   swf
>   
>   
>   
>
> (the above approach works locally for me just using the maven profile
> itself, if I make the changes to all framework modules, but as I said I
> could be missing something in relation to the issue that is being
> addressed)
>
>
> On Sun, Oct 6, 2019 at 11:20 PM Greg Dove  wrote:
>
> > Hi Piotr, I will check that in the morning local time... in about 8
> hours.
> >
> > On Sun, 6 Oct 2019, 21:54 Piotr Zarzycki,  >
> > wrote:
> >
> >> Hi Greg,
> >>
> >> I run into merge conflict during merge release branch to develop
> into file
> >> which you have changed lately. Could you please verify on develop
> if I
> >> didn't remove anything, if I resolve conflict correctly. [1]
> >>
> >> [1]
> >>
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-compiler%2Fblob%2Fdevelop%2Fcompiler-jx%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Froyale%2Fcompiler%2Finternal%2Fcodegen%2Fjs%2Fjx%2FMemberAccessEmitter.javadata=02%7C01%7Caharui%40adobe.com%7C8e7bf2601258466052f808d74ab7db82%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637060025834669854sdata=AdnP68Opu%2BA8bOMc34%2FsNR2ZXT6gAHRsio9NX758278%3Dreserved=0
> >>
> >> Thanks,
> >> Piotr
> >>
> >> śr., 2 paź 2019 o 11:06 Harbs  napisał(a):
> >>
> >> > OK.
> >> >
> >> > I’ll test memory with and without your changes and let you know
> the
> >> > differences. :-)
> >> >
> >> > Harbs
> >> >
> >> > > On Oct 2, 2019, at 11:29 AM, Greg Dove 
> wrote:
> >> > >
> >> > > @harbs
> >> > >
> >> > > FYI in addition to some other stuff, I am close to pushing my
> updates
> >> to
> >> > > XML. This should be in the next hour or so.
> >> > >
> >> > > I kept the QName caching pretty close to how you had it, with
> only
> >> some
> >> > > minor changes.
> >> > > I tried to do some extra memory optimization, and in theory it
> should
> >> > > provide better results, but to be honest I don't have a good
> way to
> >> > measure
> >> > > this in the browser. I tried the Chrome performance.memory
> extensions
> >> > but I
> >> > > don't have much confidence in that given how much it varies
> between
> >> > reloads
> >> > > without changing anything else. The extra code changes I made
> were to
> >> > make
> >> > > the '_nodeKind' strings into String object references, so they
> only
> >> refer
> >> > > to a single reference to a string instead of multiple copies of
> >> > primitives.
> >> > > That change is isolated to a single 

Re: Heads up on XML

2019-10-06 Thread Alex Harui
Improvements to the Maven builds and Ant builds are always welcome.  Just make 
sure they work from a truly clean machine (empty the local Maven repo, build 
without access to the snapshots repo, etc).

There are some issues with profile inheritance in Maven, but I don't understand 
your proposal enough to know if there is some hole in it.  Try it and find out.

-Alex

On 10/6/19, 4:49 PM, "Greg Dove"  wrote:

Hi Piotr, just a quick follow-up to let you know that was all good, I had
already tested the merge and conflict resolution myself and was ready to
step in and help with that if that was necessary, but you already did it
before I got a chance to send my email about that. :)

I have to say: well done for getting through the release process. I could
sense your frustration at times, and I know it must have seemed like it
took far too long, but I am sure you have made a huge difference for the
future in terms of that process.


also fyi, I had to use -Dgenerate.swf.swcs=true in my local maven build
today, and I was vaguely aware of discussions about this during release
prep.
But I wonder if this is necessary. Can't we just use the top level profiles
at the lower levels instead of creating new profiles? There's probably a
gap in my understanding of why this was necessary, but I would have
expected that we could simply use something like:


generate-swcs-for-swf


org.apache.royale.framework
Core
0.9.7-SNAPSHOT
swc
swf




in the framework modules, instead of:

  
  swf-dependencies
  
  
  generate.swf.swcs
  
  
  
  
  org.apache.royale.framework
  Core
  0.9.7-SNAPSHOT
  swc
  swf
  
  
  

(the above approach works locally for me just using the maven profile
itself, if I make the changes to all framework modules, but as I said I
could be missing something in relation to the issue that is being addressed)


On Sun, Oct 6, 2019 at 11:20 PM Greg Dove  wrote:

> Hi Piotr, I will check that in the morning local time... in about 8 hours.
>
> On Sun, 6 Oct 2019, 21:54 Piotr Zarzycki, 
> wrote:
>
>> Hi Greg,
>>
>> I run into merge conflict during merge release branch to develop into 
file
>> which you have changed lately. Could you please verify on develop if I
>> didn't remove anything, if I resolve conflict correctly. [1]
>>
>> [1]
>>
>> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-compiler%2Fblob%2Fdevelop%2Fcompiler-jx%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Froyale%2Fcompiler%2Finternal%2Fcodegen%2Fjs%2Fjx%2FMemberAccessEmitter.javadata=02%7C01%7Caharui%40adobe.com%7C8e7bf2601258466052f808d74ab7db82%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637060025834669854sdata=AdnP68Opu%2BA8bOMc34%2FsNR2ZXT6gAHRsio9NX758278%3Dreserved=0
>>
>> Thanks,
>> Piotr
>>
>> śr., 2 paź 2019 o 11:06 Harbs  napisał(a):
>>
>> > OK.
>> >
>> > I’ll test memory with and without your changes and let you know the
>> > differences. :-)
>> >
>> > Harbs
>> >
>> > > On Oct 2, 2019, at 11:29 AM, Greg Dove  wrote:
>> > >
>> > > @harbs
>> > >
>> > > FYI in addition to some other stuff, I am close to pushing my updates
>> to
>> > > XML. This should be in the next hour or so.
>> > >
>> > > I kept the QName caching pretty close to how you had it, with only
>> some
>> > > minor changes.
>> > > I tried to do some extra memory optimization, and in theory it should
>> > > provide better results, but to be honest I don't have a good way to
>> > measure
>> > > this in the browser. I tried the Chrome performance.memory extensions
>> > but I
>> > > don't have much confidence in that given how much it varies between
>> > reloads
>> > > without changing anything else. The extra code changes I made were to
>> > make
>> > > the '_nodeKind' strings into String object references, so they only
>> refer
>> > > to a single reference to a string instead of multiple copies of
>> > primitives.
>> > > That change is isolated to a single commit so can easily be reversed
>> if
>> > > there is something not good about it... but all my local tests
>> continue
>> > to
>> > > pass. I will get the new tests into RoyaleUnit in the coming days.
>> > >
>> > >
>> > >
>> > >
>> > > On Thu, Sep 5, 2019 at 7:39 AM Greg Dove  wrote:
 

Re: Heads up on XML

2019-10-06 Thread Greg Dove
Hi Piotr, just a quick follow-up to let you know that was all good, I had
already tested the merge and conflict resolution myself and was ready to
step in and help with that if that was necessary, but you already did it
before I got a chance to send my email about that. :)

I have to say: well done for getting through the release process. I could
sense your frustration at times, and I know it must have seemed like it
took far too long, but I am sure you have made a huge difference for the
future in terms of that process.


also fyi, I had to use -Dgenerate.swf.swcs=true in my local maven build
today, and I was vaguely aware of discussions about this during release
prep.
But I wonder if this is necessary. Can't we just use the top level profiles
at the lower levels instead of creating new profiles? There's probably a
gap in my understanding of why this was necessary, but I would have
expected that we could simply use something like:


generate-swcs-for-swf


org.apache.royale.framework
Core
0.9.7-SNAPSHOT
swc
swf




in the framework modules, instead of:

  
  swf-dependencies
  
  
  generate.swf.swcs
  
  
  
  
  org.apache.royale.framework
  Core
  0.9.7-SNAPSHOT
  swc
  swf
  
  
  

(the above approach works locally for me just using the maven profile
itself, if I make the changes to all framework modules, but as I said I
could be missing something in relation to the issue that is being addressed)


On Sun, Oct 6, 2019 at 11:20 PM Greg Dove  wrote:

> Hi Piotr, I will check that in the morning local time... in about 8 hours.
>
> On Sun, 6 Oct 2019, 21:54 Piotr Zarzycki, 
> wrote:
>
>> Hi Greg,
>>
>> I run into merge conflict during merge release branch to develop into file
>> which you have changed lately. Could you please verify on develop if I
>> didn't remove anything, if I resolve conflict correctly. [1]
>>
>> [1]
>>
>> https://github.com/apache/royale-compiler/blob/develop/compiler-jx/src/main/java/org/apache/royale/compiler/internal/codegen/js/jx/MemberAccessEmitter.java
>>
>> Thanks,
>> Piotr
>>
>> śr., 2 paź 2019 o 11:06 Harbs  napisał(a):
>>
>> > OK.
>> >
>> > I’ll test memory with and without your changes and let you know the
>> > differences. :-)
>> >
>> > Harbs
>> >
>> > > On Oct 2, 2019, at 11:29 AM, Greg Dove  wrote:
>> > >
>> > > @harbs
>> > >
>> > > FYI in addition to some other stuff, I am close to pushing my updates
>> to
>> > > XML. This should be in the next hour or so.
>> > >
>> > > I kept the QName caching pretty close to how you had it, with only
>> some
>> > > minor changes.
>> > > I tried to do some extra memory optimization, and in theory it should
>> > > provide better results, but to be honest I don't have a good way to
>> > measure
>> > > this in the browser. I tried the Chrome performance.memory extensions
>> > but I
>> > > don't have much confidence in that given how much it varies between
>> > reloads
>> > > without changing anything else. The extra code changes I made were to
>> > make
>> > > the '_nodeKind' strings into String object references, so they only
>> refer
>> > > to a single reference to a string instead of multiple copies of
>> > primitives.
>> > > That change is isolated to a single commit so can easily be reversed
>> if
>> > > there is something not good about it... but all my local tests
>> continue
>> > to
>> > > pass. I will get the new tests into RoyaleUnit in the coming days.
>> > >
>> > >
>> > >
>> > >
>> > > On Thu, Sep 5, 2019 at 7:39 AM Greg Dove  wrote:
>> > >
>> > >> Yeah, I saw that ;) Don't worry, I am aware of it.
>> > >>
>> > >> My first goal is to make sure it works like it should, because that
>> > comes
>> > >> first, and then to optimize. I'll check the memory side of things and
>> > make
>> > >> sure it's at least the same as before. If you can point me to some
>> > >> publicly accessible large test cases that would be really helpful. I
>> > will
>> > >> work through that before I push anything.
>> > >>
>> > >> On Thu, Sep 5, 2019 at 7:26 AM Harbs  wrote:
>> > >>
>> > >>> Heads up:
>> > >>>
>> > >>> I did some (on first blush) odd things in XML related to QNames.
>> QNames
>> > >>> are pooled and many XML properties are not initialized by default.
>> The
>> > >>> reason I did this was it avoided many MB of memory waste for complex
>> > XML.
>> > >>> Please don’t mess that up.
>> > >>>
>> > >>> Thanks,
>> > >>> Harbs
>> > >>>
>> >  On Sep 4, 2019, at 1:02 PM, Greg Dove  wrote:
>> > 
>> >  This is particularly for Harbs and Yishay, as I think you are both
>> (or
>> > >>> both
>> >  have been) using XML quite a bit. I have quite a few  fixes coming.
>> > All
>> >  with tests that match on swf 

Build failed in Jenkins: royale-asjs_jsonly #3648

2019-10-06 Thread Apache Royale CI Server
works>
 [echo] doc_output = 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/asdoc-output>
 [echo] compiler.source-path = 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/projects/*/src/main/royale>

clean:

super-clean:

create-description:
 [echo] build.number is 20191006

js-output-royale-description:

swf-js-output-royale-description:

create-config:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks>

tweak-for-jsonly:

tweak-for-jsonly:

BUILD FAILED
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/build.xml>:441:
 The following error occurred while executing this line:
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/build.xml>:1061:
 Warning: Could not find file 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/js/libs/js.swc>
 to copy.

Total time: 4 seconds
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g 
Build step 'Invoke Ant' marked build as failure
Archiving artifacts


New apache-royale questions for Oct 6 - Stack Exchange

2019-10-06 Thread Stack Exchange
***1 new question in [ApacheRoyale Tag Notifications 
filter]()
 on stackexchange.com***


[DropDownList giving an error: this.view is 
undefined]()

Main File: j:Application xmlns:fx="http://ns.adobe.com/mxml/2009; 
xmlns:local="*" xmlns:models="models.*" ...

Tagged: apache-royale

by [Bash]() on 






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

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

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

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



Build failed in Jenkins: royale-asjs_jsonly #3647

2019-10-06 Thread Apache Royale CI Server
dapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/TextJS/TextJS.swc.properties>

check-for-tests:

clean-tests:
 [echo] swc-date is 10/06/19 12:14 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/TLFJS/TLFJS.swc.properties>

clean:
 [echo] swc-date is 10/06/19 12:14 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/TLFJS/TLFJS.swc.properties>

check-for-tests:

clean-tests:
 [echo] swc-date is 10/06/19 12:14 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/XMLJS/XMLJS.swc.properties>

clean:
 [echo] swc-date is 10/06/19 12:14 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/XMLJS/XMLJS.swc.properties>

check-for-tests:

clean-tests:

clean:
 [echo] swc-date is 10/06/19 12:14 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/IconsJS/IconsJS.swc.properties>

clean:
 [echo] swc-date is 10/06/19 12:14 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/IconsJS/IconsJS.swc.properties>

check-for-tests:

clean-tests:
 [echo] swc-date is 10/06/19 12:14 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/JewelJS/JewelJS.swc.properties>

clean:
 [echo] swc-date is 10/06/19 12:14 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/JewelJS/JewelJS.swc.properties>

check-for-tests:

clean-tests:
 [echo] swc-date is 10/06/19 12:14 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/MXRoyaleJS/MXRoyaleJS.swc.properties>

clean:
 [echo] swc-date is 10/06/19 12:14 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/MXRoyaleJS/MXRoyaleJS.swc.properties>

check-for-tests:

clean-tests:
 [echo] swc-date is 10/06/19 12:14 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/CruxJS/CruxJS.swc.properties>

clean:
 [echo] swc-date is 10/06/19 12:14 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/CruxJS/CruxJS.swc.properties>

check-for-tests:

clean-tests:
 [echo] swc-date is 10/06/19 12:14 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/SparkRoyaleJS/SparkRoyaleJS.swc.properties>

clean:
 [echo] swc-date is 10/06/19 12:14 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/SparkRoyaleJS/SparkRoyaleJS.swc.properties>

check-for-tests:

clean-tests:
 [echo] swc-date is 10/06/19 12:14 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/AceJS/AceJS.swc.properties>

clean:
 [echo] swc-date is 10/06/19 12:14 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/AceJS/AceJS.swc.properties>

check-for-tests:

clean-tests:
 [echo] swc-date is 10/06/19 12:14 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/RoyaleSiteJS/RoyaleSiteJS.swc.properties>

clean:
 [echo] swc-date is 10/06/19 12:14 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/RoyaleSiteJS/RoyaleSiteJS.swc.properties>

check-for-tests:

clean-tests:

package-clean:

clean-temp:

checkintests-clean:

mxtests-clean:

clean:
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/royale-sdk-description.xml>
 [echo] ROYALE_HOME = 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/>
 [echo] royalelib = 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks>
 [echo] doc_output = 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/asdoc-output>
 [echo] compiler.source-path = 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs

Build failed in Jenkins: royale-asjs_jsonly #3646

2019-10-06 Thread Apache Royale CI Server
cho] swc-date is 10/06/19 10:40 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/TextJS/TextJS.swc.properties>

check-for-tests:

clean-tests:
 [echo] swc-date is 10/06/19 10:40 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/TLFJS/TLFJS.swc.properties>

clean:
 [echo] swc-date is 10/06/19 10:40 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/TLFJS/TLFJS.swc.properties>

check-for-tests:

clean-tests:
 [echo] swc-date is 10/06/19 10:40 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/XMLJS/XMLJS.swc.properties>

clean:
 [echo] swc-date is 10/06/19 10:40 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/XMLJS/XMLJS.swc.properties>

check-for-tests:

clean-tests:

clean:
 [echo] swc-date is 10/06/19 10:40 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/IconsJS/IconsJS.swc.properties>

clean:
 [echo] swc-date is 10/06/19 10:40 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/IconsJS/IconsJS.swc.properties>

check-for-tests:

clean-tests:
 [echo] swc-date is 10/06/19 10:40 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/JewelJS/JewelJS.swc.properties>

clean:
 [echo] swc-date is 10/06/19 10:40 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/JewelJS/JewelJS.swc.properties>

check-for-tests:

clean-tests:
 [echo] swc-date is 10/06/19 10:40 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/MXRoyaleJS/MXRoyaleJS.swc.properties>

clean:
 [echo] swc-date is 10/06/19 10:40 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/MXRoyaleJS/MXRoyaleJS.swc.properties>

check-for-tests:

clean-tests:
 [echo] swc-date is 10/06/19 10:40 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/CruxJS/CruxJS.swc.properties>

clean:
 [echo] swc-date is 10/06/19 10:40 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/CruxJS/CruxJS.swc.properties>

check-for-tests:

clean-tests:
 [echo] swc-date is 10/06/19 10:40 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/SparkRoyaleJS/SparkRoyaleJS.swc.properties>

clean:
 [echo] swc-date is 10/06/19 10:40 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/SparkRoyaleJS/SparkRoyaleJS.swc.properties>

check-for-tests:

clean-tests:
 [echo] swc-date is 10/06/19 10:40 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/AceJS/AceJS.swc.properties>

clean:
 [echo] swc-date is 10/06/19 10:40 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/AceJS/AceJS.swc.properties>

check-for-tests:

clean-tests:
 [echo] swc-date is 10/06/19 10:40 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/RoyaleSiteJS/RoyaleSiteJS.swc.properties>

clean:
 [echo] swc-date is 10/06/19 10:40 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/RoyaleSiteJS/RoyaleSiteJS.swc.properties>

check-for-tests:

clean-tests:

package-clean:

clean-temp:

checkintests-clean:

mxtests-clean:

clean:
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/royale-sdk-description.xml>
 [echo] ROYALE_HOME = 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/>
 [echo] royalelib = 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks>
 [echo] doc_output = 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/asdoc-output>
 [echo

Re: Heads up on XML

2019-10-06 Thread Greg Dove
Hi Piotr, I will check that in the morning local time... in about 8 hours.

On Sun, 6 Oct 2019, 21:54 Piotr Zarzycki,  wrote:

> Hi Greg,
>
> I run into merge conflict during merge release branch to develop into file
> which you have changed lately. Could you please verify on develop if I
> didn't remove anything, if I resolve conflict correctly. [1]
>
> [1]
>
> https://github.com/apache/royale-compiler/blob/develop/compiler-jx/src/main/java/org/apache/royale/compiler/internal/codegen/js/jx/MemberAccessEmitter.java
>
> Thanks,
> Piotr
>
> śr., 2 paź 2019 o 11:06 Harbs  napisał(a):
>
> > OK.
> >
> > I’ll test memory with and without your changes and let you know the
> > differences. :-)
> >
> > Harbs
> >
> > > On Oct 2, 2019, at 11:29 AM, Greg Dove  wrote:
> > >
> > > @harbs
> > >
> > > FYI in addition to some other stuff, I am close to pushing my updates
> to
> > > XML. This should be in the next hour or so.
> > >
> > > I kept the QName caching pretty close to how you had it, with only some
> > > minor changes.
> > > I tried to do some extra memory optimization, and in theory it should
> > > provide better results, but to be honest I don't have a good way to
> > measure
> > > this in the browser. I tried the Chrome performance.memory extensions
> > but I
> > > don't have much confidence in that given how much it varies between
> > reloads
> > > without changing anything else. The extra code changes I made were to
> > make
> > > the '_nodeKind' strings into String object references, so they only
> refer
> > > to a single reference to a string instead of multiple copies of
> > primitives.
> > > That change is isolated to a single commit so can easily be reversed if
> > > there is something not good about it... but all my local tests continue
> > to
> > > pass. I will get the new tests into RoyaleUnit in the coming days.
> > >
> > >
> > >
> > >
> > > On Thu, Sep 5, 2019 at 7:39 AM Greg Dove  wrote:
> > >
> > >> Yeah, I saw that ;) Don't worry, I am aware of it.
> > >>
> > >> My first goal is to make sure it works like it should, because that
> > comes
> > >> first, and then to optimize. I'll check the memory side of things and
> > make
> > >> sure it's at least the same as before. If you can point me to some
> > >> publicly accessible large test cases that would be really helpful. I
> > will
> > >> work through that before I push anything.
> > >>
> > >> On Thu, Sep 5, 2019 at 7:26 AM Harbs  wrote:
> > >>
> > >>> Heads up:
> > >>>
> > >>> I did some (on first blush) odd things in XML related to QNames.
> QNames
> > >>> are pooled and many XML properties are not initialized by default.
> The
> > >>> reason I did this was it avoided many MB of memory waste for complex
> > XML.
> > >>> Please don’t mess that up.
> > >>>
> > >>> Thanks,
> > >>> Harbs
> > >>>
> >  On Sep 4, 2019, at 1:02 PM, Greg Dove  wrote:
> > 
> >  This is particularly for Harbs and Yishay, as I think you are both
> (or
> > >>> both
> >  have been) using XML quite a bit. I have quite a few  fixes coming.
> > All
> >  with tests that match on swf and js.
> > 
> >  I am currently working to demonstrate proof of concept to a
> > prospective
> >  client for migration of a Flex app. The app makes extensive use of
> e4x
> > >>> and
> >  uses a bunch of features that I expect had not received attention
> >  previously, because they were originally either not working with the
> >  codebase I am porting, or i think some even caused errors in the
> > >>> javascript
> >  output.
> > 
> >  So I have spent the last several days almost full time figuring
> things
> > >>> out
> >  and working on fixes, between the compiler and emulation classes.
> >  All the previous XML tests continue to pass, but I have many more
> unit
> >  tests and fixes lined up for the following:
> > 
> >  namespace directives
> >  default xml namespace
> >  use namespace (multiple)
> > 
> >  a number of fixes for xml filtering, including:
> >  -'this' resolves correctly in filters that include external
> references
> > >>> from
> >  the fitler expression to the 'this' scope
> >  -handles alternate ordering of comparisons between XML 'getters' and
> >  literals
> >  e.g. something.(name() = "cat")  or something.("cat" = name())
> (these
> > >>> are
> >  the same)
> >  -it (will) now handle XML e4x references in nested function calls
> > inside
> >  the filter, e.g. things like:
> >  e.g.
> >  var people:XML = 
> >    
> >    Bob
> >    32
> >    
> >    
> >    Joe
> >    46
> >    
> >    ;
> >  var findJoeByAge:Function = function (i:int):Boolean {
> >    return i > 40;
> >    };
> >  people.person.(findJoeByAge(parseInt(age))).name
> > 
> > 
> >  I 

[DRAFT][ANNOUNCE] Apache Royale 0.9.6 released!

2019-10-06 Thread Piotr Zarzycki
Hi Guys,

Below draft of our announcement. I made also draft of the release on
GitHub. [1] I will wait 48h before I send it to announce. I think there is
one more place where I need to update in whimsy - can someone remember me
where it was ?

---
The Apache Royale community is pleased to announce the release of Apache
Royale 0.9.6.

The Apache Royale project is developing a next-generation of the Apache
Flex SDK. Royale has the goal of allowing applications developed in MXML
and ActionScript to not only run in the Flash/AIR runtimes, but also to run
natively in the browser without Flash, on mobile devices as a
PhoneGap/Cordova application, and in embedded JS environments such as
Chromium Embedded Framework. Royale has the potential to allow your MXML
and ActionScript code to run in even more places than Flash currently does.

This release should be considered ‘beta' quality. The purpose of this
release is to gather feedback about the features and implementation
strategies, and to recruit new contributors. We hope to grow the code base
into an SDK and tool chain that delivers the highest productivity when
developing applications that can run on many platforms. Beta releases may
not handle production needs.

Please file bugs at:

https://github.com/apache/royale-asjs/issues

If you happen to know it is a compiler issue, please use:

https://github.com/apache/royale-compiler/issues

For questions about how to use Royale, send email to us...@royale.apache.org.
For questions and feedback on the development of the source code in the
release, send email to dev@royale.apache.org.

Apache Royale is available in source and binary form from the Apache
mirrors:

Source:
http://www.apache.org/dyn/closer.lua/royale/0.9.6/apache-royale-0.9.6-src.tar.gz

http://www.apache.org/dyn/closer.lua/royale/0.9.6/apache-royale-0.9.6-src.zip

Binary:
http://www.apache.org/dyn/closer.lua/royale/0.9.6/binaries/apache-royale-0.9.6-bin-js.tar.gz
http://www.apache.org/dyn/closer.lua/royale/0.9.6/binaries/apache-royale-0.9.6-bin-js.zip

Binary with SWF support:
http://www.apache.org/dyn/closer.lua/royale/0.9.6/binaries/apache-royale-0.9.6-bin-js-swf.tar.gz
http://www.apache.org/dyn/closer.lua/royale/0.9.6/binaries/apache-royale-0.9.6-bin-js-swf.zip

When downloading from a mirror site, please remember to verify the
downloads using signatures or MD5 hashes.

The binary packages can also be installed via NPM.

Mac:

  sudo npm install @apache-royale/royale-js -g

Or for SWF Support:

  sudo npm install @apache-royale/royale-js-swf -g

Windows:

  npm install @apache-royale/royale-js -g

Or for SWF Support:

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


See the README for more information. The language reference (ASDoc) is here:

  http://royale.apache.org/asdoc/

Additional documentation is here:

  https://apache.github.io/royale-docs/

The documentation is still a work in progress.  Volunteers are welcome to
help improve it. Visit http://royale.apache.org/ for links to other
resources.

Please try Royale and become involved in shaping the future of application
development.

The Apache Royale Community
---

[1]
https://github.com/apache/royale-asjs/releases/tag/untagged-279226b72126eeb56c78

Thanks,
-- 

Piotr Zarzycki

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


Build failed in Jenkins: royale-asjs_jsonly #3644

2019-10-06 Thread Apache Royale CI Server
dapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/TextJS/TextJS.swc.properties>

check-for-tests:

clean-tests:
 [echo] swc-date is 10/06/19 08:56 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/TLFJS/TLFJS.swc.properties>

clean:
 [echo] swc-date is 10/06/19 08:56 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/TLFJS/TLFJS.swc.properties>

check-for-tests:

clean-tests:
 [echo] swc-date is 10/06/19 08:56 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/XMLJS/XMLJS.swc.properties>

clean:
 [echo] swc-date is 10/06/19 08:56 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/XMLJS/XMLJS.swc.properties>

check-for-tests:

clean-tests:

clean:
 [echo] swc-date is 10/06/19 08:56 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/IconsJS/IconsJS.swc.properties>

clean:
 [echo] swc-date is 10/06/19 08:56 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/IconsJS/IconsJS.swc.properties>

check-for-tests:

clean-tests:
 [echo] swc-date is 10/06/19 08:56 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/JewelJS/JewelJS.swc.properties>

clean:
 [echo] swc-date is 10/06/19 08:56 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/JewelJS/JewelJS.swc.properties>

check-for-tests:

clean-tests:
 [echo] swc-date is 10/06/19 08:56 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/MXRoyaleJS/MXRoyaleJS.swc.properties>

clean:
 [echo] swc-date is 10/06/19 08:56 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/MXRoyaleJS/MXRoyaleJS.swc.properties>

check-for-tests:

clean-tests:
 [echo] swc-date is 10/06/19 08:56 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/CruxJS/CruxJS.swc.properties>

clean:
 [echo] swc-date is 10/06/19 08:56 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/CruxJS/CruxJS.swc.properties>

check-for-tests:

clean-tests:
 [echo] swc-date is 10/06/19 08:56 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/SparkRoyaleJS/SparkRoyaleJS.swc.properties>

clean:
 [echo] swc-date is 10/06/19 08:56 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/SparkRoyaleJS/SparkRoyaleJS.swc.properties>

check-for-tests:

clean-tests:
 [echo] swc-date is 10/06/19 08:56 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/AceJS/AceJS.swc.properties>

clean:
 [echo] swc-date is 10/06/19 08:56 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/AceJS/AceJS.swc.properties>

check-for-tests:

clean-tests:
 [echo] swc-date is 10/06/19 08:56 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/RoyaleSiteJS/RoyaleSiteJS.swc.properties>

clean:
 [echo] swc-date is 10/06/19 08:56 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/RoyaleSiteJS/RoyaleSiteJS.swc.properties>

check-for-tests:

clean-tests:

package-clean:

clean-temp:

checkintests-clean:

mxtests-clean:

clean:
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/royale-sdk-description.xml>
 [echo] ROYALE_HOME = 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/>
 [echo] royalelib = 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks>
 [echo] doc_output = 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/asdoc-output>
 [echo] compiler.source-path = 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs

Build failed in Jenkins: royale-asjs_jsonly #3645

2019-10-06 Thread Apache Royale CI Server
dapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/TextJS/TextJS.swc.properties>

check-for-tests:

clean-tests:
 [echo] swc-date is 10/06/19 08:57 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/TLFJS/TLFJS.swc.properties>

clean:
 [echo] swc-date is 10/06/19 08:57 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/TLFJS/TLFJS.swc.properties>

check-for-tests:

clean-tests:
 [echo] swc-date is 10/06/19 08:57 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/XMLJS/XMLJS.swc.properties>

clean:
 [echo] swc-date is 10/06/19 08:57 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/XMLJS/XMLJS.swc.properties>

check-for-tests:

clean-tests:

clean:
 [echo] swc-date is 10/06/19 08:57 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/IconsJS/IconsJS.swc.properties>

clean:
 [echo] swc-date is 10/06/19 08:57 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/IconsJS/IconsJS.swc.properties>

check-for-tests:

clean-tests:
 [echo] swc-date is 10/06/19 08:57 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/JewelJS/JewelJS.swc.properties>

clean:
 [echo] swc-date is 10/06/19 08:57 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/JewelJS/JewelJS.swc.properties>

check-for-tests:

clean-tests:
 [echo] swc-date is 10/06/19 08:57 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/MXRoyaleJS/MXRoyaleJS.swc.properties>

clean:
 [echo] swc-date is 10/06/19 08:57 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/MXRoyaleJS/MXRoyaleJS.swc.properties>

check-for-tests:

clean-tests:
 [echo] swc-date is 10/06/19 08:57 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/CruxJS/CruxJS.swc.properties>

clean:
 [echo] swc-date is 10/06/19 08:57 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/CruxJS/CruxJS.swc.properties>

check-for-tests:

clean-tests:
 [echo] swc-date is 10/06/19 08:57 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/SparkRoyaleJS/SparkRoyaleJS.swc.properties>

clean:
 [echo] swc-date is 10/06/19 08:57 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/SparkRoyaleJS/SparkRoyaleJS.swc.properties>

check-for-tests:

clean-tests:
 [echo] swc-date is 10/06/19 08:57 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/AceJS/AceJS.swc.properties>

clean:
 [echo] swc-date is 10/06/19 08:57 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/AceJS/AceJS.swc.properties>

check-for-tests:

clean-tests:
 [echo] swc-date is 10/06/19 08:57 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/RoyaleSiteJS/RoyaleSiteJS.swc.properties>

clean:
 [echo] swc-date is 10/06/19 08:57 +
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/RoyaleSiteJS/RoyaleSiteJS.swc.properties>

check-for-tests:

clean-tests:

package-clean:

clean-temp:

checkintests-clean:

mxtests-clean:

clean:
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/royale-sdk-description.xml>
 [echo] ROYALE_HOME = 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/>
 [echo] royalelib = 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks>
 [echo] doc_output = 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/asdoc-output>
 [echo] compiler.source-path = 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs

Build failed in Jenkins: royale-asjs_jsonly #3643

2019-10-06 Thread Apache Royale CI Server
fig.xml>
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/macfonts.ser>
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/winfonts.ser>
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/localfonts.ser>
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/mxml-manifest.xml>
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/spark-manifest.xml>
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/ide/flashbuilder/flashbuilder-config.xml>

create-description:
 [echo] build.number is 20191006

js-output-royale-description:

swf-js-output-royale-description:

create-config:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks>

tweak-for-jsonly:

tweak-for-jsonly:

BUILD FAILED
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/build.xml>:441:
 The following error occurred while executing this line:
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/build.xml>:1061:
 Warning: Could not find file 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/js/libs/js.swc>
 to copy.

Total time: 24 seconds
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g 
Build step 'Invoke Ant' marked build as failure
Archiving artifacts


Re: Heads up on XML

2019-10-06 Thread Piotr Zarzycki
Hi Greg,

I run into merge conflict during merge release branch to develop into file
which you have changed lately. Could you please verify on develop if I
didn't remove anything, if I resolve conflict correctly. [1]

[1]
https://github.com/apache/royale-compiler/blob/develop/compiler-jx/src/main/java/org/apache/royale/compiler/internal/codegen/js/jx/MemberAccessEmitter.java

Thanks,
Piotr

śr., 2 paź 2019 o 11:06 Harbs  napisał(a):

> OK.
>
> I’ll test memory with and without your changes and let you know the
> differences. :-)
>
> Harbs
>
> > On Oct 2, 2019, at 11:29 AM, Greg Dove  wrote:
> >
> > @harbs
> >
> > FYI in addition to some other stuff, I am close to pushing my updates to
> > XML. This should be in the next hour or so.
> >
> > I kept the QName caching pretty close to how you had it, with only some
> > minor changes.
> > I tried to do some extra memory optimization, and in theory it should
> > provide better results, but to be honest I don't have a good way to
> measure
> > this in the browser. I tried the Chrome performance.memory extensions
> but I
> > don't have much confidence in that given how much it varies between
> reloads
> > without changing anything else. The extra code changes I made were to
> make
> > the '_nodeKind' strings into String object references, so they only refer
> > to a single reference to a string instead of multiple copies of
> primitives.
> > That change is isolated to a single commit so can easily be reversed if
> > there is something not good about it... but all my local tests continue
> to
> > pass. I will get the new tests into RoyaleUnit in the coming days.
> >
> >
> >
> >
> > On Thu, Sep 5, 2019 at 7:39 AM Greg Dove  wrote:
> >
> >> Yeah, I saw that ;) Don't worry, I am aware of it.
> >>
> >> My first goal is to make sure it works like it should, because that
> comes
> >> first, and then to optimize. I'll check the memory side of things and
> make
> >> sure it's at least the same as before. If you can point me to some
> >> publicly accessible large test cases that would be really helpful. I
> will
> >> work through that before I push anything.
> >>
> >> On Thu, Sep 5, 2019 at 7:26 AM Harbs  wrote:
> >>
> >>> Heads up:
> >>>
> >>> I did some (on first blush) odd things in XML related to QNames. QNames
> >>> are pooled and many XML properties are not initialized by default. The
> >>> reason I did this was it avoided many MB of memory waste for complex
> XML.
> >>> Please don’t mess that up.
> >>>
> >>> Thanks,
> >>> Harbs
> >>>
>  On Sep 4, 2019, at 1:02 PM, Greg Dove  wrote:
> 
>  This is particularly for Harbs and Yishay, as I think you are both (or
> >>> both
>  have been) using XML quite a bit. I have quite a few  fixes coming.
> All
>  with tests that match on swf and js.
> 
>  I am currently working to demonstrate proof of concept to a
> prospective
>  client for migration of a Flex app. The app makes extensive use of e4x
> >>> and
>  uses a bunch of features that I expect had not received attention
>  previously, because they were originally either not working with the
>  codebase I am porting, or i think some even caused errors in the
> >>> javascript
>  output.
> 
>  So I have spent the last several days almost full time figuring things
> >>> out
>  and working on fixes, between the compiler and emulation classes.
>  All the previous XML tests continue to pass, but I have many more unit
>  tests and fixes lined up for the following:
> 
>  namespace directives
>  default xml namespace
>  use namespace (multiple)
> 
>  a number of fixes for xml filtering, including:
>  -'this' resolves correctly in filters that include external references
> >>> from
>  the fitler expression to the 'this' scope
>  -handles alternate ordering of comparisons between XML 'getters' and
>  literals
>  e.g. something.(name() = "cat")  or something.("cat" = name()) (these
> >>> are
>  the same)
>  -it (will) now handle XML e4x references in nested function calls
> inside
>  the filter, e.g. things like:
>  e.g.
>  var people:XML = 
>    
>    Bob
>    32
>    
>    
>    Joe
>    46
>    
>    ;
>  var findJoeByAge:Function = function (i:int):Boolean {
>    return i > 40;
>    };
>  people.person.(findJoeByAge(parseInt(age))).name
> 
> 
>  I have lots more granular tests in QName, Namespace, and XML with
> >>> tuning to
>  improve reliability.
>  toXMLString XML node output also matches flash more correctly in what
> I
>  have coming.
> 
>  One thing that I am trying to figure out, which I would appreciate
> >>> input on
>  if someone has an answer:
>  For the example:
> 
>  var feed:XML = new XML(
>   

Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-10-06 Thread Piotr Zarzycki
Hi Alex,

Thank you for the fix. Everything worked fine this time.

Piotr

sob., 5 paź 2019 o 01:51 Alex Harui  napisał(a):

> I found some time to try the releasecandidate.xml and found the problem.
> I pushed the fix to release/0.9.6.  So try that and see what happens.  It
> seemed to do the right thing for me on my Windows computer.
>
> You will next likely run into several merge conflicts.  I have not looked
> into the conflicts, but there is a good chance that some of that is due to
> the cherry-picking.  I am going to start a separate thread about branch
> management.
>
> -Alex
>
> On 10/4/19, 10:55 AM, "Alex Harui"  wrote:
>
> If we don't fix the release scripts, then the next RM is probably
> going to run into the same problem.  The time we spend now helps save time
> in the future.  It is wise to improve the process now in case I get run
> over by a bus tomorrow.  If you do it manually and make a mistake, we might
> not catch it until later or cause more problems.
>
> IIRC, the Poms should not require changing.  Maven should have done
> that already.
>
> All the places I know of changing are in the script.
>
> -Alex
>
> On 10/4/19, 10:46 AM, "Piotr Zarzycki" 
> wrote:
>
> Alex,
>
> Can I just do that changes manually on release branch and merge
> stuff to
> develop?
>
> I just don't won't to spend any more minute on release process
> anymore.
>
> 1) I should change build properties
> 2) I should change all poms
>
> Is there anymore place which I should know to change?
>
> Thanks,
> Piotr
>
> On Fri, Oct 4, 2019, 7:41 PM Alex Harui 
> wrote:
>
> > Piotr,
> >
> > Again, I am asking you to get in the mindset of a developer and
> not just a
> > user.  You can see that the Ant script is making some updates.
> You can
> > verify that the release branch does not have 0.9.7 for the
> release.version
> > in build.properties.  You can see there is 1 commit pending in
> > royale-asjs.  You can see that the build.properties did get
> changed to have
> > release.version=0.9.7.
> >
> > So, you will have to investigate further.  What is in that
> commit?  Is
> > this output from a fresh start of cloning the repo or could that
> commit be
> > from a previous run?  How could Git change a file but not report
> it?  Maybe
> > add some  tags or use -verbose to get more output.  But
> just giving
> > me minimal information and waiting for me to guess as to what to
> do next is
> > not very efficient, IMO.
> >
> > Thanks,
> > -Alex
> >
> > On 10/4/19, 4:01 AM, "Piotr Zarzycki" 
> wrote:
> >
> > Hi Alex,
> >
> > Git status after failing for all 3 repos [1].
> >
> > Here is how build.properties look like after performing
> update.versions
> > target [2].
> >
> > I will skip some part to move forward but update.versions is
> important.
> >
> > [1]
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fl3zs9data=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010sdata=nvSDESjmBw5j%2FlBoaIPGTUiBKrkoXcAVGIyUV371eE8%3Dreserved=0
> > [2]
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F0zvoudata=02%7C01%7Caharui%40adobe.com%7C500bc3fa811d49d7fae908d748f40ca3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058085331719010sdata=ljQmwiJbtqsTIj3tx9%2FtKyy%2Bns5Sz7P%2BCQE3Knb%2F1fA%3Dreserved=0
> >
> > Thanks,
> > Piotr
> >
> > czw., 3 paź 2019 o 17:49 Alex Harui  >
> > napisał(a):
> >
> > > What does "git status" show in the 3 repos?
> > >
> > > The update.versions should have at least changed the
> > build.properties file
> > > in the repo.
> > >
> > > You can try skipping over steps by listing the steps on
> the command
> > line.
> > > You might need to list some pre-requisite steps before or
> add them
> > to the
> > > "depends" of the step that needs it.
> > >
> > > ant -e -f releasecandidate.xml -Drelease.version=0.9.6
> -Drc=3
> > > update.versions merge_rc_to_develop
> release.maven.staging.repo
> > >
> > > -Alex
> > >
> > > On 10/3/19, 1:49 AM, "Piotr Zarzycki" <
> piotrzarzyck...@gmail.com>
> > wrote:
> > >
> > > Those are the steps from the script which need to be
> done still:
> > >
> > > 1)  
> > > 2) 
> > > 3) 

Re: Nightly Build Server going offline

2019-10-06 Thread Harbs
Seems fine to me.

> On Oct 6, 2019, at 1:33 AM, Alex Harui  wrote:
> 
> I was only thinking about temporary distribution of the nightly build while 
> the CI server is offline.  I'm not sure it makes sense to always copy the 
> nightly build somewhere else.  I think the bandwidth would add up.
> 
> I'm mainly asking if anyone thinks it would be a problem if the nightly 
> builds were unavailable for a day (hopefully only a day).
> 
> -Alex
> 
> On 10/5/19, 6:41 AM, "Carlos Rovira"  > wrote:
> 
>Hi Alex,
> 
>you're talking about just storing nightly builds? what about using some
>free storage out there, like a google drive, dropbox, or other service like
>this. We can create an "apacheroyale" account and share credentials in
>private.
> 
>El sáb., 5 oct. 2019 a las 2:18, Alex Harui ()
>escribió:
> 
>> Hi,
>> 
>> To prove that we can rebuild our nightly build server (so that someone
>> else can host a build server someday and to prove we know what our
>> dependencies are), I'm going to try to rebuild it once the release branch
>> is merged into develop.  Could just take a day if I've saved a record of
>> everything we need.  Or not...
>> 
>> There will be other emails when I finally shut it down to try it.  If
>> someone wants to host the last nightly somewhere and update our links to
>> it, great, otherwise we'll just cross our fingers...
>> 
>> Thanks,
>> -Alex
>> 
>> 
> 
>-- 
>Carlos Rovira
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C7c275412ee1640742d6d08d74999bf61%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637058797001459149sdata=YKPzypxxtGprdoc3vB3n8MXGYL1Ds%2BU6n2vXgZ6cQcM%3Dreserved=0
>  
> 


Build failed in Jenkins: royale-asjs_MXTests #1220

2019-10-06 Thread Apache Royale CI Server
See 


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