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

Support for jakarta namespace #92

Open
cstamas opened this issue Jun 16, 2023 · 2 comments
Open

Support for jakarta namespace #92

cstamas opened this issue Jun 16, 2023 · 2 comments

Comments

@cstamas
Copy link
Member

cstamas commented Jun 16, 2023

Just a discussion starter: "what do we plan with jakarta namespace"?

Guice released "transitional" 6.0.0 (supporting both, javax and jakarta) and 7.0.0 (supporting jakarta only).
Apps using sisu built from the scratch may want to choose jakarta, while Maven (due legacy, especially 4.x) may want to "sit tight" on javax still.... (just to note, supporting newer bytecode is doable with "external asm").

@HannesWell
Copy link

Supporting jakarta annotations would be great.
The Eclipse E4 Dependency Injector is currently capable to handle both, jakarta and javax annotations and is prepared to handle the absence of javax annotations in the runtime (jakarta absence would of course be possible). Just in case you want to use a similar strategy:
eclipse-platform/eclipse.platform#792

@rfscholte
Copy link

The question is how to implement this in the SpaceModule and ClassFinder? Does the user need to select one of both, or should there be scanned for both?

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

3 participants