Build failed in Jenkins: royale-asjs_MXTests #1131

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

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

2019-09-07 Thread Apache Royale CI Server
See

Re: [royale-compiler] branch develop updated: MemberAccessEmitter: fixed issue where fully-qualified names were emitted as dynamic access with -js-dynamic-access-unknown-members=true

2019-09-07 Thread Alex Harui
Josh, What is the .factorypath file? It is in the release package. Should it even be in the repo? -Alex On 8/12/19, 11:12 AM, "joshtynj...@apache.org" wrote: This is an automated email from the ASF dual-hosted git repository. joshtynjala pushed a commit to branch develop

Re: Heads up on XML

2019-09-07 Thread Greg Dove
Yeah thanks Josh, Alex made a suggestion for that option too, it was the one I thought I would try first. I hope to get there later today, so I will see if I can figure that out. On Sun, Sep 8, 2019 at 7:20 AM Josh Tynjala wrote: > I think the DITA files generated by asdoc are pretty big too,

Re: Heads up on XML

2019-09-07 Thread Josh Tynjala
I think the DITA files generated by asdoc are pretty big too, so they're probably really useful for your testing. - Josh On Friday, September 6, 2019, Greg Dove wrote: > 'I think that SWFDump will generate valid XML and there is a way to get > DITA files from Flex ASDoc that are valid XML.' >

Re: Discuss of release steps preparation

2019-09-07 Thread Andrew Wetmore
I think the release notes should definitely cover 0.9.6, at least at a high level. Maybe points like this, if they are true: - Compiles faster - Many additional components available - Emulations of many other components available - For applications targeting JavaScript, you can now

Discuss of release steps preparation

2019-09-07 Thread Piotr Zarzycki
Hi Alex, That is only partially true what you are saying. Cause I'm definitely not the person, developer who when reaching some wall do not try to resolve it on it's own - Not that is not me. However in case of Royale release it's partially true, but let me explain why I asked first rather fix

Build failed in Jenkins: royale-asjs_MXTests #1130

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