Community
Participate
Working Groups
Steps to reproduce (assuming you have a langauge with customizable severities for validation rules): 1) Open editor for the language. 2) Ensure the editor contains error markers. 3) Close the editor. 4) Disable the validation rules. -> This should trigger a rebuild. 5) Reopen the editor -> no error markers. 6) Insert a space and save the editor. 7) Change the validation settings and reenable the constraints. -> Rebuild is triggered. 8) The editor will contain "deleted" annotations for the newly created error markers. The annotations should not be flagged as deleted since a newly inserted space will recreate them anyway. The problem is not reproducable when step (6) is omitted.
As the markers are up to date after the builder created them, I guess Xtext does nothing fundamentally wrong. Clients with this special use case should extend the XtextDocumentProvider and register a Preference-listener that triggers the validation after the settings have been changed. Alternatively, validation should be triggered by means of IResource#touch through the builder infrastructure instead of custom marker creation. Closed as won't fix.
Closing bug which were set to RESOLVED before Eclipse Neon.0.
