Unfortunately there's not much to report. I don't believe the feature reasonably implementable without some kind of extension to the Gradle tooling API.
Essentially I could already implement the maven case because I can get the required information from m2e and find maven projects corresponding to a given gradle dependency in the workspace. But for gradle there is not really a good way to determine what binary artifacts a project in the workspace corresponds to. To put it simply, I can easily determine for a gradle project what binary jars it depends on. But the other side, what jar a project itself corresponds to is not available.
I assume you already voted on STS-2834? That would a way to express that you care about this.
There's already a couple of votes, maybe its time for me to take another look at this.
To make progres on the issue someone, (probably me :-) will need to think a bit more about what's needed from Gradle's side and raise an issue with the Gradle folks to get that implemented.
You can help by voting and keeping an eye on the issue, and when a corresponding tooling API issue gets raised, vote on that as well.
Kris De Volder -- SpringSource