-
Notifications
You must be signed in to change notification settings - Fork 193
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
[e4] support new jakarta.inject #1129
Comments
That would be very nice work! |
See also eclipse-platform/eclipse.platform.releng.aggregator#1056. In general I think it should not be too complicated and the injector should simply look for the new and old annotations and the bundle could import both as optional dependencies and should be prepared that both are potentially absent. |
The javax.annotation / javax.inject are effectively deprecated as they are now supersede by the jakarta.inject / jakarta.annotation 2.0 API. This adds support for E4 to optionally process these annotations as well so users can migrate their code away from the old namespace. See eclipse-platform/eclipse.platform.ui#1129
The javax.annotation / javax.inject are effectively deprecated as they are now supersede by the jakarta.inject / jakarta.annotation 2.0 API. This adds support for E4 to optionally process these annotations as well so users can migrate their code away from the old namespace. See eclipse-platform/eclipse.platform.ui#1129
The javax.annotation / javax.inject are effectively deprecated as they are now supersede by the jakarta.inject / jakarta.annotation 2.0 API. This adds support for E4 to optionally process these annotations as well so users can migrate their code away from the old namespace. See eclipse-platform/eclipse.platform.ui#1129
The javax.annotation / javax.inject are effectively deprecated as they are now supersede by the jakarta.inject / jakarta.annotation 2.0 API. This adds support for E4 to optionally process these annotations as well so users can migrate their code away from the old namespace. See eclipse-platform/eclipse.platform.ui#1129
The javax.annotation / javax.inject are effectively deprecated as they are now supersede by the jakarta.inject / jakarta.annotation 2.0 API. This adds support for E4 to optionally process these annotations as well so users can migrate their code away from the old namespace. See eclipse-platform/eclipse.platform.ui#1129
The javax.annotation / javax.inject are effectively deprecated as they are now supersede by the jakarta.inject / jakarta.annotation 2.0 API. This adds support for E4 to optionally process these annotations as well so users can migrate their code away from the old namespace. See eclipse-platform/eclipse.platform.ui#1129
The javax.annotation / javax.inject are effectively deprecated as they are now supersede by the jakarta.inject / jakarta.annotation 2.0 API. This adds support for E4 to optionally process these annotations as well so users can migrate their code away from the old namespace. See eclipse-platform/eclipse.platform.ui#1129
The javax.annotation / javax.inject are effectively deprecated as they are now supersede by the jakarta.inject / jakarta.annotation 2.0 API. This adds support for E4 to optionally process these annotations as well so users can migrate their code away from the old namespace. See eclipse-platform/eclipse.platform.ui#1129
With eclipse-platform/eclipse.platform#696 merged, I think we can consider this done. |
Currently E4 supports
javax.*
but this is replaced by newjakarta.*
namespace:E4 should allow uses to simply use both annotations in parallel (and maybe even warn in the IDE or at runtime if the "old" namespace is used).
The text was updated successfully, but these errors were encountered: