Bug 62522 - [nls tooling] Externalize Strings Configure Accessor class always defaults to Message [nls] [refactoring]
Summary: [nls tooling] Externalize Strings Configure Accessor class always defaults to...
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal with 3 votes (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
: 122564 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-05-17 14:53 EDT by Michael Valenta CLA
Modified: 2023-12-15 14:06 EST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Valenta CLA 2004-05-17 14:53:55 EDT
When externalizing strings, the default class on the Configure Accessor class 
dialog is always Message and the method name is always getString. We use 
Policy#bind as our pattren. Other fields seem to get remembered but I always 
have to enter these. I am using build I20040517.
Comment 1 Michael Valenta CLA 2004-05-17 14:55:12 EDT
Also, we use the same settings for the whole project but the tool seems to 
remeber then per-package.
Comment 2 Dirk Baeumer CLA 2004-05-18 04:08:29 EDT
There isn't a mechanism yet to define the default accessor class and method.
Comment 3 Dirk Baeumer CLA 2004-09-14 12:42:40 EDT
In HEAD there is now a combo box letting you select that last used class names 
and properties file. Hoewever we don't remember the substitution pattern. 
Martin, it would make sense to remember that one as well.
Comment 4 Dani Megert CLA 2006-01-04 03:43:14 EST
*** Bug 122564 has been marked as a duplicate of this bug. ***
Comment 5 Dani Megert CLA 2008-04-18 10:37:47 EDT
We should add a mode which simply uses the previous settings. This would fit both worlds.
Comment 6 Eclipse Genie CLA 2020-01-03 09:54:05 EST
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.

If you have further information on the current state of the bug, please add it. 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.
Comment 7 Eclipse Genie CLA 2021-12-24 14:19:09 EST
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.

If you have further information on the current state of the bug, please add it. 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.
Comment 8 Eclipse Genie CLA 2023-12-15 14:06:25 EST
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.

If you have further information on the current state of the bug, please add it. 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.