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.
I'm using intellij ide, please see www.intellij.com. This ide has got a very nice feature: * if you have a very long method definition, you can put an area of code into a new method. The method parameters, result are recognized automatical * other refactoring patterns are provided > > functionality This feature is very useful in development! It would be great to have this incorporated into netBeans. Thank you, -- markus.
Refactoring is becoming an industry standard feature of IDE's, witness IntelliJ, Eclipse, VAJ, and JBuilder all have either partner support for refactoring or the feature baked into their product. We must begin to offer this support to our users. I know MDR will help enable this, however we need to move with MDR and not wait for it. I believe MDR is defining for 4.0, then refactoring must make it's first appearance in 4.0 as well. Thanks, Dan
Complete source model needed for the refactoring to be reliable (not exactly for "extract method" pattern though, it may be approximated by less complex infrastructure as well). Consider moving to the java module for infrastructure development.
CCing Mila
Target milestone -> 3.3.1.
From my every day work the most interesting refactorings are (ordered by importance): - find/navigate some java element usage - rename package/class/member - move package/class - find/navigate package/class/method dependences - view/navigate class/interface hierarchy (extends, implements, is extended by, is implemented by) - find/navigate "too opened" classes/methods (for example, public instead private, and so on) - find/navigate not used classes/methods - find/navigate overridden methods declaration
My preferences: 1. references to a variable/method - very useful to "trace" code and navigate through it. 2. change a variable/method/package name - saves the guess work (compile-fix-compile-...) involved in such an action, when you realize the name you chose is misleading or has a typo. 3. find unused methods / variables. 4. change the package association of a class - helpful when you want to "clean up" the place.
I would like to have also some metrics data like: - how much is a package depending of another - how much package are depending of my package - my package is depending from another one ? If yes, which ones - is package dependency cyclic (package A use a class of package B that use a class of package A) - ...
Cleaning up before 4.0 planning
Target milestone was changed from not determined to TBD
How can I help? Where to subscribe? I tried e-mailing to dev@java.netbeans.org without any success yet. Why Is your newsgroup not on NNTP? That would be nice. Please post an ad: "Help for Refactoring team needed" to nbdev/nbusers, you'll get responses, at least from the users about what refactorings to implement first. Create a detailed plan, see http://www.joelonsoftware.com/articles/fog0000000245.html for many reasons why detailed planning forewards is good.
*** This issue has been marked as a duplicate of 41954 ***
Sorry, about the last action, I wanted to mark another bug as a duplicate...
The basic refactoring support is implemented. Please create separate issues for particular refactoring features you are still missing and vote for these issues if you feel strongly about them. Thanks.