You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Kevin Sheehan (JIRA)" <ji...@codehaus.org> on 2006/05/11 19:18:42 UTC

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

    [ http://jira.codehaus.org/browse/MNG-624?page=comments#action_65208 ] 

Kevin Sheehan commented on MNG-624:
-----------------------------------

...and another two cents...

It appears (from my tests) that the <parent></parent> element is absolutely the first tag accted upon when encountered in the POM. That makes sense HOWEVER... I would like to read / load / substitute variables in that section.

i.e. 
mvn -Dapp.version=1.0-SNAPSHOT compile

with POM that contains
...
    <parent>
        <artifactId>artifact-id</artifactId>
        <groupId>group-id</groupId>
        <version>${app.version}</version>
    </parent>
...

should be the same as
...
    <parent>
        <artifactId>artifact-id</artifactId>
        <groupId>group-id</groupId>
        <version>1.0-SNAPSHOT</version>
    </parent>
...

but is not as the <version>${app.version}</version> is LITERALLY substituted rather than recognizing this as an instance of variable substitution.

Allowing variable substitution in the <parent></parent> section should provide enough flexibility to successfully close this.

> automatic parent versioning
> ---------------------------
>
>          Key: MNG-624
>          URL: http://jira.codehaus.org/browse/MNG-624
>      Project: Maven 2
>         Type: Improvement

>   Components: Inheritence and Interpolation
>     Reporter: Brett Porter
>     Assignee: Brett Porter
>     Priority: Blocker
>      Fix For: 2.1

>
> Original Estimate: 4 hours
>         Remaining: 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