Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EclipseLink issues that need to be fixed for Jakarta Data #28366

Open
13 of 31 tasks
njr-11 opened this issue May 7, 2024 · 3 comments
Open
13 of 31 tasks

EclipseLink issues that need to be fixed for Jakarta Data #28366

njr-11 opened this issue May 7, 2024 · 3 comments

Comments

@njr-11
Copy link
Contributor

njr-11 commented May 7, 2024

This issue will keep a list of EclipseLink issues that need to be fixed/implemented for Jakarta Data. More issues will be added as they are found. This list is in order of priority (top of list is highest priority).

for #19508
for #25091

@Riva-Tholoor-Philip
Copy link
Contributor

Riva-Tholoor-Philip commented Jun 11, 2024

JPA team will work on these items as per the priority. Currently we are giving higher priority for Jakarta 11 (Persistence 3.2) issues and Salesforce L3 cases. That is, Issue# 25091.

@njr-11
Copy link
Contributor Author

njr-11 commented Jun 11, 2024

JPA team will work on these items as per the priority. Currently we are giving higher priority for Jakarta 11 (Persistence 3.2) issues and Salesforce L3 cases. That is, Issue# 25091.

To clarify, these issues are also for Jakarta EE 11, and it is fine if they are only fixed in Persistence 3.2 and not 3.1 or earlier.

@Riva-Tholoor-Philip
Copy link
Contributor

Created EclipseLink issues for the above mentioned issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants