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

Bug 30204

Summary: [Markers] Perform multiple quick fixes of same type at once
Product: [Eclipse Project] Platform Reporter: Joerg Pleumann <joerg>
Component: UIAssignee: Tod Creasey <Tod_Creasey>
Status: RESOLVED DUPLICATE QA Contact:
Severity: enhancement    
Priority: P3 CC: bogofilter+eclipse.org, ghulands, igor, markus, preuss, vlsergey
Version: 2.1   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Joerg Pleumann CLA 2003-01-24 14:47:29 EST 
It would be nice if Eclipse allowed to select and perform multiple quick fixes 
of the same type at once. Otherwise, if - for example - you import old source 
code into Eclipse the first time and want to clean it up, you have to select 
dozens of errors or warning and run the (same) quick fix for each of them. At 
least that's when I encounter this problem regularly.

Good examples for this are:

- Add missing import
- Remove unused import
- Add to version control
- Add to .cvsignore
- Static field should be accessed in static way
Comment 1 Dirk Baeumer CLA 2003-01-28 03:37:12 EST 
The first two can be fixed by selecting the project and using Organize imports.

Are you selecting the errors in the task list ?
Comment 2 Joerg Pleumann CLA 2003-01-28 03:56:57 EST 
Yes, the idea was to select then bugs in the bug list, because it is easy to 
select multiple items at once there. When opening the context menu for these, 
I'd like to see quick fixes that apply to all selected entries. If the tasks 
are too different, this list would be empty.
Comment 3 Dirk Baeumer CLA 2003-01-28 04:52:53 EST 
Moving to platform since they own the task list.
Comment 4 Stefan van den Oord CLA 2003-03-24 04:06:15 EST 
Yes, I REALLY would like to see this added. But not only using the task list, also by 
selecting text in the editor that contains more than one error (curly-underlined part). So it 
is NOT task-list specific!
Comment 5 Markus Gebhard CLA 2005-01-08 05:55:42 EST 
A good example is the quick fix for "Non-externalized string literal" in unit 
tests: It really drives you nuts to quick-fix them when you have 65 occurences 
in one file...
Comment 6 Dirk Baeumer CLA 2005-01-13 05:29:49 EST 
*** Bug 82704 has been marked as a duplicate of this bug. ***
Comment 7 Dirk Baeumer CLA 2005-05-24 08:24:11 EDT 
*** Bug 96412 has been marked as a duplicate of this bug. ***
Comment 8 Sergey Vladimirov CLA 2005-05-26 04:32:53 EDT 
"The method ... of type ... should be tagged with @Override since 
it actually overrides a superclass method" too (Bug 96412)
Comment 9 Benjamin Hill CLA 2005-07-18 20:08:42 EDT 
Suggesting that this is a duplicate of 23889, which has a lot of discussion
around batch fixing.
Comment 10 Ben Aveling CLA 2005-07-20 21:10:41 EDT 
Agree this is a duplicate of bug 23889.

More importantly, why offer the intersection of all relevant fixes?

Why not offer the superset, and apply the selected fix where relevant?
Comment 11 Ilja Preuss CLA 2005-07-21 03:15:26 EDT 
(In reply to comment #10)
> More importantly, why offer the intersection of all relevant fixes?
> Why not offer the superset, and apply the selected fix where relevant?

I think that would be confusing. At least give a warning (dialog?) that the fix 
will not be applied to all problems, perhaps with the option to cancel the 
action? Or even better, already mark fixes that do not apply to the whole 
selection appropriately in the context menu.
Comment 12 Martin Aeschlimann CLA 2005-09-27 11:50:14 EDT 
*** Bug 110748 has been marked as a duplicate of this bug. ***
Comment 13 Tod Creasey CLA 2005-10-14 07:07:22 EDT 

*** This bug has been marked as a duplicate of 111429 ***