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.

Bug 39646 - CVS outputs are shared between projects
Summary: CVS outputs are shared between projects
Status: VERIFIED FIXED
Alias: None
Product: obsolete
Classification: Unclassified
Component: vcscore (show other bugs)
Version: 3.x
Hardware: PC Windows XP
: P4 blocker (vote)
Assignee: issues@obsolete
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-05 14:28 UTC by Lukas Hasik
Modified: 2004-08-13 12:12 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lukas Hasik 2004-02-05 14:28:19 UTC
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
Comment 1 Lukas Hasik 2004-02-05 14:45:02 UTC
oops, sorry, little correction

switch to different/create new project before last step -"Windows |
Versioning | VCS output"
Comment 2 David Simonek 2004-02-09 15:37:58 UTC
Passing to Tim.
Comment 3 _ tboudreau 2004-02-17 14:01:33 UTC
Another symptom of issue 39645.

*** This issue has been marked as a duplicate of 39645 ***
Comment 4 Lukas Hasik 2004-02-20 09:27:03 UTC
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...
Comment 5 _ tboudreau 2004-02-20 09:48:55 UTC
Possibly annoying, but definitely not a P2
Comment 6 Lukas Hasik 2004-02-20 09:53:20 UTC
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.
Comment 7 _ tboudreau 2004-02-21 12:09:29 UTC
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).
Comment 8 Martin Entlicher 2004-04-20 14:48:06 UTC
I suppose that this is no longer problem in 4.0, since there is no
"project change" any more.
Comment 9 Lukas Hasik 2004-04-21 10:02:42 UTC
ok, verifying, no project switching in 4.0