Use Thread.yield() instead of yield()

As per yield is restricted identifier
and this breaks javadoc build with Java 17 with:
UI/org/eclipse/ui/application/ error: invalid
use of a restricted identifier 'yield'
  (to invoke a method called yield, qualify the yield with a receiver or
type name)

Signed-off-by: Alexander Kurtakov <>

Change-Id: Ib769d0e744c786871dffb94bd297f96c2c9ddb8e
Tested-by: Alexander Kurtakov <>
Reviewed-by: Alexander Kurtakov <>
1 file changed
tree: 3fb6a4ff14bbbf1da6ea26c991846eb52b91fa86
  1. .mvn/
  2. bundles/
  3. examples/
  4. features/
  5. releng/
  6. tests/
  7. .gitignore
  10. Jenkinsfile
  12. NOTICE
  13. pom.xml

Contributing to Eclipse Platform UI project

Thanks for your interest in this project.

Project description:

Platform UI provides the basic building blocks for user interfaces built with Eclipse.

Some of these form the Eclipse Rich Client Platform (RCP) and can be used for arbitrary rich client applications, while others are specific to the Eclipse IDE. The Platform UI codebase is built on top of the Eclipse Standard Widget Toolkit (SWT), which is developed as an independent project.


For more information, refer to the Platform UI wiki page.

How to contribute:

Contributions to Platform UI are most welcome. There are many ways to contribute, from entering high quality bug reports, to contributing code or documentation changes. For a complete guide, see the Platform UI - How to contribute wiki page page on the team wiki.

Test dependencies

Several test plug-ins have a dependency to the Mockito and Hamcrest libraries. Please install them from the Orbit Download page:

Currently the following plug-ins are required:

  • net.bytebuddy.byte-buddy
  • net.bytebuddy.byte-buddy-agent
  • org.hamcrest.core
  • org.mockito
  • org.objenesis

How to build on the command line

You need Maven 3.3.1 installed. After this you can run the build via the following command:

mvn clean verify -Pbuild-individual-bundles

Developer resources:

Information regarding source code management, builds, coding standards, and more.

Contributor License Agreement:

Before your contribution can be accepted by the project, you need to create and electronically sign the Eclipse Foundation Contributor License Agreement (CLA).

Search for bugs:

This project uses Bugzilla to track ongoing development and issues.

Create a new bug:

Be sure to search for existing bugs before you create another one. Remember that contributions are always welcome!


Contact the project developers via the project's “dev” list.


Eclipse Public License (EPL) 2.0