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

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

    [ http://jira.codehaus.org/browse/MNG-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114699 ] 

Ian commented on MNG-624:
-------------------------

Allowing variable substitution in the parent section would fix  MNG-3070 as well.  I've encountered the same problem as Prasad Kashyap with labelling builds on the fly.  This also has a side effect that if you have a hierarchical directory structure you can't guarantee to be able to build from an arbitrary sub directory.  I *think* that what is happening is like this - imagine parent project A with sub project B which is dependent on C which is also a child of A.:

/projectA
   /projectB child of projectA dependent on projectC
   /projectC child of projectA

If you build from directory B it resolves C as a binary artifact, looks the parent pom of C up in the repository, fails to make the variable substitution and then explodes.   This makes it impossible to label builds on the fly AND build from any directory without editing all your pom.xml files.

> automatic parent versioning
> ---------------------------
>
>                 Key: MNG-624
>                 URL: http://jira.codehaus.org/browse/MNG-624
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Inheritance and Interpolation
>            Reporter: Brett Porter
>            Assignee: Jason van Zyl
>            Priority: Blocker
>             Fix For: 2.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.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira