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 ${bl
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/d
On Wednesday 02 July 2008 Kallin Nagelberg wrote:
> So what do you use for the version label in the root pom and the 'parent'
> tags of all the modules?
Just the version number, no variables. The release plugin will take care to
replace all version numbers correctly.
hth,
- martin
signature.as
We also use release plugin. During a release process the plugin asks for
versions of your modules and sets them for you.
Siarhei
On Wed, Jul 2, 2008 at 6: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 t
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 any
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. Th
On Mon, Jun 30, 2008 at 7:47 PM, <[EMAIL PROTECTED]> wrote:
> I remove the version from all of the module poms entirely and just have
> the multi module build pom have it. It works for me.
How do you handle the version in the section?
What about inter-module dependencies, do you use the depend
I remove the version from all of the module poms entirely and just have
the multi module build pom have it. It works for me.
-Chris
"Kallin Nagelberg" <[EMAIL PROTECTED]> wrote on 01/07/2008
04:55:00:
> Can anyone tell me what is the best/simplest way to maintain a version
> number across all
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.
Ideally, the version could be declared in one place (the superpom), and all
children would know to use it.
I'
