Uploaded image for project: 'Maven Release Plugin'
  1. Maven Release Plugin
  2. MRELEASE-387

command line versions don't seem to work on release:branch

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.0-beta-8
    • 2.0
    • branch
    • None
    • maven 2.0.9 and 2.1.0 M1, maven release plugin 2.0-beta-8
    • Patch

    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

        1. addSupportForVersion.patch
          1 kB
          Philippe Kernevez

        Issue Links

          Activity

            People

              olamy Olivier Lamy
              basker Jeff Vogelsang
              Votes:
              7 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: