Ticket #2035 (closed defect: moved)

Sometimes people want to deploy a version of Fiji that never checks for updates, and/or does not even have updater functionality at all, preferring to carefully control the updates themselves using an alternative mechanism (e.g., Git).

We should make sure the architecture of ImageJ2 allows for this.

For example, right now, Fiji tries to invoke the remote ImageJ updater if ij-updater*.jar is missing from its installation, and ImageJ2 has a hardcoded invocation of the UpToDate command directly in AbstractUserInterface, which is definitely the wrong approach. Better would be for commands to be able to annotate themselves as auto-run, and/or have a flexible auto-run mechanism that by default ships with the UpToDate check included. That way, users can just remove the UpToDate check from the auto-run configuration to disable the updater.