On 5/6/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
I have a project with multiple modules.
I'm keeping the version numbers synced.
This ends up with a lot of repetition of the version number:
<artifactId>tapestry-core</artifactId>
<packaging>jar</packaging>
<version>5.0.5-SNAPSHOT</version>
<parent>
<groupId>org.apache.tapestry</groupId>
<artifactId>tapestry-project</artifactId>
<version>5.0.5-SNAPSHOT</version>
<relativePath>../tapestry-project/pom.xml</relativePath>
</parent>
Looking at this again after reading Bryan's response... yes, you will
have to specify the version for the parent in every child pom. (In
the example above, I think the first <version> element is redundant as
it will get inherited from the parent.)
${project.version} is useful when there are dependencies between child
modules, such as if a webapp depends on a jar within the same
multi-module build.
And yes, the release plugin will take care of changing all of these
version elements to the released version for the tag, and then to the
next snapshot version.
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
