Just append "@2x" to the file name and place the high-DPI icons into the same folder as the original icon. If you use OSGi bundles, you can also put the icons into a fragment that contains the same folder structure.

Example:
100%: newclass_wiz.png
200%: newclass_wiz@2x.png

IResource resource = ...;
Job.create("Refreshing files",
    monitor -> resource.refreshLocal(IResource.DEPTH_INFINITE, monitor)
).schedule();

IResource resource = ...;
Job.createSystem(
    monitor -> resource.refreshLocal(IResource.DEPTH_INFINITE, monitor)
).schedule();

Due to Java type system constraints, ListenerList#getListeners() still returns Object[]. Clients should not only add type arguments to the ListenerList, but also convert usages of #getListeners() to an enhanced for loop, thereby taking advantage of the type-safe #iterator().

Old:

ListenerList fInputChangeListeners = new ListenerList();
...
Object[] listeners= fInputChangeListeners.getListeners();
for (int i= 0; i < listeners.length; i++) {
	((IInputChangedListener) listeners[i]).inputChanged(fInput);
}

New:

ListenerList<IInputChangedListener> fInputChangeListeners = new ListenerList<>();
...
for (IInputChangedListener listener : fInputChangeListeners) {
	listener.inputChanged(fInput);
}

Before this change, you had to create a subclass of ComputedValue, but the new create method, which expects a Supplier<T> allows you to create an instance of ComputedValue by using a lambda expression.

Examples:

IObservableValue<Integer> listSizeObservable =
	ComputedValue.create(() -> observableList.size());

IObservableValue<String> fullNameObservable =
	ComputedValue.create(() -> personFirstNameObservable.getValue() + " "
		+ personLastNameObservable.getValue());

More details about tracked getters can be found in the org.eclipse.core.databinding.observable.ObservableTracker's getterCalled(IObservable) method. Almost every IObservable's get methods are tracked getters.

        IObservableValue<String> username = ...
        Label yourUsername = ...

        ISideEffect sideEffect = ISideEffect.create(
        	() -> {return "Your username is: " + username.getValue();},
          	yourUsername::setText);
      

For example, all ISideEffect instances that are created by the ISideEffectFactory obtained from the WidgetSideEffects#createFactory(Widget disposableWidget) method are automatically disposed once the corresponding widget is disposed.

Example:

ISWTObservableValue personFirstNameTextObservable = WidgetProperties.text(SWT.Modify)
	.observe(personFirstNameText);
ISWTObservableValue personLastNameTextObservable = WidgetProperties.text(SWT.Modify)
	.observe(personLastNameText);

ISideEffectFactory sideEffectFactory = WidgetSideEffects.createFactory(personFirstNameText);

sideEffectFactory.create(person::getFirstName, personFirstNameText::setText);
sideEffectFactory.create(personFirstNameTextObservable::getValue, person::setFirstName);
sideEffectFactory.create(person::getLastName, personLastNameText::setText);
sideEffectFactory.create(personLastNameTextObservable::getValue, person::setLastName);

• org.eclipse.jface.viewers.StructuredViewer#setFilters(ViewerFilter...)
• org.eclipse.jface.databinding.viewers.ViewerSupport#bind(*, IValueProperty...)
• org.eclipse.swt.graphics.PaletteData#PaletteData(RGB...)
• org.eclipse.swt.widgets.Combo#setItems(String...)

Old:

new MessageDialog(shell, "MessageDialog", null, "DialogMessage",
		MessageDialog.NONE, new String[] { "Button1", "Button2" }, 0);

new MessageDialog(shell, "MessageDialog", null, "DialogMessage",
		MessageDialog.NONE, 0, "Button1", "Button2");

      // this is a child context
      IEclipseContext ctx =...;
      // get the application context
      IEclipseContext applicationContext = ctx.get(IWorkbench.APPLICATION_CONTEXT_KEY);
      

