[
https://issues.apache.org/jira/browse/SCM-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960475#comment-17960475
]
ASF GitHub Bot commented on SCM-209:
------------------------------------
jira-importer commented on issue #413:
URL: https://github.com/apache/maven-scm/issues/413#issuecomment-2964592621
**[Patrick
Schneider](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=pschneider)**
commented
Now passes -d flag to command line instead of using setWorkingDirectory.
The resulting command is different which is why the unit tests were failing.
Updated all failing tests to new expected value.
> 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)
