new projects are not detected as gwt projects.

[rdwallis]

And the google web toolkit properties window doesn't open either so it's not easy to fix this problem manually.

See discussion: https://groups.google.com/forum/#!topic/gwt-platform/5iE5B_RTCuQ

[branflake2267]

I see this getting better in the future.

[rdwallis]

@branflake2267 is this being fixed already in the gwt plugin?

I fixed a similar issue a few months ago by adding https://github.com/ArcBees/gwtp-eclipse-plugin/blob/master/gwtp.plugin.core/src/main/resources/templates/project/.settings/com.google.gwt.eclipse.core.prefs.template to the new project's settings directory.

Obviously a bit fragile which is probably why it's not working anymore. Do you know a better way to mark a project as a web toolkit project in eclipse?

[branflake2267]

I was thinking about the GWT Nature, which may be different context. I've seen some configurations, the GPE m2e detector not turning on the GWT Nature. There is a workaround to a couple of these cases. Erase the the .settings directory and reimport the project. There are some npes that are getting thrown during the process and causing issues. But I can't be sure its this case yet.

[rdwallis]

Yes I think it's the same issue.

The gwtp project creator is pretty stupid. It just creates a new project unzips the template project into the new projects folder and then enables maven nature:

https://github.com/ArcBees/gwtp-eclipse-plugin/blob/master/gwtp.plugin.core/src/main/java/com/arcbees/gwtp/plugin/core/project/CreateProjectWizard.java#L148

So probably I'll need to make the gwtp plugin use the gwt plugin as a dependency and then enable the GWT nature. Although I think if the m2e detector can be made a bit more reliable that'll solve the problem automatically.