RE: Discuss of release steps preparation

2019-09-04 Thread Yishay Weiss
> /Users/piotr/Downloads/royale/release/releaseasjs_ant/sources/royale-asjs/build.xml:1636: > > /Users/piotr/Downloads/royale/release/releaseasjs_ant/sources/royale-asjs/${env.ANT_HOME}/lib > does not exist. Is ANT_HOME env var defined? From: Piotr

Re: Discuss of release steps preparation

2019-09-04 Thread Piotr Zarzycki
I was able to produce ant artifacts on Mac! I will try get an RC1 today. śr., 4 wrz 2019 o 11:11 Yishay Weiss napisał(a): > Here’s what I’ve got. > > > > ANT_HOME > > C:\dev\ant\apache-ant-1.10.1 > > > > > From: Piotr Zarzycki > Sent: Wednesday, September 4,

Re: Discuss of release steps preparation

2019-09-04 Thread Piotr Zarzycki
Hi, It moved farther, but failed with different stacktrace [1]. I will try to investigate this, unless someone has immediate idea why I got that issue. [1] https://paste.apache.org/r48at Thanks, Piotr śr., 4 wrz 2019 o 07:36 Alex Harui napisał(a): > FWIW, my Mac has: > >

Re: Discuss of release steps preparation

2019-09-04 Thread Piotr Zarzycki
Hi Yishay, It was pretty stupid from my sight. I was certain that I have this env variable setup, cause ant is working for me. I have no idea how. Let me set it and see whether it help. Thanks, Piotr śr., 4 wrz 2019 o 10:37 Yishay Weiss napisał(a): > > >

RE: Discuss of release steps preparation

2019-09-04 Thread Yishay Weiss
Here’s what I’ve got. ANT_HOME C:\dev\ant\apache-ant-1.10.1 From: Piotr Zarzycki Sent: Wednesday, September 4, 2019 11:56:02 AM To: dev@royale.apache.org Subject: Re: Discuss of release steps preparation Hi Yishay, It was pretty stupid from my sight. I

Heads up on XML

2019-09-04 Thread Greg Dove
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

Re: Discuss of release steps preparation

2019-09-04 Thread Alex Harui
Again, the goal is here to debug the scripts, not to skip them. And it is hard to help without console output to examine. Yes, you have set the variables, but have the other steps run that generate an SVN working copy at that destination? Show the console output related to it. HTH, -Alex On

Re: Heads up on XML

2019-09-04 Thread Greg Dove
'Have you rummaged through the spec?' Yes, if anything I probably need to step away from it and experience the world a bit more! I have been focused on each portion of the spec as I create unit tests and verify things between the player and the Royale implementation. I've also glanced a few times

Re: Heads up on XML

2019-09-04 Thread Alex Harui
Don't know. Have you rummaged through the spec? https://www.ecma-international.org/publications/files/ECMA-ST-WITHDRAWN/Ecma-357.pdf HTH, -Alex On 9/4/19, 3:11 AM, "Greg Dove" wrote: This is particularly for Harbs and Yishay, as I think you are both (or both have been) using XML

Re: Discuss of release steps preparation

2019-09-04 Thread Piotr Zarzycki
Hi Alex, I know that is the goal, but I simply failed to meet those goals and I gave up on that. I have artifacts and I would like to release Royale - that's may goal, whether I do this in 90% automatically and 10% manually after so many hours of work it doesn't matter to me now. You are seeing

Re: Heads up on XML

2019-09-04 Thread Alex Harui
Speaking of multinames, what is the ABC code generated by the Flex compiler for the two cases? It might contain some clues. I would have expected both to return "1" and the node. But I did see in the spec the notion of "InScopeNamespaces". I generally hate reading specs like these so I am

Re: Discuss of release steps preparation

2019-09-04 Thread Piotr Zarzycki
>From that point I will probably upload artifacts manually and run RC1. śr., 4 wrz 2019 o 16:30 Piotr Zarzycki napisał(a): > It looks like I have another problems. Target for uploading ant artifacts > is failing: > > ant -f releasesteps_asjs.xml Release_Step_013_Upload > -Drelease.version=0.9.6

Re: Discuss of release steps preparation

2019-09-04 Thread Alex Harui
Piotr, Well, I can't tell you what to do, but if we want to encourage more frequent releases and more people volunteering to be the RM, at some point, somebody else besides me has to either create a rather complex step-by-step manual/runbook or help debug these scripts. I'm willing to help

Re: Heads up on XML

2019-09-04 Thread Greg Dove
Good idea. I'll check the swf output, although probably tomorrow as I need to focus on something else today. ' I would have expected both to return "1" and the node. ' In that example I would expect the opposite (because the the link node being returned by the second query is not in the

Build failed in Jenkins: royale-asjs_MXTests #1120

2019-09-04 Thread Apache Royale CI Server
See -- [...truncated 968.90 KB...] [mxmlc] scanning for overrides: SolidBorderUtil [mxmlc] scanning for overrides: StringTrimmer [mxmlc]

Re: Discuss of release steps preparation

2019-09-04 Thread Piotr Zarzycki
It looks like I have another problems. Target for uploading ant artifacts is failing: ant -f releasesteps_asjs.xml Release_Step_013_Upload -Drelease.version=0.9.6 -Drc=1 Buildfile: /Users/piotr/Downloads/royale/releasesteps_asjs.xml check-name-and-svn: [echo] Name: 'Piotr Zarzycki'

Re: Heads up on XML

2019-09-04 Thread Greg Dove
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

Re: Heads up on XML

2019-09-04 Thread Alex Harui
I read the example incorrectly. So yeah, it should return 0 and empty string in both cases, IMO. There might be some subtlety in how the namespaces are specified for a QName or how QName works in child(). HTH, -Alex On 9/4/19, 11:33 AM, "Greg Dove" wrote: Good idea. I'll check the swf

Re: Heads up on XML

2019-09-04 Thread Harbs
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

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

2019-09-04 Thread Apache Royale CI Server
See

Build failed in Jenkins: royale-asjs_MXTests #1121

2019-09-04 Thread Apache Royale CI Server
See -- [...truncated 967.68 KB...] [mxmlc] scanning for overrides: SolidBorderUtil [mxmlc] scanning for overrides: StringTrimmer [mxmlc]