[
http://jira.codehaus.org/browse/MJAVADOC-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=265345#action_265345
]
Herve Boutemy commented on MJAVADOC-285:
----------------------------------------
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,
bq. 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?
> "combine.children='append'" not being honored in <reporting/>
> -------------------------------------------------------------
>
> Key: MJAVADOC-285
> URL: http://jira.codehaus.org/browse/MJAVADOC-285
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
> Reporter: Brian Lalor
> Attachments: maven_config_bug.tgz
>
>
> I'm trying to combine multiple maven-javadoc-plugin configuration stanzas
> such that child modules can append {{<link/>}} elements to those specified by
> the parent. This supposedly can be done by adding the attribute
> "{{combine.children='append'}}" to the {{<links/>}} element in the child
> module's {{<configuration/>}} element, like so:
> {code:xml}
> <reporting>
> <plugins>
> <plugin>
> <artifactId>maven-javadoc-plugin</artifactId>
> <configuration>
> <links combine.children="append">
>
> <link>http://static.springframework.org/spring/docs/2.5.x/api/</link>
> </links>
> </configuration>
> </plugin>
> </plugins>
> </reporting>
> {code}
> What actually happens is that the child module's configuration reflects only
> the single {{<link/>}}, and not any {{<link/>}} elements also defined in the
> parent. The output of {{mvn help:effective-pom}} bears this out. Putting
> the plugin configuration into the {{<build/>}} element instead of
> {{<reporting/>}} shows the correct combination occurring (except that the
> report is obviously not configured that way...).
> The attached tarball contains a barebones multi-module project that shows
> this bug, as well as the output of {{help:effective-pom}} in separate files.
> I've also included the output of {{mvn -X help:effective-pom}} in the file
> {{build.log}}.
--
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
