[MJAVADOC-137] javadoc:javadoc always runs as "aggregator"

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.3
• Fix Version/s: 2.4
• Assignee: Unassigned
• Reporter: Peter Hendriks
• Created: 26/Jul/07 07:42
• Updated: 30/Aug/21 17:53
• Resolved: 05/Mar/08 20:35

Description

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.

Issue Links

• is depended upon by: MJAVADOC-141 regression: Adding "jar" execution to the parent of a multi-module javadoc plugin causes "recursive invocations" error
• is related to: MNG-2184 Possible problem with @aggregator and forked lifecycles
• is related to: MJAVADOC-104 Javadoc of generated sources is not generated when aggregate=true
• is related to: MJAVADOC-111 Can't release when I use javadoc aggregate/groups
• is related to: MJAVADOC-119 Aggregate does not work for multiple module project when doing install.
• is related to: MJAVADOC-171 Modules in multi-module projects are "built" too often
• relates to: MJAVADOC-161 performRelease=true breaks install/deploy with multimodule projects
• relates to: MJAVADOC-194 javadoc 2.4 does not [build-helper:add-source {execution: add-source}] when aggregating a javadoc for a project