Fix added for powershell command using maven executable path

TrevCraw · Dec 2, 2024 · 1d7741c · 1d7741c
1 parent c7b0f3f
commit 1d7741c
Showing 1 changed file with 6 additions and 0 deletions.
diff --git a/src/util/commandUtils.ts b/src/util/commandUtils.ts
@@ -32,6 +32,12 @@ export async function getCommandForMaven(pomPath: string, command: string, termi
     // attempt to use the Maven executable path, if empty try using mvn or mvnw according to the preferMavenWrapper setting
     const mavenExecutablePath: string | undefined = vscode.workspace.getConfiguration("maven").get<string>("executable.path");
     if (mavenExecutablePath) {
+        if (isWin() && terminalType === ShellType.POWERSHELL) {
+            /**
+            * Function call to get the command for powershell in Windows OS
+            */
+            return formPowershellCommand(mavenExecutablePath, pomPath, command, "-f ", customCommand);
+        }
         return formDefaultCommandWithPath(mavenExecutablePath, pomPath, command, "-f ", customCommand);
     }
     let mvnCmdStart = await mvnCmd(pomPath);