Feature idea
As an IDEasy user, I want IDE-specific metadata (.idea, .vscode) to be stored outside of my workspace so that workspaces remain clean and independent of the IDE being used.
Currently, IDE-specific metadata is stored under $IDE_HOME/workspaces/<workspace>/. This metadata should be moved to a dedicated location below $IDE_HOME/.ide.
If IDE-specific metadata needs to remain separated per workspace, a corresponding workspace-specific subfolder should be created (e.g. $IDE_HOME/.ide/vscode/main/config).
Implementation should consider the existing IDE workspace configuration mechanism (e.g. ~/.ide/<IDE>/workspace/) and ensure compatibility with workspace-specific IDE settings.
Additional context
Existing workspaces may already contain .idea and .vscode folders. The migration and upgrade path for existing IDEasy installations should be considered to avoid requiring users to manually recreate or reconfigure their IDE workspace settings.
https://github.com/devonfw/IDEasy/tree/main/cli/src/main/java/com/devonfw/tools/ide/migration
ATTENTION: I would recommend to create separate PRs (and maybe even subtasks) for IntelliJ, VSocde (will Android-Studio and PyCharm be handled together with IntelliJ because we can solve it in their common super-class?)
Feature idea
As an IDEasy user, I want IDE-specific metadata (
.idea,.vscode) to be stored outside of my workspace so that workspaces remain clean and independent of the IDE being used.Currently, IDE-specific metadata is stored under
$IDE_HOME/workspaces/<workspace>/. This metadata should be moved to a dedicated location below$IDE_HOME/.ide.If IDE-specific metadata needs to remain separated per workspace, a corresponding workspace-specific subfolder should be created (e.g.
$IDE_HOME/.ide/vscode/main/config).Implementation should consider the existing IDE workspace configuration mechanism (e.g.
~/.ide/<IDE>/workspace/) and ensure compatibility with workspace-specific IDE settings.Additional context
Existing workspaces may already contain
.ideaand.vscodefolders. The migration and upgrade path for existing IDEasy installations should be considered to avoid requiring users to manually recreate or reconfigure their IDE workspace settings.https://github.com/devonfw/IDEasy/tree/main/cli/src/main/java/com/devonfw/tools/ide/migration
ATTENTION: I would recommend to create separate PRs (and maybe even subtasks) for IntelliJ, VSocde (will Android-Studio and PyCharm be handled together with IntelliJ because we can solve it in their common super-class?)