I've noticed that using the pluginmanagment the plugin is not associated to lifecycle events by default in the children. Is there a way to make this happen so that I don't have to declare the plugin in every child?
On Wed, Jul 2, 2008 at 3:22 PM, Kallin Nagelberg <[EMAIL PROTECTED]> wrote: > great, thanks for the help > > > On Wed, Jul 2, 2008 at 2:21 PM, Dennis Lundberg <[EMAIL PROTECTED]> > wrote: > >> You can put your plugin configuration in a pluginManagement [1] element >> inside the build element >> build >> pluginManagement >> plugins >> plugin >> >> This only configures the plugins, but don't execute them. >> >> [1] >> http://maven.apache.org/ref/current/maven-model/maven.html#class_pluginManagement >> >> >> Kallin Nagelberg wrote: >> >>> I'm trying to create a multi-module project that uses the same plugin for >>> source generation. >>> To make it as simple as possible I have a parent POM that contains the >>> configuration of the plugin in a >>> >>> <build> >>> <plugins> >>> <plugin> >>> >>> tag. >>> >>> My problem is that the plugin is being executed when the parent is built, >>> even though it is of type 'pom', and i only want to use it to aggregate >>> the >>> modules and define some standard config. Is there a way to configure a >>> plugin and prevent it's execution? >>> >>> >> >> -- >> Dennis Lundberg >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >
