Bug 244511 - Need to know which problem markers (ids) are replaced by temporary problems
Summary: Need to know which problem markers (ids) are replaced by temporary problems
Status: CLOSED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.4   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: api
Depends on:
Blocks: 186118
  Show dependency tree
 
Reported: 2008-08-19 03:41 EDT by Dani Megert CLA
Modified: 2020-04-02 08:55 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 Dani Megert CLA 2008-08-19 03:41:31 EDT
I20080812-0800.

We need to know which problem markers (i.e. ids) are replaced by temporary problems reported during reconcile.

See bug 186118 for details.
Comment 1 Jerome Lanneluc CLA 2008-08-21 06:24:43 EDT
I've seen bug 186118 but I still don't understand this request. Can you be more specific on the API you need?
Comment 2 Dani Megert CLA 2008-08-21 08:54:42 EDT
I assume (maybe that's wrong) that for some problem markers that JDT Core creates during build there aren't corresponding IProblems issued during reconcile. If my assumption is wrong i.e. if I can assume that if I have a Java marker on a non-dirty CU (with auto-build on) I will also get a corresponding IProblem reported during reconcile then we don't need new API.
Comment 3 Jerome Lanneluc CLA 2008-08-21 10:20:16 EDT
The markers created by the Java builder and the problems reported by the compiler during reconcile are the same (same order, same problem id, etc.).

However, we don't control compiler participants. So a compiler participant could create more markers during build than problems it reports during reconcile. Is that the case you're worrying about?
Comment 4 Dani Megert CLA 2008-08-21 10:26:42 EDT
Yes that plus as said, I wasn't sure whether we can expect that for each marker from JDT Core we will get an IProblem. The idea is that we no longer show any JDT markers but only IProblems. This has two advantages:
1) we no longer need compute merge marker and IProblem
2) we get rid of update problems because the editor isn't saved yet (bug 186118)
Comment 5 Jerome Lanneluc CLA 2008-08-22 05:09:30 EDT
I think I understand now. So the answer is:
1. We know for sure that each JDT/Core markers (created at build time) has a corresponding JDT/Core problem (reported at reconcile time)
2. We don't know if this is true for other compiler participants and we have no way to know.
Comment 6 Eclipse Genie CLA 2020-04-02 08:55:29 EDT
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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.