Didn't know about that before but I gave it a shot. It appears that my problem is simply that I'm trying to use the plugin at the parent project level and thus maven assumes it needs to execute it for the child objects as well.
It would appear that the only solution is to pass "-N" at the commandline to prevent the recursion into the subprojects. I tried setting up a profile with an empty <modules> tag but it appears to assume that empty means it should use the modules defined at the root. So is there any other way you can think of to prevent the recursion without passing -N at the commandline? MAR -----Original Message----- From: Mike Perham [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 28, 2006 9:27 AM To: Maven Users List Subject: RE: Plugin Question (plugin executing multiple times when it shouldn't) Mark, are you familiar with the <build><pluginManagement> section? If you are just trying to configure your plugin but will execute it by hand via command-line, you want to use <pluginManagement>, not <plugins>. > -----Original Message----- > From: Russell, Mark [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 28, 2006 10:02 AM > To: Maven Users List > Subject: RE: Plugin Question (plugin executing multiple times > when it shouldn't) > > Ok a further piece of information. Not sure how to deal with this... > > The setup: > ProjectA > Child-projectA > Child-projectB > > The plugin is configure in the pom of ProjectA in the <build><plugins> > section. It appears that due to inheritance the 2 child projects are > getting the plugin as well, and thus the plugin goal executes once for > each project (thus the 3 times) > > Is there any way around this? IE prevent the child projects from > knowing anything about the plugin? > > MAR > > -----Original Message----- > From: Russell, Mark [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 28, 2006 8:52 AM > To: Maven Users List > Subject: RE: Plugin Question (plugin executing multiple times when it > shouldn't) > > Another piece of info... > > If I take the exact same configuration for the plugin and move it to a > pom that uses "jar" packaging, the goal executes exactly ONE time. > > In both cases I use the following commandline: > mvn pluginprefix:goal -DuserId=xxx -Dpassword=xxx > > Am I running into some weird bug with "pom" packaging projects? > > MAR > > -----Original Message----- > From: Napoleon Esmundo Ramirez [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 27, 2006 7:32 PM > To: Maven Users List > Subject: Re: Plugin Question (plugin executing multiple times when it > shouldn't) > > Hello, > > You don't have to bind it to a phase when you call it in the > commandline. > The pom fragment doesn't look wrong at all. There must be something > wrong > in the code itself. > > Cheers, > Nap > > On 6/28/06, Russell, Mark <[EMAIL PROTECTED]> wrote: > > > > I have a plugin that I will generally call directly from the > commandline > > (though I don't want to preclude putting it in the lifecycle). > > Currently this plugin is configured inside a pom project (ie the > project > > itself uses pom for the packaging) > > > > > > > > When I invoke the plugin from the commandline it seems to > be executing > 3 > > times. > > > > > > > > The configuration from the pom.xml: > > > > > > > > <build> > > > > <plugins> > > > > <plugin> > > > > <groupId>com.comverse.mvn.plugins</groupId> > > > > <artifactId>my-maven-plugin</artifactId> > > > > <configuration> > > > > <hostName>some.host.com</hostName> > > > > <userId>${userId}</userId> > > > > <password>${password}</password> > > > > </configuration> > > > > </plugin> > > </plugins> > > > > </build> > > > > > > > > Any idea on why this executes three times? Do I have to > bind it to a > > specific phase even though I'm only calling it on the commandline? > > > > > > > > > > > > Mark Russell > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > 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]
