Blocking Fiji's Updater

Posted by Olivier Burri on Dec 13, 2013; 4:53pm
URL: http://imagej.273.s1.nabble.com/Blocking-Fiji-s-Updater-tp5005907.html

Dear ImageJ/Fiji list,

We're using Git to keep a good working copy of Fiji with all our custom plugins and modifications. This way we can deploy a copy very easily on all our computers. An update site was not good enough for us, as we're using several plugins that do not yet have their update sites. Also sometimes (And I do say only sometimes) an update will break some older plugin until we fix it, and Git makes it super fast to revert to the previous state.

The idea here is that we do not want the users of our computers to do the updates of Fiji. As the "Image Processing Analysts" (Which seems to be our new name), we want to get the update, make sure we have the latest copy running properly and only then commit it to our Git server.
Whenever a user opens Fiji through a shortcut, the latest branch is pulled from the server and we are now sure that they are running the same version as us.

However using Git this way makes the Fiji Updater unhappy and it sees many locally modified files and prompts for an update at every run

So my question is this: Is there a way to have the updater not automatically check for updates?

Best regards,

Oli

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html