-
Notifications
You must be signed in to change notification settings - Fork 120
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
WARNING: dangerous @SuppressWarnings("removal") added #385
Comments
Please also note, that already JDK 17 loggs warnings to ERR like (when for example running org.eclipse.ant.tests.ui.BuildTests.testVerboseStackTrace()):
|
Deprecation warnings we see in JDK 17 on API that is marked for removal (probably with JDK 21 - next LTS) :
We should address that. |
Rawtypes one was removed by error while moving to Java 17 and AccessController.doPrivileged has no clear replacement and stays until JVM actually removes this one. eclipse-platform/eclipse.platform#385 is the general tracking issue for SecurityManager removal in the JVM
Rawtypes one was removed by error while moving to Java 17 and AccessController.doPrivileged has no clear replacement and stays until JVM actually removes this one. eclipse-platform/eclipse.platform#385 is the general tracking issue for SecurityManager removal in the JVM
Rawtypes one was removed by error while moving to Java 17 and AccessController.doPrivileged has no clear replacement and stays until JVM actually removes this one. eclipse-platform/eclipse.platform#385 is the general tracking issue for SecurityManager removal in the JVM
It's not fun to work with a current OOmphed Platform workspace with JDK 19 (eclipse-platform/.github#114) as there are repeadadly exceptions logged: 'Setting Security Manager is not supported'
|
see #356 (comment)
Eclipse IDE needs to get rid of code to be removed or changed in future JDK. Even if not removed but becoming a NO-OP in future JDKs there could be serious issues with future JDKs when code does not do anymore what it used to do.
The text was updated successfully, but these errors were encountered: