[
https://jira.codehaus.org/browse/MNG-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290606#comment-290606
]
Christian Lewold commented on MNG-624:
--------------------------------------
This is a valid issue, but there is a simple workaround:
{code:title=parent pom.xml}
<project ....>
<properties>
<currentVersion>0.0.2-SNAPSHOT</currentVersion>
</properties>
<artifactId>parent</artifactId>
<groupId>my.group</groupId>
<version>${currentVersion}</version>
<modules>
<module>../child</module>
</modules>
....
</project>
{code}
and in all childs you use
{code:title=child pom.xml}
<project ....>
<parent>
<groupId>my.group</groupId>
<artifactId>parent</artifactId>
<version>${currentVersion}</version>
<relativePath>../parent/pom.xml</relativePath>
</parent>
<artifactId>child</artifactId>
....
</project>
{code}
This way you just need to change the version once within the properties section
of the parent pom.
Hope this helps some out there, as I was searching for a solution for days.
Chris
> automatic parent versioning
> ---------------------------
>
> Key: MNG-624
> URL: https://jira.codehaus.org/browse/MNG-624
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Inheritance and Interpolation
> Reporter: Brett Porter
> Assignee: Ralph Goers
> Priority: Blocker
> Fix For: 3.1
>
> Attachments: MNG-624-maven-2.0.x-r507648.patch, MNG-624-tests.tar.gz
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> (this may be bumped to 2.1 or even made WON't FIX as it is contentious - see
> MNG-521)
> currently, you have to specify the parent version when extending which makes
> a project stand alone very easily, but has the drawback of being a
> maintainance problem when you start development on a new version. Tools can
> help, but it would be nice not to have to rely on them.
> One alternative is to allow the parent version to be omitted, and when it is
> it is assumed you want the latest. The parent is used from the reactor or the
> universal source directory. IT may also be read from a LATEST in the
> repository though this is contentious - it may be better to simply fail in
> that environment and require builds be in a known checkout structure for
> building individual projects.
> This also introduces the need for tool support to populate the version on
> release and deployment for reproducibility.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
