maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abhishekh Padmanbhan (JIRA)" <>
Subject [jira] Issue Comment Edited: (MNG-624) automatic parent versioning
Date Wed, 17 Feb 2010 17:27:10 GMT


Abhishekh Padmanbhan edited comment on MNG-624 at 2/17/10 11:25 AM:

Yes you are correct this breaks the transitive dependency resolution when these POM's are
used as dependencies in other projects. We almost always do not benefit from the transitive
dependencies on our internal projects anyway. Any such tightly coupled modules are placed
usually as sub modules which I guess would be atypical with open source development scenario.

      was (Author: abhishekhp):
    I think in general to support transitive dependency resolution when these POM's are used
as dependencies in other projects (modules not in the project hierarchy) it is usually necessary
to have redundant property in the ROOT pom.xml as shown below.



This way the currentVersion property gets resolved outside the scope of the profiles.xml file.

Although this is redundant in a way as we have the currentVersion defined in 2 places its
always better that having it changed in all of the submodules every time.
> 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 contact one of the administrators:
For more information on JIRA, see:


View raw message