Task summary
Currently, when installing LocalToolCommandlets, the installation logic requires us to be inside a project when installing a tool, e.g. Java. This is, because the installation logic always tries to create symlinks (if not via install(), installToolDependencies() ends up doing this nevertheless). For some use-cases however (like launching the GUI using java and maven), we do need dependencies like java to be installed in the software repo, however, the requirement for being inside a project in order to install those dependencies creates an unnecessary obstacle (example: we want to be able to launch the GUI from everywhere, not only inside project folders, while at the same time still being able to use the java tool installed in the software repo.)
Additional context
No response
Task summary
Currently, when installing LocalToolCommandlets, the installation logic requires us to be inside a project when installing a tool, e.g. Java. This is, because the installation logic always tries to create symlinks (if not via install(), installToolDependencies() ends up doing this nevertheless). For some use-cases however (like launching the GUI using java and maven), we do need dependencies like java to be installed in the software repo, however, the requirement for being inside a project in order to install those dependencies creates an unnecessary obstacle (example: we want to be able to launch the GUI from everywhere, not only inside project folders, while at the same time still being able to use the java tool installed in the software repo.)
Additional context
No response