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

release:update-versions should not need SCM config

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 2.4
    • update-versions
    • None

    Description

      Currently, on a project without <scm> configured, mvn release:update-versions ends up with:

      Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.0:update-versions (default-cli) on project wicketstuff-dojo: Missing required setting: scm connection or developerConnection must be specified.

      Updating versions recursively definitely does not need SCM.
      Could this restriction be removed? Thanks.

      Attachments

        Issue Links

        is duplicated by

        Improvement - An improvement or enhancement to an existing feature or task. MRELEASE-584 Skip checking SCM setting for update-versions

        • Major - Major loss of function.
        • Closed

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            rfscholte Robert Scholte
            pekarna Ondra Žižka
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment