> > 1) maintain the structure and use a tool (like you did) to transform the > sdk to maven compliant sdk. > > 2) change sdk structure to get directly a maven compliant sdk > > IMHO the best way should be 2), since now is the right time to make > changes. Maybe just as soon as Apache Flex 4.8 sdk will be released, right? > > Tools should change to make Apache Flex SDK compliant. >
I respectfully disagree. I think (1) is the way to go. This gives us (Flex SDK team) the freedom to maintain whatever structure we want. If some of us want to make it Maven compliant, they should write a tool to create a Maven-specific directory structure and maintain it either part of Apache Flex or outside of Apache Flex. Maven is not the only build management system we want to support. Lots of folks use Ant, GradleFx, custom build scripts, etc. If we favor Maven, then it is not fair for the other tools. Breaking existing tools like Flash Builder, IntelliJ just to make Maven work is not the best idea. We are at a very delicate point in terms of end users' confidence and trust. Lets not break the camel's back. Thanks, Om
