title: FDT ANT tasks - exportAirApplication vs release.AirApplication
body: <p>I'm struggling with customised ANT-driven AIR packaging under FDT 5.6.x .</p>
  
  <p>I've just upgraded from FDT 5.0.x and I'm struggling to rebuild by workflow. I had an ANT script which loaded current project properties (build numbers etc), injected them into an AIR properties.xml file and then packaged a version of the app using the fdt.release.AirApplication task, with a custom file name to indicate the release etc. </p>
  
  <p>I can see that there's been significant refactoring of the release packaging mechanism; gone is the ability to create a release profile in the Launch Configuration dialog, instead it's now in the Project Properties.</p>
  
  <p>Also gone is the ANT task that I was using (fdt.release.AirApplication) . The only thing that seems to come close is fdt.exportAirApplication, which only takes 2 arguments, and according to the <a href="http://fdt.powerflasher.com/docs/FDT_Ant_Tasks#fdt.exportAirApplication_.28FDT_5.6.29" rel="nofollow" title="FDT ANT Docs">docs</a> is:</p>
  
  <blockquote>
    <p>This task executes the same behaviour as pressing the 'Export
    Application' button within 'Mobile properties > Deploy'</p>
  </blockquote>
  
  <p>I'm not sure the dialog it references is even called that anymore.</p>
  
  <p>The dialog in Project Properties > FDT AIR Properties > Desktop indicates you can pass custom parameters to the AIR packager, but I've been unable to find any documentation of how to use this feature. </p>
  
  <p>Like so much in FDT there is great power here, and so little documentation to accompany it. Has anyone got ANT-driven customised compiles working under 5.6.x?</p>