Mercurial > hg > Blog

comparison content/Eclipse/workspacemechanic.md @ 37:9c4944f26b00

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
new blog post about the workspacemechanic plugin
author Dirk Olmes <dirk@xanthippe.ping.de>
date Mon, 08 Sep 2014 11:34:16 +0200
parents
children 47fa61e1845e
comparison
equal deleted inserted replaced
36:96084c11584a 37:9c4944f26b00
1 Title: Automating Eclipse Workspace Settings
2 Date: 2014-09-08
3 Lang: en
4
5 Working in a team of developers sometimes requires you to unify certain settings in the Eclipse workspace. We used to solve this manually by documenting the required settings on a wiki page. This woks only so good because everyone (including me) tends to forget about those settings and when crating a new workspace all is mixed up.
6
7 Since manually managing the workspace settings does not quite work it would be good to automate the preference management. The [workspacemechanic plugin](https://code.google.com/a/eclipselabs.org/p/workspacemechanic/) comes in very handy here. It works quite simple: you install the plugin, define the settings you want to unify across all workspaces and distribute those rules. The plugin then checks your current preference settings and will allow you to fix anything that does not match the required setup.
8
9 A rather undocumented feature of the plugin is how to distribute rules. Just put all rules on a HTTP server. Then, create a json document that references all these rules in the same directory as the rules files. Use this snippet as a template:
10
11 {
12 type : 'com.google.eclipse.mechanic.UriTaskProviderModel',
13 metadata : {
14 name : 'Workspace Settings',
15 description : 'Sample Mandatory Workspace Settings',
16 contact: 'my@email.com'
17 },
18 tasks : [
19 'MyFirstRule.epf',
20 'MySecondRule.epf',
21 ]
22 }
23
24 As the last step, configure the full URL to the json file as task source. The plugin will load these rules and apply them.