Good read. Documentation can be much better, but I suppose it is up to us as community members to make that happen. Maven isn't owned by anyone. The guys at Sonatype have done a good job of posting various blogs. If anyone has the time and desire I am sure she/he could pull many of these various tid bits of good practices into one coherent doc.
I think it says something that it has not been done yet. While everyone says it would be great to have, clearly no one has felt strongly enough about it (yet) to make it happen. It is more of a very nice to have than a hard and fast requirement. > -----Original Message----- > From: chad.da...@emc.com [mailto:chad.da...@emc.com] > Sent: Tuesday, April 17, 2012 2:32 PM > To: users@maven.apache.org > Subject: RE: The Maven Way > > > > You are not alone in that. Especially since the most valuable single > bit of > > advice one can give a new Maven user is: "if you don't do things > Maven's > > way, Maven will fight you and Maven will win." > > > > People extol the virtues of "convention over configuration", but > where is the > > compact definitive specification of The Conventions? > > > > Interestingly, I just wrote a detailed blog entry about the irony of a > CoC tool with a body of documentation that documents the configuration > rather than the conventions. It's kind of darkly humorous if you think > about it. The configuration is the way to get in trouble with maven, > but it's the only thing documented. > > In case you're interested: > > http://zeroinsertionforce.blogspot.com/2012/04/maven-does-not-suck-but- > maven-docs-do.html > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
