Hi all,
I am attempting to setup code formatting preferences for my company that are identical across all of our projects. Initially I looked at Workspace Mechanic and the Common Preferences plugin, but these seem to have died off after Oomph was introduced - presumably because Oomph does the same things better and offers additional capabilities?

Basically what we are trying to achieve is to define a global code format profile, and use a tool (like Oomph) to keep all of the developers' environments up to date with the central definition. This way a team lead can modify the central code format profile and the change will be pushed to every dev's eclipse the next time it starts up (or better yet at some polling interval).

Is this possible?

I tried to achieve this by creating my own product.setup file with all the plugins/repos we use. I was then trying to populate it with User Preferences by first recording preference changes into my workspace.setup file, and then copying those into the product.setup file. The problem I ran into with the formatter is that the only preference the Oomph recorder saved was the profile name that is selected. Is there a way to include the profile in the setup file as well?

I've seen comments on the forum and in blog articles about using project settings for formatter preferences, but we don't want to do that. We don't work on code external to our company, we always use the same formatter. We don't want to maintain multiple project.setup files every time a format setting changes.

My hope is that after defining a product.setup file with formatter and other preferences, I can host it at an HTTP url, and our developers can point the Eclipse installer at it to install the company flavor of Eclipse. If the installer is pointed at a URL for the product.setup file, does that mean that Eclipse will check this remote product.setup file each time it starts to see if it has changed and then update Eclipse accordingly?

I'm afraid I may be fundamentally misunderstanding Oomph's capabilities. Most of the blogs/docs are more interested in explaining how to roll up all your plugins in a distro, which is neat, but not our main requirement. I'm really hoping Oomph is able to facilitate team code formatting standards because it looks like a lot of thought and effort has gone into this tool, and it seems to be the future of Eclipse preference management.

<?xml version="1.0" encoding="UTF-8"?>
<setup:CompoundTask
    xmi:version="2.0"
    xmlns:xmi="http://www.omg.org/XMI"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:setup="http://www.eclipse.org/oomph/setup/1.0"
    name="org.eclipse.jdt.ui">
  <setupTask
      xsi:type="setup:PreferenceTask"
      key="/instance/org.eclipse.jdt.ui/formatter_profile"
      value="_MyFormatter"/>
  <setupTask
      xsi:type="setup:PreferenceTask"
      key="/instance/org.eclipse.jdt.ui/formatter_settings_version"
      value="12"/>
  <setupTask
      xsi:type="setup:PreferenceTask"
      key="/instance/org.eclipse.jdt.ui/org.eclipse.jdt.ui.formatterprofiles"
      value="*** removed because it's very big ***"/>
</setup:CompoundTask>