Maven 2.2.1 Site goal not generating doclava

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Add the Maven pom.xml like in the Wiki Instructions
2. Run mvn site

What is the expected output? What do you see instead?

Site documentation is generated.  However this only appears if mvn 
javadoc:javadoc is run and mvn site reverts to the normal Javadoc.

I tried moving it to the <reporting> section of the pom.xml but the site is not 
built correctly.  Would prefer to have doclava built with my site goal!

Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
Java version: 1.6.0_18
Java home: C:\Program Files (x86)\Java\jdk1.6.0_18\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7" version: "6.1" arch: "x86" Family: "windows"

POM file attached for viewing.

Original issue reported on code.google.com by mellowaredev on 6 Dec 2010 at 6:41

Attachments:

• pom.xml

[GoogleCodeExporter]

I'm experiencing the same issue in my projects with Maven3, I've been trying 
for two days without finding even a turnaround... what looks really wired is 
that it seems Doclava is not turned on when reporting.
Stay tuned, I'm investigating I hope I'll let you know ASAP.

Original comment by simone.t...@gmail.com on 9 Jan 2011 at 1:18

[GoogleCodeExporter]

Original comment by simone.t...@gmail.com on 9 Jan 2011 at 1:27

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

I found the solution, at least for Maven 3.X, I suggest to take a look at my 
public parent pom[1], see the `doclava` profile at bottom.

some hint:
 * replicate the doclava configuration for both `reporting` and `build` - maybe commons stuff could be configured in the `pluginManagement`, or just configure `reporting` would be enough if you don't want to Doclava-fy jar'd javadoc (I still haven't had the time to try these solutions);
 * pay attention on `additionalparam` tag differences;
 * avoid using standard doclet options when using Doclava.

I already checked out your project and I'll give a try with your configuration 
- patches will be submitted on your project issue tracker, but I consider this 
issue resolved.

[1] https://github.com/99soft/infra/blob/master/pom.xml

Original comment by simone.t...@gmail.com on 9 Jan 2011 at 7:29

• Changed state: Verified

[GoogleCodeExporter]

excellent!  Thanks for looking into this.  I suspect Maven 2.2.1 and Maven 3.0 
are very similar and should hopefully have the same fix.

Original comment by mellowaredev on 10 Jan 2011 at 11:49