Dennis,
I noticed similar problems when someone tried to release the cobertura-m-p-2.5.
He rolled back the release, made a jira-issue[1], changed the configuration of
the m-javadoc-p[2] and retried the release.
I didn't have time to investigate this yet (this should be fixed in the
mojo-parent of course) but I know he's using M2 while I'm using M3.
It might give you a hint.
-Robert
[1] http://jira.codehaus.org/browse/MCOBERTURA-141
[2] https://fisheye.codehaus.org/changelog/mojo/?cs=13909
> Date: Wed, 27 Apr 2011 20:32:10 +0200
> From: denn...@apache.org
> To: dev@maven.apache.org
> Subject: Javadoc Plugin problems during Doxia release
>
> Hi
>
> As I mentioned in the vote thread I had serious problems with the
> Javadoc Plugin during the release. After having done some more testing
> I'd like to present my findings.
>
>
> 1. The Javadoc Plugin has class loading interference when run from
> Maven 2.2.1. Somehow the class path is modified and broken during a
> build. In my case this leads to an exception during Javadoc generation.
> See stack trace below. This meant that I could not publish the site
> using Maven 2.2.1. Using Maven 3.0.3 worked.
>
> Upgrading to the latest 2.8-SNAPSHOT of the plugin does not solve this
> issue. I don't know whether the bug is in Maven or the Javadoc Plugin,
> but I'm guessing the latter. Looking through the current unresolved
> issues fr Javadoc Plugin I'm unable to find a matching issue.
>
>
> 2. Version 2.7 of the Javadoc Plugin takes exponentionally longer time
> to run based on the number of modules in a multi module build. Doing
> 'mvn site:stage-deploy -Preporting' for Doxia took 89 minutes on my new
> 4-core, 8GB, SSD-equipped machine. No, I'm not kidding - 89 minutes!
>
> Doxia has 19 modules. For each module the Javadocs (and test Javadocs)
> for *all* the other modules are created. You do the math.
>
> The good thing is that this seems to have been fixed in 2.8-SNAPSHOT,
> probably in MJAVADOC-284. We need to release 2.8 and update maven-parent
> to that ASAP.
>
>
>
> Stacktrace when running 'mvn site -Preporting' on the current trunk of
> Doxia Sitetools. You should be able to use the revision prior to the
> release (r1096869) to see this, if you haven't yet downloaded the staged
> 1.2-version of Doxia. A similar stacktrace occurs for Doxia, but the
> build time for that project is considerably longer.
>
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Error during page generation
>
> Embedded error: Error rendering Maven report:
> Exit code: 1 -
> G:\apache\maven\trunks\doxia\doxia-sitetools\doxia-site-renderer\src\main\java\org\apache\maven\doxia\siterenderer\DefaultSiteRenderer.java:57:
> cannot find symbol
> symbol : class Doxia
> location: package org.apache.maven.doxia
> import org.apache.maven.doxia.Doxia;
> ^
> ...
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
