Home >
You may know that Adobe's Ant tasks for Flex (http://labs.adobe.com/wiki/index.php/Flex_Ant_Tasks) are suboptimal. You may not know that Adobe is waiting for people to vote before making improvements. Right now the priority for improvements to the Ant tasks is level C, and dropping.
You can make a difference, by voting and thereby boosting the priority. If you would like AIR support in the Ant Tasks for Flex, please vote at the following link. You will need a login using your free login id in order to vote:
https://bugs.adobe.com/jira/browse/SDK-14235
Why not add a comment after you vote? Just click on the word 'Comment' on the left menu of the Adobe Bug Database page.
Comments
4 Comments
Leave a comment
Tag Cloud
New Recommended eBooks
Get free updates and all-access to O'Reilly eBooks on your iPhone, Kindle, Sony Reader, or other mobile device.
Learn more about eBook bundles
News & Events
Books Excerpts
Read excerpts of RIA books provided by InsideRIA and O'Reilly Digital Media.
Find more book excerpts
We have developed a compiler Wrapper for eclipse and standalone to use ADL, ADT, mxmlc and many more with ant. In eclipse you have codecompletion for every compiler. Just have a look at http://zarkov.bigsource.de.
Cheers
Alex
I think the reason they're dropping is that there's other/better alternatives out there for compiling apps. For the most part, we're using a Maven build server that builds and publishes our Flex applications.
There's some projects like: http://code.google.com/p/flex-mojos/. Flex Mojos seems to have A LOT of support for it, and it has what appears to be a pretty big community. (We're not using this yet).
I also don't find that I'm missing much with the AIR command line tools, including code signing. Given limited resources, there's other things I'd like to see built. As it is now, I can build easily locally (using FB), and server side builds, which usually are pretty customized anyway, can happen easily enough with command line tools.
I think the reason they're dropping is that there's other/better alternatives out there for compiling apps. For the most part, we're using a Maven build server that builds and publishes our Flex applications.
There's some projects like: http://code.google.com/p/flex-mojos/. Flex Mojos seems to have A LOT of support for it, and it has what appears to be a pretty big community. (We're not using this yet).
I also don't find that I'm missing much with the AIR command line tools, including code signing. Given limited resources, there's other things I'd like to see built. As it is now, I can build easily locally (using FB), and server side builds, which usually are pretty customized anyway, can happen easily enough with command line tools.
Mike,
After reviewing the jira submission plus comments and the comments posted here, I think there are probably some differences between what tools/techniques folks from 'big shops with adequate budgets' may do and what a little one-man shop like me does to increase productivity. For over 45 years with more than a half-dozen primary language/platform/environment combinations, productivity has meant maximizing test turn-arounds per hour.
Thus, the example of using ant for adt is helpful, but since that is not a frequently-run set of procedures, I just leave that in ant. The example of using ant for mxmlc does not contribute nearly as much as the incremental compilation via fcsh. [If you are embedding even minimal fonts, you know that the difference between mxmlc and compile inside fcsh is on the order of 2-3 minutes versus 10-20 seconds.]
So, I will be happy to provide you and others the small source changes I made to SimpleShell to:
A. Let me compile AIR apps with as few keystrokes as compiling Flex apps.
B. Run an adl test inside the 'fcsh session' so that I don't have to keep yet another window to yet another command line session open on my already-way-too-cluttered desktop.