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

Feature/jakarta migration #12520

Closed
wants to merge 44 commits into from

Conversation

chrisdutz
Copy link
Contributor

In this branch I am trying to migrate IoTDB to using the Jakarta namespace instead of the old JavaX.

It's probably going to take a while.

chrisdutz and others added 30 commits August 17, 2023 11:31
@chrisdutz chrisdutz changed the title Feature/jackarta migration Feature/jakarta migration May 13, 2024
@chrisdutz
Copy link
Contributor Author

chrisdutz commented May 13, 2024

While going through the project it seems that when migrating to Jakarta, we will have to update the version of Jetty to at least 11, but that breaks compatibility with Java 8 and would set Java 11 as new base-line.

@chrisdutz chrisdutz marked this pull request as ready for review May 16, 2024 14:44
@chrisdutz
Copy link
Contributor Author

So it seems I'm done with transitioning everything to Jakarta. As mentioned above, I had to give up on Java 8 support setting the new base-line at Java 11, which also allowed updating some dependencies for which unfixed CVEs were being reported. I think now the build is completely CVE-free. I however haven't updated all places where I could now update (Thrift etc.).

I haven't migrated the Extras repo however as I thought it wouldn't make sense to do this, if we haven't decided to actually do the migration.

@chrisdutz
Copy link
Contributor Author

Not merging.

@chrisdutz chrisdutz closed this May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant