Don't use Display.syncExec() for refresh in RuntimeClasspathViewer

The listener may be called from a background thread that already holds
some locks. To refresh RuntimeClasspathViewer UI in the current case,
syncExec is not needed, asyncExec is enough and it would not acquire the
UI lock from an unknown thread.

Fixes #672

Author: iloveeclipse

org.eclipse.jdt.debug.ui/ui/org/eclipse/jdt/internal/debug/ui/classpath/RuntimeClasspathViewer.java

@@ -43,6 +43,7 @@
 import org.eclipse.swt.events.KeyAdapter;
 import org.eclipse.swt.events.KeyEvent;
 import org.eclipse.swt.widgets.Composite;
+import org.eclipse.swt.widgets.Display;
 import org.eclipse.swt.widgets.Shell;
 import org.eclipse.ui.dialogs.FilteredTree;
 import org.eclipse.ui.dialogs.PatternFilter;
@@ -64,17 +65,12 @@ public class RuntimeClasspathViewer implements IClasspathViewer {
 
 		@Override
 		public void preferenceChange(PreferenceChangeEvent event) {
-			if (DebugUIPlugin.getStandardDisplay().getThread().equals(Thread.currentThread())) {
+			Display display = DebugUIPlugin.getStandardDisplay();
+			if (display.getThread().equals(Thread.currentThread())) {
 				refresh(true);
 			} else {
-				DebugUIPlugin.getStandardDisplay().syncExec(new Runnable() {
-					@Override
-					public void run() {
-						refresh(true);
-					}
-				});
+				display.asyncExec(() -> refresh(true));
 			}
-
 		}
 	};