Re: Configuring source maps on Royale with new compiler options

2021-01-13 Thread Josh Tynjala
Okay, I've determined a couple of tweaks to the process that made things work on my machine to allow source map debugging with Maven. The source-map-source-root for Jewel and other SDK libs must include src/main/royale/ at the end. -source-map=true; -source-map-source-root=/frameworks/projec

Re: Configuring source maps on Royale with new compiler options

2021-01-13 Thread Josh Tynjala
I just gave it a try myself, and it looks like the compiler is failing to recognize the +royalelib token when you try to put it into Maven's additionalCompilerOptions. As I implied, it was certainly possible that this might or might not work. I'll let you know if I have another suggestion. -- Jos

RE: [EXTERNAL] Re: Configuring source maps on Royale with new compiler options

2021-01-13 Thread Brian Raymes
I'm not sure this is working properly. Here are some observations: I'm seeing a very strange error with my Royale application Firefox (see initially in a release build), and I have no idea how/where it is coming from: Uncaught TypeError: Error #1034: Type Coercion failed: cannot convert "functio

Royale-Typedefs : mvn install : [ERROR] Failed to execute goal org.apache.royale.compiler:royale-maven-plugin:0.9.8-SNAPSHOT:compile-extern (default-compile-extern)

2021-01-13 Thread ZAMOUN, Mourad
[INFO] --- royale-maven-plugin:0.9.8-SNAPSHOT:compile-extern (default-compile-extern) @ royale-typedefs-js --- [INFO] Executing COMPC in tool group Royale with args: [-load-config=C:\tools\royale\royale-typedefs\js\target\compile-extern-config.xml, -compiler.targets=SWF] args: -load-config=C:\tools