Eclipse Community Forums: Eclipse Platform » How to contribute configurations programmatically

Help

Home

Home » Eclipse Projects » Eclipse Platform » How to contribute configurations programmatically

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

How to contribute configurations programmatically [message #634807]

Sat, 23 October 2010 18:49

Markus Oley

Messages: 301
Registered: July 2009
Location: Germany

Senior Member

Hi to all,

I have to contribute some preconfigured eclipse-versions for the developers of our company.

So I looked for a possibility to configure for things like:
-CodeFormatting
-JDK-Settings
-Show heapmonitor
-Configuring CVS-Servers

and many others.

I developed plugins and headless applications to config and create distributions and establish an mirror in our intranet.

Actually I do some configurations just by editing property-files in the .metadata-path, but I'm not very happy with it, because if these configurations change, I don't notice and I guess not all configurations are possible with this technique
.
Would be better to use a API for this, but I didn't find anything I can use. Didn't I search at the right place?

What way should I go to preconfigure these settings?

Hope you can help me,

best regards
Markus

Report message to a moderator

Re: How to contribute configurations programmatically [message #635018 is a reply to message #634807]

Mon, 25 October 2010 12:28

Paul Webster

Messages: 6859
Registered: July 2009
Location: Ottawa

Senior Member

For many workspace level properties, you can use your product's
plugin_customization.ini file to provide defaults (see
eclipse/plugins/org.eclipse.sdk_3.6.0.v201006080911/plugin_c ustomization.ini
for an example).

For some things, like default update sites, they can be provided by a
p2.inf file for your product. This works if you are building your
product using PDE build and p2.

PW

--
Paul Webster
http://wiki.eclipse.org/Platform_Command_Framework
http://wiki.eclipse.org/Command_Core_Expressions
http://wiki.eclipse.org/Platform_Expression_Framework
http://wiki.eclipse.org/Menu_Contributions
http://wiki.eclipse.org/Menus_Extension_Mapping
http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse .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

Re: How to contribute configurations programmatically [message #635420 is a reply to message #635018]

Tue, 26 October 2010 17:50

Markus Oley

Messages: 301
Registered: July 2009
Location: Germany

Senior Member

Hi Paul,

thank you for your answer.

I have still questions:

Can you please give me a hint, were I can find all items I can configure with this solution?

Is this a feature save technique or may the settings be incompatible changed in following releases?

I guess it's very similar to my solution, only difference is that my changes are noticed after eclipse restarts and has to be done manually at each workspace - is there any further difference?

Thanks in advance

Best regards
Markus

Report message to a moderator

Re: How to contribute configurations programmatically [message #635579 is a reply to message #635420]

Wed, 27 October 2010 12:13

Paul Webster

Messages: 6859
Registered: July 2009
Location: Ottawa

Senior Member

Markus Oley wrote:
> Hi Paul,
> thank you for your answer.
> I have still questions:
>
> Can you please give me a hint, were I can find all items I can configure
> with this solution?

It's the list of preferences, and you can only find them by working
through the code.

> Is this a feature save technique or may the settings be incompatible
> changed in following releases?

Preferences published as API will be available, like:
org.eclipse.ui.IWorkbenchPreferenceConstants. Each bundle or component
can choose to make preferences API by publishing them as constants.

> I guess it's very similar to my solution, only difference is that my
> changes are noticed after eclipse restarts and has to be done manually
> at each workspace - is there any further difference?

plugin_customization.ini will be distributed as part of the build and
run on every start. It can also be passed in as a runtime parameter (so
if you really wanted to customize the standard Eclipse SDK product).

The p2.inf solution (for creating default update sites, for example) is
done at build time and will also appear for users on every start.

PW

--
Paul Webster
http://wiki.eclipse.org/Platform_Command_Framework
http://wiki.eclipse.org/Command_Core_Expressions
http://wiki.eclipse.org/Platform_Expression_Framework
http://wiki.eclipse.org/Menu_Contributions
http://wiki.eclipse.org/Menus_Extension_Mapping
http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse .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