[jira] [Commented] (SCM-970) Have separate APIs for distributed and centralized version control

["Konrad Windszus (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SCM-970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17570713#comment-17570713 ] 

Konrad Windszus commented on SCM-970:
-------------------------------------

Although I agree that having separate APIs would be a nice long-term goal, for the short-term a documentation would help a lot how the decentralized providers (particularly git) behave for the existing {{ScmManager}} methods (i.e. when the index is updated and when/which parts are committed/pushed).

> Have separate APIs for distributed and centralized version control
> ------------------------------------------------------------------
>
>                 Key: SCM-970
>                 URL: https://issues.apache.org/jira/browse/SCM-970
>             Project: Maven SCM
>          Issue Type: Improvement
>            Reporter: Robert Scholte
>            Priority: Major
>             Fix For: 3.0.0
>
>
> 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).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)