The GWT Eclipse Plugin has become unmaintained, and over the last several months several community members have stepped up to update it to run on recent Eclipse versions, and support the new GWT groupId.
As part of that process, we've created a new marketplace entry, and while it is still pointed at the old 3.0 release, we're preparing a new release, and hope to have it out within a week.
In order to deploy a new version, we need to deploy the unpacked repository somewhere - which rules out a maven repository. The footprint of the unpacked workspace is fairly large, around 350mb, which would be too big for github pages after three releases. We could still deploy releases zips, but need somewhere else to put the unpacked content.
If there are no objections, once we've finished the 4.0 plugin and are ready for a release, I'll formally set up
eclipse.gwtproject.org. For the moment I anticipate only a plugins/ directory, with each versioned release (and maybe a nightly build setup too), to allow for additional content later.
Using the
gwtproject.org domain name seems natural as a large number of GWT developers use Eclipse and this plugin, and the documentation at
gwtproject.org has long since offered Eclipse instructions, with little space given to IntelliJ or Maven/Gradle. I'd further propose we should improve that situation, but that's a separate discussion. Vertispan intends to host this new plugin content, and we are already hosting the
gwtproject.org domain content.
If there are reservations about
gwtproject.org also hosting the eclipse plugin, we can set up an alternate domain name for this work, though at least for the time being, Vertspan will be hosting these together.