[
http://jira.codehaus.org/browse/MJAVADOC-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=136865#action_136865
]
Vincent Siveton commented on MJAVADOC-145:
------------------------------------------
FYI I readded @execute phase="generate-sources" and @execute
phase=generate-test-sources in r661899
I tried the tapestry build [1] with "mvn site -Pjavadoc" and all seems ok in
2.4 and 2.5-SNAPSHOT
[1] http://svn.apache.org/repos/asf/tapestry/tapestry5/trunk
> If Javadoc is set to aggregate, the build fails inside a Maven plugin module
> ----------------------------------------------------------------------------
>
> Key: MJAVADOC-145
> URL: http://jira.codehaus.org/browse/MJAVADOC-145
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 2.3
> Reporter: Howard M. Lewis Ship
> Assignee: Vincent Siveton
> Priority: Critical
> Fix For: 2.4
>
> Attachments: ComponentReport.java, maven.out, pom.xml, pom.xml
>
>
> 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
