Each SDK is now build as it's own Plugin, so we do no longer need to …

[keinhaar]

…rebuild all SDKs if just one new Version is added.

• Changed the names of the plugins and features from ...gwt210.feature to ...gwt2_10_1.feature to make clear which exact version this is. Because something like 210 could also mean 2.1.0.

[niloc132]

Are you deliberately leaving 2.12.0 and 2.10.0 out? I can see a case for that, but I could also imagine a team wanted to use an earlier bugfix release in certain cases.

[keinhaar]

I can easily add them with the new Script, but they were not included in the 4.1 Eclipse Plugin either.
Just tell me if i should add them anyway.
Apart from that anything works fine in my local testing.
Maybe we are ready for 4.2?
The only things left seem to be merging the pull requests here and in the gwt-eclipse-plugin, and creating creating new version numbers for the eclipse plugin.

[difflaender]

Another example for why previous releases may be good to keep around: Our team intentionally stayed on 2.8.1 for a while because 2.8.2 introduced some breaking changes like gwtproject/gwt#9653. Back then we forked the Eclipse Plugin repo to downgrade the included SDK version to the one that was more suitable for us.