[MNG-7541] Native support for PowerShell to start Maven

• Type: Improvement
• Status: Open
• Priority: Trivial
• Resolution: Unresolved
• Affects Version/s: 3.8.3
• Component/s: Command Line
• Labels: Script Windows10 Windows11
• Environment: windows 10 / 11

Language

powershell

• Assignee: Unassigned
• Reporter: Jurrian Fahner
• Created: 17/Sep/22 13:09
• Updated: 28/Apr/24 09:56

Description

Maven has two files in the bin dir:

command	its use
mvn	POSIX shell
mvn.cmd	cmd.exe

On windows there are two ways to write scripts, by using cmd.exe or using powershell.

If you enter mvn in powershell it will look for `mvn.ps1` on the PATH first. If it doesn't find anything it will execute `mvn.cmd` as fall-back.

When running maven for starting a server for development purposes and you do ctrl-c to exit the server it will ask the question: Terminate batch job (Y/N)?

As far as I know it is default behaviour of cmd.exe.

Well if I don't want to terminate, I wouldn't press ctrl-c.

It is not the case (as far as I know that Microsoft is going to deprecate cmd.exe in favor of powershell: https://devblogs.microsoft.com/commandline/rumors-of-cmds-death-have-been-greatly-exaggerated/

Allthough I think it would be a good move for maven to have also a powershell script as well... It is possible to integrate elegant support for native help in powershell, `get-help mvn`.

But it also increases the maintenance effort as well. I don't know whether this cost outweigh the benefits, though...

By the way I would happy to contribute if it is appreciated.

Issue Links

• is duplicated by: MNG-7557 Rewrite Batch scripts (*.cmd) in PowerShell (*.ps1)
• is related to: MSHARED-1150 Support for PowerShell Maven executable
• is related to: MWRAPPER-78 Rewrite mvnw.cmd in PowerShell (mvnw.ps1)
• links to: GitHub Pull Request #877
• links to: GitHub Pull Request #878
• links to: GitHub Pull Request #982