[jira] [Commented] (SCM-1002) create orphaned branches for 2.0-deprecated providers

["Michael Osipov (Jira)" <ji...@apache.org>]

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

Michael Osipov commented on SCM-1002:
-------------------------------------

As a matter of fact, the providers need to be moved away from Plexus first before they could work again. This has to be done by the volunteers.

> create orphaned branches for 2.0-deprecated providers
> -----------------------------------------------------
>
>                 Key: SCM-1002
>                 URL: https://issues.apache.org/jira/browse/SCM-1002
>             Project: Maven SCM
>          Issue Type: Wish
>          Components: maven-scm-provider-accurev, maven-scm-provider-clearcase, maven-scm-provider-cvs, maven-scm-provider-integrity, maven-scm-provider-jazz, maven-scm-provider-monotone, maven-scm-provider-perforce, maven-scm-provider-pvcs, maven-scm-provider-starteam, maven-scm-provider-synergy, maven-scm-provider-tfs, maven-scm-provider-vss
>    Affects Versions: 2.0.0-M1
>            Reporter: Herve Boutemy
>            Priority: Major
>
> less common, uneasy to test, providers have been removed in SCM-969
> the fact that the Maven team itself cannot maintain them does not mean that they should fully disappear: ideally, they should be maintained by dedicated communities which have interest in each SCM, with associated test environments to be able to maintain the code
> to help these communities involve, we can create Git orphaned branches with code history before removal so people can easily start such SCM-oriented projects outside
> if you create such a project, please tell us: we'll link to your project



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