Noel J. Bergman wrote:
The top culprits in our now 111MB site (up from 18MB for JAMES v2.1
Looks like there is almost 70MB of overhead from the svn checkout! So we
are about 42MB for an export, and that's including multiple versions of
javadocs. We'll pare things down and compare again, but the maven overhead
is almost entirely in the xref report.
It cannot be considered a maven overhead. In fact xref reports are not
even a default for Maven. I added a plugin to generate them.
Maven did not add overhead to our site generation. m2 really simplify
the usage of third party reporting plugins that I think many of them
should be used.
Adding a lot of configuration for third party tools and their
dependencies in an ant based project is a pita and I would avoid it at
all costs, but m2 is really great solving this issue. You have 2
options: learn how to configure/use/automate each tool you want to use
(javadoc, xref, pmd, checkstyle, clover, cobertura, xdoclet and so on)
or learn maven2.
Stefano
