maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Fox (JIRA)" <>
Subject [jira] Commented: (MNG-624) automatic parent versioning
Date Thu, 12 Nov 2009 21:28:56 GMT


Brian Fox commented on MNG-624:

No one is disagreeing that this wouldn't be useful. The fact is we have Maven 2 right now
and in my experience, it turns out not to be a huge problem in a "maven normalized" project.
Therefore, some guidance can be given how to minimize the impact. If that's "proselytizing",
so be it. 

Anyway, we ARE working on this, but it's not as simple as it appears at first glance. The
poms must be interpolated before they are deployed to a repository. This is contingent upon
knowing exactly where on disk to find the parent pom. The relativePath currently only points
to the root of the parent project. Since that parent project also needed to be interpolated,
we need to discover the interpolated version of it in that folder. Most of the time this would
be /target but not if someone used the build.outputDirectory to change to something else.
Finding this location in a manner that respects people's ability to customize their layout
from "maven normal" and at the same time being FAST is not easy to do in M2.

> automatic parent versioning
> ---------------------------
>                 Key: MNG-624
>                 URL:
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Inheritance and Interpolation
>            Reporter: Brett Porter
>            Assignee: Ralph Goers
>            Priority: Blocker
>             Fix For: 2.x
>         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 contact one of the administrators:
For more information on JIRA, see:


View raw message