Community
Participate
Working Groups
let's say if the follwoing classes: class A extends Exception class B extends B eclipse 3.0m5 throws a javadoc-warning for the following code: /** * @throws A if something is wrong * @throws B if something is really wrong */ public void method() throws A; to avoid the warning i have to change the method declaration: public void method() throws A, B; although this is unnessary. I would even like to have warning for cases where the throws-clase can be shortened, e.g. "throws A, B".
Fixed. Add possibility to have additional @throws tag on subclasses of declared exceptions. Note that Javadoc still expect explicit @throws tags on declared exceptions themselves. This means, based on given example: class A extends Exception class B extends B /** * @throws B if something is really wrong */ public void method() throws A; compiler will still complain about missing tag for declared exception A, even if @throws B tag is now valid... Test case added in jdt.core.tests.compiler.regression.JavadocTestMixed
Verified of 3.0M6