Community
Participate
Working Groups
In a static import of import static org.hamcrest.CoreMatchers.is; "is" is crossed out. Probably because several "is" methods are deprecated in CoreMatchers. However, the one actually used is not deprecated. Thus, it shouldn't be crossed out IMHO.
At the point where there's no usage (just the imports), we can't tell. And we don't do a usage analysis.
If there are several elements, one of which is not deprecated, should the editor highlight it as deprecated then? My feeling is 'no'. But this is up to you.
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.
This bug still occurs in latest Eclipse. I tend to agree that the import should not mark it as deprecated as the usage can be correct. For example, is(T value) is valid and in fact I can choose it via completion but still get the deprecated cross-out.
