Thanks Wayne, that solved the first problem... now on to the next :) Now it seems that the properties read by the plugin are not inherited by the child modules. I'm going to do some more checking to confirm this, and then maybe dig around in the source to find out what's going on, but if anyone has already seen this problem maybe there is already a solution. I'm guessing there's probably not much I can do about it if Maven is resolving properties for child projects before it is running plugins in the parent.
Cheers, Kevin On Sun, 2007-11-18 at 23:00 -0600, Wayne Fay wrote: > Did you try adding <inherited>false</> to the plugin declaration? > > Wayne > > On 11/18/07, Kevin Stembridge <[EMAIL PROTECTED]> wrote: > > Hi all, > > Is anyone using the properties-maven-plugin in a multi-module project? > > > > If I configure the plugin in my parent project, how do I stop the child > > modules from inheriting it and trying to run it as well? > > > > Cheers, > > Kevin > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email >
<<attachment: smiley-3.png>>
