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

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

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

Eduardo Souza commented on MNG-624:
-----------------------------------

Hello,

I work in a product that includes 150 projects. The projects are divided into groups of four projects that comprise a system module.

Today we work with maven 2.2.1 modified to not check the version of the parent project. When conducting any activity the child accesses the tag design <relativepath> and see who is the parent project that he is using. With this modification we can work normally without having to do a checkout of nearly 1GB of projects to replace the version with each new release.

>From my point of view, when working this way, the parent project does control projects.

The idea of declaring the version of the parent in the projects is valid when it has a small number of projects, but when you have a large number of projects, this activity is not feasible.

> automatic parent versioning
> ---------------------------
>
>                 Key: MNG-624
>                 URL: http://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.
-
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