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 152815 - GUI builder (refactoring) - move form from source package to other without relocate keys with messages
Summary: GUI builder (refactoring) - move form from source package to other without r...
Status: NEW
Alias: None
Product: guibuilder
Classification: Unclassified
Component: App Framework (show other bugs)
Version: 6.x
Hardware: All Windows XP
: P3 blocker (vote)
Assignee: issues@guibuilder
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-09 19:24 UTC by jakubbrach
Modified: 2008-12-08 16:03 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
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 jakubbrach 2008-11-09 19:24:25 UTC 
We tried to move form from source package to another one. Class was relocated completely, but keys with
messages from bundle file was stayed in source package. In *.form file is
still existing link to original bundle.properties file with messages.
Imho the right way is to relocate key with messages for components included in form too
(create new bundle file in new package and copy key with messages there).
We don't use standart name (Bundle.properties), we have own name for *.properties file with messages.
Comment 1 Jiri Vagner 2008-12-08 16:03:10 UTC 
We use this approach only for Java Desktop Application projects, there are rules about location of bundle files and
naming conventions, ...  In common java application projects refactoring will change only path to bundle file. Copying
of keys from one bundle file to another one leads to redundancy and moving keys from one file to another one can break
the other form if it use the same keys in the same bundle file.

>> We don't use standart name (Bundle.properties), we have own name for *.properties file with messages.
I don't understand last sentense of your comment. Name of bundle file is not hardcoded, you can change it inside
Properties view of your form. Select root form node inside Navigator tree and modify "Properties Bundle File" property.

So, from my point of view, your report is more an enancement than a bug. >> I changed issue type to an enhancement.