On 29 July 2011 22:02, Wayne Fay <[email protected]> wrote:
>
> > When I decide I want the new version of a plugin I want to update all
> > projects
> > at once instead of having to open each pom and change it by hand. From
> > your response I am guessing it is expected to use properties to control
> > this.
>
> Or use pluginManagement in a shared parent...
>
Definitely, the shared parent is your friend if you want manage plugin
versions in one central place. The shared parent is often called
corporate pom. Define all plugins in the pluginManagement section in
the corporate pom. You can also specify plugin versions as properties,
then you can easily overwrite version in the specific project:
<properties>
<acme-corporate-pom.cleanVersion>2.4.1</acme-corporate-pom.cleanVersion>
</properties>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-clean-plugin</artifactId>
<version>${acme-corporate-pom.cleanVersion}</version>
</plugin>
The same concept can be used to customize plugins configuration (can
be easily overwritten):
<properties>
<!-- Automatically assign submodules the parent version (m-release-p) -->
<autoVersionSubmodules>true</autoVersionSubmodules>
</properties>
--
Marcin Kuthan
Maven For Enterprise - http://code.google.com/p/m4enterprise/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
