On Tue, Feb 28, 2012 at 8:47 AM, Maciek Sakrejda <m.sakre...@gmail.com>wrote:
> It would be > nice to offer support for multiple build tools here so we don't > dictate what type of build system our users need to use (especially > nice when your users are building a back-end with their scripts as > well, and that may have different requirements). > There is no valid reason I can think of that would prevent us from accepting any code donations or examples of how to perform builds for different tasks, both building the SDK and building projects that use the SDK. The important part is that the output of these build systems is identical to what is needed for the task at hand. That said, I would encourage anyone that is trying to set up a build process in any technology to write the code, or gather help to write the code, and then submit it via JIRA so we can then proceed with those real examples and do something with them. As long as we can keep things organized, updated, and with clear instructions on the Wiki/website we should be able to have ANT, Maven, Gradle, and whatever other instructions to making builds so long as they produce what needs to be produced. At least that's how I think we should approach it. We don't need ANT vs. Maven vs. Gradle threads, we need ANT, Maven and Gradle contributions, such as those Justin Mclean has been doing to improve the ANT build scripts. Some people will need ANT, others will need Maven, and some will need Gradle for a wide variety of reasons. Let's embrace them all (so long as their licenses are compatible but that's a different thread :P). -- Omar Gonzalez s9tpep...@apache.org Apache Flex PPMC Member
