2. What / why / how?
● Corporate environment
● Build large projects
● 10+ modules
3. Some hate maven
Maven builds are an infinite cycle of despair that
will slowly drag you into the deepest, darkest pits
of hell (where Maven itself was forged).
http://kent.spillner.org/blog/work/2009/11/14/java-build-tools.html
5. What do I need ?
● Stable builds
● Reproducible builds
● Reports
● Releases
● Control over source code and dependencies
● Build automation
● Easy development cycle
● What else ???
6. Do you know a ninja?
● Developers are smart
● Make builds fool proof
● Have a build team
14. The Bigger, The Better
● Have many modules
● Your IDE loves modules
● Try to have separate modules if that makes
sense for you
● Do you really need multi module projects?
http://monkeyisland.pl/2010/12/11/ide-and-patterns-for-huge-maven-project/
20. Your build is unique
http://www.sonatype.com/books/mcookbook/reference/ch02s03.html
http://ronalleva.com/groovy/maven/programming/2008/01/23/using-the-groovy-maven-plugin-to-do-magic.html
26. Remember
● Maven is not that bad, could be pretty nice
● Customize maven to fit your need
● but respect the tool
● You are never done
● Have a master near by that knows the tool
● Have a look at Gradle....