Community
Participate
Working Groups
In the same way that when I open a project I'm prompted to open related project, the normal close operation should prompt me to close the unrelated projects. This would remove the need for a "close unrelated projects" action. Question: which criterias are used to decide which projects to open / close? Is there an extension point to let me plug my logic?
The problem is, "Close Project" and "Close Unrelated Projects" have opposite effect on the selected projects. The first will close the selected projects, and the second will never close the selected projects. It would be strange to have a preference that completely reverses the behaviour. The equivalent of the open behaviour would be a prompt to "Close referenced projects" as part of the close command. Answer: it uses project references. Any plugin can add/remove project references, and this would effect the open/close behaviour (IProjectDescription#setReferencedProjects).
*** Bug 130343 has been marked as a duplicate of this bug. ***
This bug seems to be about prompting the user when closing. My request was to support open related projects, by tracking dependencies on projects as they get closed.
I wasn't implying that my bug wasn't a duplicate. I was just trying to preserve my comments. (I think) Pascal is making 2 points: 1) Why not open a dialog on "Close Project" like is done with "Open Project"? This would be consistent, and could remove clutter from an already ginormous popup menu. 2) What criteria is used to include additional project in the operation. I don't think I'm the only one who finds the current behavior strange. The ultimate solution is to provide the folling: when closing: a) close downstream projects b) close related project (up and down) when opening: a) open upstream projects b) open related projects (up and down)
*** Bug 141668 has been marked as a duplicate of this bug. ***
*** Bug 141275 has been marked as a duplicate of this bug. ***
(In reply to comment #6) > *** Bug 141275 has been marked as a duplicate of this bug. *** Looking at all comments it seems to me that diverse requests are now brought under this umbrella. What I fear now, seeing comment #4, that some solution might be produced, which adds too much steps to often used commands. I think one should focus onto the functions usually needed. For this I tell you my needs and others interested in this bug can add to it their needs or confirm they are happy with this short selection: - Open the selected Project together with all other projects required by this project. This prevents to get to a state I cannot build the selected project becase some required one is closed. - Close all currently open project except the selected one and the ones needed by the selected project. I myself could happily live with these two commands alone. If you choose some solution which requires a dialog after selecting the close (unrelated) menu item, then please have a "[] remember my choice and don't ask again" checkbox allowing me to tailor the open and close (unrelated) to my desired behaviour after the first use.
*** Bug 182969 has been marked as a duplicate of this bug. ***
That's what I did foresee, marking Bug #182969 as duplicate:-) Nevertheless I want to stress out once again, so its not overseen: close project should behave exactly as open project. If one can open related projects of a project, one should be able to close related projects of a project just as well.
If one can open related projects of a project, one should be able to close related projects of a project just as well... as long as they're not used by other projects. (note: check for projects that can be closed should be recursive)
Exactly, Max. Thanks for making this clear.
duplicate bug 201981 , bug 170323 , bug 128397
duplicate bug 128543 - this is what i was actually going to put a ticket in for
*** Bug 201981 has been marked as a duplicate of this bug. ***
Bug 128543 is related but nit the same (it is asking for some different functionality)
"As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009"
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
