On Tue, 28 Feb 2012 08:47:51 -0800, Maciek Sakrejda <m.sakre...@gmail.com> wrote: > > You still seem to be confused. > > > > Why would one chose to support two build systems - when ANT, is to all > > intents and purposes a subset of Maven's functionality; minus dependency > > management and a standardized configuration? > > No, Yennick has a good point. There's the internal build tools and > scripts (which will be used to build the compiler and the SDK > libraries), and the external build tools which users of the Apache > Flex framework will use to build *their* code which links against the > framework (e.g., the current mxmlc/compc/asdoc ant tasks--although the > asdoc task is so bad, I have not seen a single project use it > directly, instead calling out to the jar or command line). 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).
Ok, For the record, and my own sanity, I'm going to clarify, just once. I was talking about the tool used to perform repeatable builds of the Flex SDK. Every single, Java base Apache project, uses Maven as it's build tool. I am NOT, repeat, NOT, advocating that every developer using the Flex SDK be obligated to use Maven as his build tool. Flex-mojos, is quite frankly a pain in the arse to use. I use it, only because I like to resurect projects every couple of months or so - because I'm one of those philistines, who gets paid to write software. The replies to this thread are so willfully obtuse, I started to wonder about two weeks ago if I were being trolled. Now I am certain of that fact. Kindest, loving regards, Bryan Hunt
