We're doing just that on the project I am working on; no version
specified in the child POMs, and it gets inherited from the parent POM.
So since the child modules get the version implicitly, it should work
just referring to ${project.version}? (haven't tried it myself)
-Rune
Erez Nahir wrote:
IMHO it should even be easier, just remove the <version> tag from the child
poms.
It will inherit the version from the parent.
Erez.
On Jan 29, 2008 9:52 PM, Manos Batsis <[EMAIL PROTECTED]> wrote:
I never actually managed to do that. IMHO that should be as easy as
<version>${project.parent.version}</version>
Oh well :-)
Cheers,
Manos
Mick Knutson wrote:
I am actually trying to use a property:
<org.delta.esp.dap.version>1.0.2</org.delta.esp.dap.version>
Then use that property in my child pom's:
${org.delta.esp.dap.version}
When I do an install and deploy it seems to work, but when I am doing a
site-deploy, the parameter is not found and I get errors.
Is there a better way?
On Jan 29, 2008 10:23 AM, Arthur Rodrigues Stilben <
[EMAIL PROTECTED]> wrote:
Is there a way to use the version of a parent project in its childrens
projects?
Arthur Rodrigues Stilben
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
