Importing / closed projects throw a lot of errors

Hello everyone,

I noticed that when importing projects, there are a lot of errors like this in the `Error Log` view:

> isGWTProject(project) hasGwtnature exception Project 'CertificateManager' is not open.

It seems to originate from [HERE](https://github.com/gwt-plugins/gwt-eclipse-plugin/blob/v4.2.0/plugins/com.gwtplugins.gwt.eclipse.core/src/com/google/gwt/eclipse/core/nature/GWTNature.java#L53-L57). I guess that the [ResourceChangeListener](https://github.com/gwt-plugins/gwt-eclipse-plugin/blob/v4.2.0/plugins/com.gwtplugins.gdt.eclipse.core/src/com/google/gdt/eclipse/core/reference/ResourceChangeListener.java) might be implemented incorrectly, assuming all projects are opened, which is then triggering the initial issue in `GWTNature#isGwtProject`.

When importing projects, we do that automatically, and initially, they are always closed before being opened. We don't have a special implementation; we rely on the Eclipse API.

Once everything is finished and the projects are all imported (and open), there are no further errors by the GWT plug-in, and everything works as expected. But this is quite annoying nevertheless.

Best,
Tobias

Comienza con GWTNature#isGwtProject en plugins/com.gwtplugins.gwt.eclipse.core/src/com/google/gwt/eclipse/core/nature/GWTNature.java y ResourceChangeListener en plugins/com.gwtplugins.gdt.eclipse.core/src/com/google/gdt/eclipse/core/reference/ResourceChangeListener.java. Reproduce una importación mientras los proyectos están cerrados y, a continuación, rastrea el manejo de los cambios de recursos; se considera terminado cuando la importación de proyectos cerrados ya no produce los errores indicados y la detección normal de proyectos sigue funcionando.

Escrito por el modelo de indexación a partir del texto del issue.