Support for plugin_customization.ini to override workspace defaults?

[dnwe]

Eclipse has the concept of a plugin_customization.ini that you can use to override the default values of workspace preferences when initializing a new workspace. This is normally used for branded eclipse product builds, but you can also manually specify one in your eclipse.ini with the -plugincustomization <filename> option (see eclipse doc here)

e.g., some examples of useful default override options that I might want to ship with a build

org.eclipse.ui/defaultPerspectiveId=org.eclipse.jdt.ui.JavaPerspective
org.eclipse.e4.ui.css.swt.theme/themeid=org.eclipse.e4.ui.css.theme.e4_classic
org.eclipse.jdt.ui.prefs/editor_save_participant_org.eclipse.jdt.ui.postsavelistener.cleanup=true
org.eclipse.jdt.ui.prefs/sp_cleanup.format_source_code=true
org.eclipse.jdt.ui.prefs/sp_cleanup.format_source_code_changes_only=true
org.eclipse.jdt.ui.prefs/sp_cleanup.on_save_use_additional_actions=true
org.eclipse.jdt.ui.prefs/sp_cleanup.remove_trailing_whitespaces=true
org.eclipse.jdt.ui.prefs/sp_cleanup.remove_trailing_whitespaces_all=true

You could even use this to ship a different default code formatter (e.g., google-style) by using org.eclipse.jdt.core.prefs/ settings

(feel free to close this off if you'd prefer to keep things simple)

[ferstl]

I think that can also be done with the Touchpoint mechanism as described in issue #6, right?