Community
Participate
Working Groups
When I switch branches, projects that I specifically closed are opened. I guess this could make sense if they were open the last time I worked on that branch. But then when I switch back to the original branch, they remain open. It is hard enough to get the right set of projects to be open in the first place without them being automatically reopened by a sequence of operations that should leave my workspace in exactly the same state it was in before.
I believe this is caused by the Branch Project Tracking feature. As a workaround you can turn this feature off. See: http://wiki.eclipse.org/EGit/New_and_Noteworthy/1.3#Branch_Project_Tracking But I agree that this is a bug in EGit. In fact, the problem is worse in the fact that it also happens for deleted projects. If I delete a project from my workspace, EGit brings it back when I check out another branch. From the description of the feature: "Projects are now closed when checking out a branch where that project does not exist and reopened when the previous branch is checked back out." I believe the goal is that if a project "does not _exist_" in a branch, it will be brought back for a branch where it does exists. I think this is a cool feature. I've actually needed it a lot. I think EGit should limit the feature that case though: when project does not _exist_ in the branch. If the project is closed or removed from the workspace, it should not trigger the feature.
Yes, I disabled that feature a long time ago. It is a really useful feature though (well, it would be if it worked properly), so I'm not sure that I'm really better off with it disabled. But it should be remembering the open/closed state of projects on a branch.
I confirm the bug still exists
