Bug 192765 - [ErrorHandling] Need better way to access resources from error messages
Summary: [ErrorHandling] Need better way to access resources from error messages
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-14 18:16 EDT by Russ Baker CLA
Modified: 2019-09-06 16:03 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 Russ Baker CLA 2007-06-14 18:16:14 EDT
If an error message associated with the project shows up in the 'Problems' pane and that resource is something that cannot be accessed, then double clicking on the error or right-clicking on the error message and selecting 'GoTo' does nothing.

To Repro:

1) Create a web services project and associate it with an EAR project
2) Create a web service --> Save the file which forces a build
3) Go into a deployment descriptor file of the EAR project and manually edit it and add some bogus implementation version of one of the libraries. 
4) Then either double clicking on the error or right-clicking on the error message in the 'Problems' pane and selecting 'GoTo.'

What I would expect to happen is to either have the 'GoTo' link grayed out or having the IDE open up widget that would allow the user to fix the problem. In the case of double clicking on the error message, maybe an Alert box pop up saying that the resource cannot be accessed.
Comment 1 Kevin McGuire CLA 2007-06-15 11:22:03 EDT
Have you seen this in other examples?  I am not sure off hand if its a platform problem (lack of resource doesn't disable goto) or a WTP problem.
Comment 2 Susan McCourt CLA 2009-07-15 12:25:45 EDT
"As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009"
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:03:39 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.

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.