Do you know how to make money from AdSense automatically? You don’t!? I’ll teach you how!

by the way, when i try to keep the master/root project.xml in a dir no subproject is constructed in the end

1. We use velocity templates to generate a list of projects on our Maven generated web site. We get weird errors when going to Maven 1.1, which we don’t have time for to solve. Even more so, these errors are likely to be solved in the final Maven 1.1. release.
2. Maven 1.1 requires JDK 1.4. As our project is not yet 100% JDK 1.4 compliant, we have to do some very dirty things to make Maven build successfully. This problem should be solved in october.
3. There seem to be some (serious) quircks with Maven 1.1 and dashboard. More specifically, I couldn’t get dashboard properties right (maven.dashboard.includes, maven.dashboard.excludes), nor could I stop dashboard from starting a reactor in each subproject (and no, I’m not too stupid to do so, because I get it to work in Maven 1.0.2 ).

All this made us decide to wait for the official release.

Some positive remarks to conclude though: Maven 1.1 has a much lower memory footprint indeed, and seems to be much faster, a typical site generation for our project went down from 45 to 30 minutes (approx.).

In fact, we cannot use the Maven reactor right now, because of “out of memory” problems, whereas Maven 1.1 did fine, except for the Dashboard and Velocity template generation.

base/project.properties
–>maven.dashboard.basedir=${pom.getArtifactId()} (this value depends on where you’ve put the base/project.xml file)

I had to add this line to make the multiproject dashboard work:
–>maven.dashboard.includes=${maven.multiproject.includes}

The reason I had my project structure laid out as described above was that I started working on a real-life instance of such a project the first of January, so the structure was already completely fixed when I started. I then had to come up with a Dashboard solution for the existing project structure.

But again, your solution looks much neater and should be the to be preferred configuration for new projects.

Thanks for your feedback.

basedir
|
|- project_1
|  |
|  |-project.xml
|  |-project.properties
|  |-maven.xml
|
|- ...
|
|- mavenbuild
|  |
|  |- project.xml
|  |- project.properties
|  |- maven.xml

# Tell dashboard to run in on this project only when run in this directory. This relative directory trick will work when called from the
# main build directory or from this directory.
maven.dashboard.basedir=../project_n
maven.dashboard.includes=project.xml

Otherwise you get the full multi-line dashboard report in each sub project because in the main project.properties you told dashboard to run in the parent directory and include all sub-projects and these properties are inherited by all the sub-projects. So you need to override this in each sub-project to create the dashboard just for it when dashboard is run in its individual directory or called from the main script.

Sorry for posting all this in bits in pieces. I should have planned my post out a little better. Hope its still usefull.

basedir
|
|- project_1
| |
| |-project.xml
| |-project.properties
| |-maven.xml
|
|- …
|
|- mavenbuild
| |
| |- project.xml
| |- project.properties
| |- maven.xml