This document lists changes made to the CHANGEME API.
Fuller descriptions of all changes can be found below (follow links).
Not all deprecations are listed here, assuming that the deprecated APIs continue to essentially work. For a full deprecation list, please consult the Javadoc.
These API specification versions may be used to indicate that a module requires a certain API feature in order to function. For example, if you see here a feature you need which is labelled 1.20, your manifest should contain in its main attributes the line:
OpenIDE-Module-Module-Dependencies: org.netbeans.modules.keyring > 1.20
Keyring; made by: phejl; issues: #206475
It hasn't been allowed to call the Keyring from EDT. This change removes the limitation as the need to read password from the UI is not so rare. To resolve this people had to code custom threading solution to prevent possible deadlock on fallback implementation of the keyring API.
Existing callers should use the Keyring directly from any thread and should not try to avoid EDT anymore.
SPI implementors should not be changed and they may continue to assume that they will not be called directly from EDT.
A new API was created for securely storing user passwords. Where possible it uses a native keyring.
Modules formerly storing passwords in some other way should
not only begin using
Keyring, but also delete any
passwords from the old storage as they are transferred.
Built on May 22 2013. | Portions Copyright 1997-2013 Oracle. All rights reserved.