It is desirable to keep native keyring implementations in a separate module from the API, to avoid a hard dependency on JNA.
While it might be desirable to keep master password encryption (no native dependencies) in the core API module, this would necessitate API changes, since EncryptionProvider is used by both master password encryption and the Crypt32.dll-based implementation. The core module implements a trivial in-memory keystore, so it is not completely useless on its own.
core-main #4d17ef4f9577 (parented to release69_base)
Also to try to stave off problems with dev AU, adjusting spec versions (would need to be done separately in release69 if needed): core-main #36c355b00cd4
Integrated into 'main-golden', will be available in build *201006120001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
User: Jesse Glick <email@example.com>
Log: #187448: keyring implementations separated from API.
Please verify bugfix for this bug, so it can be included in release691 repository.
Verified in 20100613000115.
Transplanted to release691 as b88cbe8742f2
rbalada please also note:
(In reply to comment #1)
> Also to try to stave off problems with dev AU, adjusting spec versions (would
> need to be done separately in release69 if needed): core-main #36c355b00cd4
Since the main patch involved an incompatible change to libs.jna (change of friends), it is necessary to ensure that spec versions are incremented to force a push of the new keyring, libs.jna, and keyring.impl together. Perhaps you plan to do a bulk spec version update for all of release691 anyway, in which case this can be ignored.