[SCM-970] Have separate APIs for distributed and centralized version control

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: 3.0.0
• Assignee: Unassigned
• Reporter: Robert Scholte
• Created: 17/Sep/21 07:40
• Updated: 25/Jul/22 07:22

Description

The nature of these 2 types are very different. The original scm api was based on centralized repositories, and the distributed was implemented behind those methods, which makes it more complex than required.

Splitting this will make it easier to make full use of distributed features.

Keep in mind that plugins like the maven-release-plugin must still be able to do their work, but they may need to provide implementations for both tastes (unless the original scm-api implements it).

Issue Links

• is depended upon by: MRELEASE-1030 Introduce flag to push once, not twice, during release:prepare
• is depended upon by: MRELEASE-954 maven-release-plugin should push less often to git server
• is related to: SCM-852 maven-scm-plugin:check-local-modification should optionally check for unpushed commits
• is related to: SCM-996 Streamline checkIn operation in git providers with respect to modified/added/removed files