It bites in quite a lot of places. I wanted to define one "execution" of the build-helper-maven-plugin in a parent pom and another in one of it's children then have the two merged together. However, Maven overrode the parent configuration in the child.
Given that some sections of the pom (eg dependencies, properties) merge so seamlessly it is disappointing to discover sections which don't. Perhaps future versions of Maven will improve things. c On Sat, Oct 2, 2010 at 3:41 PM, Marshall Schor <[email protected]> wrote: > > > On 10/2/2010 7:42 AM, Benjamin Bentmann wrote: >> Xavier D. wrote: >> >>> My pom structure is: pom.xml has a parent: parent-pom.xml. >>> >>> Both have a<resources> section to include files. >>> >>> The (child) pom.xml is executed directly and has the effect of only copying >>> the child's resources. Commenting out this resource section, results in >>> the parent's resources being copied. >> >> This is expected behavior, <resources> given in a child POM are not merged >> with <resources> in the parent but completely override those. > > I'm curious as to why this design decision was taken, versus an approach which > allows merging, or perhaps some kind of user (pom - specified) choice. > > I was "bitten" by this also. > > -Marshall Schor > >> >> >> Benjamin >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