This avoids a common error in Eclipse RCP implementations in which @PostConstruct was resolved to different classes in the bundle classpath. This change is backwards compatible, i.e., a dependency with a minimum version still works correctly.

// Old way
IResource selectedResource;
if (selection instanceof IAdaptable) {
  selectedResource = ((IAdaptable)selection).getAdapter(IResource.class);
}

// New way
IResource selectedResource = Adapters.adapt(selection, IResource.class);

// Old way
void myMethod(IProgressMonitor monitor) {
  SubMonitor subMonitor = SubMonitor.convert(monitor, 2);
  if (subMonitor.isCanceled()) {
    throw new OperationCanceledException();
  }
  childMethod1(subMonitor.newChild(1));
  if (subMonitor.isCanceled()) {
    throw new OperationCanceledException();
  }
  childMethod2(subMonitor.newChild(1));
}

// New way
void myMethod(IProgressMonitor monitor) {
  SubMonitor subMonitor = SubMonitor.convert(monitor, 2);
  childMethod1(subMonitor.split(1));
  childMethod2(subMonitor.split(1));
}

// Old way
void myMethod(IProgressMonitor monitor) {
  SubMonitor subMonitor = SubMonitor.convert(monitor, 2);
  uncancellableMethod(null);
  subMonitor.worked(1)
  cancellableMethod(subMonitor.newChild(1));
}

// New way
void myMethod(IProgressMonitor monitor) {
  SubMonitor subMonitor = SubMonitor.convert(monitor, 2);
  uncancellableMethod(subMonitor.newChild(1,
      SubMonitor.SUPPRESS_ISCANCELED | SubMonitor.SUPPRESS_BEGINTASK);
  cancellableMethod(subMonitor.newChild(1));
}

To shield existing clients from resolution differences, SWT now uses the Cocoa model on all three platforms. Existing SWT APIs keep using the well-known coordinate system in SWT points. In high-DPI environments, these SWT points are transparently scaled to native pixels.

To create DPI-aware org.eclipse.swt.graphics.Images, use these constructors that have already been provided in the Mars release:

• Image(Device, ImageFileNameProvider)
• Image(Device, ImageDataProvider)

• Image#getImageDataAtCurrentZoom(): Returns an ImageData that contains the full-resolution pixel data at the current OS zoom level
• Image#getBoundsInPixels(): Returns the image dimensions in pixels at the current OS zoom level

"org.eclipse.swt.internal.deviceZoom"

Note: This is a read-only value, so setting it on the command line doesn't make sense. Furthermore, SWT doesn't use the deviceZoom when HighDPI support is disabled via -Dswt.autoScale=false, see Tweaking SWT's auto-scaling

 widget.getShell().layout(new Control[] {widget}, SWT.DEFER); 

The snippet, above, is currently the most efficient method of triggering layouts in SWT, but most developers are unaware of this. Most Eclipse developers invoke Composite.layout(), which is worse in the sense of performance. This new API is intended to make it easier for developers to adopt the more efficient mechanism as opposed to using Composite#layout().

However, be aware that changing existing invocations of layout() to requestLayout() may break code that assumes that controls are completely sized and positioned at a certain point in time.

Auto text direction was introduced in the Mars (4.5) release as a bitwise OR of SWT.LEFT_TO_RIGHT | SWT.RIGHT_TO_LEFT and it was already implemented in all native controls. Now, SWT.AUTO_TEXT_DIRECTION is a dedicated SWT constant for this.

Behavior: When SWT.AUTO_TEXT_DIRECTION is set, the text direction is derived from the direction of the first strong Bidi character.

Note: This is a HINT and it works on Windows only.

Usage: control.setTextDirection(SWT.AUTO_TEXT_DIRECTION);

The corresponding getter Link#getLinkForeground() has been added which returns the foreground color of the hyperlink text in the Link widget.

For an example, see Snippet182.