On 11/16/15, 1:30 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: > >2. The Problem with a dual approach of ANT and Maven is that Maven uses >convention over configuration, this means that it is possible to setup a >maven build for the current project structure, but it's quite a >configuration effort. If however we would convert the structure of the >project to a maven structure, you could probably adjust the Ant build to >that structure. In that case a dual approach would be ok.
Yeah, that’s what I’m thinking. The Ant scripts will adjust to Maven conventions. And other conventions if needed by other packaging/build systems. > >3. I don't quite understand why a maven build would prevent FlashBuilder >from working. An Ant target is just a simple Java class in a jar, so it's >easy to setup a maven project for building Ant target jars. So we >wouldn't be giving up on those Ant targets and in the early stages of a >transition to Maven this would be essential as we would use the Maven Ant >runner to use the Flex ant task to do the Flex compiling until we have a >pure Maven replacement. Maven won’t break FB and Ant. I was just pointing out that I think we can’t totally give up on Ant. > >4. Using Maven isn't locking in on anything. The one thing most people >complain about with Maven is that you use flexibility with it, which is >true. But the upside is you also loose complexity. In my courses the one >rule I lay most emphasis on is: "If it's hard with Maven, you're just >doing it wrong". Usually re-thinking what you are doing, cutting the >packages differently etc. will not only make your project build, but also >dramatically reduce complexity of the project. > >5. You don't "have to" take a course to use Maven ... I bet 99% of the >Maven users have never taken a course, it's just an offer from my side to >help others get up to speed. I’ve read (quickly) the links on Maven Om posted. I’ve used Maven to build and test BlazeDS. But being a consumer of Maven artifacts doesn’t mean you can go create new artifacts, especially if they are not Java-based. I still don’t know what the first step would be in Mavenizing Falcon and FlexJS. For Ant, I found the task overview and started grinding away. Anyway, where do you suggest that we start? I assume we have to start with refactoring? What is your vision for it? Thanks, -Alex
