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

See if jakarta.inject-api can be removed #944

Open
elharo opened this issue Nov 29, 2024 · 1 comment
Open

See if jakarta.inject-api can be removed #944

elharo opened this issue Nov 29, 2024 · 1 comment

Comments

@elharo
Copy link

elharo commented Nov 29, 2024

javax.inject is usually sufficient

@hazendaz
Copy link
Member

hazendaz commented Dec 1, 2024

I plan to keep the supported one that has proper meta data. Open the other jar, its missing its meta data folder. I've been using CDI since like 2010 and that was a problem for a long time with a number of plugins. When eclipse took that over and started making patches they fixed that. I get in maven context maven may want to use that one instead because using jakarta will suggest version 2.x that maven cannot use yet (well maven 4 should be able to it forces java 17 and that is the same requirement). Anyway that is my preference there. When I brought that up year or two ago I got dismissed that javax.inject was the wright one. Its not, it was moved when EE was open sourced so I'll stick to the updated copy ;) I know both work here, I just like to be complete.

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

2 participants