Bug 79342

Summary:	[misc] Summary of implications of refactoring
Product:	[Eclipse Project] JDT	Reporter:	Andrew Taylor <andy>
Component:	Text	Assignee:	JDT-Text-Inbox <jdt-text-inbox>
Status:	ASSIGNED ---	QA Contact:
Severity:	enhancement
Priority:	P5
Version:	3.1
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Andrew Taylor

2004-11-23 15:33:27 EST

This is rather pie-in-the-sky, but would be *very* useful. 

It would be nice to combine editing notification and member lookup to resolve
implications of editing actions, perhaps in a background, low priority, analysis
thread.  If source is edited, events triggered (as I'm sure they are), which
cause discovery of affected methods/classes/etc.  For example, if one is editing
a superclass protected method, perhaps changing the name, and so an overridden
method in a descendant class is no longer going to be called, the implication
would be noted in a seperate view.  IE: 'rename method MyClass.overridenMethod()
caused MyOverrider.oldOverridenMethod() to not be called'.  Most of these issues
won't occur when doing things in the scope of refactoring (ie changing method
name via refactor->rename), but could help out for when refactoring is not used,
perhaps as the dev does not realize the implications.

Thoughts?

BTW, thanks for all your work.  Eclipse enables me to solely maintain a codebase
that would otherwise be impossible!

Andy

Comment 1 Dani Megert

2004-11-24 03:22:15 EST

There are currently no plans to add this but we are quite close: if you use
auto-build, and build in the background then you get what you want by saving
(Ctrl+S) in short intervals and looking at the Problems view.

Comment 2 Dani Megert

2007-06-22 09:59:22 EDT

Get rid of deprecated state.