Bug 39763 - Non NLS string is reported and it should not
Summary: Non NLS string is reported and it should not
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 3.0 M2   Edit
Assignee: David Audel CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-07-08 12:22 EDT by Olivier Thomann CLA
Modified: 2003-07-16 05:06 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 Olivier Thomann CLA 2003-07-08 12:22:04 EDT
Using latest HEAD contents, the following code reports an error for a NON-NLS
string, but it should not.

public class Foo { 

    public void foo() {
    
		System.out.println(
		"string1" + "string2" //$NON-NLS-1$//$NON-NLS-2$
		);
}

Adding a closing brace fixes both errors. The problem seems to come from the
protected boolean resumeAfterRecovery() method. During the
moveRecoveryCheckpoint() call, the currentLine is set to the next string
literal. It should be null.
Comment 1 Olivier Thomann CLA 2003-07-09 11:56:39 EDT
Fixed and released in HEAD.
Regression tests added.
Comment 2 David Audel CLA 2003-07-16 05:06:34 EDT
Verified.