[MRELEASE-883] Upgrade SCM to 1.9.1

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.5
• Fix Version/s: 2.5.1
• Component/s: scm
• Assignee: Benson Margulies
• Reporter: Robert Scholte
• Created: 12/Aug/14 15:28
• Updated: 06/Apr/15 01:08
• Resolved: 13/Sep/14 09:08

Description

Release Notes of SCM 1.9.1

• Bugs:
  • SCM-740 - Maven Release Plugin releases SNAPSHOT instead of STABLE version
  • SCM-750 - TFS-plugin fails in cases of 'TFS policies' is required by TFS upon checkin
  • SCM-752 - maven-release-plugin:2.5:prepare fails with 'Error writing POM: (Access is denied)'
  • SCM-753 - support TFS checkin-policies
  • SCM-757 - bootstrap/checkout/export goals now requires -Dproject.basedir=. set at command line
  • SCM-765 - jgit provider commits changes with system user instead of passed username
• Improvement:
  • SCM-741 - scm:validate for svn should offer a way to check the current directory actually matches what's declared in the pom
• New Feature:
  • SCM-747 - [PERFORCE] Support SSL
• Tasks:
  • SCM-754 - Require Tag/Branch Command to return the entire source tree is impractical
  • SCM-755 - Inject SecDispatcher into TCK base test case
  • SCM-756 - TCK should invoke EditCommand for provider like Perforce before any change
  • SCM-760 - remove maven-scm-plugin's RemoveMojoTest due to specific Perforce setup requirement
  • SCM-761 - Allow downstream TCK to define its own tag

Issue Links

• is related to: MRELEASE-812 "prepare" does not commit before tagging and therefore deploys snapshot instead of release
• relates to: MRELEASE-875 release:prepare does not commit pom.xml if not in the git root
• relates to: SCM-740 Maven Release Plugin releases SNAPSHOT instead of STABLE version