Jofo wrote:
Just for my understanding for what kind of things are we going to use Maven?
Nightly builds, testing, library management,...?
Likely yes, yes, and yes.
As well, we should be able to build the jar with it instead of needing ant.
We can already run the unit tests from maven and collect the results.
Maven copies dependencies to a local repository (~/.m2/ in mac/linux). So if you delete your repository, or checkout a different copy (for a branch), you don't have to re-download all the dependencies.
We can also test other plugins that might be useful. For example:
Release - update version numbers, test, and branch in SVN.
PMD & Findbugs - scans Java source code and looks for potential problem
JDepends - reports on project interdependencies
Clover - show unit test coverage (won't show much yet
)
CheckStyle - once you define a codestyle, reports on violations
The Maven-style naming for builds is usually X-SNAPSHOT until the build is final, then you remove the SNAPSHOT. So I've named our current build 0.98-SNAPSHOT.