jira-importer commented on issue #583: URL: https://github.com/apache/maven-javadoc-plugin/issues/583#issuecomment-2957336960
**[Hervé Boutemy](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=hboutemy)** commented some initial findings: - some blog posts about this combine feature: [in 2007](http://www.sonatype.com/people/2007/06/how-to-merge-sub-items-from-parent-pom-to-child-pom-in-a-maven-plugin-configuration-2/) about MNG-2591, [in 2011](http://www.sonatype.com/people/2011/01/maven-how-to-merging-plugin-configuration-in-complex-projects/) - [plexus-utils's Xpp3Dom source](http://plexus.codehaus.org/plexus-utils/xref/org/codehaus/plexus/util/xml/Xpp3Dom.html), where these attribute names come from, and [mergeXpp3() API javadoc](http://plexus.codehaus.org/plexus-utils/apidocs/org/codehaus/plexus/util/xml/Xpp3Dom.html#mergeXpp3Dom(org.codehaus.plexus.util.xml.Xpp3Dom, org.codehaus.plexus.util.xml.Xpp3Dom, java.lang.Boolean)) from 2011 blog post, > Last but not least, please note that the attributes described here to control merging only apply to plugin configuration. You cannot use these attributes on other elements of the POM. > javadoc being both a build plugin and a reporting plugin (ie. a maven-site-plugin plugin), this feature works only when it is used in build plugin configuration, not when used in reporting plugin IMHO, this is a feature request that should be moved to Maven 2.x when launched by Maven 2, or [maven-reporting-exec](http://maven.apache.org/shared/maven-reporting-exec) when run under Maven 3 WDYT? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
