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

["Anders Kr. Andersen (JIRA)" <ji...@codehaus.org>]

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

Anders Kr. Andersen commented on MNG-624:
-----------------------------------------

A solution could be just to accept this version fact in maven

And then add a command to update siblings with a trunk version number.

I sit with a large project where we have the same issue with <url>.
We want to make a site for each version == for each maven coordinate.

Here I have decided that trunk is called URL=http://my.site.server/sites/..../trunk
And the coresponding tagged versions is called URL=http://my.site.server/sites/..../tags/artifactId-vvvv

To deal with this I am going to make a pom-maintain-maven-plugin
And have this plugin being able to maintain, SITE-URL, parent version, repository URL, 

For a long time I was experimenting with expression-language. ${project.version} or  ${my-url-path} etc
I ended up dropping the expression language solution

Because I actually also want to force some naming standard into the artifacts. 
Many fields can be calculated by the projects location in the VCS etc.
I am thinking about some groovy stuff to express rules.


> 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: Ralph Goers
>            Priority: Blocker
>             Fix For: 2.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 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