Community
Participate
Working Groups
running the v20040622_2000 build. I was taking screen snaps for the ISV doc and realized that I couldn't get marker help or resolution to appear for the markers generated by the readme tool example. The context help for the markers doesn't appear - instead I get the workbench help. There is no "quick fix" in the menu. I didn't have time to investigate, but when this is fixed I will need to know so I can get better screen snaps. I left as is in the doc for now.
See Bug 65660 - this should be resolved in todays 4pm build.
*** This bug has been marked as a duplicate of 65660 ***
As I understand it, the "quick fix" feature is no longer available in the tasks list. Doesn't this mean that the readme example is incorrect in its use of the markerresolution extension? Please advise so I know whether to remove the discussion of this example feature from the doc
Just talked to Stefan. The readme example does indeed have a bug. It shouldn't be contributing marker resolution for a task marker. The example should be updated to contribute a problem marker and associated resolution. For now, for the ISV doc I will discuss a different marker resolution contribution.
Is this still a problem in 3.3? PW
I think this is still an issue. The readme example still contributes markers whose supertype is a task marker, and also contributes marker help and marker resolution (quick fix). But this can't be demonstrated in the IDE because the tasks view doesn't provide access to marker help or resolution. As I understand it, the readme example should contribute markers that are subtypes of a problem marker, so that the marker help and resolution can actually be seen in the IDE. Or something like that...
Re-opened to fix PW
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.
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.
