[
https://issues.apache.org/jira/browse/SCM-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963944#comment-17963944
]
ASF GitHub Bot commented on SCM-1002:
-------------------------------------
jira-importer commented on issue #1226:
URL: https://github.com/apache/maven-scm/issues/1226#issuecomment-2964658184
**[Hervé
Boutemy](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=hboutemy)**
commented
ah ok, it's not "moving away from Plexus", but moving from Plexus
Annotations to JSR-330: ok, we'll prepare the orphaned branches to match
evolutions done in SCM 2.0
> create orphaned branches for 2.0-deprecated providers
> -----------------------------------------------------
>
> Key: SCM-1002
> URL: https://issues.apache.org/jira/browse/SCM-1002
> Project: Maven SCM (Moved to GitHub Issues)
> 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: Hervé Boutemy
> Priority: Major
>
> proprietary and obsolete (then uneasy to test) providers have been removed in
> SCM-969 after being deprecated in SCM-953
> 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)
