[ 
https://issues.apache.org/jira/browse/OPENJPA-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18108017#comment-18108017
 ] 

ASF subversion and git services commented on OPENJPA-2940:
----------------------------------------------------------

Commit cdd9831f0773f6d4a9afa2247bc43e33ef408947 in openjpa's branch 
refs/heads/jpa32-migration-considerations from Richard Zowalla
[ https://gitbox.apache.org/repos/asf?p=openjpa.git;h=cdd9831f0 ]

[OPENJPA-2940] Add migration considerations for OpenJPA 4.2.0 (Jakarta 
Persistence 3.2)

Documents the incompatibilities, default changes, platform/dependency
requirements, database-specific changes, SPI changes and notable new
features introduced by the Jakarta Persistence 3.2 implementation (#144),
derived from the merged code changes and the PR review discussion.


> Implement Jakarta Persistence 3.2
> ---------------------------------
>
>                 Key: OPENJPA-2940
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2940
>             Project: OpenJPA
>          Issue Type: Improvement
>            Reporter: Paulo Cristovão de Araújo Silva Filho
>            Assignee: Maxim Solodovnik
>            Priority: Major
>             Fix For: 4.2.0
>
>         Attachments: image-2026-03-28-14-55-26-463.png
>
>
> Implement Jakarta Persistence API 3.2 as prescribed by 
> [specification|https://jakarta.ee/specifications/persistence/3.2/] and 
> required by Jakarta EE 11.
> This change requires JDK17 or higher compatibility and needs considerable 
> checks.
> I've already pushed a branch (WIP) without the proper API bump, focusing on 
> updating dependencies while keeping the project passing its current tests at 
> least in default profile.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to