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

Upgrade EclipseLink from 2.7.10 to 2.7.12 #5607

Merged
merged 1 commit into from
Mar 5, 2023

Conversation

pepness
Copy link
Member

@pepness pepness commented Mar 4, 2023

Library Notes:

  • This is mainly a maintenance release and contains bug fixes

NetBeans Testing:

  • Full build done
  • Verify successful execution of libraries and licenses Ant test
  • Verify successful execution of unit tests for modules websvc.restlib, j2ee.eclipselink, j2ee.eclipselinkmodelgen, j2ee.jpa.refactoring, j2ee.metadata.model.support, j2ee.persistence and j2ee.persistenceapi
  • Started NetBeans and ensure the log didn't have any ERROR or new WARNINGS
  • Checked the files are in the Ant Library Manager
  • Successfully create project as per NetBeans Documentation, with MariaDB, TomEE 8 plus and GlassFish 5.1.0

EclipseLink Web Page
EclipseLink Release Notes

@pepness pepness added Java EE/Jakarta EE [ci] enable enterprise job Upgrade Library Library (Dependency) Upgrade labels Mar 4, 2023
@pepness pepness added this to the NB18 milestone Mar 4, 2023
@pepness pepness self-assigned this Mar 4, 2023
@tbw777
Copy link
Contributor

tbw777 commented Mar 4, 2023

why not 4.0.1 ?

Copy link
Member

@mbien mbien left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good to me

@matthiasblaesing
Copy link
Contributor

@tbw777

why not 4.0.1 ?

EclipseLink is the reference implementation of JPA. As part of the transition of JavaEE from Oracle to the Eclipse Foundation, the project had to change its name and someone (my gut feeling is lawyers/markting people) force the Eclipse Foundation to also change the package names. JavaEE got renamed to JakartaEE and building against recent versions are the libraries require users to switch from the javax to the jakarta based classes.

As long as we stay in the 2.X series for Eclipselink this is a save update, Eclipselink 4.X and newser need to be packaged as separate modules as I assume, we will see a long time of coexistence of JakarteEE 8 and JakartaEE 10+ (the former still in the javax packages, the latter in the jakarta package namespace).

@pepness pepness merged commit 01f8c4b into apache:master Mar 5, 2023
vieiro pushed a commit to vieiro/netbeans-cnd that referenced this pull request Mar 6, 2023
This is mainly a maintenance release and contains bug fixes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Java EE/Jakarta EE [ci] enable enterprise job Upgrade Library Library (Dependency) Upgrade
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants