Support user after docker installation to execute docker

[maybeec]

As a user, I want to install docker and directly start using it so that I can start with my actual work instantly. Currently, after running devon docker, I got rancher desktop installed, but I cannot immediately execute docker command due to the fact, that rancher desktop is setting up $PATH variable. The system $PATH is nonetheless not updated on windows within one console session.

Thus, the user needs to restart the console to get the docker command working or (if possible), we would need to refresh / reset the $PATH within the console session. The latter would be more convenient, but I am not sure, whether this is possible in all windows consoles (Git Bash, CMD, Windows Terminal, PS)

[hohwille]

This is a general problem that we have with all commandlets if they install a new tool. We already set/extend the PATH automatically in our functions but when you call devon with additional arguments (e.g. devon docker setup), then it is run as a regular bash script so as a sub-process. Due to the nature of this changes to environment variables are not reflected to the parent process (the git-bash, cygwin, CMD, powershell, etc.).

What we could discuss is that after each devon ... command always the same side effect will happen as if you called devon command once again after that.
While this may technically possible it is rather tricky and still does not solve the real problems.
Other changes may happen to your registry, system path or other environment variables on the first installation as they are triggered by the tool-installation process itself what is yet another sub-process that we are calling. In the end we can not know what this sub-process is changing and can not workaround it in a generic way. So if it will install something to a newly created directory and that is then added to your system PATH you need to restart at least your entire shell (in case of Windows Terminal the entire Terminal app including all tabs) and there is no way to work around this or tweak that devonfw-ide could do to prevent the problem.

While I fully agree with the users PoV here, I assume it may be technically impossible to properly solve this.
We can try and pilot that at least the environment changes done by devon (if run as alias without commands) also apply after calling devon with arguments. However, the trade-off would be a small performance overhead but maybe still worth it.

[hohwille]

What we could discuss is that after each devon ... command always the same side effect will happen as if you called devon command once again after that.

setup of environment is currently happening here:

ide/scripts/src/main/resources/scripts/devon

Line 40 in 70baf93

source scripts/environment-project

We should devon AND devon.bat to do it again after the call of the commandlet:

ide/scripts/src/main/resources/scripts/devon

Line 166 in 70baf93

"${DEVON_IDE_HOME}/scripts/command/${command}" "${args}"

and

ide/scripts/src/main/resources/scripts/devon

Line 169 in 70baf93

"${DEVON_IDE_HOME}/scripts/command/${command}" "${@}"

To avoid further redundancy we should resolve the call to a single call (via if [ -z "${args}" ]; then args="${@}"; fi).