MAIA Air Execution Via ADL is Broken. Any work arounds?
I logged a bug on this but wanted to see if anyone had work around ideas. I currently have a MAIA project named "Main" that has a Flex module with an Air application in it. The project is in /idea. The module file is in the same directory. As a result MAIA compiles to /idea/out/production/Main. However when trying to run the Air project Maia builds the adl execution target wrong as "adl MyApp-app.xml /idea" it should be "adl MyApp-app.xml /idea/out/production/Main". Better yet since the second param is optional the following would be best adl /idea/out/production/Main/MyApp-app.xml". I know I can go manually run adl from the command line but that is a pain. I also can't hook into the Maia debugger running things this way. Any ideas on how to fix this or do I just have to wait for an update with a fix and more adl configuration options.
Please sign in to leave a comment.
Until the issue is fixed you should fix 'content' tag value in air
application descriptor. The path to swf should be relative to adl launch
dir, i.e. to /idea
Unfortunately this breaks relative paths. Our application loads translations and resources from a /assets and /locale folders in the same directory as the swf. This is Adobe's recommended approach. By changing the *-app.xml path ADL is able to find the swf but has the wrong relative path.
I am also facing the same issue and i need this badly to debug with intellij , tired having to have two ide's open all the time. Can you please suggest a workaround?
Fixed for the next Maia EAP (http://www.jetbrains.net/jira/browse/IDEADEV-37689).
Before the fix there's no way to change AIR launcher root directory, it is started in project root directory. So a sort of awful workaround is to copy compiled swf and all resources it needs to project root directory.