-
Notifications
You must be signed in to change notification settings - Fork 111
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
@PostConstruct sometimes not working when using higher jakarta inject version #1565
Comments
This should be fixed by #1566. But where do you get version 3 from? AFAICT it's not in the SDK TP yet.
In general this is right, but I'm not sure that there are no corner cases where just comparing the FQN is not correct. |
and specifically support jakarta.annotation version 3.0. Fixes eclipse-platform#1565
and specifically support jakarta.annotation version 3.0. Fixes eclipse-platform#1565
and specifically support jakarta.annotation version 3.0. Fixes eclipse-platform#1565
and specifically support jakarta.annotation version 3.0. Fixes eclipse-platform#1565
and specifically support jakarta.annotation version 3.0. Fixes eclipse-platform#1565
org.eclipse.ui.tests.api.workbenchpart.DependencyInjectionViewTest.testDependencyInjectionLifecycle()
fails locally.Enabling debug output in
org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(AnnotationProxy, Object, Class<?>, PrimaryObjectSupplier, PrimaryObjectSupplier, List<Class<?>>)
revealsannotated with
I think it should not matter which API version is used. Only the qualified name
jakarta.annotation.PostConstruct
should matter@HannesWell ?
The text was updated successfully, but these errors were encountered: