[
http://jira.codehaus.org/browse/MJAVADOC-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MJAVADOC-224.
------------------------------------
Assignee: (was: Vincent Siveton)
Resolution: Not A Bug
It seems to not be a bug into the javadoc plugin but I guess that you defined 2
mojos with same goal...
> CLONE -If Javadoc is set to aggregate, the build fails inside a Maven plugin
> module
> -----------------------------------------------------------------------------------
>
> Key: MJAVADOC-224
> URL: http://jira.codehaus.org/browse/MJAVADOC-224
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 2.3
> Reporter: Christian Schulte
> Priority: Critical
> Fix For: 2.4
>
>
> If your project contains a Maven plugin, then it is impossible to build
> aggregated Javadoc.
> As the output (attached) shows, Maven seems to recusively build (what's with
> all those "skipping" messages?). When it reaches the plugin:
> [INFO] Error during page generation
> Embedded error: Error rendering Maven report: Error extracting plugin
> descriptor: 'Goal: component-report already exists in the plugin descriptor
> for prefix: tapestry-component-report
> Existing implementation is: org.apache.tapestry.mojo.ComponentReport
> Conflicting implementation is: org.apache.tapestry.mojo.ComponentReport'
> I can get by this with the -fn (fail never) option.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
