Bug #5119
closed
Make switching to a specific set of modules turn off automatic update feature
Added by Sean Riddle about 14 years ago.
Updated about 14 years ago.
Description
Otherwise, as soon as someone restarts Kepler in a specific module configuration (that is not the most recent patched version of all modules) the user is immediately prompted to update. Automatic updates should be turned off until the user turns them back on.
Since I'm working on the Import Dependent Modules feature, if you can simply provide an methods that I can call to get and set automatic update status, that will be sufficient.
The functionality for this is ready to go. Derik just needs to make an appropriate call at the appropriate time.
The following code should do the trick in the appropriate place:
ConfigurationProperty common = ConfigurationManager.getInstance().
getProperty(ConfigurationManager.getModule("common"));
ConfigurationProperty checkForPatches = common.getProperty("check-for-patches");
try
{
checkForPatches.setValue("false");
ConfigurationManager.getInstance().saveConfiguration();
}
catch (ConfigurationManagerException e)
{
e.printStackTrace();
}
Thanks David, I'm now using this feature in 2.1 -- when a user with KARCompliance set to Strict restarts for a KAR requiring specific modules, automatic updating is turned off (and they're warned this will happen, and how to re-enable it).
Closing.
Original Bugzilla ID was 5119
Also available in: Atom
PDF