Community
Participate
Working Groups
Created attachment 254384 [details] all projects are on the same level it is the case for org.eclipse.e4.ui for instance: org.eclipse.e4.ui |-build --> not a project, just a folder container |- eclipse-juno-parent |- org.eclipse.ui.update in hierarchical view all projects are set as root project
I think the hierarchy is based on the .project files. Adding Mickael for confirmation.
the use-case you describe is how hierarchical view is supposed to work, so you are facing a bug. Can you please provide detailed steps of how to reproduce, and check in your log whether something is listed?
@Aurelien: in your screenshot https://bugs.eclipse.org/bugs/attachment.cgi?id=254371 , it seems to behave as expected (project->folder->project). Do you have any clue what would be a difference between those cases?
Created attachment 254387 [details] the correct screenshot emphasing the issue
hum in fact it seems that you're pointing to the screenshot of another bug
detailed steps: - import all projects of org.ecipse.e4.ui (I use the Smart Importer in my case) - go to hierarchical view --> you can see the issue
(In reply to Aurelien Pupier from comment #5) > hum in fact it seems that you're pointing to the screenshot of another bug Yes, but in this screenshot, you see that the hierarchical view works well with another project, even in a project->folder->project hierarchy.
no on the other project it is a project -> project -> project hierarchy, there is a pom.xml at each level
Hierarchical view doesn't care about pom.xml. It only understands projects in the Eclipse meaning of project (ie folder which has a .project)
there is no .project in this folder because this is not a project, this is just used as a container in a git repository. I was reporting this bugzilla in order to support also when there is non-project folder in the repository hierarchy.
@Aurelien: Is this something you can reproduce?