[jira] Commented: (MNG-624) automatic parent versioning

["Luke Lu (JIRA)" <ji...@codehaus.org>]

    [ https://jira.codehaus.org/browse/MNG-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=273902#comment-273902 ] 

Luke Lu commented on MNG-624:
-----------------------------

bq. Would the approach of denoting the parent pom by relativepath, as suggested above, work for you?

No. relativePath doesn't seem to make any sense for deployed artifacts (i.e., no source/build tree). e.g., if you have a client and a server modules with a common parent and that downstream projects need to depend on the client jar, an explicit version (either client version or the parent version) in the client pom is required to get to the right parent pom.

> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira