Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 153073

Summary:	[nls] Configure accessor dialog should adapt property file settings when accessor settings change
Product:	[Eclipse Project] JDT	Reporter:	Tobias Widmer <tobias_widmer>
Component:	UI	Assignee:	JDT-UI-Inbox <jdt-ui-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	benno.baumgartner, martinae
Version:	3.2
Target Milestone:	---
Hardware:	PC
OS:	All
Whiteboard:	stalebug

Description Tobias Widmer

2006-08-08 06:56:46 EDT

I20060807-2000

Steps to reproduce:
- Create a new Java project with two source folders
- Create a new cu with some non-nls'ed strings
- Invoke Externalize Strings
- Press Configure
- Switch source folder of resource bundle accessor
Actual: Property file location settings remain the same
Expected: Source folder of property file location changes accordingly

For the 80% case, where property files are located in the same package as their accessors, we should adapt the source folder, package and property file name if resource bundle accessor settings change.

It is very annoying having to manually set all settings to externalize strings in a fresh cu to an existing resource bundle. Clients where the property file and the accessor are not in the same package may still benefit from the proposed fix

Comment 1 Benno Baumgartner

2007-05-10 12:54:20 EDT

I'll add a checkbox:

[ ] Separate location for property file

If unchecked the location is inferred from the accessor class location. This prevents mutual synchronization of locations.

Not a bug, deferred to 3.4

Comment 2 Eclipse Genie

2020-04-29 10:14:01 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.