Posted by
dscho on
Dec 18, 2013; 3:56pm
URL: http://imagej.273.s1.nabble.com/Blocking-Fiji-s-Updater-tp5005907p5005941.html
Hi Olivier,
On Wed, 18 Dec 2013, Burri Olivier wrote:
> Thanks for the info. Just curious. This one-liner:
> > imagej.util.Prefs.put(imagej.updater.core.UpToDate.class, "latestNag", Long.MAX_VALUE);
>
> I could add it to a startup macro to my setup and push this to our Git server, that way this gets configured for each user?
>
> Would that work?
Since this would also work around the problems with the massive stitcher
containing obsolete .class files, that would probably be a good idea.
However, this would not be Fiji anymore: the updater was and is the most
useful Fiji feature.
And since it would not be Fiji without the updater anymore, and since
users could not simply install another Fiji that would get auto-updated as
it should be, I foresee exactly the same type of trouble as with the
massive stitcher, and I would like not having to deal with the diagnosis
of such problems myself again.
Therefore, I suggest to make a modified Fiji *and label it as such* so that
users do not think that this is Fiji. This modified Fiji should have a
modified updater that does not perform the up-to-date check at all.
Ciao,
Johannes
--
ImageJ mailing list:
http://imagej.nih.gov/ij/list.html