Bug 238765 - [nls tooling] Externalize wizard should provide a deselect all button or evaluate @SupressWarnings("nls")
Summary: [nls tooling] Externalize wizard should provide a deselect all button or eval...
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.4   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-27 06:32 EDT by Ulli Hafner CLA
Modified: 2022-08-02 19:29 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ulli Hafner CLA 2008-06-27 06:32:15 EDT
When I start the externalize wizard, then it starts with all not yet externalized Strings as selected, i.e. all strings that are not marked with the // NLS comments. 

It would help very much if either
a) the wizard would also evaluate a @SupressWarnings("nls") annotation and would not present the results that are in the scope of such a  annotation (There is already a filter checkbox there)
b) the wizard would provide a "Deselect All" Button so that I only need to press this button and then select the one or two strings that need to be externalized.

Currently when having a method with e.g. 20 supressed strings you need to deselect all these Strings to finally externalize a new added string
Comment 1 Dani Megert CLA 2008-06-30 09:47:53 EDT
It should mark them as ignored.
Comment 2 Eclipse Genie CLA 2020-07-06 08:36:27 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.

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 3 Eclipse Genie CLA 2022-08-02 19:29:34 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.

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.