Bug 381449 - [change method signature] consider annotations in Change Method Signature refactoring
Summary: [change method signature] consider annotations in Change Method Signature ref...
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.8   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-01 19:20 EDT by Stephan Herrmann CLA
Modified: 2012-06-06 11:05 EDT (History)
1 user (show)

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 Stephan Herrmann CLA 2012-06-01 19:20:23 EDT 
Bug 381443 gives an example where adding null annotations to a super class is perceived as burdensome, because all sub classes may need to be updated (manually or via quick fix / cleanup).

The most elegant solution would be to add null annotations via the Change Method Signature refactoring, and let it propagate null annotations to overriding methods in sub classes.
Comment 1 Markus Keller CLA 2012-06-06 11:05:50 EDT 
Yes, the refactoring should support annotations on the method (return type) as well as on parameters.

This is also interesting for annotations other than the null annotations.