[
https://issues.apache.org/jira/browse/SCM-953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963779#comment-17963779
]
ASF GitHub Bot commented on SCM-953:
------------------------------------
jira-importer opened a new issue, #1177:
URL: https://github.com/apache/maven-scm/issues/1177
**[Clemens
Quoß](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cquoss)**
opened
**[SCM-953](https://issues.apache.org/jira/browse/SCM-953?redirect=false)** and
commented
As part of the Maven SCM Cleanup process (see [Maven Ecosystem Cleanup -
Apache Maven - Apache Software
Foundation](https://cwiki.apache.org/confluence/display/MAVEN/Maven+Ecosystem+Cleanup#MavenEcosystemCleanup-MavenSCMCleanup))
all providers except gitexe, jgit, mercurial and svnexe should be declared
deprecated.
So in the main site page we publish a table listing all the now deprecated
providers followed by the notice that the maven-scm code for these can from now
on only be used on an as-is basis (no new features and/or bugfixes will be
introduced and the provider will be removed with the next major release).
For each provider a separate sub-task will be created and with each of
these sub-tasks a remark on the provider main page will be established noticing
of the deprecation of this provider.
After this has been released all issues regarding the then deprecated
providers will be rejected as 'wont fix'.
---
**Affects:** 1.11.2
**Sub-tasks:**
- [SCM-956](https://issues.apache.org/jira/browse/SCM-956) Deprecate
maven-scm-provider-accurev
- [SCM-957](https://issues.apache.org/jira/browse/SCM-957) Deprecate
maven-scm-provider-bazaar
- [SCM-958](https://issues.apache.org/jira/browse/SCM-958) Deprecate
maven-scm-provider-clearcase
- [SCM-959](https://issues.apache.org/jira/browse/SCM-959) Deprecate
maven-scm-provider-integrity
- [SCM-960](https://issues.apache.org/jira/browse/SCM-960) Deprecate
maven-scm-provider-jazz
- [SCM-961](https://issues.apache.org/jira/browse/SCM-961) Deprecate
maven-scm-provider-perforce
- [SCM-962](https://issues.apache.org/jira/browse/SCM-962) Deprecate
maven-scm-provider-starteam
- [SCM-963](https://issues.apache.org/jira/browse/SCM-963) Deprecate
maven-scm-provider-tfs
- [SCM-964](https://issues.apache.org/jira/browse/SCM-964) Deprecate
maven-scm-provider-vss
- [SCM-965](https://issues.apache.org/jira/browse/SCM-965) Deprecate
maven-scm-providers-cvs
- [SCM-966](https://issues.apache.org/jira/browse/SCM-966) Deprecate
maven-scm-provider-synergy
**Issue Links:**
- [SCM-1002](https://issues.apache.org/jira/browse/SCM-1002) create orphaned
branches for 2.0-deprecated providers
- [SCM-969](https://issues.apache.org/jira/browse/SCM-969) Remove all
deprecated (commercial + CVS) providers
(_**"is depended upon by"**_)
> Deprecate commercial and CVS providers
> --------------------------------------
>
> Key: SCM-953
> URL: https://issues.apache.org/jira/browse/SCM-953
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Task
> Components: maven-scm-provider-accurev, maven-scm-provider-bazaar,
> 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: 1.11.2
> Reporter: Clemens Quoß
> Assignee: Michael Osipov
> Priority: Minor
> Fix For: 1.12.0
>
>
> As part of the Maven SCM Cleanup process (see [Maven Ecosystem Cleanup -
> Apache Maven - Apache Software
> Foundation|https://cwiki.apache.org/confluence/display/MAVEN/Maven+Ecosystem+Cleanup#MavenEcosystemCleanup-MavenSCMCleanup])
> all providers except gitexe, jgit, mercurial and svnexe should be declared
> deprecated.
> So in the main site page we publish a table listing all the now deprecated
> providers followed by the notice that the maven-scm code for these can from
> now on only be used on an as-is basis (no new features and/or bugfixes will
> be introduced and the provider will be removed with the next major release).
> For each provider a separate sub-task will be created and with each of these
> sub-tasks a remark on the provider main page will be established noticing of
> the deprecation of this provider.
> After this has been released all issues regarding the then deprecated
> providers will be rejected as 'wont fix'.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
