Working directory is wrong when executing an ant taskdef task.

[rogerlittin]

Extension Name: vscode-gradle
Extension Version: 3.5.2
OS Version: MacOS 10.15.7
VSCode version: 1.5.2

Description
I have an ant taskdef that retrieves some git information and I am executing it from a gradle task. When I run the task from a bash console, I get the correct output, but when I run it from the vscode-gradle tasks extension, I get an error from git.
Error: fatal: not a git repository (or any of the parent directories): .git

I have added logging to the ant taskdef class, before the git command is executed, and I can see that the vscode-gradle extension is executing the ant task from the .gradle/daemon/6.7/ in my home folder instead of the project folder.

vscode-gradle: Current Working Dir: /Users/roger/.gradle/daemon/6.7/

Command line: Current Working Dir: /Users/roger/path/to/project/

To Reproduce
Create an class that extends org.apache.tools.ant.Task and have that class log the current working directory.
Create a gradle task that uses the ant task.
Execute the task from the vscode-gradle tasks list.
it should print out the Gradle User Home path instead of the project path
Executing the same task from the command line prints out the project path.

Expected behavior
The ant task should execute from the project directory

Does the bug still exist if you disable all other extensions?
not tested

[badsyntax]

This is related to #245 and #332

The problem is that I can't change the gradle working directory, so gradle will inherit the working directory from the java process that calls the gradle api.

So one potential fix, as shown in the PR above, is to set the working directory to the project directory when starting the gradle server. This will fix all relative path issues, but presents some problems for multi-root workspaces (eg, which project root do i start the server in? should i start one server for each multi-root project?)

I just need to think about the best approach for multi-root workspaces and then i'll add a fix for this.

[badsyntax]

Although your case seems a little different, i'm surprised the working directory is /Users/roger/.gradle/daemon/6.7/. Either way, I will fix the gradle server cwd issue and we'll see if that resolves it for you.

[github-actions]

Hi @rogerlittin, I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.

Possible workarounds

• In your custom Ant Task (the one you registered with <taskdef>), don’t rely on the process CWD. Instead:

  • If you invoke git via Java’s ProcessBuilder, call directory(new File(getProject().getBaseDir())) before start().
  • If you shell out inside Ant, use Ant’s <exec> element with a dir="${basedir}" attribute so that git always runs from the project root.

• As an alternative to invoking the native git binary, use JGit in your task. JGit works entirely in-process and ignores the shell’s working directory.

• If you just want to run the Gradle task with the correct CWD from VS Code, you can bypass the Gradle extension and add a custom entry to your workspace tasks.json:

  {
    "version": "2.0.0",
    "tasks": [
      {
        "label": "myGradleWithProperCwd",
        "type": "shell",
        "command": "./gradlew myTask",
        "options": { "cwd": "${workspaceFolder}" }
      }
    ]
  }

Next steps

• This appears to be a bug in the VS Code Gradle extension (it launches Gradle from ~/.gradle/daemon/... instead of your project folder). Please consider filing an issue or feature request here:
  https://github.com/microsoft/vscode-gradle/issues/new

Other references with low confidence

• “The working directory is not set to folder opened in VS Code when it's unmanaged folder” — Java Test Runner sets CWD incorrectly for unmanaged projects. The working directory is not set to folder opened in VS Code when it's unmanaged folder vscode-java-test#1606 (comment)
• “Wrong directory when running JavaCompiler/Executor. Can't find project packages.” — multi-module Java Test Runner uses ${workspaceFolder} too naively. Wrong directory when running JavaCompiler/Executor. Can't find project packages. vscode-java-test#767 (comment)

The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!