On Thu, Oct 14, 2010 at 9:59 AM, Benson Margulies <[email protected]> wrote: > I'm concerned that the circle of congratulations here is somewhat > oversimplifying this. > > I've brought Maven into my day job. > > I've arranged all the code involved to follow the maven way of doing things. > > And yet, I have some POM files that are veritable thickets of XML, and > attract a fair amount of unfavorable commentary from the people who > work for me.
This is the crux of my comment about advanced Maven users compared with advanced Ant users. When you extend your pom file piece by piece, each piece on itself is easily understandable. But when you get the less experienced person looking at the completed pom they are overwhelmed. I dont have any suggestions for this except to convince them to skill up. I'd suggest that any alternative build system would still be at least as ugly to read and understand. [del] > I don't hate on Maven. But I think that some people who show up on > this list in a state of frustration get pretty short shrift. That basic work flow of compile and install jars to repo should work out of the box with no issues. All of your examples are the "extra" bits over and above this, which definitely have some wrinkles. And mostly the wrinkles are around working out what the convention should be. The benefit is that as more people work out the convention they can be coded once in the plugin and all users can benefit from it. The problem is that very few people actually do this. If you compare this to Ant you are on your own, writing a build maintained by one. Personally, I am amazed when people expect a tool to do everything and anything they can think of out of the box. It takes an enormous amount of effort to get to that state, but it is slowly getting there. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
