Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 319641 - Allow setting a global (cross-workspace) settings path
Summary: Allow setting a global (cross-workspace) settings path
Status: CLOSED DUPLICATE of bug 79708
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Runtime (show other bugs)
Version: 4.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: platform-runtime-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-12 17:36 EDT by Mike Schrag CLA
Modified: 2010-07-12 18:20 EDT (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 Mike Schrag CLA 2010-07-12 17:36:13 EDT 
Build Identifier: 3.6

Currently settings are stored inside of the workspace/.metadata/.plugins/org.eclipse.core.runtime/.settings folder. If I have multiple workspaces, there's no way for me to specify that I want to simply have a single set of preferences that are used by all my workspaces. You can import/export except that this is a pretty clunky process if you are switching workspaces fairly often. It would be nice if the path to the .settings folder could be overridden in the root osgi properties file, or possibly in some other workspace setting. This would allow me to make the settings path for all my workspaces something like "~/.eclipse/settings" so I don't have to constantly sync them. It would also make it easier to just hand this folder to new team members.

Reproducible: Always
Comment 1 Remy Suen CLA 2010-07-12 18:18:19 EDT 
Mm, dupe of bug 79708 I guess.
Comment 2 Mike Schrag CLA 2010-07-12 18:20:58 EDT 
Yep -- it is ... I didn't pick the magic keywords on my search. Thanks!

*** This bug has been marked as a duplicate of bug 79708 ***