[
https://issues.apache.org/jira/browse/SCM-970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963817#comment-17963817
]
ASF GitHub Bot commented on SCM-970:
------------------------------------
jira-importer opened a new issue, #1195:
URL: https://github.com/apache/maven-scm/issues/1195
**[Robert
Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte)**
opened
**[SCM-970](https://issues.apache.org/jira/browse/SCM-970?redirect=false)** and
commented
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:**
- [SCM-852](https://issues.apache.org/jira/browse/SCM-852)
maven-scm-plugin:check-local-modification should optionally check for unpushed
commits
- [SCM-996](https://issues.apache.org/jira/browse/SCM-996) Streamline
checkIn operation in git providers with respect to modified/added/removed files
- [MRELEASE-1030](https://issues.apache.org/jira/browse/MRELEASE-1030)
Introduce flag to push once, not twice, during release:prepare
(_**"is depended upon by"**_)
- [MRELEASE-954](https://issues.apache.org/jira/browse/MRELEASE-954)
maven-release-plugin should push less often to git server
(_**"is depended upon by"**_)
1 votes, 3 watchers
> Have separate APIs for distributed and centralized version control
> ------------------------------------------------------------------
>
> Key: SCM-970
> URL: https://issues.apache.org/jira/browse/SCM-970
> Project: Maven SCM (Moved to GitHub Issues)
> 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)
