Bug 471706 - Multiple Unthrown and declared exceptions cannot be resolved in with a batch Quick Fix operation
Summary: Multiple Unthrown and declared exceptions cannot be resolved in with a batch ...
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.5   Edit
Hardware: PC Windows 8
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-02 10:28 EDT by Nathan Christie CLA
Modified: 2022-09-22 05:15 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nathan Christie CLA 2015-07-02 10:28:03 EDT
WIth the Errors / Warnings configuration set to display "Error" on declared exceptions that are not actually thrown, it is not possible to resolve multiple problems with a single batch Quick Fix operation initiated from the "Problems" tab. The message "The selected problems do not have a common applicable Quick Fix" is displayed, instead.

These issues clearly have the same root cause and should be eligible for a batch operation. This makes resolving multiple issues very time consuming.

Reproduction Steps:
1) With a new java class, configure the project's Java > Compiler > Error / Warnings "Unnecessary detection of thrown exceptions" to "Error"
2) Create a new java class with a main method that throws "Exception", and "IOException" (you'll have to import java.io.IOException)
3) Save the file
4) Observe the Problems tab refreshes with 2 problems
5) Select both problems and right-click, select "Quick Fix"
6) Observe error message


-- Configuration Details --
Product: Eclipse 4.5.0.20150621-1200 (org.eclipse.epp.package.jee.product)
Installed Features:
 org.eclipse.jdt 3.11.0.v20150603-2000
Comment 1 Eclipse Genie CLA 2020-09-15 13:46:59 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Eclipse Genie CLA 2022-09-22 05:15:07 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.