[
https://issues.apache.org/jira/browse/SCM-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960275#comment-17960275
]
ASF GitHub Bot commented on SCM-55:
-----------------------------------
jira-importer commented on issue #367:
URL: https://github.com/apache/maven-scm/issues/367#issuecomment-2964589845
**[Trygve
Laugstøl](https://issues.apache.org/jira/secure/[email protected])**
commented
I don't see why this is necessary, you should not be doing "cvs update"
unless there already is a checkout in the directory. I doubt that this would
work with the other providers.
To me the correct way here would be for the provider to look for an existing
checkout and fail if it's not there. IIRC there's already methods to get a
ScmRepository from a File.
> cvs update doesn't define CVSROOT
> ---------------------------------
>
> Key: SCM-55
> URL: https://issues.apache.org/jira/browse/SCM-55
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-cvs
> Affects Versions: 1.0-alpha-2
> Reporter: Arnaud Heritier
> Priority: Major
> Attachments: SCM-55.ahe.patch
>
>
> The following command is generated :
> scm:update:
> [echo] Updating from SCM
> Executing: cvs -f -q update -d
> Working directory: XXXXX
> Provider message:
> The cvs command failed.
> Command output:
> cvs update: No CVSROOT specified! Please use the `-d' option
> cvs [update aborted]: or set the CVSROOT environment variable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
