[jira] Updated: (CONTINUUM-1637) Releasing a project should not replace variables in SCM section of the POM

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

     [ http://jira.codehaus.org/browse/CONTINUUM-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated CONTINUUM-1637:
------------------------------------

    Fix Version/s: 1.x

> Releasing a project should not replace variables in SCM section of the POM
> --------------------------------------------------------------------------
>
>                 Key: CONTINUUM-1637
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-1637
>             Project: Continuum
>          Issue Type: Improvement
>          Components: Release
>    Affects Versions: 1.1
>         Environment: Any
>            Reporter: Olivier Dehon
>             Fix For: 1.x
>
>
> When variables like ${scmRoot} (defined in settings.xml) or others are used in the SCM section of the POM, releasing the project replaces the variables with their interpolated values from the release profile.
> Even using a tagBase of "${scmRoot}/.../tags" does not solve the issue.
> It would be great if the algorithm that computes the scm paths for the tagged POM version does so in a relative fashion.
> -Olivier

-- 
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