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 44512 - VCS nodes fire property changes for props that are not in their property sets
Summary: VCS nodes fire property changes for props that are not in their property sets
Status: RESOLVED WONTFIX
Alias: None
Product: obsolete
Classification: Unclassified
Component: vcsgeneric (show other bugs)
Version: 4.x
Hardware: PC Linux
: P4 blocker (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on: 43045
Blocks:
  Show dependency tree
 
Reported: 2004-06-08 12:18 UTC by _ rkubacki
Modified: 2009-12-21 07:17 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
stack traces (24.45 KB, text/plain)
2004-06-08 12:19 UTC, _ rkubacki 		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 _ rkubacki 2004-06-08 12:18:46 UTC 
These are notifed in log as IllegalStateExceptions
refering to issue 31413
Comment 1 _ rkubacki 2004-06-08 12:19:08 UTC 
Created attachment 15555 [details]
stack traces
Comment 2 Martin Entlicher 2004-06-08 12:36:53 UTC 
This concerns CommandLineVcsFileSystem object.
I don't think this IllegalStateExceptions has sense. I need to fire
property changes in order to assure serialization, but I definitely
don't want to show all properties.

Decreasing to P5, this does not affect the user in any way.
Comment 3 Martin Entlicher 2004-06-08 12:44:30 UTC 
Isn't this a bug of BeanNode?
Comment 4 Martin Entlicher 2004-06-08 13:35:04 UTC 
This depends on issue #43045 (it's like a duplicate, depending on the
solution).
Comment 5 Quality Engineering 2009-12-21 07:17:47 UTC 
This bug was reported against NetBeans IDE 6.0 or an older release, or against a non-maintained module. NetBeans team does not have enough resources to get to this issue, therefore we are closing the issue as a WONTFIX. If you are interested in providing a patch for this bug, please see our NetFIX guidelines for how to proceed. 

We apologize for any inconvenience.


Thank you.
The NetBeans Team