Skip to content

Migrate from javax to jakarta#321

Closed
jtreminio-dropbox wants to merge 7 commits intomainfrom
mbukowicz-main
Closed

Migrate from javax to jakarta#321
jtreminio-dropbox wants to merge 7 commits intomainfrom
mbukowicz-main

Conversation

@jtreminio-dropbox
Copy link
Contributor

Clone PR of #316

Original description:

This PR contains the following changes:

  • upgrade of OpenAPI generator to 7.0.1
  • upgrade from jersey2 to jersey3
  • regenerated .java classes (using ./run-build)

After packaging and deploying the result artifact to the official Maven repo it should be possible to use Dropbox Sign Java SDK with Spring Boot.

@jtreminio-dropbox
Copy link
Contributor Author

We can't merge this as-is, research shows that moving from javax to jakarta will break backwards compatibility with existing users.

We are deciding on the course of action here:

  1. A new, non-BC major version of the Java SDK (ie v2.0.0), or
  2. Maintaining a new jakarta-specific version of the Java SDK

@jtreminio-dropbox jtreminio-dropbox modified the milestones: H23SP22, H23SP23 Nov 14, 2023
@christiangoudreau
Copy link

Well, Java 8 and 11 doesn't receive any new security updates since 2019... moving to jarkata seems like the way to move forward. To me 1. should be the way to go.

Can you let me know the steps you want me to do to test this as I have never tried to run this repository before ?

@jtreminio-dropbox jtreminio-dropbox removed this from the H23SP23 milestone Jan 29, 2024
@jspaetzel
Copy link
Member

I've been continuing this some, ive created another branch #352
this'll divide the java sdk into v1 & v2 where this jakarta variant will live in v2. This will allow us to continue releasing javax variants as new features arrive without any major difficulty.

@jspaetzel jspaetzel deleted the mbukowicz-main branch March 4, 2024 23:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

SDK - Java Affects the Java SDK

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants