[
https://issues.apache.org/jira/browse/SCM-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961636#comment-17961636
]
ASF GitHub Bot commented on SCM-461:
------------------------------------
jira-importer commented on issue #677:
URL: https://github.com/apache/maven-scm/issues/677#issuecomment-2964612758
**[Mark
Struberg](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=struberg)**
commented
The JUnit tests only ensure that the tfs provider returns the commandline
_you_ think should be used. But it's not only that we need to execute the right
statements - the TCK also checks for proper return values from the provider and
many other things!
For example: the TfsAddCommand not only has to add the given files to the
repository but it also has to return an AddScmResult which must contain the
list of changed files! And all scm providers have to return the same list, e.g.
not only a directory but all files in that directory, etc
So I'd strongly recommend implementing the TCK tests.
> Support TFS as SCM Provider
> ---------------------------
>
> Key: SCM-461
> URL: https://issues.apache.org/jira/browse/SCM-461
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Improvement
> Affects Versions: 1.3
> Reporter: Subhash
> Assignee: Mark Struberg
> Priority: Major
> Fix For: 1.3
>
> Attachments: scm-461-maven-scm-provider-tfs.patch
>
>
> Support for Microsoft TFS is being added to Maven by a new scm-provider:
> maven-scm-provider-tfs. The attached patch file contains the changes made to
> http://svn.apache.org/repos/asf/maven/scm/trunk
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
