[ 
https://issues.apache.org/jira/browse/SCM-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961479#comment-17961479
 ] 

ASF GitHub Bot commented on SCM-433:
------------------------------------

jira-importer commented on issue #648:
URL: https://github.com/apache/maven-scm/issues/648#issuecomment-2964610951

   **[Dan 
Tran](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=dantran)** 
commented
   
   fixed at
   
   Revision: 733015
   Author: dantran
   Date: 3:58:12 AM, Friday, January 09, 2009
   Message:
   SCM-433: set workingDirectory of SvnInfoCommand to its fileSet.getBasedir(), 
similar to all other commands, so that we can run scm info on a local directory.
   
   ---
   
   Modified : 
/maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/info/SvnInfoCommand.java
   Added : 
/maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/test/java/org/apache/maven/scm/provider/svn/svnexe/command/info
   Added : 
/maven/scm/trunk/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/test/java/org/apache/maven/scm/provider/svn/svnexe/command/info/SvnInfoCommandTest.java
   
   




> SvnInfoCommand  should allow option to set working directory
> ------------------------------------------------------------
>
>                 Key: SCM-433
>                 URL: https://issues.apache.org/jira/browse/SCM-433
>             Project: Maven SCM (Moved to GitHub Issues)
>          Issue Type: Bug
>          Components: maven-scm-provider-svn
>    Affects Versions: 1.1
>            Reporter: Dan Tran
>            Assignee: Dan Tran
>            Priority: Major
>             Fix For: 1.2
>
>
> The invocation of SvnInfoCommand with empty fileset run "svn info" on a 
> temporary working directory and therefore fails with 
> Provider message:
> The svn command failed.
> Command output:
> svn: '.' is not a working copy



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to