fix: Correct execing of Maven/Gradle

Should work OK as `exec` seems to always run with a shell even though `spawn` (used to locate the commands) does not.

Signed-off-by: Chad Wilson <chadw@thoughtworks.com>

Author: chadlwilson

package-lock.json

@@ -8,7 +8,7 @@
   "description": "Gauge support for VScode.",
   "author": "ThoughtWorks",
   "license": "MIT",
-  "version": "0.2.2",
+  "version": "0.2.3",
   "publisher": "getgauge",
   "engines": {
     "vscode": "^1.82.0"

package.json

@@ -24,7 +24,7 @@ export class GradleProject extends GaugeProject {
 
     public envs(cli: CLI): NodeJS.ProcessEnv {
         try {
-            let classpath = execSync(`${cli.gradleCommand()} -q clean classpath`, {cwd: this.root()});
+            let classpath = execSync(`${cli.gradleCommand().command} -q clean classpath`, {cwd: this.root()});
             return {[GAUGE_CUSTOM_CLASSPATH]: classpath.toString().trim() };
         } catch (e) {
             window.showErrorMessage(`Error calculating project classpath.\t\n${e.output.toString()}`);

src/project/gradleProject.ts

@@ -23,7 +23,7 @@ export class MavenProject extends GaugeProject {
 
     public envs(cli: CLI): NodeJS.ProcessEnv {
         try {
-            let classpath = execSync(`${cli.mavenCommand()} -q gauge:classpath`, {cwd: this.root()});
+            let classpath = execSync(`${cli.mavenCommand().command} -q gauge:classpath`, {cwd: this.root()});
             return {[GAUGE_CUSTOM_CLASSPATH]: classpath.toString().trim() };
         } catch (e) {
             window.showErrorMessage(`Error calculating project classpath.\t\n${e.output.toString()}`);