Community
Participate
Working Groups
I've noticed a bogus deprecation warning in my Javadocs that only appears in Eclipse and which isn't correct when looking at the code. Consider the following example to reproduce the issue: ======================================== import java.util.List; public interface Other { @Deprecated <T> T getValue(List<T> field, T defaultValue); <T> T getValue(List<?> field, Class<?> type); /** * This doesn't get any deprecation * warning {@link Other#getValue(List, Class)} */ void x(); } import java.util.List; public interface Test { /** * Let's reference the non-deprecated * class through a {@link Other#getValue(List, Class)}. * We get a deprecation warning in the Javadocs */ void x(); } ======================================== In the above example, I get a warning in Test.x()'s Javadoc (but not in Other.x()'s Javadoc), because the link is resolved to Other.getValue(List, Object), not to Other.getValue(List, Class). It has something to do with the wildcards in Other.getValue(List<?>, Class<?>). The following method signature will help work around the issue: ======================================== import java.util.List; public interface Other { @Deprecated <T> T getValue(List<T> field, T defaultValue); <T> T getValue(List<T> field, Class<?> type); } ========================================
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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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.
Still wrong
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.
