Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 318644 - No way to flag missing localization keys as errors
Summary: No way to flag missing localization keys as errors
Status: CLOSED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-01 15:10 EDT by Randy Hudson CLA
Modified: 2019-09-09 02:28 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Randy Hudson CLA 2010-07-01 15:10:38 EDT
Build Identifier: 

The PDE compiler option "Usage of non-externalized strings" flags things like Bundle-Name as needing to be externalized. That's not too useful (which is why the default value is WARNING), since the Bundle-Name is required, forcing you to often just copy the bundle ID, which would be pointless to translate.

Yet this same preference appears to be used for values in the plugin.xml which *are* externalized but are not found in the properties file.  PDE should allow values which have been externalized but are missing to be flagged as errors separately from things which the PDE believes should be externalized but are not.  Also, the default for this compiler setting should be ERROR, not WARNING.

Reproducible: Always
Comment 1 Eclipse Webmaster CLA 2019-09-06 15:34:55 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.
Comment 2 Julian Honnen CLA 2019-09-09 02:28:30 EDT
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.