Bug 507613 - [IDE Discussion] Open the Workspace behavior making the .project optional
Summary: [IDE Discussion] Open the Workspace behavior making the .project optional
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 4.6   Edit
Hardware: PC Windows 10
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-16 09:29 EST by Patrik Suzzi CLA
Modified: 2016-11-18 18:54 EST (History)
1 user (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 Patrik Suzzi CLA 2016-11-16 09:29:14 EST 
As highlighted in the Mattermost discussion starting at [#1], we should open the workspace behavior as follows:

- Do not force the .project to be there: Remove project nature as statical annotation and advise the users they should stop relying on project's nature.
- Support nested projects "naturally."
- The content edition/build assist should be plugged in dynamically to a set of resource folders (like in Atom)

Ideally, we should allow the user to add/import/open a folder from HDD, and then let Eclipse run the import in background, setting up the workspace as the tools expect it

Note: we could use a preference store that is Workspace specific (e.g. used by Oomph), in <workspace>/.metadata/.plugins/org.eclipse.core.runtime/*.prefs , programmatically WorkbenchPlugin.getDefault().getPreferenceStore() 

[#1] https://mattermost.eclipse.org/eclipse/pl/zzky1akoc3rrp8ucxr8appdg9c