This does not work.
If you think about it you can see why.
You would define 'sensage-version' in the parent pom and use it in all the
children. The problem is that as it is parsing the child pom, maven has to
find the parent. To do that, it looks in the <parent> section and has to use
the value of "sensage-version'.
Its a classic catch-22 situation. You can't find the parent without the
value of 'sensage-version' and you you can't find the value of
'sensage-versin' without the parent.
-- Lee
On 11/14/06, Christian Goetze <[EMAIL PROTECTED]> wrote:
I recently asked the question below, but no answer.
I was wondering whether I really need to edit all pom.xml files in all
my project whenever I bump version numbers.
I'm still new at this, so if this is a trivial question, please bear
with me...
--
cg
Christian Goetze wrote:
> Why can't I do this:
>
> <project>
> <modelVersion>4.0.0</modelVersion>
>
> <!-- This project belongs to ... -->
> <parent>
> <groupId>com.sensage</groupId>
> <artifactId>sensage</artifactId>
> <version>${sensage-version}</version>
> </parent>
>
> I do run "mvn -Dsensage-version=3.6"...
>
> It works fine when I run from the top of the project down.
> --
> cg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
-- Lee Meador
Sent from gmail. My real email address is lee AT leemeador.com
