[
https://issues.apache.org/jira/browse/SCM-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960474#comment-17960474
]
ASF GitHub Bot commented on SCM-209:
------------------------------------
jira-importer opened a new issue, #413:
URL: https://github.com/apache/maven-scm/issues/413
**[John
Didion](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jdidion)**
opened
**[SCM-209](https://issues.apache.org/jira/browse/SCM-209?redirect=false)** and
commented
Passing the working directory as an argument to Runtime.exec seems to have
no effect on linux...perforce still goes with whatever the VM's initial working
directory was. You need to set -d to make it use the correct one.
In PerforceScmProvider.createP4Command():
command.createArgument().setValue("-d");
command.createArgument().setValue(workingDir.getAbsolutePath());
---
**Affects:** 1.0-beta-3
**Issue Links:**
- [SCM-245](https://issues.apache.org/jira/browse/SCM-245) scm:edit doesn't
work with perforce as it refers the file without depot path
1 votes, 0 watchers
> Specifying working directory for Runtime.exec() on linux has no effect
> ----------------------------------------------------------------------
>
> Key: SCM-209
> URL: https://issues.apache.org/jira/browse/SCM-209
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-perforce
> Affects Versions: 1.0-beta-3
> Reporter: John Didion
> Assignee: Patrick Schneider
> Priority: Major
> Fix For: 1.0
>
>
> Passing the working directory as an argument to Runtime.exec seems to have no
> effect on linux...perforce still goes with whatever the VM's initial working
> directory was. You need to set -d to make it use the correct one.
> In PerforceScmProvider.createP4Command():
> command.createArgument().setValue("-d");
> command.createArgument().setValue(workingDir.getAbsolutePath());
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
