> >5) Why not use Ant for the things that are hard and Maven for the rest? > >This way we have to configure two build systems. And it doesn't make us >think twice about design decisions. If our first thought doesn't work >with maven we do it with Ant. Anyway it wouldn't solve the root problem: >The large amount of people having problem with the Ant build. If the Ant >build is so good, why do we tend to have Build related questions on these >lists avery few days? IF the Ant build was solid and good I would never >have put so much weight into migrating. Do you hear me migrating the old >SDK? Probably not cause that build simply seems to be working. Except for >those periodic dropouts of download sources, but by downloading stuff >from Maven central I can't even remember the last time someone had a >problem with that.
I'm not saying the Ant build is perfect, but with the community's help it could get better. But as far as having the Maven build call Ant here and there, I don't think it would be as hard as configuring two build systems. I don't think there'd be a lot of Ant scripts to maintain in the Maven build. > >12) would having a parallel set of projects in an "externs" folder help >or not? > >No it would not. I read your emails but you don't seem to be reading my >answers. Building the externs is the smallest problems I am having. >Actually that's the part that's working nicely. I am having problems with >the rest- Building ASJS libraries that depend on other ASJS libraries. Maybe I'm still not clear on the place you are stuck. The Ant build currently builds a set of SWCs that go frameworks/externs and another set that goes in frameworks/libs. Each set of SWCs are used to build the downstream SWCs. The SWCs in the frameworks/externs folders have a different set of dependencies than the SWCs that end up in frameworks/libs. I know you can build extern SWCS in flex-falcon, but I thought you were having problems building the SWCs that go in frameworks/externs. I'm wondering if one Ant target could be like a macro/mojo that builds the SWC that goes in frameworks/externs so you can use Maven to generate the JS files and the final SWCs. > >13) Flex isn't a corporate sponsored project > >I think it is ... Adobe is paying you full time to work on this, so I >guess it is a corporate sponsored project. What is if Adobe decided to >stop paying you for working on Flex? Adobe has no control over Flex. They cannot prevent me from contributing to it. If they stop paying me and I can find another way to make money and have time to contribute, I can and will. >... Adobe promised to support us for 5 years by paying someone to >continue working on Flex ... so how much time do we have left? Don't know, which is why I'd rather not spend time right now trying to make Maven build a SWC that our end-user customers won't need. Call a little bit of Ant as a workaround for now and use Maven for the rest. Later, if we get more time and more folks involved, maybe we'll find a better all-Maven solution. -Alex
