Re: ${body} in index template

2019-09-06 Thread Carlos Rovira
Hi Greg, so the proposal is to end with: -body -application (used for standard Royale apps) -AppClassName (for Flex emulated apps that will have "_mx_managers_SystemManager" as part of the string. so this is really "{application}" + "_mx_managers_SystemManager") right? what do you think about

Re: Testing the npm install error fixes

2019-09-06 Thread Carlos Rovira
Hi, I'll try to see Om links as I have time. In the mean while here is the log: https://paste.apache.org/p/pomzf and dependencies.js https://paste.apache.org/p/6nu70 HTH Carlos El jue., 5 sept. 2019 a las 18:32, OmPrakash Muppirala (< bigosma...@apache.org>) escribió: > If you have to

Re: Discuss of release steps preparation

2019-09-06 Thread Piotr Zarzycki
Hi Alex, I would love to encourage more people to be RM, but unfortunately my time which I should spend on that release was exceeded at least double. I prefer make now manually commit than deal with it - I'm sorry about that. As for console output - you are saying that previous steps matters to t

Re: Discuss of release steps preparation

2019-09-06 Thread Carlos Rovira
Hi, maybe is not so bad to end this 0.9.6 manually, since there was many progress in that front. Does not need necessarily be "all or nothing". Or 100% success. Releasing now 0.9.6 can make lower the stress a bit and make a the 0.9.7 in few more weeks catch the final problems. As soon as we have t

[TEST2] Release Apache Royale 0.9.6 RC1

2019-09-06 Thread Apache Royale CI Server
This is the discussion thread. Thanks, Piotr Zarzycki

[TEST] Release Apache Royale 0.9.6 RC1

2019-09-06 Thread Apache Royale CI Server
Hi, This is the vote for the 0.9.6 release of Apache Royale. The release candidate can be found here; https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc1/ Before voting please review the section,'What are the ASF requirements on approving a release?', at: http://www.apache.org/dev/release.ht

[VOTE] Release Apache Royale 0.9.6 RC1

2019-09-06 Thread Apache Royale CI Server
Hi, This is the vote for the 0.9.6 release of Apache Royale. The release candidate can be found here; https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc1/ Before voting please review the section,'What are the ASF requirements on approving a release?', at: http://www.apache.org/dev/release.ht

[DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-06 Thread Apache Royale CI Server
This is the discussion thread. Thanks, Piotr Zarzycki

[DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-06 Thread Piotr Zarzycki
Hi Guys, I have upload manually ant artifacts. Please start reviewing stuff. What if vote passes - Should we merge 0.9.6 tag to develop ? Thanks, Piotr pt., 6 wrz 2019 o 13:09 Apache Royale CI Server napisał(a): > This is the discussion thread. > > Thanks, > Piotr Zarzycki -- Piotr Zarzyc

Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-06 Thread Carlos Rovira
Hi Piotr, thanks. One question I have is: I think MX Test was failing, does it affects the release or are not crucial to get the bits out? Thanks El vie., 6 sept. 2019 a las 13:10, Piotr Zarzycki (< piotrzarzyck...@gmail.com>) escribió: > Hi Guys, > > I have upload manually ant artifacts. Pleas

Build failed in Jenkins: royale-asjs_MXTests #1127

2019-09-06 Thread Apache Royale CI Server
See -- [...truncated 968.27 KB...] [mxmlc] scanning for overrides: ObjectUtil [mxmlc] scanning for overrides: SolidBorderUtil [mxmlc] scanning

[DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-06 Thread Piotr Zarzycki
Hi Carlos, IT depends on what commit MX is failing. I did branch for this RC couple of days ago. In that time I was seeing some commits to develop related to MX. Thanks, Piotr On Fri, Sep 6, 2019, 4:02 PM Carlos Rovira wrote: > Hi Piotr, > > thanks. One question I have is: I think MX Test was

Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-06 Thread Andrew Wetmore
The release notes file doesn't seem to have a section about what's in 0.9.6, the current release. a On Fri, Sep 6, 2019 at 11:29 AM Piotr Zarzycki wrote: > Hi Carlos, > > IT depends on what commit MX is failing. I did branch for this RC couple of > days ago. In that time I was seeing some commi

[DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-06 Thread Piotr Zarzycki
I was thinking about that in a very brave way at the beginning ! I was going to go trough commits from our last 0.9.4 release and prepare nice list for CHANGELOG, but since everything took double time then I assume. - It's not going to happen from my sight. On Fri, Sep 6, 2019, 5:13 PM Andrew Wetm

Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-06 Thread Josh Tynjala
I just updated the royale-compiler and royale-asjs release notes with the things that I worked on. They're in the develop branch for now. -- Josh Tynjala Bowler Hat LLC On Fri, Sep 6, 2019 at 9:37 AM Piotr Zarzycki wrote: > I was thinking about that in a very brave way

Re: Discuss of release steps preparation

2019-09-06 Thread OmPrakash Muppirala
On Fri, Sep 6, 2019 at 3:59 AM Carlos Rovira wrote: > Hi, > > maybe is not so bad to end this 0.9.6 manually, since there was many > progress in that front. Does not need necessarily be "all or nothing". Or > 100% success. > Releasing now 0.9.6 can make lower the stress a bit and make a the 0.9.7

Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

2019-09-06 Thread Andrew Wetmore
I have only looked at the top-level release notes and readme files. Should I wait a day or so before digging down to look at the similar files in folders? On Fri, Sep 6, 2019 at 1:45 PM Josh Tynjala wrote: > I just updated the royale-compiler and royale-asjs release notes with the > things that

Re: Testing the npm install error fixes

2019-09-06 Thread OmPrakash Muppirala
Thanks Carlos, this is useful! Can you send the path for the dependencies.js file you have shown here? Regards, Om On Fri, Sep 6, 2019 at 12:42 AM Carlos Rovira wrote: > Hi, > > I'll try to see Om links as I have time. In the mean while here is the log: > > https://paste.apache.org/p/pomzf > >

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

2019-09-06 Thread Apache Royale CI Server
See

Build failed in Jenkins: royale-asjs_MXTests #1128

2019-09-06 Thread Apache Royale CI Server
See Changes: [joshtynjala] added RoyaleUnit to release notes for 0.9.6 -- [...truncated 966.80 KB...] [mxmlc] scanning for overrides: Ob

Re: ${body} in index template

2019-09-06 Thread Greg Dove
Hi Carlos, Based on the variation that happens, I'm not sure ${application} is useful in its current form, although at first glance it appeared to be when I used it. Probably we just need ${applicationclass} The code that handles this is here: https://github.com/apache/royale-compiler/blob/a9fcf

Re: ${body} in index template

2019-09-06 Thread Alex Harui
FWIW, the current implementation was just a quick hack to get something working. No serious thought went into it so feel free to change it. I think there are "projectName" and "mainClassQName" variables in the compiler. IIRC, projectName maps to the output file name and mainClassQName maps to

Re: Heads up on XML

2019-09-06 Thread Alex Harui
FWIW, I went and looked at the ABC. The first syntax sets up a getProperty just like any other property fetch. The second (as expected) calls "child()". I've looked at the E4X spec a couple of times now and cannot see where the behavior we are seeing in child() is specified so I am going to a

Re: Heads up on XML

2019-09-06 Thread Greg Dove
Thanks for checking that. child is specified in 13.4.4.6 and essentially calls [[Get]] (After cycling through this kind of thing a few times, I found the easiest way to find methods is to search in the spec for 'e.mehodName' which gets you XML.prototype.methodName) and [[Get]] is specified in 9.1

Re: Heads up on XML

2019-09-06 Thread Greg Dove
Actually I know you are looking into the WSDL stuff maybe this is going to be important for that (not sure)? My goal is to get the XML stuff tidied up and ready to push by end of day tomorrow, worst case the following morning, local time (UTC+12). I also need to find some big XML test cases to

Re: Heads up on XML

2019-09-06 Thread Alex Harui
I haven't looked at what XML is used/supported by MX HTTPService. It looks like WebService does use MX HTTPService. I am currently migrating other things that WebService needs (XMLEncoder/Decoder, SOAPEncoder/Decoder). These are new files that aren't in the repo yet, so HTTPService couldn't b

Re: Heads up on XML

2019-09-06 Thread Greg Dove
Just to clarify I was referring to this stuff here: https://github.com/apache/royale-asjs/blob/8ab1d813ee2f72bab957f9485e56ad89dcf6e1ab/frameworks/projects/MXRoyale/src/main/royale/mx/rpc/http/AbstractOperation.as#L1038 with '//old XML style' On Sat, Sep 7, 2019 at 12:24 PM Alex Harui w

Re: Heads up on XML

2019-09-06 Thread Alex Harui
Thanks. Yeah I remember that is commented out. In a quick look, it wasn't clear why XMLDocument was used instead of E4x in the WebService code. I will probably just use e4x and see what happens. -Alex On 9/6/19, 5:30 PM, "Greg Dove" wrote: Just to clarify I was referring to this s

Re: Heads up on XML

2019-09-06 Thread Greg Dove
'I think that SWFDump will generate valid XML and there is a way to get DITA files from Flex ASDoc that are valid XML.' Sounds like a good idea for some large xml files. I did not use that yet, so will take a look and see if I can figure it out. Thanks! On Sat, Sep 7, 2019 at 12:30 PM Greg Dove

Build failed in Jenkins: royale-asjs_MXTests #1129

2019-09-06 Thread Apache Royale CI Server
See -- [...truncated 966.64 KB...] [mxmlc] scanning for overrides: ObjectUtil [mxmlc] scanning for overrides: SolidBorderUtil [mxmlc] scanning

Build failed in Jenkins: royale-asjs_MXTests #1130

2019-09-06 Thread Apache Royale CI Server
See -- [...truncated 967.37 KB...] [mxmlc] scanning for overrides: ObjectUtil [mxmlc] scanning for overrides: SolidBorderUtil [mxmlc] scanning