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 to JavaEE/JakartaEE 8 #4603

Open
erikgb opened this issue May 27, 2023 · 0 comments
Open

Upgrade to JavaEE/JakartaEE 8 #4603

erikgb opened this issue May 27, 2023 · 0 comments
Assignees
Labels
📶 enhancement issue is a new feature or improvement
Milestone

Comments

@erikgb
Copy link
Contributor

erikgb commented May 27, 2023

Problem description

Java EE has become Jakarta EE, and we have to migrate to Jakarta EE to be able to upgrade our "EE" dependencies like servlet, jsp and jaxb.

Jakarta EE 8 is the first release of Jakarta EE, and is fully compatible with Java EE 8 - which means that we can migrate dependencies to jakarta artifacts before addressing the massive code migration of javax to jakarta. I am assuming #3559 is addressing the latter and will only be resolved by an upgrade to Jakarta EE 9. Jakarta EE also releases a BOM, which will make it significantly easier to manage Jakarta EE dependencies.

Preferred solution

I have worked on a draft PR for a long time already (#4397), and I suggest creating a new PR with the changes proposed in the WIP PR.

One of the main issues seems to be that our Solr/ES compatibility tests pull in dependencies to a legacy version of Jetty that blocks us from using a newer version of Jetty (compatible with JavaEE 8) in this module.

Are you interested in contributing a solution yourself?

Yes

Alternatives you've considered

No response

Anything else?

No response

@erikgb erikgb added the 📶 enhancement issue is a new feature or improvement label May 27, 2023
@github-project-automation github-project-automation bot moved this to 🆕 Triage in RDF4J Planning May 27, 2023
erikgb added a commit to erikgb/rdf4j that referenced this issue May 27, 2023
@abrokenjester abrokenjester moved this from 🆕 Triage to 🏗 In progress in RDF4J Planning Jun 1, 2023
@abrokenjester abrokenjester added this to the 5.0.0 milestone Jun 1, 2023
erikgb added a commit to erikgb/rdf4j that referenced this issue Jun 11, 2023
@hmottestad hmottestad modified the milestones: 5.0.0, 5.1.0 Jun 20, 2024
@hmottestad hmottestad modified the milestones: 5.1.0, 5.2.0 Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📶 enhancement issue is a new feature or improvement
Projects
None yet
Development

No branches or pull requests

3 participants