Bug 76940 [Preferences] Update JFace javadoc for #putValue and notification
build R3.0 The javadoc for JFace's IPreferenceStore#putValue needs to be updated. The #putValue method does not send out any notification which can cause ill effects if people call this method while others are relying on property change listeners for changes to the values. The spec should be updated to say that clients should only call it when changing their own private preference keys and should not be calling it when modifying public API preference keys.
bundles/org.eclipse.jface/src/org/eclipse/jface/preference/IPreferenceStore.java
* 	<li><code>String</code> = <code>""</code> (the empty string)</li>
 * </ul>
 * <p>
 * Thus a preference store maintains two values for each of a set of
 * names: a current value and a default value.
 * The typical usage is to establish the defaults for all known preferences
 * and then restore previously stored values for preferences whose values 
 * were different from their defaults. After the current values of
 * the preferences have been modified, it is a simple matter to write
 * out only those preferences whose values are different from their defaults.
 * This two-tiered approach to saving and restoring preference setting
 * minimized the number of preferences that need to be persisted; indeed,
 * the normal starting state does not require storing any preferences
 * at all.
 * </p>
 * <p>
 * A property change event is reported whenever a preferences current
 * value actually changes (whether through <code>setValue</code>,
 * <code>setToDefault</code>, or other unspecified means). Note, however,
 * that manipulating default values (with <code>setDefault</code>)
 * does not cause such events to be reported.
 * </p>
 * <p>
 * Clients who need a preference store may implement this interface or 
 * instantiate the standard implementation <code>PreferenceStore</code>.
 * </p>
 *
 * @see PreferenceStore
 */
public interface IPreferenceStore {