[
https://issues.apache.org/jira/browse/SCM-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960056#comment-17960056
]
ASF GitHub Bot commented on SCM-18:
-----------------------------------
jira-importer commented on issue #312:
URL: https://github.com/apache/maven-scm/issues/312#issuecomment-2964584974
**[Brett
Porter](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=brettporter)**
commented
Like SCM-17, I didn't notice the version change. The idea was that I felt
this was a prerequisite for a 1.0 release.
> complete commands and expose through ScmManager
> -----------------------------------------------
>
> Key: SCM-18
> URL: https://issues.apache.org/jira/browse/SCM-18
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Task
> Components: maven-scm-api, maven-scm-provider-clearcase,
> maven-scm-provider-cvs, maven-scm-provider-local,
> maven-scm-provider-perforce, maven-scm-provider-starteam,
> maven-scm-provider-svn
> Reporter: Brett Porter
> Priority: Major
>
> many commands are not completely implemented, or not implemented at all, and
> some that are have not been exposed through the ScmManager interface.
> These all need to be rounded out and tested via the TCK for a final 1.0
> release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
