So I guess the bottom line is 'use the release plugin'. If that's the only
effective way to accomplish it I wonder why there is anything associated
with the deploy phase by default.
On Thu, Jul 3, 2008 at 4:09 AM, Stephen Connolly <
[EMAIL PROTECTED]> wrote:
> FYI, You are not allowed to use ${blah} in the project/parent/version
> or project/version tags.
>
> There are bugs in Maven that mean it won't blow up in obvious ways if
> you do use ${blah} in those two tags... but it will blow up when you
> least expect it
>
> You can use ${blah} in
> project/dependencies/dependency/version
> project/dependencyManagement/dependencies/dependency/version
> project/build/plugins/plugin/version
> project/build/pluginManagement/plugins/plugin/version
> project/build/plugins/plugin/dependencies/dependency/version
>
> project/build/pluginManagement/plugins/plugin/dependencies/dependency/version
>
> On Wed, Jul 2, 2008 at 5:16 PM, Kallin Nagelberg
> <[EMAIL PROTECTED]> wrote:
> > So what do you use for the version label in the root pom and the 'parent'
> > tags of all the modules?
> > For inter-module dependencies ${project.version} seems to work..
> >
> > On Wed, Jul 2, 2008 at 2:52 AM, Martin Höller <[EMAIL PROTECTED]> wrote:
> >
> >> On Monday 30 June 2008 Kallin Nagelberg wrote:
> >> > Can anyone tell me what is the best/simplest way to maintain a version
> >> > number across all the poms in a multi-module project?
> >> >
> >> > They are all to be deployed with the same version every time.
> >>
> >> Use the maven-release-plugin to release your project. The plugin will
> take
> >> care to replace alle version occurences in any pom.xml file.
> >>
> >> hth,
> >> - martin
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
