On Wed, Feb 29, 2012 at 2:39 PM, Om wrote:
> The (lazy) decision was:
>
> 1) Keep Ant for now - because it just works. This is how Flex SDK is built
> today.
> 2) Maven, Gradle, Scon etc. support can be added by anyone interested. No
> one is blocking those efforts.
> 3) Once the other mechansims work properly and all kinks have been ironed
> out, we take a vote on whether we want to switch from Ant and chose a new
> build mechanism.
>
> I hope no one has any issues with this.
>
> Thanks,
> Om
I agree with this Om, its the most pragmatic approach being that we
actually have an ANT build script and we do not have anything written with
Maven, Gradle or Scons to replace it. I think if anyone feels really
passionate about Maven, Gradle or Scons they should totally write
something, then we can talk about how or if we support it. I would image at
the very least we should have instructions and examples of using alternate
systems, but if people are willing to keep those alternate systems updated
then there's a bigger possibility about supporting alternate build scripts,
at that point we can decide how that happens. I do feel we need to go with
what we have and make that the baseline for any scripts that might replace
it in the future. If something is really better than ANT my guess is people
will recognize it quickly and want to move anyway. It'll happen organically
once we actually have code to talk about.
--
Omar Gonzalez
s9tpepper@apache.org
Apache Flex PPMC Member