Your suggestion still requires me to edit pom.xml (and I don't even understand how that "pluginManagement" stuff works). What I'm really looking for is something which I can configure in MAVEN_HOME/conf/settings.xml or somewhere else. My goal is to avoid putting any settings into the POM, unless I want to override my custom default system-wide plugin settings.
I may misunderstand how exactly this works ... Thanks, Chris --- dan tran <[EMAIL PROTECTED]> wrote: > you can do that with build-->pluginManagement > element > > -D > > > On 1/3/06, [EMAIL PROTECTED] > <[EMAIL PROTECTED]> > wrote: > > > > I forgot to mention that this is related to Maven2 > > (2.0.1) > > > > --- [EMAIL PROTECTED] wrote: > > > > > I'd like to preconfigure a couple of plugins > (e.g. > > > javadoc, etc.), so that they don't have to be > > > configured in each single project. But it should > > > still > > > be possible to overwrite those settings (e.g. if > we > > > deal with a customer project which has very > specific > > > requirements for Javadoc, etc.). > > > > > > I looked at the settings descriptor and can not > find > > > anything related to plugins. Any hint on whether > > > this > > > is possible (and how) or not? > > > > > > Thanks, > > > Chris > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > 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]
