maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <>
Subject [jira] [Closed] (MRELEASE-694) -SNAPSHOT is unexpectedly appended to version in branched pom.xml
Date Sun, 25 Feb 2018 14:00:00 GMT


Robert Scholte closed MRELEASE-694.
       Resolution: Fixed
         Assignee: Robert Scholte
    Fix Version/s: 3.0.0

I've improved the implementation. There's one detail I'd missed: you're specifying a non-snapshot
version to the branch. Branches are considered working copies, so it expects a snapshot.
Interactive and batchmode should have these same requirements, so next time it'll break the
process, making it not unexpected anymore.

> -SNAPSHOT is unexpectedly appended to version in branched pom.xml
> -----------------------------------------------------------------
>                 Key: MRELEASE-694
>                 URL:
>             Project: Maven Release Plugin
>          Issue Type: Bug
>          Components: branch
>    Affects Versions: 2.1, 2.2
>         Environment: apache-maven-2.2.1
>            Reporter: Ken Alexandersson
>            Assignee: Robert Scholte
>            Priority: Critical
>             Fix For: 3.0.0
>         Attachments: pom.xml.branch,, pom.xml.releaseBackup
> When running the following
> {{mvn org.apache.maven.plugins:maven-release-plugin:2.2:branch -DbranchName=ROOT_1.0_RB
-DupdateBranchVersions=true -DautoVersionSubmodules=true -DdryRun=true -DreleaseVersion=1.0
> the branched pom.xml gets the version "1.0-SNAPSHOT" instead of expected "1.0" (please
see attached poms for details). Trying to add {{-DupdateVersionsToSnapshot=false}} does not
help either. 
> Side note: Did a run in interactive mode (by leaving out {{-DreleaseVersion=1.0}} and
{{-DdevelopmentVersion=1.1-SNAPSHOT}}, which produced an expected result where the submitted
versions were reflected correctly in the pom-files.  

This message was sent by Atlassian JIRA

View raw message