[ http://jira.codehaus.org/browse/SCM-55?page=comments#action_47009 ]
Trygve Laugstol commented on SCM-55: ------------------------------------ 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: http://jira.codehaus.org/browse/SCM-55 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-cvs > Versions: 1.0-alpha-2 > Reporter: Arnaud Heritier > 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 is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
