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
hohwille opened this issue
Mar 14, 2023
· 1 comment
· Fixed by #1072
Labels
bugSomething isn't workingscriptsrelated to shell scripts (bash and CMD)setuprelated to the setup process of devonfw-ide (setup[.bat] and devon ... setup)windowsspecific for Microsoft Windows OS
I received feedback that people have been facing #954 again with latest release (2023.03.001).
After digging into devon.bat I discovered at least one part about setting the user PATH that IMHO was wrong from the start:
If the user PATH is actually empty for reason, then windows behaves such that it sets the PATH to the system PATH.
So if we run into this IF statement on proper purpose, we have to set PATH to %PATH%;%%USERPROFILE%%\scripts instead.
That is already one bug.
Another question is if #954 was never entirely fixed, is now back due to #1067, or whatever leads to the problem that a user PATH is set but gets lost after calling setup.bat or devon.bat.
The text was updated successfully, but these errors were encountered:
hohwille
added
bug
Something isn't working
windows
specific for Microsoft Windows OS
scripts
related to shell scripts (bash and CMD)
setup
related to the setup process of devonfw-ide (setup[.bat] and devon ... setup)
labels
Mar 14, 2023
With PR #1072 I fix the first thing.
Further I added according output that we can now easily trace down the second thing.
If someone can reproduce the second problem earlier we can create a fix immediately but otherwise I would already release the current state to make progress and finally get this ugly windows CMD *.bat scripts stable again.
bugSomething isn't workingscriptsrelated to shell scripts (bash and CMD)setuprelated to the setup process of devonfw-ide (setup[.bat] and devon ... setup)windowsspecific for Microsoft Windows OS
I received feedback that people have been facing #954 again with latest release (2023.03.001).
After digging into
devon.bat
I discovered at least one part about setting the user PATH that IMHO was wrong from the start:ide/scripts/src/main/resources/scripts/devon.bat
Line 138 in 39a248a
If the user
PATH
is actually empty for reason, then windows behaves such that it sets thePATH
to the systemPATH
.So if we run into this IF statement on proper purpose, we have to set
PATH
to%PATH%;%%USERPROFILE%%\scripts
instead.That is already one bug.
Another question is if #954 was never entirely fixed, is now back due to #1067, or whatever leads to the problem that a user
PATH
is set but gets lost after callingsetup.bat
ordevon.bat
.The text was updated successfully, but these errors were encountered: