maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From TenLeftFingers <>
Subject Making parent pom the absolute authority over it's children's versioning
Date Wed, 14 Aug 2013 09:01:29 GMT
I have a project laid out like this:

The parent defines its own version:
And child-project two has in it's pom:
The issue I'm having is that I want the person doing the builds to only have
to change the <version> in the parent-project. I want the child-projects to
*take* their version from there so that he only has to make one change. But
if I change the child to declare it's own version as:


this actually takes it from the version declared in the child .pom. Yet, if
I don't delcare the version in the child pom it won't know which version of
the parent to go for... 

Am I trying to do the impossible? I don't want to have every child's pom
modified to go from SNAPSHOT to release because in reality the projects are
much larger.

Thanks & regards,

View this message in context:
Sent from the Maven - Users mailing list archive at

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message