Bug 150522 - [compare] Java Structure/Source Compare initial difference selection isn't useful
Summary: [compare] Java Structure/Source Compare initial difference selection isn't us...
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: All All
: P3 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Andre Weinand CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-13 11:21 EDT by Gary Johnston CLA
Modified: 2006-07-17 08:35 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gary Johnston CLA 2006-07-13 11:21:42 EDT
In a Java project, make some changes to some Java source files such that there is a change in its imports as well as in its code.  Synchronize the project with your repository.  In the Synchronize view, double click on one of the changed files to open the comparison view.  Notice that in the Java Source Compare pane the first difference is initially selected.  In this case, since the imports changed, the initially selected difference is the first changed import.  However, the import changes are almost never what I'm interested in, so I alsmost always have to then go over and scroll down to (or select) the first difference in the actual code.  Tedious.  It would be much better if the Java Structure/Source Compare could be made to initially select the first difference in the code (or, at least, the first difference after the imports, which might be the class comment, of course).  Ideally, I think, this could be a preference.
Comment 1 Martin Aeschlimann CLA 2006-07-17 06:27:21 EDT
Michael, why did you move this back?
Comment 2 Michael Valenta CLA 2006-07-17 07:16:51 EDT
You may not be aware but Compare hasd been moved into Team and we plan to address several Comapre issues in 3.3. I have been triaging the Compare bugs to get a feel for what we could do in 3.3. 

This particular bug can be viewed two ways. It can be viewed as a JDT bug that requires support from Compare or a Compare bug that has overlap with JDT. I guess I thought it fit into the former category. If you feel it belongs in the later category, feel free to move it back.
Comment 3 Martin Aeschlimann CLA 2006-07-17 08:35:53 EDT
I also think this is a JDT bug. We currently collecting JDT compare bugs in Andre's inbox. It doesn't necessarly mean that Andre will fix these bugs.
We are planing to allocate some time in 3.3 to look at all non-critival compare bugs.