Bug 442620

Summary:	[syntax highlighting] static imported methods crossed out looking deprecated but aren't
Product:	[Eclipse Project] JDT	Reporter:	Marcel Bruch <marcel.bruch>
Component:	Text	Assignee:	JDT-Text-Inbox <jdt-text-inbox>
Status:	ASSIGNED ---	QA Contact:
Severity:	minor
Priority:	P5	CC:	daniel_megert, jjohnstn
Version:	4.4
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:	stalebug

Description Marcel Bruch

2014-08-26 14:02:51 EDT

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.

Comment 1 Dani Megert

2014-08-26 14:52:03 EDT

At the point where there's no usage (just the imports), we can't tell. And we don't do a usage analysis.

Comment 2 Marcel Bruch

2014-08-26 14:55:15 EDT

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.

Comment 3 Eclipse Genie

2020-07-17 08:05:12 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 4 Jeff Johnston

2020-07-17 15:41:38 EDT

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.

Comment 5 Eclipse Genie

2022-09-20 17:17:34 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.