Bug 113238 - [reconciling] Create minimal annotation model updates when reconciling
Summary: [reconciling] Create minimal annotation model updates when reconciling
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.2   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: performance
Depends on:
Blocks:
 
Reported: 2005-10-20 10:59 EDT by Tom Hofmann CLA
Modified: 2022-11-17 10:19 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Hofmann CLA 2005-10-20 10:59:40 EDT 
up to 3.1 M2

CompilationUnitAnnotationModel contains the logic to map temporary
reconcile-time problems to persistent Markers created by the last build. See
CompilationUnitAnnotationModel::reportProblems(List).

Currently, any previous annotations are discarded and replaces with new ones,
even if this is not needed. The result is a huge annotation model event fired
with every reconcile, resulting in all annotations being repainted.

The mapping algorithm should try to come up with the minimal change required by
the reconcile.
Comment 1 Dani Megert CLA 2005-11-09 11:39:28 EST 
There were bugs in the past about missing annotation and marker updates in the
editor which got fixed with the current approach. Those bugs would have to be
identified and verified against a new implementation.
Comment 2 Eclipse Genie CLA 2018-12-01 11:54:43 EST 
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.

--
The automated Eclipse Genie.
Comment 3 Eclipse Genie CLA 2020-11-21 11:04:04 EST 
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.

--
The automated Eclipse Genie.
Comment 4 Eclipse Genie CLA 2022-11-17 10:19:08 EST 
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.

--
The automated Eclipse Genie.