Eclipse Community Forums: Eclipse Platform » Default configuration for dev environment

Help

Home

Home » Eclipse Projects » Eclipse Platform » Default configuration for dev environment

Show: Today's Messages :: Show Polls :: Message Navigator

Default configuration for dev environment [message #331910]

Sun, 28 September 2008 18:44

Baptiste Mathus

Messages: 5
Registered: July 2009

Junior Member

Hi all,

I'm responsible of providing the Eclipse development environment in my
company.
We're using a lot of different plugins (from eclipse.org or not), most of
the time, each plugin config has to be the same in every developer
workspaces.

From my understanding, to automatically initialize a given workspace with
default configuration for many plugins, I should define files inside the
configurationArea/.settings/some.plugin.fqn

So, some questions:
* Am I right saying this about the .settings directory?
* Is this the right/recommended way to do it?
* How to know the right name for each file? I guess it's something like
the bundle-symbolicname of the plugin I want to be configured. Could I
just take the values exported using "Export Preferences"?

Thanks a lot for any hints.
Cheers.
PS : if you think there's a better newsgroup for this question, please let
me know.

Report message to a moderator

Re: Default configuration for dev environment [message #332009 is a reply to message #331910]

Wed, 01 October 2008 13:41

Paul Webster

Messages: 6859
Registered: July 2009
Location: Ottawa

Senior Member

Baptiste MATHUS wrote:
> Hi all,
>
> I'm responsible of providing the Eclipse development environment in my
> company. We're using a lot of different plugins (from eclipse.org or
> not), most of the time, each plugin config has to be the same in every
> developer workspaces.
>
> From my understanding, to automatically initialize a given workspace
> with default configuration for many plugins, I should define files
> inside the configurationArea/.settings/some.plugin.fqn

AFAIK this may or may not work, depending on if the specific code that
needs the preferences searches the config scope or not (many do not).

The 2 ways to do that at the moment are 1) export all of the preferences
and then import them into each new workspace or 2) copy all of the
*.prefs file from the
<workspace>/.metadata/.plugins/org.eclipse.core.runtime/.settings/ into
(or as you create) each new workspace.

Some preferences (like compiler preferences) can be set per project,
which means they can be saved in your source control along with the
project files.

PW

--
Paul Webster
http://wiki.eclipse.org/Platform_Command_Framework
http://wiki.eclipse.org/Command_Core_Expressions
http://wiki.eclipse.org/Menu_Contributions
http://wiki.eclipse.org/Menus_Extension_Mapping
http://help.eclipse.org/ganymede/index.jsp?topic=/org.eclips e.platform.doc.isv/guide/workbench.htm

Paul Webster
http://wiki.eclipse.org/Platform_Command_Framework
http://wiki.eclipse.org/Command_Core_Expressions
http://wiki.eclipse.org/Menu_Contributions

Report message to a moderator

Previous Topic:	Question about extension-point org.eclipse.ui ViewActions
Next Topic:	ActiveEditorId Expression

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat Aug 17 06:18:17 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter