Migrating your project to Maven 2 – Part II

06 Mar, 2006

The last thing I did was running the test classes successfully. Now let’s put in all the reports. We currently have the following reports in our maven build are:

  1. Jira
  2. Javadoc
  3. JavaNCSS
  4. Checkstyle
  5. PMD
  6. FindBugs
  7. JDepend
  8. Simian
  9. JUnit
  10. Clover
  11. Dashboard

First lets start by running mvn site out of the box (one of my favorite test cases ;-)), this should create the default reports according to the maven documentation ( Here we go: mvn site….

[INFO] Generate "Continuous Integration" report.
[ERROR] VM #displayTree: error : too few arguments to macro. Wanted 2 got 0
[ERROR] VM #menuItem: error : too few arguments to macro. Wanted 1 got 0
[INFO] Generate "Dependencies" report.
[INFO] null
[INFO] Trace
at org.apache.maven.artifact.resolver.DefaultArtifactResolver
at org.apache.maven.artifact.resolver.DefaultArtifactResolver
at org.apache.maven.project.DefaultMavenProjectBuilder
at org.apache.maven.project.DefaultMavenProjectBuilder

Nope, not out of the box… It seems that maven site does not work, although it’s mentioned on the maven website that it should work without any adjustments.
I googled about and found the following suggested solutions: Using a snapshot version of the project-info-reports plugin as mentioned on the following link:–t1095846.html, but that caused another error.
Maven said something about a default skin that did not exist. I also found a link that possibly would fix this,—where-do-i-get-it–t1180771.html, but that led me to the same NullPointer mentioned above.
I just wanted to conclude that site doesnot work yet in maven 2, but then I read this article on javaworld: were they managed to get it work. I tried the example attached to the article and that one did work indeed. The main difference between the two pom’s are the relative huge amount of dependencies that I have in my pom. That’s exactly the report is throwing the NullPointer according to the stacktrace. I will try to find out whats going on, and which depedency causes this NullPointer later. (But even if it is a broken dependency or whatsoever I would not expect the NullPointer…)
Let’s now focus on the individual reports that I want to use in Maven 2 and see if they are available yet

Report Name Does it work in Maven 2?
Jira Not found
Javadoc OK
JavaNCSS Sandbox
Checkstyle OK
FindBugs Sandbox
JDepend Sandbox
Simian Sandbox
JUnit OK, its called surefire now.
Clover NOT OK, could not get it to work.
Dashboard Not found

I could not download any of the sandbox plugins, I followed the instructions on, but no luck. Maven just could not download the plugins for some reason.
A lot of the reports we use now are still in sandboxes, so it’s not possible to migrate yet for us. Also I still need to investigate why maven site is throwing me the NullPointer before I can use the site generation. Untill this gets fixed or I get it working we are still stuck with maven 1.x.
(I used jdk 1.5.6_06 and maven 2.0.2 for this test)

Newest Most Voted
Inline Feedbacks
View all comments
Jeroen van Erp
Jeroen van Erp
16 years ago

Well, maven 2.0.3 has been released. Let’s see how (and whether) it runs.

Ravan Naidoo
Ravan Naidoo
16 years ago

I’m currently using jdk 1.5.6_06 and maven 2.0.2.
The maven 2 reports are really not up to scratch, but with a little tweaking it is possible to get them to work. The reports generated were the default reports and I have not tried to customize them.
For the sandbox reports, I usually just download the source and build/install it locally. I’ve successfully done this for Cobertura (Test coverage) and Findbugs.
For JavaNCSS, I had to add the jaxen.jar dependency to the pom before getting it to install. However when run, JavaNCSS didnot seem to like my java 5.0 generics and enums. Kept on getting ParserExceptions.
JDepend has graduated from the sandbox, and this report worked out of the box.
From what I’ve seen in the forums and in maven’s jira, the developers agree that maven 2.0.2 site is not very stable. They promise that site would be alot more stable in 2.0.3 release. But I have not idea when that comes out.

Lars Vonk
Lars Vonk
16 years ago

I would not choose maven 2 yet. Main reason is the missing reporting feature.I would still choose maven 1.x for projects (or maybe look at something else).
BTW There are some appserver supporting java 5, like weblogic 9 (you probably missed the last techrally ;-)).

Maarten Winkels
Maarten Winkels
16 years ago

this was me ^

16 years ago

Good read! To bad you got stuck so quickly in the second part.
Do you think we should maven2 for our projects? We can build them with maven2, probably easier than in maven1 (is it?), but I think reporting is a very important feature of maven. It might be quite some time before we can really use maven2 for a project then.
It’s probably similar to Java 5.0. It’s been available quite some time now, but since none of the Application Servers support it, it’s hardly useable in any project we do.

15 years ago

After long strenuous hours of working on Maven2, I figured out what the “null pointer accpetion” was (as I was getting it a lot too). It means you are trying to download a plugin meant for Maven1. Also, it seems a lot have changed names (as you mentioned above about junit now being surefire) and many are still not yet converted. This is a good post though, I read a few things it took me a bit to figure out, and I wish I had happened on this site before!

Explore related posts