Summary: | Propose to make Eclipse part of the PATH and associate it with files at OS level | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Mickael Istria <mistria> |
Component: | UI | Assignee: | Platform-UI-Inbox <Platform-UI-Inbox> |
Status: | NEW --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | akurtakov, daniel_megert, Ed.Merks, mober.at+eclipse, psuzzi, stepper |
Version: | 4.5 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: |
Description
Mickael Istria
2016-03-16 04:57:12 EDT
First questions that comes to my mind: What happens if you have multiple eclipse instances? Do they all fight which one to be default? (In reply to Alexander Kurtakov from comment #1) > First questions that comes to my mind: > What happens if you have multiple eclipse instances? Do they all fight which > one to be default? IMHO, the latest one that was set to be configured as default becomes default (ie gets to the top position in the PATH) We can use the Java approach by having a control center to manage different instances. In this case we should involve The Eclipse Oomph team as 1. Oomph already has an efficient model to manage multiple Eclipse installations, 2. they already developed a system-wide installer 3. Oomph can save space and keep the bundles within bundle-pools, avoiding to re-download twice a bundle that is already in the system (like a maven local repository) Something else that could be improved as part of this wizard is that the static web project template generates a WebContent folder, which is not useful for JS+HTML Web projects. The specific wizard would directly have index.html on the root. |