History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: MNG-3660
Type: Bug Bug
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Brian Lalor
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Maven 2

"combine.children='append'" not being honored in <reporting/>

Created: 09/Jul/08 03:39 PM   Updated: 05/Aug/08 11:16 PM
Component/s: POM, Plugins and Lifecycle, Inheritance and Interpolation
Affects Version/s: 2.0.9
Fix Version/s: 2.0.x

Time Tracking:
Not Specified

File Attachments: 1. File maven_config_bug.tgz (36 kb)


Complexity: Intermediate


 Description  « Hide
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:
<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>

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.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
There are no comments yet on this issue.