-
Notifications
You must be signed in to change notification settings - Fork 65
Create warning when using CMD or PowerShell #1252
Copy link
Copy link
Labels
CLIIDEasy command-line-interface (parsing args, etc.)IDEasy command-line-interface (parsing args, etc.)CMDSupport in Windows CMD/MSDOS via ide.batSupport in Windows CMD/MSDOS via ide.batPowerShellWindows PowerShell integration and supportWindows PowerShell integration and supportenhancementNew feature or requestNew feature or requestwindowsspecific for Microsoft Windows OSspecific for Microsoft Windows OS
Milestone
Metadata
Metadata
Assignees
Labels
CLIIDEasy command-line-interface (parsing args, etc.)IDEasy command-line-interface (parsing args, etc.)CMDSupport in Windows CMD/MSDOS via ide.batSupport in Windows CMD/MSDOS via ide.batPowerShellWindows PowerShell integration and supportWindows PowerShell integration and supportenhancementNew feature or requestNew feature or requestwindowsspecific for Microsoft Windows OSspecific for Microsoft Windows OS
Type
Projects
Status
✅ Done
We keep on telling our users that they should use bash (or zsh) because:
*.ps1not executed due to security while*.batalways is, the security idea behind this is nice but makes PowerShell not an option for seamless scripting, etc. - there are also bugs in edge-cases)As suggested by @maybeec we should simply log a warning end the end of our wrapper script that users should get used to bash and stop using CMD or PowerShell when using IDEasy CLI.
IMHO this is the best way to "spread the word".
We still give compatibility as possible and Windows users that insist on using CMD or PowerShell may still ignore it but then they cannot say they did not knew and had never been warned.
Acceptance criteria:
CMDorPowerShellthe user should get the following warning:Hint
The functionality needs to be integrated here:
IDEasy/cli/src/main/package/bin/ide.bat
Line 27 in 26670c9
and:
IDEasy/cli/src/main/package/bin/ide.bat
Line 39 in 26670c9