[Regression] Configuration of m-javadoc-p at reportSet level is not taken into
account
--------------------------------------------------------------------------------------
Key: MNG-4852
URL: http://jira.codehaus.org/browse/MNG-4852
Project: Maven 2 & 3
Issue Type: Bug
Affects Versions: 3.0
Environment: Apache Maven 3.0 (r1004208; 2010-10-04 13:50:56+0200)
Java version: 1.6.0_21
Reporter: Julien HENRY
In the JWebUnit project I am using Javadoc aggregation and I put configuration
at the <reportSet> level. But after upgrading to Maven 3 the configuration is
not taken into account. Moving the configuration to the top level/common
section works but may not be acceptable for all project especially when a
different configuration for each reportSet is needed.
{code:xml}
<reporting>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<version>2.7</version>
<configuration>
<!-- What is put here is taken into account -->
</configuration>
<reportSets>
<reportSet>
<id>aggregate</id>
<configuration>
<!-- What is put here is NOT taken into account -->
</configuration>
<reports>
<report>aggregate</report>
</reports>
</reportSet>
</reportSets>
</plugin>
</plugins>
</reporting>
{code}
- with Maven 2 I am using m-site-p 2.1.1
- with Maven 3 I am using m-site-p 3.0-beta-2
I don't know if this is a M3 or a m-site-p regression.
--
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
