groovy-eclipse is quite a moving target at the moment.
lately they have merged-in support for refactorings -
refeactorings were developed on a separate branch before.

according to the developers there will be a new
release in a month or so. i think it may be admissible,
to move the issue from 0.5 to 0.6.

the workaround for now is to set src-folders and groovy-nature
by hand which is acceptable for me as my groovy-projects
dont change their compile-classpath very often. -> can be
synced by hand too

a description of the workaround in the wiki would help
out most developers ... may be i find time to do that ...
cant promise ...

Such a wiki page would be most appreciated . Thanks also for your update on the groovy eclipse status. I will move the issue from 0.5 to 0.6

Groovy Eclipse is at a far more stable point now, so I've taken the liberty of creating a patch to make this work.

Adding the 'eclipse' plugin to the Gradle build.gradle works perfectly - I can import it directly and the project setup is spot on.

I've pushed the changes to my GRADLE-198 branch at http://github.com/smangelsdorf/gradle/tree/GRADLE-198 for review. At the time of writing, it merges into the current master without conflict.

Note that this change flows on from my commits on GRADLE-758 (in a branch of that name). If the changes I made there aren't accepted, I can port this change back to fit the ProjectType as it was previously.

The patch looks good. I will apply it soon. It will need some merging with the patch for GRADLE-751.

This has been applied. Thank you for the patch.