[
http://jira.codehaus.org/browse/MJAVADOC-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=176272#action_176272
]
rt15 commented on MJAVADOC-224:
-------------------------------
org.apache.maven.plugins:maven-javadoc-plugin:2.5:aggregate
-> error
org.apache.maven.plugins:maven-javadoc-plugin:2.2:javadoc
-> works fine
Other topics on the subject :
http://mail-archives.apache.org/mod_mbox/maven-doxia-dev/200709.mbox/%[email protected]%3e
http://jira.codehaus.org/browse/MJAVADOC-145
http://www.nabble.com/%22Goal:-clean-already-exists-in-the-plugin-descriptor-for-prefix:-...%22-td23127658.html
> 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
