[jira] Commented: (MJAVADOC-145) If Javadoc is set to aggregate, the build fails inside a Maven plugin module
[ 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
[jira] Commented: (MJAVADOC-145) If Javadoc is set to aggregate, the build fails inside a Maven plugin module
[
http://jira.codehaus.org/browse/MJAVADOC-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159310#action_159310
]
Christian Schulte commented on MJAVADOC-145:
Having
{{code}}
org.apache.maven.plugins
maven-javadoc-plugin
2.5
javadoc
true
javadoc
false
true
UTF-8
UTF-8
UTF-8
true
${pom.name} Specification ${pom.version}
true
true
false
false
true
${pom.name} Specification
${pom.version}
${basedir}/src/main/javadoc/overview.html
public
http://java.sun.com/j2se/1.5.0/docs/api
aggregate
false
aggregate
true
true
UTF-8
UTF-8
UTF-8
false
true
true
private
${pom.name} Specification ${pom.version}
${pom.name} Specification
${pom.version}
{{code}}
in a parent pom from a multi-module project containing a mojo artifact defined
like
{{code}}
* @goal java-resources
* @phase generate-sources
* @requiresDependencyResolution compile
{{code}}
still produces a similar stacktrace for me
{{code}}
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error extracting plugin
descriptor: 'Goal: java-resources already exists in the plugin descriptor for
prefix: some-prefix
Existing implementation is: some.package.JavaResourcesMojo
Conflicting implementation is: some.package.JavaResourcesMojo'
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:549)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error extracting
plugin descriptor: 'Goal: java-resources already exists in the plugin
descriptor for prefix: some-prefix
Existing implementation is: some.package.JavaResourcesMojo
Conflicting implementation is: some.package.JavaResourcesMojo'
at
org.apache.maven.plugin.plugin.AbstractGeneratorMojo.execute(AbstractGeneratorMojo.java:158)
at
org.apache.maven.plugin.plugin.HelpGeneratorMojo.execute(HelpGeneratorMojo.java:63)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
... 20 more
Caused by: org.apache.maven.plugin.descriptor.DuplicateMojoDescriptorException:
Goal: java-resources already exists in the plugin descriptor for prefix:
some-prefix
Existing implementation is: some.package.JavaResourcesMojo
Conflicting implementation
[jira] Commented: (MJAVADOC-145) If Javadoc is set to aggregate, the build fails inside a Maven plugin module
[ http://jira.codehaus.org/browse/MJAVADOC-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159312#action_159312 ] Vincent Siveton commented on MJAVADOC-145: -- Christian, it is not a Javadoc plugin error so try to open a new issue in MNG with your test case. Thanks! > 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
[jira] Commented: (MJAVADOC-145) If Javadoc is set to aggregate, the build fails inside a Maven plugin module
[ http://jira.codehaus.org/browse/MJAVADOC-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106865 ] Lukas Theussl commented on MJAVADOC-145: This seems to be a regression. We just had the same problem in doxia [1], it works with v 2.2. [1] http://www.nabble.com/can%27t-build-site-tf4408106s177.html > 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 >Priority: Critical > 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
[jira] Commented: (MJAVADOC-145) If Javadoc is set to aggregate, the build fails inside a Maven plugin module
[
http://jira.codehaus.org/browse/MJAVADOC-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=184118#action_184118
]
Martin Desruisseaux commented on MJAVADOC-145:
--
Is this bug really fixed? I'm using Maven 2.1 with {{maven-javadoc-plugin}} 2.5
in a project having a few Maven plugins, and still get "_Error extracting
plugin descriptor: Goal already exists in the plugin descriptor_" when running
{{mvn clean install site}}. The same command without the {{site}} goal works
fine. Removing the aggregated javadoc configuration from the {{}}
section in the root {{pom.xml}} fixes the build as well.
> 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
[jira] Commented: (MJAVADOC-145) If Javadoc is set to aggregate, the build fails inside a Maven plugin module
[ http://jira.codehaus.org/browse/MJAVADOC-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=184125#action_184125 ] Vincent Siveton commented on MJAVADOC-145: -- Martin, it should be. If you have an error, please create a new issue *with* a test project, I will have a look to. > 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
