Skip to content
New issue

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

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

Already on GitHub? # to your account

Eclipselink libs upgrade (4.0.5) #25313

Closed
chicko12345 opened this issue Jan 7, 2025 · 4 comments · Fixed by #25318
Closed

Eclipselink libs upgrade (4.0.5) #25313

chicko12345 opened this issue Jan 7, 2025 · 4 comments · Fixed by #25318

Comments

@chicko12345
Copy link

Environment Details

  • GlassFish 7.0.21
  • JDK version: 21
  • OS: Windows
  • Database: Oracle/PostgreSQL

Problem Description

Hi Community,
Is there a reason why the eclipselink libraries in modules are provided in version 4.0.3?
There was a release 4.0.4 and since end of last year there is a version 4.0.5 containing important bug fixes.
Is it possible to update the libs to 4.0.5 in the comming 7.0.22 release of glassfish?

Kind regards.

@arjantijms
Copy link
Contributor

4.0.4 caused big failures in the TCK, so we reverted that. 4.0.5 came in just too late for the 7.0.21 so that we could still conduct adequate testing. If no major problems pop up 4.0.5 will certainly be in 7.0.22

@chicko12345
Copy link
Author

4.0.4 caused big failures in the TCK, so we reverted that. 4.0.5 came in just too late for the 7.0.21 so that we could still conduct adequate testing. If no major problems pop up 4.0.5 will certainly be in 7.0.22

OK. Thank you for the information.
Is the eclipselink community aware of the problems in 4.0.4 for glassfish?

Kind regards.

@arjantijms
Copy link
Contributor

Yes, they are.

See eclipse-ee4j/eclipselink#2323

And

eclipse-ee4j/eclipselink#2319

@chicko12345
Copy link
Author

Yes, they are.

See eclipse-ee4j/eclipselink#2323

And

eclipse-ee4j/eclipselink#2319

Nice. Thank you! And it seems to be fixed now. That means, 4.0.5 could be considered for glassfish 7.0.22. Am i right?

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants