On Wed, 18 Feb 2026 07:17:51 GMT, Alan Bateman <[email protected]> wrote:
>> Please review the finalized PEM API at https://openjdk.org/jeps/8360563. The >> most significant changes from the second preview, JEP 524 >> (https://openjdk.org/jeps/524), include: >> >> - `PEM` is changed from a record to a class, with content stored in binary >> form and data defensively copied. >> - `DEREncodable` is renamed to `BinaryEncodable` to more accurately reflect >> the binary data stored in PEM text. >> - In `EncryptedPrivateKeyInfo`, the `encrypt` methods now accept >> `BinaryEncodable`, and the `getKey()` and `getKeyPair()` methods no longer >> include a `Provider` parameter. >> - A new `CryptoException` indicates failures during cryptographic processing >> at runtime. >> >> thanks > > src/java.base/share/classes/jdk/internal/javac/PreviewFeature.java line 92: > >> 90: @JEP(number=524, title="PEM Encodings of Cryptographic Objects", >> 91: status="Second Preview") >> 92: PEM_API, > > @lahodaj This comes up each time that a feature proposes to become permanent > after being in preview. Do we still leave the value in place for one release > and then cleanup in release N+1 ? This came up the last time too and Jan explained how to deal with the removal of these constants. I've now added a comment and pinned it to that previous JBS issue at https://bugs.openjdk.org/browse/JDK-8365699?focusedId=14856891&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14856891 ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/29640#discussion_r2820795515
