Bug 381449

Summary:	[change method signature] consider annotations in Change Method Signature refactoring
Product:	[Eclipse Project] JDT	Reporter:	Stephan Herrmann <stephan.herrmann>
Component:	UI	Assignee:	JDT-UI-Inbox <jdt-ui-inbox>
Status:	ASSIGNED ---	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	markus.kell.r
Version:	3.8
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Stephan Herrmann

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

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.