flex-dev mailing list archives

On Tue, 28 Feb 2012 01:31:52 -0800, Om <bigosmallm@gmail.com> wrote:
Non-text part: multipart/alternative
> It looks like the last time we discussed this issue, we never came up with
> a definitive answer. I hope to settle this question here.
>
> First of all, there are two different issues:
>
> 1. What do we devs use to build the Apache Flex SDK?
> 2. What build mechanisms should we build support for end users who use
> the Flex SDK?
>
> I will let the team decide what we do for 1 (My personal preference is
> GradleFX)
GradleFX is for building Flex projects, not for compiling (mainly Java) source code
and outputting a Flex SDK.
For compiling complex, multi-dependent Java projects, in a reproducable
fashion, there really only one option, Maven.
> But, for 2, the answer is pretty obvious. We should build support for all
> build management systems. Ant, Maven, Gradle, etc. This is to ensure that
> we do not exclude any developer from makeing use of the Flex SDK.
I've been down that road before, trust me, it can only end in
pain. You will exclude all developers from building the SDK when it
degenerates into the Moras of Complexity.
Choose one build system, and stick to it.
There's nothing worse than checking out a project with 3 different ways
to build, none of which work properly.
Ultimately, it always ends up that one or two 'master' developers manage
the build process.
Make sure that anyone else can easily reproduce their build or you store
up many problems for the future.
Regards,
Bryan Hunt