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.
Combo box in Resource Bundle Property Customizer or in I18N Wizard shows another keys than bundle realy contains. Key added this way is added into bundle but it is not listed when cutomizing another property or when editing another line in I18N Wizard.
Set terget milestone to TBD
In the case of wizard the keys are not actually added into properties file yet. I'll need to add notion of proposed keys and show them in the combo. Another inconsistency I found is in Inset I18n string action. The properties file is for perfomance purposes queried only once i.e. ommiting to invoke PropertyPanel.updateBundleKeys() method for subsequent insertions.
I fixed the Insert i18n string inconsistency by backporting prj40_prototype implementation. The wizard one seems to be trickier. I defer it till the wizard UI/flow redesign stage.
Please describe the steps to reproduce the bug.
After a discussion with the reporter, the steps to reproduce are as follows: 1) In the filesystems explorer, right-click on a Java file and select action Tools / Internationalization / Internationalize... 2) Using the "Internationalize" dialog, when the first hard-coded string is found, make sure the key name is not yet present in the properties file. Then confirm change of the code by pressing button "Replace". When then next hard-coded string is found, look into the pop-down menu of the "Key" combo-box. The key added in the previous step should be there but it is not there (if this bug exhibits). Another way to found a buggy behaviour is to invoke an Internatialization Wizard simoultaneously (while the "Internationalize" dialog is displayed) - right click on the same file and select action Tools / Internationalization / Internationalization Wizard. In the wizard, press button Next until you advance to step "Modify Found Strings". In the wizard, press any button labeled "..." (in the rightmost column of the table) - a customizer dialog appears - and check whether the key/value pair added in dialog "Internationalize" is offered in the customizer (it should be if there is no bug).
I cannot reproduce any of the described bugs (on Linux+PC). Because one of the described problems was accepted and fixed (by Petr Kuzel), I mark it FIXED (not WORKSFORME).