Community
Participate
Working Groups
In Eclipse Mars M5, I work on webtools.jsdt project with a hierarchical presentation. If I close the parent project with "Close Project" option (right click on the project then close project) then the project is closed but children are always open. I think that closing parent project should close children.
(In reply to Gautier de SAINT MARTIN LACAZE from comment #0) > I think that closing parent project should close children. I'm not sure the generic "Close" operation should do that. However, we could think of a new contextMenu, only visible when hierarchical view in enabled, called "Close project hierarchy" that would perform this operation. What do you think? @Dani @Lars: what's also your opinion about my proposal?
(In reply to Mickael Istria from comment #1) > (In reply to Gautier de SAINT MARTIN LACAZE from comment #0) > > I think that closing parent project should close children. > > I'm not sure the generic "Close" operation should do that. However, we could > think of a new contextMenu, only visible when hierarchical view in enabled, > called "Close project hierarchy" that would perform this operation. > What do you think? Or open similar question as on opening projects: "schould nested projects be closed too ?"
How about other operations like Delete, Move, etc.? It would be nice to find a common solution instead of duplicating the commands.
Personally I prefer Andrey proposal and I agree with Dani. It will be nice to have the same behaviour for each action about opening and closing a project with subproject.
I also prefer Andrey's and Dani's approach, although it's another level of difficulty.
We also need the inverse - to Open Hierarchy. See Bug 499231.
For the record, Mickael Istria implemeted in Eclipse Photon the feature to delete the children when the parent is deleted. Bug 525882 - Delete project dialog to also allow to delete "children" projects : https://bugs.eclipse.org/bugs/show_bug.cgi?id=525882 I think this "recursive close" feature would be very usefull and I can imagine its implementation would be very similar to the "recursive delete" one.
Any news on this feature? I think having to manually close every project should be a no go, in my case it would be 20-30 projects. Mosly I leave the projects open although I do not want to, or just delete them. Just because it is not possible to close child projects automatically.
Have you tried to just delete them? It's actually not so different from closing in term of result. The only difference is that you'll need to reimport instead of reopening, but imoorting projects is an easy operation with File > Open Projects from Filesystem... So there is no big overhead with deleting instead of closing. That said, if you want to contribute the code to close a hierarchy of projects, it would be welcome.
That is actually a good enough workaround, deleting the projects but not the contents on the disk, did not think of that. I have no experience with the technologies used within eclipse, I'm just a regular Java EE developer. Can you point me to resources so I can give it a try in my free time? For example, looking at the eclipse git repositories, I have no idea where the relevant code is.
(In reply to Samir Huremovic from comment #10) > I have no experience with the technologies used within eclipse, I'm just a > regular Java EE developer. Can you point me to resources so I can give it a > try in my free time? I suggest you start by some tutorial about plugin development so you'll see how to run and debug a modified Eclipse IDE from your development IDE with simple example. Then, you can start opening some bits of the IDE code in your workspace and can modify/run/debug them. > For example, looking at the eclipse git repositories, I have no idea where > the relevant code is. The relevant code is probably https://git.eclipse.org/c/platform/eclipse.platform.ui.git/tree/bundles/org.eclipse.ui.ide/extensions/org/eclipse/ui/actions/CloseResourceAction.java
