public final class DfsConfig extends StoredConfig
The current implementation acts as if there is no persistent storage: loading simply clears the config, and saving does nothing.
Config.ConfigEnum, Config.SectionParser<T>
Constructor and Description |
---|
DfsConfig() |
Modifier and Type | Method and Description |
---|---|
void |
load()
Load the configuration from the persistent store.
|
void |
save()
Save the configuration to the persistent store.
|
clear
addChangeListener, fireConfigChangedEvent, fromText, get, getBoolean, getBoolean, getEnum, getEnum, getInt, getInt, getLong, getLong, getNames, getNames, getNames, getNames, getRefSpecs, getSections, getString, getStringList, getSubsections, getTimeUnit, isUtf8, notifyUponTransientChanges, readIncludedConfig, setBoolean, setEnum, setInt, setLong, setString, setStringList, setTypedConfigGetter, toText, uncache, unset, unsetSection
public void load() throws IOException, ConfigInvalidException
If the configuration does not exist, this configuration is cleared, and thus behaves the same as though the backing store exists, but is empty.
load
in class StoredConfig
IOException
- the configuration could not be read (but does exist).ConfigInvalidException
- the configuration is not properly formatted.public void save() throws IOException
save
in class StoredConfig
IOException
- the configuration could not be written.Copyright © 2019 Eclipse JGit Project. All rights reserved.