On 1/31/17, 10:16 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote:
>Hi Alex, > >I’ll have a look at the changes and eventually try to prepare the maven >plugin for these changes. In theory, MXMLJSC is backwards compatible. I will try to remember to make sure of that before merging to develop. Longer term, I leave it up to you and others to decide if the Maven support should be tweaked. In some ways, MXMLJSC and the compiler.targets option may only be needed for non-Maven users, especially in IDEs where you want one launch of the compiler to compile against different API sets. If I understand Maven correctly, you can already do that with Maven by having the POM dictate to run the various compiler "executions". > >Just to be on the safe side … with “cordova” you mean producing a >directory that I can pass into cordova. Not include the cordova >functionality in Flex, correct? IMO, the goal is to produce, for Cordova for Android, a .apk file. You shouldn't have to pass anything into Cordova. We pretty much know the steps are going to be the same every time so why make you do those steps some other way. I was going to call Cordova CLI to do it so it works in the Node distribution. Again this might be only for non-Maven users. The key here is that one of the pain points around Cordova is remembering to add the various plugins to your Cordova Project. Because the FlexJS Publisher visits every .JS file, it is possible that on the visit we can see that a plugin is needed and automatically add the plugin. But maybe in Maven for Cordova you have to specify the plugin in the POM anyway. -Alex
