Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 353221 - [correction][quick fix] Should jump to closest problem even if there's a breakpoint
Summary: [correction][quick fix] Should jump to closest problem even if there's a brea...
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.3   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 3.8 M7   Edit
Assignee: Dani Megert CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-27 11:08 EDT by Markus Keller CLA
Modified: 2012-03-26 12:01 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Keller CLA 2011-07-27 11:08:51 EDT 
BETA_JAVA7, same in 3.6.2

package xy;
public class Try {
	void foo() {
		equals(); // add breakpoint
	}
}

- add a line breakpoint to indicated line
- put caret at end of line
- Ctrl+1
=> expected: Caret should jump to error position
=> was: Caret stays at end, no quick fix offered
Comment 1 Dani Megert CLA 2011-07-28 02:39:08 EDT 
This used to work but got broken in two steps:

- First it got broken when we introduced the jumping: there it worked at the
  end of the line but not at the beginning.
- Then the range of the line breakpoint was changed, which also broke it for
  the end of the line.