You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was not able to reproduce this bug as described.
After making the changes (Run as administrator), I got a UAC Popup.
If I reject to grant admin rights, then the process is not started at all and the setup.bat fails like illustrated in the screenshot.
That is not a bug - if you prevent git-bash from being executed then IDEasy cannot start it and therefore the setup fails that needs it. You can also delete git bash or git and then you will notice that IDEasy stops working since this is a pre-requisite for IDEasy as documented on our website.
However, if I answered the UAC Popup with Yes and granted admin rights, the setup worked.
The installation afterwards is fully functional.
Finally, I would rather consider that setting "run as admin" for processes like bash.exe is the actual bug.
Why would I do that? This seems just a wrong configuration done by the end user.
So IMHO this bug report might be closed as invalid.
However, we might want to do a screen-sharing since your situation behaves quite differently and if we have many users in the future and someone else might run into the same problem, it will still not be easy to trace down what is going wrong and why. If we can somehow detect the problem during our setup and show a better error message, it might still be helpful.
Expected behavior
As a dev, I want to execute IDEasy tests via mvn goal (cmd) or via IntelliJ maven goal so that the project gets build
Actual behavior
The tests fail with the following exception:
Steps to reproduce (bug) / Use Case of feature request (enhancement)
Related/Dependent Issues
Comments/Hints:
If the "Run this program as an administrator" is checked, setup.bat also doesn't work like expected when ideasy is already installed.
If "Run this program as an administrator" is NOT checked and setup.bat is executed
Affected version:
2025.02.001-beta
The text was updated successfully, but these errors were encountered: