Jump to: navigation, search

Difference between revisions of "Workspace4.0"

(New page: This page describes some ideas we have for the Workspace components in Eclipse 4.0. Disclaimer: What follows is not to be considered a commitment to address any of the mentioned issues in...)
 
(Eclipse File System)
Line 12: Line 12:
 
editor associations [https://bugs.eclipse.org/bugs/show_bug.cgi?id=120602 120602]
 
editor associations [https://bugs.eclipse.org/bugs/show_bug.cgi?id=120602 120602]
 
session and persistent property caches
 
session and persistent property caches
 +
deltas/change notification
 
repository providers
 
repository providers
 +
transactions
  
 
== Decouple Workspace ==
 
== Decouple Workspace ==

Revision as of 13:59, 7 September 2007

This page describes some ideas we have for the Workspace components in Eclipse 4.0.

Disclaimer: What follows is not to be considered a commitment to address any of the mentioned issues in 4.0. It is only meant as a place to discuss the possibilities.

Eclipse File System

Push down some functionality to the EFS level

local history search compare editor associations 120602 session and persistent property caches deltas/change notification repository providers transactions

Decouple Workspace

Support access to multiple workspaces simultaneously

Support remote workspaces

Decouple the concept of the workspace w.r.t the application from the concept used by the Resources plug-in

Flexible Project Organization

(see bug 35973)

sharing of settings above the project level but below the workspace level

repository root above the project level but below the workspace level

separate namespaces within a single workspace to support development on multiple project versions, for example

isolate sets of projects within a single workspace (although multiple workspace support is similar) so that builds and searches and be localized to a single set (or, it is easier to identify what set a particular java clas is found in, for instance)

configure location of project meta-data either at the workspace level or at some level above the project

Ensure Maven2 is well supported

Support scenario where two source folders within a single project can have a one way dependency (comment 54 of bug 35973)

Resource Links

repository root at the link level