Community
Participate
Working Groups
I am able to reproduce this issue with a new workspace, wanted to make sure it wasn't related to my legacy workspace from Eclipse 3.7. I am using Eclipse 4.2M3. 1. Set the workspace preference for 'open new perspective' under General->Perspectives to open in a new window. 2. Checked out a project from CVS and synchronized it, choosing to open the Team Synchronize perspective(opens it in a new window) 3. Restarted eclipse and went to the Team Synchronize perspective and selected the 'Synchronize CVS' toolbar button. It opens another Team Synchronize window, so now there are 2 open.
I cannot reproduce this problem with 4.2M3 or with I20111214-1100 on Windows 7. The second synchronize request is processed by the window I have up instead of spawning another window. Can you think of something that I may be doing wrong, Karen?
It appears I gave the wrong steps as I can't reproduce with those steps either! Let me try this again with step 3 being different: 1. Set the workspace preference for 'open new perspective' under General->Perspectives to open in a new window. 2. Checked out a project from CVS and synchronized it, choosing to open the Team Synchronize perspective(opens it in a new window) **3. Restarted eclipse and went to the Java perspective and chose to synchronize the project. It prompts me to switch to the team synchronize perspective and then opens a second team sync perspective.
(In reply to comment #2) > **3. Restarted eclipse and went to the Java perspective and chose to > synchronize the project. It prompts me to switch to the team synchronize > perspective and then opens a second team sync perspective. I can reproduce the problem with I20120105-2100 now. Thanks, Karen.
It seems the input of a particular workbench page is not being preserved across sessions. While the perspective id matches what is being requested to be open, the page's input do not match so a new workbench window is instantiated.
Not immediately clear how to persist this information at the moment because windows cannot store information in the model.
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. -- The automated Eclipse Genie.
