This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
jdk1.4.2, 3.6beta -IDE with fresh userdir -mount any CVS filesystem and let it do some output - try update *** VCS output window opens with tabs -"Windows | Versioning | VCS output" **** VCS output window opens with tabs from previous project
oops, sorry, little correction switch to different/create new project before last step -"Windows | Versioning | VCS output"
Passing to Tim.
Another symptom of issue 39645. *** This issue has been marked as a duplicate of 39645 ***
I have to reopen, after fix of issue 39645, this one still remains. Reproduced on 200402191900. Have some CVS output and switch to different project, it's still there. The same happens for normal OW. Try sout("xxxx") in one project, switch to another project and open OW (CTRL+4). The "xxxx" output is still there, the tab persist amongs projects...
Possibly annoying, but definitely not a P2
ok, from TM=3.6 I suppose that you'll fix it for 3.6 ;) I think that there was a issue about growing amout of tabs in OW and thise 'sharing' among project makes it worse.
Passing to Martin: You should be able to fix this by weakly referencing the TopComponents & Modes, you create/use; when the project change happens, they will be removed from the AWT hierarchy and no longer be referenced. It's looking like we may need some official API for notifying TopComponents that the project has changed - I just fixed a bunch of problems with components holding references to nodes across a project change (very dangerous - anything referencing a DataObject from the old project will throw all sorts of exceptions). It required a bunch of hacks because there's no real way to do this. However, I don't think you're referencing any nodes, so probably garbage collection will take care of the problem (this assumes that a full GC will happen during the project change, but at least with our current projects infrastructure that's pretty likely).
I suppose that this is no longer problem in 4.0, since there is no "project change" any more.
ok, verifying, no project switching in 4.0