Indeed it get's merged. But only if you want it to: if you leave the
configuration out of the second POM and only declare
the groupId and artifactId, it takes the configuration of the first POM.
I'm not sure where I found this, but I do recall reading this somewhere... It
could've been the cargo-website...
Roland
On Tuesday 27 June 2006 19:15, Stefan Hübner wrote:
> This would meen, that the configuration contents of the second pom
> gets merged with that from parent pom. Is any documentation available
> about this feature?
>
> 2006/6/27, Roland Asmann <[EMAIL PROTECTED]>:
> > Here's a sample of 2 of my POM's:
> >
> > Parent:
> > <build>
> > <pluginManagement>
> > <plugins>
> > <plugin>
> > <groupId>org.codehaus.cargo</groupId>
> >
> > <artifactId>cargo-maven2-plugin</artifactId> <configuration>
> > <container>
> >
> > <containerId>jboss4x</containerId> <home>${appserver.home}</home>
> > <output>${project.build.directory}/jboss4x.log</output> </container>
> > <configuration>
> > <type>standalone</type>
> >
> > <home>${project.build.directory}/jboss4x</home> </configuration>
> > <wait>false</wait>
> > </configuration>
> > <executions>
> > <execution>
> > <id>start</id>
> >
> > <phase>test-compile</phase> <goals>
> >
> > <goal>start</goal> </goals>
> > </execution>
> > <execution>
> > <id>stop</id>
> > <phase>test</phase>
> > <goals>
> > <goal>stop</goal>
> > </goals>
> > </execution>
> > </executions>
> > </plugin>
> > </plugins>
> > </pluginManagement>
> > </build>
> >
> > Child:
> > <build>
> > <plugins>
> > <!-- Plugins that are already configured in the parent
> > POM --> <plugin>
> > <groupId>org.codehaus.cargo</groupId>
> > <artifactId>cargo-maven2-plugin</artifactId>
> > <!-- Extend the configuration -->
> > <configuration>
> > <configuration>
> > <deployables>
> > <deployable>
> >
> > <groupId>${groupId}</groupId> <artifactId>my-ear</artifactId>
> > <type>ear</type> </deployable>
> > </deployables>
> > </configuration>
> > </configuration>
> > </plugin>
> > </plugins>
> > </build>
> >
> >
> > And this works perfectly for me...
> >
> > Roland
> >
> > On Tuesday 27 June 2006 18:45, Stefan Hübner wrote:
> > > I think, that inheriting plugin configuration, whether by <plugins> or
> > > <pluginManagement>, only inherits full configurations. That meens,
> > > whenever you reference a plugin and define a configuration-element
> > > inside, its inherited configuration will be lost.
> > >
> > > That's just my experience (and I think a was reading about this
> > > behaviour, but not sure where or when) and I'd appreciate any other
> > > opinions :-)
> > >
> > > --Stefan
> > >
> > > 2006/6/27, Brad Harper <[EMAIL PROTECTED]>:
> > > > Stefan:
> > > >
> > > > Until recently, I've had the expectation that plugin configurations
> > > > *should* be inherited by default. Apparently not.
> > > >
> > > > Another poster (Dan Tran) has recommended using <pluginManagement> to
> > > > control build configuration inheritance. "Better Builds" doesn't even
> > > > reference the element.
> > > >
> > > > I've tried using <inherited>true</inherited> in several positions,
> > > > now including within <pluginManagement>, but without success.
> > > >
> > > > Brad
> > > >
> > > > -----Original Message-----
> > > > From: Stefan Hübner [mailto:[EMAIL PROTECTED]
> > > > Sent: Tuesday, June 27, 2006 10:59 AM
> > > > To: Maven Users List
> > > > Subject: Re: plugin configuration inheritance?
> > > >
> > > >
> > > > Hi Brad,
> > > >
> > > > see comment inside:
> > > >
> > > > 2006/6/27, Brad Harper <[EMAIL PROTECTED]>:
> > > > > Are plugin configurations inherited/cumulative? E.g., given
> > > > > project 'A' descriptor containing
> > > > >
> > > > > <build>
> > > > > <plugins>
> > > > > <plugin>
> > > > > <artifactId>P</artifactId>
> > > > > <configuration>
> > > > > blah-1
> > > > >
> > > > > and sub-project/module 'B', with descriptor containing
> > > > >
> > > > > <build>
> > > > > <plugins>
> > > > > <plugin>
> > > > > <artifactId>P</artifactId>
> > > > > <configuration>
> > > > > blah-2
> > > > > blah-3
> > > > >
> > > > > Does plugin 'P' see 'blah-1' in its configuration?
> > > >
> > > > I would assume, it doesn't. Not sure though.
> > > >
> > > > --Stefan
> > > >
> > > > ---------------------------------------------------------------------
> > > > 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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
