-
Notifications
You must be signed in to change notification settings - Fork 130
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
Bug 533327 - [9] Implement JEP 211 #2679
Comments
Wondering about "ordinarily" in the above I see the JLS has the same import exception regarding "ordinarily deprecated" and "terminally deprecated" (causing otherwise a "removal warning"). So, nothing to worry about, in this regard all deprecation is treated the same. See https://docs.oracle.com/javase/specs/jls/se22/html/jls-9.html#jls-9.6.4.6 |
Thanks for implementing this. Should render @SuppressWarnings at class level for the imports unneeded, allowing more fine grained @SuppressWarnings |
- Adjust deprecation test due to eclipse-jdt/eclipse.jdt.core#2679 - Ensure Java 17 compliance is used for projects with sealed classes - core.net fragments merged into host eclipse-platform/eclipse.platform#1440 Signed-off-by: Roland Grunberg <[email protected]>
Don't raise warnings on imports (deprecation, restricted access) fixes eclipse-jdt#2679
- Adjust deprecation test due to eclipse-jdt/eclipse.jdt.core#2679 - Ensure Java 17 compliance is used for projects with sealed classes - core.net fragments merged into host eclipse-platform/eclipse.platform#1440 Signed-off-by: Roland Grunberg <[email protected]>
Don't raise warnings on imports (deprecation, restricted access) fixes eclipse-jdt#2679
See https://bugs.eclipse.org/533327 :
The text was updated successfully, but these errors were encountered: