Bug 83643 - [1.5] @Deprecated members not 'slashed'
Summary: [1.5] @Deprecated members not 'slashed'
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 3.1 M6   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-25 14:31 EST by Adam Kiezun CLA
Modified: 2005-03-31 19:14 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Kiezun CLA 2005-01-25 14:31:22 EST 
3.1M4
things that are deprecated in javadoc get special treatment in java views.

but things with the @Deprecate annotation enjoy no such treatment
Comment 1 Dirk Baeumer CLA 2005-02-10 13:40:11 EST 
The Java model doesn't surface annotations. 

However for this special case the annotation could be surfaced via the
deprecated flag. 

Moving to JDT/Core for comments
Comment 2 Philipe Mulet CLA 2005-02-10 16:21:00 EST 
Support for @Deprecation isn't in yet. Planned for M6.
Comment 3 Philipe Mulet CLA 2005-03-14 17:01:17 EST 
Added support; @Deprecated is now equivalent to proper deprecated javadoc tag.
Added AnnotationTest#test116-120.
Fixed
Comment 4 Olivier Thomann CLA 2005-03-30 23:53:40 EST 
Using the following code,

public class X
{
    @Deprecated
    protected static <T extends Exception> void foo() throws T, Exception {
    }
}

In the outliner the method foo is not slashed.
Comment 5 Philipe Mulet CLA 2005-03-31 06:15:42 EST 
Entered bug 89807 for latter issue. Note that the model is not meant to surface
the deprecated flag in this case, as it cannot statically be determined at
parsing stage. It needs to resolve in order to be able to interpret the meaning
of the annotation.
Comment 6 Olivier Thomann CLA 2005-03-31 19:14:50 EST 
Verified in I20050331-1600