Thanks for the response!
We tried v1.0.16. We were hitting “Error importing gradle project into Eclipse”.
We also need some features not available such as the above and “Binary dependency substitution”.
Speaking of community help, we MAY be able to help but would need help ourselves - guidance as to where things are and the preferred way to accomplish things. We already planned to do something like this for the coexistence with Maven projects in Eclipse (replacing binary dependencies with in-Eclipse Maven projects) but also crucial to us is the classpath separation - it actual breaks the build (classpath is scanned, classes that should not be found are and cause errors). This affects things like Spring classpath scanning (may find beans it shouldn’t) and GWT code servers (will try to transpile test code to JavaScript but fails to find the source code for dependencies such as JUnit, for example).