On 4/10/07, DI Kurt Edegger <[EMAIL PROTECTED]> wrote:
Hi,
I do have a question regarding referencing the parent pom of a multi module project as
described in chapter 3 of "Better Builds With Maven".
If a project consists of multiple modules (e.g.: api, core, model, ..), these
modules reside in sub-directories of a top level directory. Each module has
it's own pom.xml and the top level directory
holds a pom.xml where project global settings are defined. Each module's pom
sets a reference to the parent, by defining the following snippet:
<parent>
<groupId/>
<artifactId/>
<version/>
</parent>
Is there a way to reference the parent module without explicitly specifying the
version? In a scenario where all modules are released at the same time, their
version should be the same, so the
application version is defined in the parent pom.xml. But whenever this version
changes, all references in the sub-modules need to be updated.
It's cumbersome to manually edit every pom.xml in every sub-directory, just
because the application version has changed.
Do I miss something here?
Yes: http://maven.apache.org/plugins/maven-release-plugin/
The plugin will take care if the POM updates for you.
Jerome
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
