Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 319768

Summary:	Double clicking on a dependency related issue in problems view doesn't open the correct tab in the project descriptor
Product:	[Technology] Tigerstripe	Reporter:	Navid Mehregani <nmehrega>
Component:	UI	Assignee:	Project Inbox <tigerstripe.ui-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	chrhartl
Version:	unspecified
Target Milestone:	0.5M0
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:

Description Navid Mehregani

2010-07-13 14:18:08 EDT

Build Identifier: 

When a dependency related issue is reported in Problems view, user can double click on it to open the corresponding project descriptor file.  However, the Overview tab is selected, which basically leaves it up to the user to figure out where the dependencies are specified.  Compare this to a compiler issue reported for a Java file.  Double clicking on the issue will open the corresponding Java file and scroll to the exact line number that needs to be addressed.

Similarly, Tigerstripe should open the corresponding project descriptor file, select the Dependency tab, and scroll down to the list of dependencies.

Reproducible: Always

Steps to Reproduce:
1. Create two TS projects 
2. Have one of the projects depend on the other
3. Close the project used as a dependency
4. Double click on the issue reported in Problems view

Comment 1 Chris Hartley

2010-08-06 01:32:31 EDT

I think the issue is more general.
In most cases double clicking on a problem opens the wrong editor.

Also quick fixes aren't defined for TS problems.

Comment 2 Navid Mehregani

2010-09-21 17:03:26 EDT

Now when there are dependency related issues and user opens Tigerstripe descriptor (either from TS Explorer or by double clicking on a marker in Problems view), dependency page gets activated and the error message is printed in the form's header.  This is integrated with the build, and the message goes away when the dependencies are resolved and a clean build is done.  

Also see bug#321257 for a somewhat similar issue as this defect.