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 132139 - Property File Editor duplicates previous entry in new entry
Summary: Property File Editor duplicates previous entry in new entry
Status: RESOLVED DUPLICATE of bug 122347
Alias: None
Product: utilities
Classification: Unclassified
Component: Properties (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: issues@utilities
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-05 18:51 UTC by tsromney
Modified: 2008-04-07 08:57 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Screen shot #1 (83.67 KB, image/jpeg)
2008-04-05 18:53 UTC, tsromney 		Details
Screen shot #2 (88.77 KB, image/jpeg)
2008-04-05 18:53 UTC, tsromney 		Details
Screen shot #2 (87.28 KB, image/jpeg)
2008-04-05 18:54 UTC, tsromney 		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 tsromney 2008-04-05 18:51:59 UTC 
In the property file editor add a new property by clicking the "New Property".  In the popup window enter the key and
value. Lets say I entry fname for the key and First Name for the value. Now add another property by clicking the "New
Property" button again.  This time I enter lname for the key and Last Name for the value. After clicking ok the property
editor displays the previous value First Name as the value for lname.  This bug can be reproduced every time.
Comment 1 tsromney 2008-04-05 18:53:18 UTC 
Created attachment 59734 [details]
Screen shot #1
Comment 2 tsromney 2008-04-05 18:53:56 UTC 
Created attachment 59735 [details]
Screen shot #2
Comment 3 tsromney 2008-04-05 18:54:37 UTC 
Created attachment 59736 [details]
Screen shot #2
Comment 4 rbalada 2008-04-07 08:57:38 UTC 
I was able to reproduce on NB 6.1 Build 200804062002.
I was *not* able to reproduce on NB trunk Build 200804070002

This issue seems to be a duplicate of issue 122347, feel free to reopen, if it's not that case.

*** This issue has been marked as a duplicate of 122347 ***