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

Jakarta EE 10 / Quarkus 3 #5264

Closed
snazy opened this issue Sep 26, 2022 · 1 comment
Closed

Jakarta EE 10 / Quarkus 3 #5264

snazy opened this issue Sep 26, 2022 · 1 comment

Comments

@snazy
Copy link
Member

snazy commented Sep 26, 2022

Quarkus 3 will move to Jakarta EE 10. This means that basically all import javax.* have to be replaced with import jakarta.*. All the jakarta.* packages are built for bytecode version 55 (Java 11), which means, that the dependencies cannot "just be bumped with some find+replace".

Hint:

jakarta/servlet/http/HttpServletRequest has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0

As long as only annotations are affected, I think, that it's possible (although definitely not really nice) to repeat the annotations for javax.* and jakarta.*. For example instead of having

  @NotBlank
  public abstract String getMessage();

use:

  @javax.validation.constraints.NotBlank
  @jakarta.validation.constraints.NotBlank
  public abstract String getMessage();

See #5255 for dependencies.

@snazy snazy changed the title Track Jakarta EE dependencies Jakarta EE 10 / Quarkus 3 Feb 9, 2023
snazy added a commit that referenced this issue Feb 9, 2023
This change adds the Jakarta API dependencies next to the (old) javax
dependencies. Hint: the findbugs JSR-305 dependency is the
"javax-equivalent" for jakarta-annotations.

There's no production code change in this PR, but dependency
configurations/scopes have changed. Assuming that server
_implementations_ come with the "right" dependencies for the
annotations, which should work fine.

This change alone will _not_ make Nessie work with Jakarte EE 10,
because
* neither the javax-annotations are not "duplicated" with their "jakarta
counterparts",
* nor are the javax-interface implementations duplicated with their
"jakarta counterparts" (think: `implements
javax.ws.rs.ext.ParamConverterProvider` or `implements
javax.ws.rs.ext.ExceptionMapper`).

Related to: #5264
@snazy
Copy link
Member Author

snazy commented Feb 25, 2023

Fixed via #6172 and #6174

@snazy snazy closed this as completed Feb 25, 2023
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

No branches or pull requests

1 participant