Bug 489719 - Propose to make Eclipse part of the PATH and associate it with files at OS level
Summary: Propose to make Eclipse part of the PATH and associate it with files at OS level
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.5   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-16 04:57 EDT by Mickael Istria CLA
Modified: 2016-03-21 07:58 EDT (History)
6 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mickael Istria CLA 2016-03-16 04:57:12 EDT 
When opening the IDE for the first time, it would be convenient that it suggests to integrate better with the OS, by proposing to:
* Add itself to some OS menus
* Add itself to the PATH
* Register file-associations at OS-level
* ... maybe others ...
Comment 1 Alexander Kurtakov CLA 2016-03-16 05:54:01 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?
Comment 2 Mickael Istria CLA 2016-03-16 06:03:07 EDT 
(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)
Comment 3 Patrik Suzzi CLA 2016-03-16 06:13:18 EDT 
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)
Comment 4 Mickael Istria CLA 2016-03-21 07:58:47 EDT 
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.