Eclipse Community Forums: Java Development Tools (JDT) » Possible bug: Deprecated warning in deprecated class

Home » Language IDEs » Java Development Tools (JDT) » Possible bug: Deprecated warning in deprecated class

Possible bug: Deprecated warning in deprecated class [message #222458]

Thu, 19 January 2006 00:18

Eclipse User

Hi,

1. Using M4, create a Java file, and use a deprecated class (IDOMNode
for example)
=> Both the import and the line that uses the class should have the
deprecation warning

2. Deprecate the class you've just created
=> The import has the deprecation warning

I would expect the warning at the import to go away as well so that the
Java file itself was not "yellow" marked.

Is this a bug?

Cheers,
Marcelo

Re: Possible bug: Deprecated warning in deprecated class [message #222476 is a reply to message #222458]

Thu, 19 January 2006 11:37

Eclipse User

Originally posted by: olivier_thomann.NOca.ibm.comSPAM

Marcelo Paternostro a écrit :
> 1. Using M4, create a Java file, and use a deprecated class (IDOMNode
> for example)
> => Both the import and the line that uses the class should have the
> deprecation warning
> 2. Deprecate the class you've just created
> => The import has the deprecation warning
> I would expect the warning at the import to go away as well so that the
> Java file itself was not "yellow" marked.
> Is this a bug?
yes and no :-).
The scope of the deprecation on the type doesn't enclose the import
statements. Imports belongs to the unit, not to the type.

This might be the same issue than
https://bugs.eclipse.org/bugs/show_bug.cgi?id=123522.
--
Olivier

Re: Possible bug: Deprecated warning in deprecated class [message #222482 is a reply to message #222476]

Thu, 19 January 2006 12:37

Eclipse User

Thx for the bugzilla pointer. It does seem to be related so I've added
this scenario to it.

Olivier Thomann wrote:
> Marcelo Paternostro a écrit :
>
>> 1. Using M4, create a Java file, and use a deprecated class (IDOMNode
>> for example)
>> => Both the import and the line that uses the class should have the
>> deprecation warning
>> 2. Deprecate the class you've just created
>> => The import has the deprecation warning
>> I would expect the warning at the import to go away as well so that
>> the Java file itself was not "yellow" marked.
>> Is this a bug?
>
> yes and no :-).
> The scope of the deprecation on the type doesn't enclose the import
> statements. Imports belongs to the unit, not to the type.
>
> This might be the same issue than
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=123522.
> --
> Olivier

Previous Topic:	How to attach source to binary automatically
Next Topic:	Change Eclipse Memory on Mac OS 10.4.4

Goto Forum:

-=] Back to Top [=-

Current Time: Tue May 06 20:57:07 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter