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 28142 - In some cases new group is not added
Summary: In some cases new group is not added
Status: RESOLVED WORKSFORME
Alias: None
Product: obsolete
Classification: Unclassified
Component: vcscore (show other bugs)
Version: 3.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Martin Entlicher
URL:
Keywords: T9Y
Depends on:
Blocks:
 
Reported: 2002-10-21 15:46 UTC by David Kaspar
Modified: 2004-02-22 10:23 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Test (1.44 KB, text/plain)
2002-10-21 15:47 UTC, David Kaspar 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Kaspar 2002-10-21 15:46:18 UTC 
How to reproduce:
Open "VCS Groups" window
Run Test from the attachment.
ERROR - Second group is not added. If it is
created, do not close "VCS Groups" window and run
test once again.
Comment 1 David Kaspar 2002-10-21 15:47:43 UTC 
Created attachment 7717 [details]
Test
Comment 2 Jiri Kovalsky 2003-02-12 10:39:51 UTC 
VCS groups were not available in NetBeans 3.1 so changing version of
this issue accordingly.
Comment 3 Martin Entlicher 2003-02-20 12:30:05 UTC 
This might be a problem of Nodes as well.
I suppose, that this is not reproducible manually, right? :((
Can you add a group later manually, after the test fails?
Comment 4 Jiri Kovalsky 2003-02-20 12:42:33 UTC 
Frankly speaking I was not able to reproduce it manually. You were,
Davide ?
Comment 5 Martin Entlicher 2003-08-08 11:42:09 UTC 
This is not a problem for users, but affects testability - adding T9Y
keyword.
Comment 6 Martin Entlicher 2004-02-05 12:55:10 UTC 
Is this still a problem in 3.6 builds? Is the test still affected?
Comment 7 Martin Entlicher 2004-02-22 10:23:19 UTC 
It works for me in 3.6 builds. Also this might be fixed after fix of
issue #40312. Reopen if this is still a problem.