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

when not pushing changes to remote git repo in 2.1, the release plugin fails on release:perform

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 2.1
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      as it tries to clone the remote repo, which has not yet been pushed - so there's no tag in the remote repo yet.

      Ideally if pushChanges is false, it should use a value of

        <scm>
           <developerConnectionL>scm:git:file://${baseDir}</developerConnection>
           ...
        </scm>
      

      so that it clones from the current local git repo (which has everything inside it) rather than the remote repo which has yet to be pushed.

      BTW a great use case for not pushing is using a staging maven repo like Nexus; which may reject an attempt to promote a staged build, so you only want to push after a downstream stage works.

        Attachments

          Activity

            People

            • Assignee:
              struberg Mark Struberg
              Reporter:
              jstrachan james strachan
            • Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: