Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RCP launcher: support additional VM args configuration file #695

Open
serge-rider opened this issue Nov 8, 2024 · 0 comments
Open

RCP launcher: support additional VM args configuration file #695

serge-rider opened this issue Nov 8, 2024 · 0 comments

Comments

@serge-rider
Copy link

serge-rider commented Nov 8, 2024

Eclipse RCP apps have main configuration file eclipse.ini (or <app-name>.ini) where users can change default launch parameters.

The problem is: every time user reinstall application it loses all changes in this file.
Proposed solution: allow users to create separate default configuration file which will remain after application uninstall. Exact location must be application-specific, it maybe something like ${user.home}/default-eclipse-config.ini.

This will significantly simplify life of users who perform frequent application update or who use some automation for app install on end-user machines.

Original feature request in DBeaver project: dbeaver/dbeaver#35080
I think it will be a useful addition for Equinox infrastructure.

Proposed solution is implemented in PR #690

Currently we are trying to build custom Equinox launcher for DBeaver with these changes on our side. But it is quite tricky because of sophisticated compile/link procedure on different platforms. It would be wonderful to have it in the upstream codebase.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant