Bug 95951

Summary: Add "nls" support in @SuppressWarnings
Product: [Eclipse Project] JDT Reporter: Artur Brinkmann <artur.brinkmann>
Component: CoreAssignee: Olivier Thomann <Olivier_Thomann>
Status: VERIFIED DUPLICATE QA Contact:
Severity: normal    
Priority: P3    
Version: 3.1   
Target Milestone: 3.1 RC2   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Artur Brinkmann CLA 2005-05-19 10:53:10 EDT
Build N20050518-0010

I still get the "Non-externalized string literal" warning, with
@SuppressWarnings("all") it disappears though. Since I don't get the "unhandled
warning token" warning, I suppose "nls" is the correct warning name.
Comment 1 Olivier Thomann CLA 2005-05-20 10:33:07 EDT
Not all warnings are supported yet.
See bug 83739 comment 14. Only "all", "unchecked",
"deprecation", "finally" and "serial" are sypported for now.
Update title accordingly.
Comment 2 Philipe Mulet CLA 2005-05-20 11:08:03 EDT
Actually, they are all supported now, check build notes from M7 build:

http://download.eclipse.org/downloads/drops/S-3.1M7-200505131415/buildnotes/buildnotes_jdt-core.html

The supported warning tokens are listed in v_555 entry. We are trying to make
these more intuitive.

"nls" should work. Could you provide steps to reproduce this issue ?
Comment 3 Artur Brinkmann CLA 2005-05-20 13:00:13 EDT
// Example:
// (the "Usage of non-externalized strings" warning in the code style section
has to be enabled for project or workspace first)

package test;

@SuppressWarnings("nls") //$NON-NLS-1$
public class Test {
	private String foo = "foo"; // warning should be suppressed here...
}
Comment 4 Olivier Thomann CLA 2005-05-27 11:38:27 EDT
This should indeed work.
Comment 5 Olivier Thomann CLA 2005-05-27 11:44:27 EDT

*** This bug has been marked as a duplicate of 96974 ***
Comment 6 Frederic Fusier CLA 2005-06-08 03:26:27 EDT
Verified for 3.1 RC2 using build N20050608-0010