Skip to content

#1966: Support separate VSCodium plugins folder#2017

Merged
hohwille merged 5 commits into
devonfw:mainfrom
laert-ll:feature/1966-support-separate-vscodium-plugins-folder
Jun 15, 2026
Merged

#1966: Support separate VSCodium plugins folder#2017
hohwille merged 5 commits into
devonfw:mainfrom
laert-ll:feature/1966-support-separate-vscodium-plugins-folder

Conversation

@laert-ll

@laert-ll laert-ll commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

This PR fixes #1966

Related: ide-settings PR#87

Implemented changes:

  • Added Vscode.getPluginsConfigPath(): the VSCodium edition reads plugins from $IDE_HOME/settings/vscodium/plugins, falling back to $IDE_HOME/settings/vscode/plugins when that folder doesn't exist.
  • Removed the leftover VSCodium plugin error-suppression.
  • Added VscodeTest cases for folder selection + fallback.

Testing instructions

  1. Set VSCODE_EDITION=vscodium in $IDE_HOME/settings/ide.properties.
  2. Copy over the $IDE_HOME/settings/vscodium/plugins folder from the ide-settings repository if ide-settings PR#87 not merged yet.
  3. Run ide vscode and confirm those (47) plugins install.
  4. Fallback case: remove settings/vscodium/plugins/, run again and confirm it now installs from $IDE_HOME/settings/vscodium/plugins (7 incompatible plugins are expected to fail)

Checklist for this PR

Make sure everything is checked before merging this PR. For further info please also see
our DoD.

  • When running mvn clean test locally all tests pass and build is successful
  • PR title is of the form #«issue-id»: «brief summary» (e.g. #921: fixed setup.bat). If no issue ID exists, title only.
  • PR top-level comment summarizes what has been done and contains link to addressed issue(s)
  • PR and issue(s) have suitable labels
  • Issue is set to In Progress and assigned to you or there is no issue (might happen for very small PRs)
  • You followed all coding conventions
  • You have added the issue implemented by your PR in CHANGELOG.adoc unless issue is labeled
    with internal
  • You have formulated clear instructions on how to test your contribution under "Testing instructions"

@github-project-automation github-project-automation Bot moved this to 🆕 New in IDEasy board Jun 11, 2026
@laert-ll laert-ll changed the title 1966: Add path configuration for separate VSCodium plugin folder, rem… 1966: Support separate VSCodium plugins folder Jun 11, 2026
@laert-ll laert-ll self-assigned this Jun 11, 2026
@coveralls

coveralls commented Jun 11, 2026

Copy link
Copy Markdown
Collaborator

Coverage Report for CI Build 27561107228

Coverage increased (+0.04%) to 71.14%

Details

  • Coverage increased (+0.04%) from the base build.
  • Patch coverage: No coverable lines changed in this PR.
  • 4 coverage regressions across 1 file.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

4 previously-covered lines in 1 file lost coverage.

File Lines Losing Coverage Coverage
com/devonfw/tools/ide/tool/vscode/Vscode.java 4 86.11%

Coverage Stats

Coverage Status
Relevant Lines: 15873
Covered Lines: 11785
Line Coverage: 74.25%
Relevant Branches: 7072
Covered Branches: 4538
Branch Coverage: 64.17%
Branches in Coverage %: Yes
Coverage Strength: 3.15 hits per line

💛 - Coveralls

@laert-ll laert-ll force-pushed the feature/1966-support-separate-vscodium-plugins-folder branch from 114318b to af6b3c1 Compare June 12, 2026 07:14
@laert-ll laert-ll marked this pull request as ready for review June 12, 2026 07:27
@laert-ll laert-ll moved this from 🆕 New to Team Review in IDEasy board Jun 12, 2026
@AdemZarrouki AdemZarrouki self-assigned this Jun 12, 2026
@AdemZarrouki AdemZarrouki self-requested a review June 12, 2026 09:36
@AdemZarrouki

AdemZarrouki commented Jun 15, 2026

Copy link
Copy Markdown
Contributor

tested with GraalVM

$ "C:\Users\projects\IDEasy\workspaces\main\IDEasy\cli\target\ideasy.exe" vscode
Start: Configuring workspace test for IDE vscode
Successfully ended step 'Configuring workspace test for IDE vscode'.
No CVEs found for version 1.121.03429 of tool vscode/vscodium.
Installing Plugins 100% [=====================================================================================] 47/47 Plugins (0:00:00 / 0:00:00) ? Plugins/s
Successfully completed ide (vscode)

when deleting $IDE_HOME/settings/vscodium/plugins 7 plugins fail

@AdemZarrouki AdemZarrouki moved this from Team Review to 👀 In review in IDEasy board Jun 15, 2026
@laert-ll laert-ll changed the title 1966: Support separate VSCodium plugins folder #1966: Support separate VSCodium plugins folder Jun 15, 2026

@hohwille hohwille left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@laert-ll thanks for your PR. All great and ready for merge. 👍

@hohwille hohwille added this to the release:2026.06.001 milestone Jun 15, 2026
@hohwille hohwille merged commit 3536fda into devonfw:main Jun 15, 2026
2 checks passed
@github-project-automation github-project-automation Bot moved this from 👀 In review to ✅ Done in IDEasy board Jun 15, 2026
@hohwille hohwille added vscode Microsoft visual studio code plugins related to plugins (for Eclipse, Intellij, VSCode, etc.) labels Jun 18, 2026
@laert-ll laert-ll added the QA approved Label a PR that has been re-testet via nightly SNAPSHOT after merge and commented. label Jun 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

plugins related to plugins (for Eclipse, Intellij, VSCode, etc.) QA approved Label a PR that has been re-testet via nightly SNAPSHOT after merge and commented. vscode Microsoft visual studio code

Projects

Status: ✅ Done

Development

Successfully merging this pull request may close these issues.

Support separate VSCodium plugins folder

4 participants