Hi all, I fixed an issue about records (java 16) JSON-B annotation support - no annotation mapping (ie our mapper) was working but not JSON-B custom annotations and changed the path used to test "dedup" enablement to avoid the regular issues we get about it (unsupported types, un-opened types on recent JVM etc).
Changelog is: PTKeySummaryAssigneeStatus [image: Major] [image: Improvement] JOHNZON-348 <https://issues.apache.org/jira/browse/JOHNZON-348> JSON-B annotations not supported on record constructor parameters <https://issues.apache.org/jira/browse/JOHNZON-348> Romain Manni-Bucau <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=romain.manni-bucau> RESOLVED [image: Major] [image: Improvement] JOHNZON-349 <https://issues.apache.org/jira/browse/JOHNZON-349> Rework dedup check code path to ensure to only read related annotation when classmapping is loaded <https://issues.apache.org/jira/browse/JOHNZON-349> Romain Manni-Bucau <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=romain.manni-bucau> RESOLVED Is it ok to release 1.2.14 like that? #348 is not hurting but #349 is worth some validations in applications using it so was thinking about giving some opportunity to test master before letting go out. Just let me know if there is a blocker to release next week, some features/fixes are awaited by users (including some related to the dedup issue I mentionned). Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance>
