Re: configuring a plugin while preventing its execution
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 >>> >>> >>> >>> >>> >>> 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] >> >> >
Re: configuring a plugin while preventing its execution
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 >> >> >> >> >> >> 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] > >
Re: configuring a plugin while preventing its execution
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 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]
configuring a plugin while preventing its execution
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 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?
configuring a plugin.
I want to use the javadoc goal of the maven-javadoc-plugin. But I want to run it in three different ways 1. generate a .properties file from a source java file, using a custom doclet. My doclet expects 3 command line parameters. 2. generate javadoc for all other java files (excluding the java files of step1) So I want to run the goal javadoc, two times, but with different configuartion. I know that once needs to use the , , , , but I want to know what should be the order of these? and go here this needs to be written twice bu i get a parse error. maven expects a inside a Also how do i pass command line parameter values to my doclet. With ANT, this was a paramname, value pair passed. But iwth maven we have elemnt. where will te param value go? -- Regards, Niranjan Deshpande "Shut yourself from the world and create the reality you want"
Configuring a plugin from inside a different plugin?
Is it possible to configure a plugin via code inside another plugin? Specifically I have a plugin that generates a bunch of source code, and based on its output it needs to configure the manifest of the jar that will be created. Thus my custom plugin basically needs to configure the maven-jar-plugin at runtime, but before the jar plugin executes. Anyone know how I might do something like that? Mark Russell
