[ http://jira.codehaus.org/browse/MSITE-512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237559#action_237559 ]
Julien HENRY commented on MSITE-512: ------------------------------------ You can try with JWebUnit trunk: https://jwebunit.svn.sourceforge.net/svnroot/jwebunit/trunk/ But you have to configure a toolchains: http://jwebunit.sourceforge.net/building-maven.html Then run mvn clean site on the top level folder. > [Regression] Configuration of m-javadoc-p at reportSet level is not taken > into account > -------------------------------------------------------------------------------------- > > Key: MSITE-512 > URL: http://jira.codehaus.org/browse/MSITE-512 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Affects Versions: 3.0-beta-2 > Environment: Apache Maven 3.0 (r1004208; 2010-10-04 13:50:56+0200) > Java version: 1.6.0_21 > Reporter: Julien HENRY > Assignee: Olivier Lamy > > 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