Default Location of Workspace - (bug 33976, 34532) Currently if the user doesn't specify the location of their workspace, then the default is to place is in a "workspace" directory under the Eclipse install directory. (equivalent of using "user.dir" java System property) This is very problematic, especially in the cases where you have a multi-user system and a single shared installation (like Linux) where users don't have write access to the installation directory. A better solution would be to use the user's home directory ("user.home" java System property) as a default location. This would result in (for instance) /usr/home/fred (on Linux) or C:/Documents and Settings/Fred/My Documents (on Windows).
Separation of User Settings and Plug-in Metadata - (bug 36965) It is common for users to want to share some settings (like background colours and fonts) with all workspaces that they use with a particular Eclipse install, while other settings (like compiler settings) should be on a per workspace basis. Currently Eclipse all of these settings on a per workspace basis and we would like to remove this bundling.
Multiple Workspaces - (bug 37681, 5509) Users want to be able to better manage multiple workspace within the Eclipse environment. This could either mean coming up with a way to pretty a single Eclipse image running with 2 workspaces loaded, switching between multiple workspaces within the same session (via File -> Open/Close for instance), etc.
Translation of Executable Messages - (bug 35135) The messages which are displayed by the Eclipse executable are currently not translated. We need to define an external message story for this code, as well as the code which is in the startup.jar.
Show User Log File Location - (bug 33974)
When there is an error trying to start Eclipse we produce a dialog to
the user telling them to check their log file but we don't print out the
exact location of this file. If the user specified the -data command-line
argument then the location of the file is easy to calculate. Otherwise,
it is done through Java System properties which is much harder to do in
C code.