On Tue, 28 Feb 2012 12:13:14 -0500, Michel Boudreau <michelboudr...@gmail.com> wrote: Non-text part: multipart/alternative > I'd agree with the comment about it doesn't matter what we build Flex with > as long as it's available on the maven repo. I haven't looked at the build > script just yet, but as long as it doesn't have external dependencies that > needs to be added to the codebase, I don't have any issue with using Ant. > > However, I do think it would be nice to have a more separated build > process. Think about it, just because we are building some new flex code > doesn't mean the compiler necessarily changes or any other piece within the > framework. One of the main problems I've found with the Flex framework > when using Maven is that Adobe never considered how it does things and > keeps using Ant standards. This normally results in weird configurations > when it comes to setting up flex-mojos.
>From conversations with Marvin Froever of Flex-Mojos, my understanding was that the biggest problem was that the Flex SDK contained non-standard versions of Apache Commons lang, etc. The lack of disciplined dependency management with an eye towards the larger eco-system was the most significant problem. Ant is fine for small projects, I used to use it myself back in 2003 or thereabouts but for larger stuff, with big teams it sucks. Regards, Bryan Hunt
