-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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.inject support #1009
Comments
yeah, I was wondering about what to do here. An easy fix is to write an adapter rather than directly wire up An issue that is not easy to work around is if you use I'd be fine updating to use the newer annotation, but I don't know if that would resolve your woes. |
You are spot on for both points!!!
I copied the source of Or I can do like you mentioned and manually set the FactoryCreator on TypesafeConfigurator. |
Released in 3.1.7 |
This should not have been a patch version |
This change should only require that Guice users who leverage this static injection upgrade to 6.0, which has support for both namespaces. That is a backwards compatible release and usages of the RI annotations will work until Guice 7.0 which drops support for javax. |
The
javax
toJakarta
headache never ends. :)I see that this project is using
javax.inject.Inject
in TypesafeConfigurator.This is causing issues when I upgraded to Guice 7.0 as my
FactoryCreator
is not being injected into TypesafeConfigurator.I see that you are aware of the headaches this is causing by your comments in google/guice#1383 so I am wondering on what your thoughts are on being able to support
jakarta.inject.Inject
?The text was updated successfully, but these errors were encountered: