[MRELEASE-605] when not pushing changes to remote git repo in 2.1, the release plugin fails on release:perform

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.1
• Assignee: Mark Struberg
• Reporter: James Strachan
• Created: 06/Oct/10 06:06
• Updated: 31/Jan/15 14:13
• Resolved: 27/Jun/11 03:34

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.