Bug 506137 - [rename] Rename Method refactoring should supporting adding @Deprecated annotation
Summary: [rename] Rename Method refactoring should supporting adding @Deprecated annot...
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.6   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-18 07:08 EDT by Andreas Sewe CLA
Modified: 2016-10-18 07:08 EDT (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 Andreas Sewe CLA 2016-10-18 07:08:51 EDT 
At the moment, the Rename Method dialog's "Mark as deprecated" checkbox only applies the @deprecated *Javadoc tag* to the original method.

If the source level is 1.5 or higher, it should also add the @Deprecated *annotation*.

Not sure whether this is worth a second checkbox or whether the existing "Mark as deprecated" checkbox should control both the Javadoc tag and the Java annotation.