Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 424193

Summary: Old error/warning annotations aren't removed from Java Script Editor's overview ruler when disabling the Semantic Validation
Product: [WebTools] JSDT Reporter: Victor Rubezhny <vrubezhny>
Component: GeneralAssignee: Victor Rubezhny <vrubezhny>
Status: CLOSED DUPLICATE QA Contact: Chris Jaun <cmjaun>
Severity: normal    
Priority: P3 CC: alkazako, thatnitind
Version: 3.6   
Target Milestone: 3.5.2   
Hardware: All   
OS: All   
Whiteboard:

Description Victor Rubezhny CLA 2013-12-16 18:14:37 EST
Old error/warning annotations aren't removed from Java Script Editor's overview ruler when disabling the Semantic Validation.

Steps to reproduce:

1) Open a JavaScript file in JavaScript Editor.

2) Make sure that "Enable Semantic Validation" is checked in JavaScript->Validator->Errors/Warnings preference page as well as the severity level of some Validator Problems is set to either "Warning" or "Error"

3) Find an Error or Warning problem marker in Problems View for your JavaScript file (If there are no problems found edit your file that one or more problems (enabled at step #2) appeared. For example, enable "Missing Semicolon" problem marker in the preference page and add a statement without closing semicolon into your JavaScript file.)
ASSERT: There are some problem markers in Problems View as well as according problem annotations in editor's overview ruller.

4) Go back to JavaaScript->Validator->Errors/Warnings preference page and uncheck "Enable Semantic Validation" preference due to disable the Semantic Validation, apply the changes and close the preference page by pressing "OK" button.
ASSERT: 
- No Error/Warning problems (that are listed in the Preference page) are listed in Probems View; 
- (FAIL) No Error/Warning annotations are displayed in the Editor's overview Ruler;
- (FAIL) No Error/Warning decorations are shown in the Editor
Comment 1 Victor Rubezhny CLA 2014-01-13 08:01:02 EST
The fix for Bug #424131 fixed this issue too. Closing the issue as a duplicate of #424131.

*** This bug has been marked as a duplicate of bug 424131 ***