How do I check the default values?

I don't understand what problem you're trying to solve.
--
Robert Konigsberg

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.

Martin, you may be looking for the RECONCILE preference type. [1] Note, though, that RECONCILE tasks could be slower than LASTMOD tasks, especially with such a large number -- so -- profile, please.

--
You received this message because you are subscribed to the Google Groups "Workspace Mechanic for Eclipse" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Thanks Robert,

I see your point and I think you are right.

I had originally thought about deploying team defaults via LASTMOD and then allowing users to have their own modifications on top of that with RECONCILE. But at least for "important" settings where I need to keep users from shooting themselves we'll need RECONCILE tasks on system level anyways (to revert when they accidentally set the preference; independent of the modification time of the task).

The one thing I don't quite understand at this point is, what happens if multiple tasks have overlapping Preferences. Looks like "fixing" one task might then make another one fail. For example, my team settings define "Refresh on access OFF" but a user knows what he's doing and he sets a private usertask "Refresh on access ON" to share across all his Eclipse instances and workspaces.

Is this something that you have experienced, or that you have heard people discuss and what is the general approach here ?

Many thanks for your input !
Martin

Thanks Robin,

I see your point and in fact the "let users choose" philosophy is what I like best about Workspace Mechanic. Still I'd like to notify users when they (accidentally) change a Preference that is recommended to be set differently; thus I believe that RECONCILE is the right task type for settings that are important for overall system sanity and not just cosmetic. In other words, notify users when they are about to shoot themselves.

Unfortunately - coming back to the original topic of this thread - I've noticed that also RECONCILE tasks don't take default values into account on their "compare" step. So when my task wants /instance/foo=false and that Preference happens not to be set but I have default foo=false via plugin_customization.ini, I still get a workspace mechanic popup.

That seems wrong to me, and I want to change the code to allow a comparison to return "OK" when the desired value is unset but the default is proper. I'm ready to change the code (and potentially contribute), I'm just wondering how to best expose the new functionality ... new task type eg RECONCILE_DEFAULT ? Or a new metadata tag eg @allow_default ? Or simply make the new behavior standard ? - Personally I can't see what would be wrong with making the new behavior the standard, but I wanted to hear your opinion.

Thanks!
Martin

Martin,

--