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. I guess that the ResourceChangeListener 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
Hello everyone,
I noticed that when importing projects, there are a lot of errors like this in the
Error Logview:It seems to originate from HERE. I guess that the ResourceChangeListener 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