Separate eclipse plugins and keep software installation pristine #1114
Labels
eclipse
related to Eclipse IDE
enhancement
New feature or request
plugins
related to plugins (for Eclipse, Intellij, VSCode, etc.)
setup
related to the setup process of devonfw-ide (setup[.bat] and devon ... setup)
software
software-package with 3rd party products
Milestone
As a devonfw-ide maintainer and product-owner, I want to keep the installation of the
Eclipse
IDE product pristine and have plugins and their updates in a separate folder so that theEclipse
installation itself remains "read-only" and pristine and can be shared across multiple devonfw-ide instances without side-effects between projects.We already have managed to archive this goal for vscode and intellij so Eclipse is the only tool missing to complete the goal (see also bug #1082 that otherwise cannot be cleanly resolved).
One option could be to set this:
However, this will only cause Eclipse to load (additional) plugins/features from there while still installing new plugins/features into the
Eclipse
product itself that therefore manipulates itself.Another option to try could be:
See related issue #1147
Maybe there are even other options so first step would be to test, evaluate and analyse this before even creating a PR.
The goal would be that plugins installed via commandline AND plugins installed within Eclipse itself (ideally including via Eclipse update functionality of its own internal plugins shipped with the product) would go to the newly configured
«my-plugin-folder»
that could be${DEVON_IDE_HOME}/software/eclipse-plugins
to follow current conventions. But also we could revisit this and consider moving plugins fromsoftware
to their own top-levelplugins
folder as they are something different to the rest we put insoftware
.The text was updated successfully, but these errors were encountered: