Description Gordon Henriksen 2006-08-10 17:00:47 EDT

This particular behavior frequently interrupts my workflow.

1. Under Preferences > Java > Compiler > Errors/Warnings > Unnecessary code, set 'unused import' to 'error'.
2. Create these 2 classes:

package test2;
public class Bar {
	public static class BarException extends Exception {/* empty */}
	public static void bar() throws BarException {
		if (true)
			throw new BarException();
	}
}

package test1;
import test2.Bar;
import test2.Bar.BarException;
public class Foo {
	public static void foo() throws BarException {
		 Bar.bar();
	}
}

3. Build. Observe success.
4. As if in preparation of handling the BarException, make this edit:
-	public static void foo() throws BarException {
+	public static void foo() {
4. Build. Observe: only 1 error: 'the import test2.Bar.BarException is never used' (a discretionary error).
-- then either: --
5a. Return to Preferences and set 'unused import' back to warning.
6a. Build. Observe: The error from step 4 is now a warning, and is joined by the 'Unhandled exception type Bar.BarException'.
-- or: --
5b. Make this edit:
-import test2.Bar.BarException;
6b. Build. Observe: The 'Unhandled exception type' error appears now, only after the import necessary to catch it was deleted...

Desired behavior: At step 4, both errors should be presented, as they are if the 'unused import' warning is not configured as an error.