Community
Participate
Working Groups
Bug 536589 introduced support for an OS-level URI handler using the eclipse+mpc:// uri scheme to trigger MPC installations. The OS-level handler is currently one fixed Eclipse installation, and clicking an eclipse+mpc:// link will always open MPC in that Eclipse. As a user with multiple Eclipse installations, I want to be able to install marketplace entries into different Eclipse installations though. Ideally, the handler would let me choose from a list of known installations (or picking unknown ones via file chooser), favoring any currently running ones, and dispatch the action to that Eclipse. If the target Eclipse is not running, we could eitehr start it immediately, or remember the request until its next startup and trigger the action then.
We could also investigate moving the handler and dispatcher part out into a minimal RCP that we could put e.g. into ~/.eclipse. This way, we would decrease the risk of the installation that happens to provide the registered handler to be deleted/uninstalled, and thus breaking the handler support.
@Matthias: Can the uri scheme registration implementation be used to customize which Eclipse is registered and how it is started (e.g. with a different application id)?
(In reply to Carsten Reckord - Out of office until August 13 from comment #2) > @Matthias: Can the uri scheme registration implementation be used to > customize which Eclipse is registered and how it is started (e.g. with a > different application id)? So on OS level you just specify a binary that should be started when clicking a link with that scheme. I don't know how to customize this.
