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: | "Extract Class" and "Move method" refactor options. | ||
---|---|---|---|
Product: | java | Reporter: | jonathanvilalopez <jonathanvilalopez> |
Component: | Refactoring | Assignee: | Ralph Ruijs <ralphbenjamin> |
Status: | REOPENED --- | ||
Severity: | normal | CC: | ralphbenjamin |
Priority: | P2 | ||
Version: | 7.1.1 | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
jonathanvilalopez
2012-04-17 16:12:47 UTC
I f I understand correctly; the refactor command, list is the refactoring menu? In NetBeans 7.2 (avaiable in the current dev builds [1]) move is extended to also support moving (instance) methods and variables. Please reopen the issue if I misunderstood. [1] http://wiki.netbeans.org/NewAndNoteworthyNB72_BigImg#Refactoring Oki, ralphbenjamin. When I mention "refactor command list" I mean the Refactor menu options. But what about the feature "Extract Class" ?I've seen in the new version 7.2 ( nightly build ) that the Move refactor option allows to move class members to an already created class. But, that would need to first create a new empty class and then move the members to it..... I think that if package and class drop down objects allow enter free text that would also allow to create a new class and move the members in that class. *** Bug 208165 has been marked as a duplicate of this bug. *** Thanks you for the clear description. I agree, it should be possible to move members (methods/fields) to a new Class in a possible new package. As we passed the feature freeze for 7.2 and this change requires some new precondition checking and different transformations, I'm not sure if this will be implemented in 7.2, but I will look into it. Will this new refactoring feature ( move members to a new empty class not existing yet ) be included in the 7.3 release ? |