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 21672 - Accessing Generic VCS node from tests through API cause problems
Summary: Accessing Generic VCS node from tests through API cause problems
Status: CLOSED FIXED
Alias: None
Product: obsolete
Classification: Unclassified
Component: vcsgeneric (show other bugs)
Version: 3.x
Hardware: All All
: P3 blocker (vote)
Assignee: Martin Entlicher
URL:
Keywords: T9Y
Depends on:
Blocks:
 
Reported: 2002-03-18 14:16 UTC by Adam Sotona
Modified: 2003-07-01 13:05 UTC (History)
0 users

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 Adam Sotona 2002-03-18 14:16:40 UTC
Accessing Generic VCS node in Options from tests through API cause Filesystem
Cache Thread to start.
This thread is created as child of current test thread and keeps test process
active.
IDE could not be finally closed because of still active test process.

Correct behaviour should be to ensure usual conditions for API tests and
re-parent Filesystem Cache Thread.
Comment 1 Martin Entlicher 2002-04-04 16:38:42 UTC
I suppose you mean node under "IDE Configuration/System/Filesystem
Settings" right?
Can you please tell me the exact name of the thread which starts?
Thanks.
Comment 2 Adam Sotona 2002-04-05 08:21:40 UTC
The node exact path is:
Options/Source Creation and Management/Templates/Filesystems/Version
Control/Generic VCS

Thread name is:"FileSystem Cache Queue"
Comment 3 Martin Entlicher 2002-04-29 10:44:45 UTC
Not sure, how to re-parent the thread. Can I get to the IDE's thread
group?
I've set the Thread as the daemon thread. Not sure if it helps.
Reopen if it didn't help.
Comment 4 Jiri Kovalsky 2002-06-10 13:26:24 UTC
Adam seems to be satisfied so far. :-) Works fine in development build
#200206100100 of NetBeans 3.4.
Comment 5 Quality Engineering 2003-07-01 13:05:23 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.