Developing Maven 2.1
This page outlines the processes and tools that help with developing Maven 2.1. To give you some idea of what we're developing here is a picture of the dependency graph created by m2e:
Preparation
It is highly recommended that you install m2e if you want to try and easily work with Maven 2.1. It is possible using some trickery in m2e to load the entire Maven platform, run, and debug it all from within Eclipse. With the workspace resolution capabilities in m2e, it is possible to debug not only Maven, but also Maven plugins in-situ i.e. without having to install them first. You can follow Igor's guide below to setup your workspace correctly:
Running and debugging Maven 2.1 from m2e workspace
We are also going to prepare some PSF files, and try and finish a workspace resolution descriptor (some tools Sonatype is working on to aid team collaboration) so that new folks trying to develop with Maven can up to speed in minutes.
Hudson for CI
The primary CI instance that we are using for Maven 2.1 is an instance of Hudson that you can find here:
The goal is to have most thing in the dependency graph you see above loaded and running so that problems can easily be found, and nightlies can easily be created from any rapidly changing dependencies, and we can automate release staging along with artifact promotion when releases are deemed fit. We will have the canonical instance running on RedHat Linux, and then we are building out Windows, OS X, Solaris, and BSD build nodes so that we can adequately test the components and final releases on all the widely used platforms. Hudson's build in grid support makes this convenient to do.
