Hello, I believe the usual thing to do is declare one parent pom for all projects in your organization and put "globals" in there. Then, all your poms need to declare it or one of its children as <parent>.
That's how we do it at elca. Yours, David > -----Original Message----- > From: Olivier Dehon [mailto:[EMAIL PROTECTED] > Sent: 30 April 2008 14:05 > To: Maven Users List > Subject: Re: Global settings for a plugin > > I haven't tried, but I believe you could have a look at the > <pluginManagement> section, and add the global configuration for the > eclipse plugin in your super pom. > > -Olivier > > On Wed, 2008-04-30 at 11:19 +0300, Eugeny N Dzhurinsky wrote: > > Hello everybody! > > > > Could you please explain how can I provide some specific > settings for a > > plugin, which would apply to any Maven project? For > instance, I need to > > configure the Eclipse plugin to add the project version to > a generated > > project, currently I need to provide each and every POM > file with the settings > > like below: > > > > <plugin> > > <groupId>org.apache.maven.plugins</groupId> > > <artifactId>maven-eclipse-plugin</artifactId> > > <configuration> > > > <addVersionToProjectName>true</addVersionToProjectName> > > </configuration> > > </plugin> > > > > and this is a bit annoying. > > > > I learned settings.xml description and found there's no way > to specify plugin > > settings in it. Any advice? > > > > > --------------------------------------------------------------------- > 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]
