maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "LEONID ILYEVSKY (JIRA)" <j...@codehaus.org>
Subject [jira] Issue Comment Edited: (MNG-624) automatic parent versioning
Date Thu, 04 Mar 2010 15:31:03 GMT

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

LEONID ILYEVSKY edited comment on MNG-624 at 3/4/10 9:29 AM:
-------------------------------------------------------------

Thanks Abhishekh, this looks like an interesting workaround.

To solve the issue of undefined ${currentVersion} variable in the deployed pom I am trying
to put the profile description right there in pom.xml of the parent project, not in the separate
profiles.xml file. Then it is deployed to the repository. However, it does not actually solve
anything.
I guess, as the last resort, I will have to use the "versions" plugin.

On the other note, I agree with Robert that "<relativePath> should be enough to specify
a parent POM.". Maybe we will see this fixed in the near future.

      was (Author: lilyevsky):
    Thanks Abhishekh, this looks like a great workaround, hopefully it will solve my problem.

To solve the issue of undefined ${currentVersion} variable in the deployed pom I am trying
to put the profile description right there in pom.xml of the parent project, not in the separate
profiles.xml file. Then it is deployed to the repository.
I am not sure though if this actually solves anything.
I guess, as the last resort, I will have to use the "versions" plugin.

On the other note, I agree with Robert that "<relativePath> should be enough to specify
a parent POM.". Maybe we will see this fixed in the near future.
  
> 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

        

Mime
View raw message