On 2/28/12 11:37 AM, "Greg Reddin" <gred...@gmail.com> wrote:
> On Tue, Feb 28, 2012 at 12:57 PM, Alex Harui <aha...@adobe.com> wrote:
>> If I need to change the build, I should only have to change the Ant build
>> script. If that breaks the Maven or Gradle build scripts, too bad and folks
>> who know those build systems will have to react.
>>
>> Official releases would only include the Ant script and require Ant to
>> build, not Maven or Gradle or anything else. Once a release is approved,
>> Maven folks will have to create whatever Maven users need from the release.
>
> That's basically another abstract idea because there is no Maven or
> Gradle build. On the surface I can't really support it because it
> elevates ant to a level of a "master build" and anyone doing something
> else has to figure out how to make it work. If I ever get some time I
> intend to look into what it would take to get the framework to build
> with Maven. Thus far I haven't been able to do it. But when (if) I do
> or someone else does, we can compare the Maven (or Gradle) build with
> the current build and decide if we want to pick one going forward. We
> may decide there's a new model that's far superior to what we have
> now.
>
> Greg
I'm not sure I understand why that's abstract. That is the reality right
now. I'm certainly open to change going forward, but I would think it would
be a barrier to progress for the commit process to require that you wait for
more than one build script to complete, and know how to fix multiple build
systems if they break.
But sure, once you get something working with Maven, you can certainly argue
that it should replace Ant as the way we build.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
