Community
Participate
Working Groups
Created attachment 146610 [details] Phantom perspectives I've been creating and removing a link to a non-P2 extension location (CCRC). Between Eclipse restarts the IDE grow references to multiple "ClearCase" perspectives. The extension location I'm pointing at only has one version of CCRC D090713 (the latest from the IBM update site: http://www3.software.ibm.com/ibmdl/pub/software/rationalsdp/clearcase/ccrc/701/update/) and was created using the old UM. Only one perspective actually works (the one without angle brackets). The others have no views, and Window > Reset Perspective has no effect. The multiple perspectives seem to be tied to this workspace as using the same configuration with a different workspace works as expected. Apart from this link (+ a link to a config containing GEF) the configuration I'm using is clean. Screenshot attached
Created attachment 146624 [details] duplicate perspectives macos runtime Hmmm. This is happening in my Runtime Workspace on OS X as well (with 3.5) and I haven't been doing any interesting configuration tweaks... Perhaps this is unrelated to p2?
Pascal could you give any pointers on which classes might be implicated with this so I can have a go tracking down the source of this bug? I'm getting this a lot migrating users between versions of my product.
Wondering whether this might be specific for CCRC. Are you going to try with the latest (CCRC 7.1.1) ? http://www-01.ibm.com/support/docview.wss?rcss=rtlcc&rs=984&uid=swg21265307#Version%207.1.1 https://publib.boulder.ibm.com/infocenter/cchelp/v7r1m0/index.jsp?topic=/com.ibm.rational.clearcase.help.ic.doc/helpindex_ccrc.htm
(In reply to comment #3) > Wondering whether this might be specific for CCRC. > Are you going to try with the latest (CCRC 7.1.1) ? Nope, I'm on 7.0.x still. Don't think it much matters -- it also happens with CDT which is part of my base platform. As far as I'm aware I'm not changing anything perspective related in the CDT release.
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.
