[
http://jira.codehaus.org/browse/MJAVADOC-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125842
]
Wendy Smoak commented on MJAVADOC-137:
--------------------------------------
I added an integration test for this in r632888. Unfortunately, I can't figure
out how to get it to fail when javadoc plugin's 'jar' goal is run from the pom.
http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-javadoc-plugin/src/it/MJAVADOC-137/
If you check that out and execute 'mvn javadoc:jar' you do *not* get the
javadoc jars. It says:
INFO] [javadoc:jar]
[INFO] Not executing Javadoc as the project is not a Java classpath-capable
package
Change pluginManagement to version 2.2 and it will work.
Any idea how to demonstrate that from a pom? I really don't want to touch the
code without a failing automated test.
> 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
> Fix For: 2.4
>
>
> 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
