Details
Description
I have tried all the various permutations for passing versions to the command line while making a branch. The plugin ignores my parameters when running release:branch. It either interactively prompts for new versions, or injects the defaults if I pass parameters in batch mode.
Here's an example of two commands I have tried running that don't work:
mvn release:branch DbranchName=RB[top-level-project-name]-1.0.4 -DautoVersionSubmodules=true -DupdateBranchVersions=true -DupdateWorkingCopyVersions=false -DdevelopmentVersion=1.0.4-SNAPSHOT
mvn release:branch DbranchName=RB[top-level-project-name]-1.0.4 -DautoVersionSubmodules=true -DupdateBranchVersions=true -DupdateWorkingCopyVersions=false -Dproject.dev.[org package].[top-level-project-name]=1.0.4-SNAPSHOT
Both of those commands prompt me for versions and no matter what parameters I type use the current project revision as the default. If I do batch mode with --batch or -B, the release plugin just injects the current project revision into the branch and ignores my parameters.
Attachments
Attachments
Issue Links
- is related to
-
MRELEASE-389 Properties releaseVersion and developmentVersion are not read correctly during release:prepare (eventually release:perform)
- Closed
-
MRELEASE-600 command line versions don't work as documented on release:branch
- Closed
- relates to
-
MRELEASE-173 Allow command line specification of versions
- Closed
-
MRELEASE-377 Missing releaseVersion parameter in release:branch goal
- Closed