Community
Participate
Working Groups
If I understand the current state of the platform UI correctly the nested project representation happens automatically based on the physical folder structure. As we are trying to develop Buildship - Gradle integration for Eclipse - we see this as a restriction: with Gradle one can define a project hierarchy independently from the where a given element is stored. Consequently we're seeking a way to explicitly define hierarchy information on a project. Is there a way to do this?
Michael did the work for representing the nested projects. All this state is maintained by the UI layer, and required no changes to the Core Resources. He created a NestedProjectManager that is responsible for building and managing the nesting state, and then a JFace tree-based content provider that would reify that nesting state into a tree.
Brian is right. This API is pure usage of Eclipse CNF framework and its extension points: http://help.eclipse.org/luna/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fguide%2Fcnf.htm I believe you'd also like to develop your own extensions to CNF for BuildShip. Both Hierarchical Project view and Buildship can probably remain independant and compatible together.
It's good to know that the whole implementation is CNF-based. With this I will prototype the same thing for Buildship. But this means that Buildship will have a slightly modified version of the org.eclipse.ui.navigator.resources where IPath.isPrefixOf() is replaced with the logic from Gradle. I still can imagine an extension point where a contributor can define for example a project nature and the hierarchy definition between the elements. I'm confident that other projects will benefit from organizing large projects in a custom-defined hierarchy.
Donat, can this bug be closed?
Yes, let's close it.
