Maven 2 is becoming increasingly popular in larger organizations looking to standardize and industrialize their build processes as well as in smaller shops simply trying to get more out of their builds. This session, for developers wanting to learn about Maven and Maven users wanting to get more out of their build tool, covers the main features and benefits of Maven and then looks at some of the more advanced uses of Maven in the real world, including complex transitive dependency management, dependency conflicts, multimodule projects, and integration with other build systems. It also looks at how the m2eclipse plug-in can be used to improve the Maven user experience and how to use the Nexus repository manager with the Maven release process to publish your APIs within your organization

Proximity is in function somewhere between http-proxy and proactive-mirror. Proximity is not HTTP Proxy. One of it's primary use is as Java web application to serve as maven proxy on our company's intranet. As for reducing outgoing traffic (caching central and other maven repos), aggregating more repositories (reducing project config) with acting as one logical repository and for publishing in-house and other external maven artifacts which are not uploadable to ibiblio (like commercial projects, J2EE Jars, etc...).

This mojo is designed to get a unique build number for each time you build your project. So while your version may remain constant at 1.0-SNAPSHOT for many iterations until release, you will have a build number that can uniquely identify each build during that time. The build number is obtained from scm, and in particular, at this time, from svn. You can then place that build number in metadata, which can be accessed from your app, if desired.

Artifactory is a Maven2 proxy repository with advanced features. It is based on JCR (using JackRabbit as the implementation), with a web UI based on Wicket, and embeded Jetty for quick start. All artifacts are stored in an embedded Derby DB.

The DepGraph plugin can be used to draw a dependency graph from the project, the mojo is executed in. It traverses all dependencies and creates a graph using Graphviz.

maven-proxy is a lightweight servlet engine that sits on your main server and imitates ibiblio (for instance). When it gets a request for a jar it doesn't have, it gets the jar from the upstream servers and stores it into it's cache before returning it to the requester.