Community
Participate
Working Groups
Created attachment 273983 [details] Options used 1) Launch eclipse with Java 10 2) Go to Java preference page Java -> Compiler 3) Change the various preference options to the one in image attached 4) Click on Configure... Nothing happens. Click cancel, you get NPE java.lang.NullPointerException at org.eclipse.jdt.internal.debug.ui.jres.JREsPreferencePage.dispose(JREsPreferencePage.java:321) at org.eclipse.jface.preference.PreferenceNode.disposeResources(PreferenceNode.java:160) at org.eclipse.ui.internal.preferences.WorkbenchPreferenceExtensionNode.disposeResources(WorkbenchPreferenceExtensionNode.java:132) at org.eclipse.jface.preference.Preference
New Gerrit change created: https://git.eclipse.org/r/122367
Not a regression.
Increasing severity since after that, an error is logged every time when 'Apply and Close' is pressed (after reopening the dialog), no matter on what preference page.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
Still happens with 4.16 M2.
New Gerrit change created: https://git.eclipse.org/r/161866
(In reply to Eclipse Genie from comment #6) > New Gerrit change created: https://git.eclipse.org/r/161866 Debug should definitely check if JREBlock is not null.
Gerrit change https://git.eclipse.org/r/161866 was merged to [master]. Commit: http://git.eclipse.org/c/jdt/eclipse.jdt.debug.git/commit/?id=3f388d287c54eaba259c017ec08cc67b30670592
(In reply to Dani Megert from comment #5) > Still happens with 4.16 M2. I tried new workspaces launching with Java 10, 11, and 14 but could not reproduce. Kept the .class compatibility to a higher level than others, got the error and warning as the atachment but clicking on Configure Project settings openened the Project selection dialog. Any other step which could have mattered?
(In reply to Sarika Sinha from comment #9) > (In reply to Dani Megert from comment #5) > > Still happens with 4.16 M2. > > I tried new workspaces launching with Java 10, 11, and 14 but could not > reproduce. > Kept the .class compatibility to a higher level than others, got the error > and warning as the atachment but clicking on Configure Project settings > openened the Project selection dialog. > > Any other step which could have mattered? I can reproduce that the link doesn't work, but no NPE. 1. Start new workspace with Java 10 2. Set the options as in the attached screenshot 3. Click the 'Configure...' link ==> nothing happens NOTE: When trying it again in the still running workspace it gives a dialog telling that there are invalid values.
(In reply to Dani Megert from comment #10) > I can reproduce that the link doesn't work, but no NPE. > > 1. Start new workspace with Java 10 > 2. Set the options as in the attached screenshot > 3. Click the 'Configure...' link > ==> nothing happens > > NOTE: When trying it again in the still running workspace it gives a dialog > telling that there are invalid values. Tried on Windows and Mac launching with Java 10 and -data option for new workspace, Following the steps and clicking on "Configure" gives dialog for "The currently displayed page contains invalid values".
Sarika, can you please update the TM/status?
(In reply to Noopur Gupta from comment #12) > Sarika, can you please update the TM/status? What update do you want other than comment#11 ?
If some one is able to reproduce, please take it forward. I will not be able to work without reproducing it.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
