Is the directory C:\Users\sehonc in your PATH environment variable? If it's not try using .\mvn.exe -v

Is "mvn" an executable? Or is it a script?

Why my maven commands don't work in PowerShell but the same commands work in the cmd?

SERHII 1

2 answers

Rich Matheisen 44,621 Reputation points

2022-02-22T19:01:37.593+00:00

Is the directory C:\Users\sehonc in your PATH environment variable? If it's not try using .\mvn.exe -v
Please sign in to rate this answer.
SERHII 1 Reputation point

2022-02-22T19:17:59.853+00:00

In my PATH (User variables for sehonc) directory C:\Users\sehonc is absent.
Do I need to add C:\Users\sehonc to the PATH?

Unfortunately, I didn't get where I need to use .\mvn.exe -v
Can you please explain in more detail?
Sign in to comment
Rich Matheisen 44,621 Reputation points

2022-02-23T03:48:05.913+00:00

Is "mvn" an executable? Or is it a script?
Please sign in to rate this answer.
SERHII 1 Reputation point

2022-02-23T10:35:01.443+00:00

It's a maven command.
https://www.geeksforgeeks.org/maven-lifecycle-and-basic-maven-commands/

MotoX80 31,561 Reputation points

2022-02-23T14:35:04.767+00:00

Redirect the output and see if there is anything in it.

mvn.exe -v 1> $env:temp\Maven.log 2>&1 notepad.exe $env:temp\Maven.log

I noticed that the first line of output from "mvn -v" is highlighted. Maybe it's displaying some control character that is confusing PS.

SERHII 1 Reputation point

2022-03-08T13:12:49.127+00:00

mvn.exe -v 1> $env:temp\Maven.log 2>&1 not working

Rich Matheisen 44,621 Reputation points

2022-03-08T15:39:26.14+00:00

Because that executable isn't in a directory that's in your PATH environment variable you need to specify where the executable is. Unlike the DOS CMD.EXE shell PowerShell doesn't assume that you meant to run something in whatever happens to be the current working directory.

If you current working directory is "C:\Users\Sehonc" and that's where the mvn.exe file is found simply prefix the executable name with ".\". E.g., .\mvn.exe
Sign in to comment