Maven 2 is both loved and despised by many, but the people who despise it may not be aware of all the ways to work around Maven's conventions. This presentation walks through the process of "Mavenizing" Google's Guice framework, illustrating some common pitfalls along the way and making minimal changes to the codebase as needed while being as minimally invasive as possible. The session shows how to take full advantage of Maven's multimodule build management and reporting capabilities. The net result is a build system that requires no configuration for a new developer, speeding ramp-up time significantly and making dependency management very simple as well for lead developers/architects.

The presentation starts out by Mavenizing Guice's core module and then moves the core module to be a peer of the other modules so it can proceed to Mavenize Guice's plug-ins in order to take full advantage of Maven's multiproject build mechanism. At that point, we'll Mavenize the plug-ins we have time for: Guice's Spring bridge, then Guice's Servlet plug-in, and finally Guice's Struts2 plug-in, which all have Java™ Archive (JAR) deliverables.

During the process, attendees will see how Maven manages dependencies transitively in a couple of ways:
• The version of a used JAR has to be declared only once.
• If the JAR is used in a dependent project module, the same JAR does not need to be declared in a sibling project module.