Maven is a project management tool that can be used to build projects and manage dependencies.
Maven greatly reduces the overhead of managing dependencies for a project. At build time, it automatically retrieves the most recent versions (or other version that you specify) of the libraries and jars on which your project depends, and - perhaps more importantly - the appropriate versions the libraries and jars on which those depend. Maven can be configured to retrieve files from a central location so copies of updated jars do not need to be distributed to individual developers.
Maven also supports the creation and use of archetypes, or project templates. By invoking an appropriate archetype, Maven will create the framework for new projects for you. MAP hopes to provide archetypes for some common project types.
Maven can be invoked from within Eclipse. Click here for instructions.
(if this is possible, we should probably have a separate page that is linked from a MyEclipse page and the Maven page.)
*Use the default Maven project structure for new projects. Although there is nothing inherently superior in this structure, experience has shown that it's easy to sink a lot of time on debating and deciding on a project structure with the ultimate selection not being significantly better than the alternative. The default Maven project structure works, so save time and consider the decision made. Plus, you won't have to configure Maven to use a different structure.
http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html documents the default Maven project structure.
The official Maven project site
http://maven.apache.org
Books available through MIT subscriptions (certificates required)
On Safari Books (http://libraries.mit.edu/get/safari/)
Maven: A Developer's Notebook
by Vincent Massoi; Timothy M. O'Brien