You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "msangel (Jira)" <ji...@apache.org> on 2023/02/05 01:04:00 UTC

[jira] [Created] (MRELEASE-1113) updateWorkingCopyVersions false still update the version

msangel created MRELEASE-1113:
---------------------------------

             Summary: updateWorkingCopyVersions false still update the version
                 Key: MRELEASE-1113
                 URL: https://issues.apache.org/jira/browse/MRELEASE-1113
             Project: Maven Release Plugin
          Issue Type: Bug
          Components: prepare
    Affects Versions: 3.0.0-M7
            Reporter: msangel
         Attachments: image-2023-02-05-03-02-17-768.png

Having this in source pom.xml:
{code:java}
<version>${majorversion}.3.4-SNAPSHOT</version> {code}
meaning the major version is set via profile properties, but running the plugin with -DupdateWorkingCopyVersions=false still causes the version in pom.xml to be overridden with actual value (which is never "actual" as defined in profile property):
{code:java}
<profile>
  <id>java8</id>
  <properties>
    <majorversion>0.8</majorversion>
  </properties>
</profile>
<profile>
  <id>java11</id>
  <properties>
    <majorversion>0.9</majorversion>
  </properties>
</profile> {code}
The command I run:
{code:java}
 mvn -DdryRun=true -DcheckModificationExcludeList="pom.xml" -DupdateWorkingCopyVersions=false  release:prepare -P java11 {code}
the diff:

!image-2023-02-05-03-02-17-768.png!

can this plugin not touch the version if there are set flag "updateWorkingCopyVersions" to "false"?



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