Eclipse plugin is too lazy with Gradle projects

[wilkinsona]

The Eclipse plugin is not activated until one of its classes is loaded. This happens when one of its extensions is going to be called, for example because m2e is configuring a project (ProjectSettingsConfigurator) or because some code is being formatted (SpringCodeFormatter). There are no extensions specifically for Gradle projects so if no other projects have caused the plugin to be activated, there will be nothing to listen to the Gradle project's settings being refreshed and the plugin will never get a chance to customise its settings.