maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jörg Hohwiller (JIRA) <>
Subject [jira] (MNG-624) automatic parent versioning
Date Fri, 07 Mar 2014 22:48:06 GMT


Jörg Hohwiller commented on MNG-624:

while this feature would be still desirable there is a workaround possible with consumer-maven-plugin:
Please note that the plugin will move out of sandbox in the future so try mojo instead of
sandbox if the link stopped working:

What you can now do is keep all the versions of your parent POMs fixed and consider them as
development artifacts that will not be relevant for end-users of your artifacts. If you use
consumer-maven-plugin it will generate a "minified" POM with variables and dependencies resolved
and without parent POM relation, etc. This allows you to define variables, dependency management,
etc. in your parent POMs but bump the final GAV coordinates and dependencies of your child/leaf
modules on install/deploy.

Simply check-out and install this plugin. Then add this to your toplevel POMs build-section:

I hope that the plugin will move out of sandbox and be released soon.

If you have any feedback please let us know (ideally on MOJOs dev mailing list).

> 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: Issues to be reviewed for 4.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 was sent by Atlassian JIRA

View raw message