I’m looking for a workaround to this annoying issue.
Given a gradle project with subprojects, sometimes nested more than one level deep, if one does a search for something in the code, Eclipse finds the target at the top level project, any intermediate projects, all the way down to the leaf node.
However, only the leaf node instance is considered a Java project by Eclipse. Therefore, a “References” search gets an error. One must drill down to the leaf subproject node to be able to follow a reference. This is annoying.
I realize that Buildship is working with what Eclipse gives us. But it would sure be nice to have a way to do searches where only the leaf node shows up, and not it’s “echoes” at higher levels of the subproject hierarchy. Or maybe it’s a hole in my understanding of Eclipse.