[
http://jira.codehaus.org/browse/MJAVADOC-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103634
]
Francois Fernandes commented on MJAVADOC-137:
---------------------------------------------
Got a problem with the aggregator here. Since javadoc 2.3 and the plugin
running as an aggregator, our build is broken. Due to the forking of a
lifecycle there are arifacts not beeing generated and referenced by other
modules. This results in a build failure. Up until now I was unable to create a
simple testcase which reproduces our problem. But here is the basic layout of
our project.
{noformat}
parent
+-- assembly
+-- submodule-A
+-- mod-A
+-- mod-B
+-- mod-C
{noformat}
In our case the mod-B produces a javadoc jar (using javadoc:jar) und creates a
assembly using the assembly (attached mojo) plugin. Both mojos are beeing
executed at the package phase. The assembly module has a dependecy to the mod-B
generated assembly as a zip file. If the javadoc mojo executes and forks the
lifecycle, the assembly hasn't been created yet. That means that building
assembly is failing due to the missing depenency of mod-B:zip.
> javadoc:javadoc always runs as "aggregator"
> -------------------------------------------
>
> Key: MJAVADOC-137
> URL: http://jira.codehaus.org/browse/MJAVADOC-137
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 2.3
> Reporter: Peter Hendriks
> Priority: Critical
>
> In version 2.2, javadoc aggregation was configurable using the configuration
> property "aggregate". In version 2.3, all javadoc goals got the @aggregator
> attribute added to its mojos (through a change in
> org/apache/maven/plugin/javadoc/AbstractJavadocMojo.java), and the goals now
> always run aggregated regardless of the configuration setting. This breaks
> our build as we require non-aggregated javadoc execution in our multi-module
> poms. Please fix this so this is once again configurable and backwards
> compatible with previous versions of the javadoc plug-in.
--
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
