[jira] Moved: (MSITE-452) "combine.children='append'" not being honored in

["Jason van Zyl (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MSITE-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason van Zyl moved MNG-3660 to MSITE-452:
------------------------------------------

           Complexity:   (was: Intermediate)
          Component/s:     (was: Inheritance and Interpolation)
                           (was: Plugins and Lifecycle)
                           (was: POM)
        Fix Version/s:     (was: 2.2.x)
    Affects Version/s:     (was: 2.0.9)
                  Key: MSITE-452  (was: MNG-3660)
              Project: Maven 2.x Site Plugin  (was: Maven 2 & 3)

> "combine.children='append'" not being honored in <reporting/>
> -------------------------------------------------------------
>
>                 Key: MSITE-452
>                 URL: http://jira.codehaus.org/browse/MSITE-452
>             Project: Maven 2.x Site 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