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.
|Summary:||Need an action to navigate to the Bundle.properties for the currently edited file|
|Product:||java||Reporter:||_ wadechandler <wadechandler>|
|Component:||Navigation||Assignee:||Tomas Zezula <tzezula>|
|Issue Type:||ENHANCEMENT||Exception Reporter:|
Description _ wadechandler 2012-10-18 10:04:21 UTC
When working in a Java file, and one wants to make changes to the current Bundle.properties file, and it isn't opened, getting to that file could be made much simpler by a navigation editor to go directly to the file. This action could 1) open the correct Bundle.properties or perhaps be dynamic with a JMenu and allow either Bundle.properties or one of either Bundle.properties or its internationalized counter parts to be opened 2) Select the navigated Bundle in the projects window as to expand the package so any other related file can be easily accessed. For #2 I'm using Maven projects where a different sources folder exists entirely, and access the Bundle is harder or at least more time consuming. I'm using the NbBundle class in an RCP project where a new top component was created which uses the Messages annotation, and I have had to change that due to a bug with the @Messages annotation which causes the Bundle not to be updated at build time and errors are thrown at runtime, so I need to copy and paste my messages and jump to my bundle. Instead I need to search for it directly as goto file isn't efficient as there are many Bundle.properties files in my project.
Comment 1 _ wadechandler 2012-10-18 10:08:00 UTC
If the Bundle doesn't exist, it should either be created or at least alert the user and let them create it if they need/want to.