SWT Errors after repository reset

Background

Sometimes you need to do a hard reset of the SWT repository in order to fix a change. This will reset the repository to the HEAD state, but you will loose also changes you made. You will notice after doing a hard reset that many SWT files have import statement errors.

Solution

When you do a hard reset, the .classpath file is also wiped out. This means that the original .classpath_gtk is back: simply rename this file from .classpath_gtk to .classpath. Clean your workspace, and the errors will be gone. This seems pretty self explanatory but it's easy to forget this step if you haven't set up a new Eclipse environment in awhile.