To respond to the original question: I think we didn't get into talking about Maven because I (and I think) Tor don't have much experience with it. Dick does, I know, but I guess he didn't have much to say about it.
I looked at it briefly when figuring out how to evolve our build system at Netflix, but rejected it as too disruptive. Our teams are very independent, and it would have been a difficult sell to some of them. It also seemed that trying to adapt or extend Maven in ways it didn't agree with would be an exercise in pain. I instead opted for a gradual evolution of our ad-hoc Ant-based build files into a simple Ant framework with Ivy dependency management and lots of Groovy doing the hard work. Almost all projects have tiny build files that leverage the common framework. Now we are in a position and in the process of migrating to Gradle, which I think takes a better, more scalable approach to the build problem than Maven's do-it-my-way-or-suffer approach. --carl -- You received this message because you are subscribed to the Google Groups "Java Posse" group. To view this discussion on the web visit https://groups.google.com/d/msg/javaposse/-/PL7_zcRa1vYJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
