Summary: | [quick fix] Moving a class via Quick Fix will not refactor the imports anywhere | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Eugen Paraschiv <hanriseldon> |
Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
Status: | ASSIGNED --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | amj87.iitr, deepakazad, manju656, tomasz.zarna |
Version: | 4.2 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux | ||
Whiteboard: |
Description
Eugen Paraschiv
2012-06-28 08:40:00 EDT
This is pretty similar to bug 383787, where iiuc you're suggesting the quick fix should be more like a refactor action, not just dummy package move. Is that correct? Yes, it's pretty similar, and yes, one fix would potentially fix both. I added two bugs, because the failures are related but ultimately different. Thanks. Eugen. Moving to JDT/UI Our current Quick Fix is not capable of handling a fix which require modification in more than one file. In such scenario we have to choose one of the refactoring options available so that the internal consistency of the files are maintained. We can think of taking this up an improvement point for the current Quick Fix. See also bug 383787 Our current Quick Fix is not capable of handling a fix which require modification in more than one file. In such scenario we have to choose one of the refactoring options available so that the internal consistency of the files are maintained. We can think of taking this up an improvement point for the current Quick Fix. See also bug 383787 |