Extension Name: vscode-gradle
Extension Version: 2.4.13
OS Version: Windows 10
VSCode version: 1.43.2

Describe the bug
We add an entry in the gradle.properties file to override the trust authority to use our local artifact repository instead of Maven Central. Executing using the gradle wrapper from Command prompt works fine. Executing from the Gradle Tasks explorer gives the error that it can't find the cacerts file specified. If we give full path in the properties file, then it works. This is not acceptable for our processes.

Update: Looks like it is executing the tasks from the /User//.vscode/extensions/... directory when applying the Java parameter to set the truststore. I'm guessing Java parameters are being parsed/applied in different context than other gradle.properties values.

To Reproduce
Define a relative path in the gradle.properties file of any project. Execute from the Gradle Tasks Explorer.

Expected behavior
Relative paths should be supported from within gradle.properties file.

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

Additional context
Add any other context about the problem here.