Project

General

Profile

Bug #5119

Make switching to a specific set of modules turn off automatic update feature

Added by Sean Riddle almost 9 years ago. Updated almost 9 years ago.

Status:
Resolved
Priority:
Normal
Category:
build system
Target version:
Start date:
08/04/2010
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
5119

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.


Related issues

Blocked by Kepler - Bug #5099: Import Dependent Modules for KAR doesn't workResolved07/21/2010

History

#1 Updated by Derik Barseghian almost 9 years ago

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.

#2 Updated by David Welker almost 9 years ago

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();
}

#3 Updated by Derik Barseghian almost 9 years ago

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.

#4 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 5119

Also available in: Atom PDF