maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gustavo Chaves (JIRA)" <>
Subject [jira] (MNG-624) automatic parent versioning
Date Sat, 10 Mar 2012 15:19:04 GMT


Gustavo Chaves commented on MNG-624:

There is a [discussion going on|]
in the maven users list which that seems relevant. Basically we're discussing how to avoid
all that POM editing that has to be done whenever you cut a (release or feature) branch. The
release plugin can do the editing for you, when you create a release branch, but it does not
help with feature branches that need to be reintegrated later. Also, all that POM editing
causes unecessary pain when you do merges, either rebase merges from trunk or reintegration
merges to trunk.

The idea being discussed there is based on the notion that the proper location to record artifact
version numbers is in the SCM tool and not in the POM. Basically, maven should be able to
derive the artifact version number from the actual SCM tag or branch that the working area
is associated to.

Note that there is not a complete solution yet due to missing funcionality treated in MNG-2971,
an issue from which this depends on.

> automatic parent versioning
> ---------------------------
>                 Key: MNG-624
>                 URL:
>             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
> 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:!default.jspa
For more information on JIRA, see:


View raw message