Endless loop when installing Eclipse in force mode

[hohwille]

Expected behavior

As a IDEasy user, I want to be able to combine CLI options with tool installations seamlessly so that I do not end up in errors.

Actual behavior

When installing eclipse with --force mode I end up in an infinity loop.

Steps to reproduce (bug) / Use Case of feature request (enhancement)

1. Ensure eclipse is not installed or not up-to-date.
2. ide -f eclipse

Comments/Hints:

This is causing the error:

IDEasy/cli/src/main/java/com/devonfw/tools/ide/tool/LocalToolCommandlet.java

Lines 195 to 196 in 42201ed

	if (this.context.isForceMode()) {
	fileAccess.delete(installationPath);

The problem is that at the end of the installation postInstall is called that then triggers the plugin installation what for Eclipse needs to run the tool itself to install plugins via runTool. The latter again calls install to ensure the tool is already installed before running it.
This is rather a design problem than a real implementation bug.
We could somehow keep a state to track that we just installed eclipse and then consider this state to prevent the deletion in force-mode but for KISS I would suggest to remove this force feature here. The user can do ide uninstall eclipse && ide install eclipse to get this behaviour consistently.
IMHO: --force should rather disable caches like git-cache timeouts or download-cache. Besides for the end-user the behaviour of --force is so far rather undocumented or at least unclear:

-f | --force    enable force mode.

So what does that mean?

Affected version:

• 2024.09.002-beta-SNAPSHOT