This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Move method to different Type | ||
---|---|---|---|
Product: | editor | Reporter: | belur_1d <belur_1d> |
Component: | Refactoring | Assignee: | issues@java <issues> |
Status: | RESOLVED DUPLICATE | ||
Severity: | blocker | CC: | gglazer |
Priority: | P3 | ||
Version: | 5.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
belur_1d
2007-03-24 07:02:13 UTC
I agree that this is an important feature and much more common event than some of the more obscure refactoring choices already in NetBeans, such as abstracting to a superclass. A typical example involves moving a method from a worker object to a service after it becomes known that multiple types of workers will require the same type of processing. Here, the method is being generalized in usage, but not with respect to inheritance, so refactoring tools like pull up, push down, extract and so on are not useful. *** This issue has been marked as a duplicate of 57767 *** |