You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Marcel Stör (Jira)" <ji...@apache.org> on 2022/11/16 08:16:00 UTC

[jira] [Updated] (MRELEASE-1109) update-versions removes the CI-friendly ${revisions}

     [ https://issues.apache.org/jira/browse/MRELEASE-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcel Stör updated MRELEASE-1109:
----------------------------------
    Summary: update-versions removes the CI-friendly ${revisions}  (was: update-versions removes the CI-friendly {revisions})

> update-versions removes the CI-friendly ${revisions}
> ----------------------------------------------------
>
>                 Key: MRELEASE-1109
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-1109
>             Project: Maven Release Plugin
>          Issue Type: Bug
>          Components: update-versions
>    Affects Versions: 2.5.3, 3.0.0-M7
>            Reporter: Marcel Stör
>            Priority: Major
>
> Given: a project using CI-friendly versions as per [https://maven.apache.org/maven-ci-friendly.html]
> {code:xml}
>   <version>${revision}</version>
>   ...
>   <properties>
>     <revision>1.0.0-SNAPSHOT</revision>
>   </properties>
> {code}
> If I run {{mvn release:update-versions}} (with or without {{{}-DautoVersionSubmodules=true{}}}) I expect the release plugin to change the {{$revision}} property. Instead it blindly replaces {{<version>${revision}</version>}} with the hard-coded version set on the CLI.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)