I think I have a related question:
I'm using Workspace Mechanic for rollout of Eclipse to a large team. There is a number of default Preferences that I want all team members to use. I'm using plugin_customization.ini to set these "silently" by default, along with Workspace Mechanic to check if anybody changes the default after the fact. I have a large list of indiivdual Mechanic tasks for individual Preferences to check, such that people who change a Preference (and see the warning) can understand what they are doing.
Now the problem with this setup is, that people who launch Eclipse for the first time see a very large number of Mechanic warnings, for each and every task - although in reality all of these warnings are bogus since the plugin_custimization,ini already specifies proper defaults. This is confusing and I'd like to avoid it.
Has anybody had this problem before ? - I think what I'd like is the Mechanic checker to only report an error if a Preference _exists_ AND has a value other than what the task says. Preferences which do not exist yet (since a respective plugin has not been activated yet, and thus its PreferenceInitializer has not run) should not be warned about. Preferences which do exist but are set to the default value and the default value is proper should also not be warned. If I'm not mistaken, this is the same request as the original submitter Mats had.
This should be a relatively simple change to the checker, shouldn't it ?
If a solution doesn't exist yet I'd be happy contributing if you give me some minimal advice about the approach (eg should I use meta-tags in the task for the new functionality) and where to change things.