Friday, August 20, 2004

Maven woes again

As Xdoclet uses Maven to produce the final documentation and web site, I thought I could enable the maven-statcvs-plugin to get to fancy line of code charts.
But instead:

[java] StatCvs-XML - CVS statistics generation
[java] java.lang.NullPointerException
[java] at net.sf.statcvs.Main.getModuleName(

When looking at the documentation, I found out, that this plugin uses a cvs command found on the host, while the maven-changelog-plugin uses a built-in cvs client.
This explains why maven takes that much space *sigh*.

Even worse: both plugins get the change log from the cvs server. Instead of fetching it one time only and then processing it twice, the load on the server is doubled!

No comments: