[
https://issues.apache.org/jira/browse/SCM-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960057#comment-17960057
]
ASF GitHub Bot commented on SCM-50:
-----------------------------------
jira-importer opened a new issue, #313:
URL: https://github.com/apache/maven-scm/issues/313
**[Brett
Porter](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=brettporter)**
opened
**[SCM-50](https://issues.apache.org/jira/browse/SCM-50?redirect=false)** and
commented
instead of having an execute() method, the ScmProvider interface should have
individual commands in the interface, like ScmManager currently does.
In fact, after this, the ScmManager need not have the commands, and just
needs to expose a getProvider method.
This should eventually lead to the removal of CommandNameConstants
---
No further details from
[SCM-50](https://issues.apache.org/jira/browse/SCM-50?redirect=false)
> flesh out the SCM provider interface
> ------------------------------------
>
> Key: SCM-50
> URL: https://issues.apache.org/jira/browse/SCM-50
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Task
> Components: maven-scm-api
> Reporter: Brett Porter
> Assignee: Emmanuel Venisse
> Priority: Major
> Fix For: 1.0-alpha-2
>
>
> instead of having an execute() method, the ScmProvider interface should have
> individual commands in the interface, like ScmManager currently does.
> In fact, after this, the ScmManager need not have the commands, and just
> needs to expose a getProvider method.
> This should eventually lead to the removal of CommandNameConstants
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
