Revision as of 11:21, 26 July 2011 by Ignition (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)


NetBeans for Eclipse Users

This page is devoted entirely to features in Eclipse for Eclipse users switching to or using NetBeans. Information on this page should be in 3 categories:

  1. ) A feature matrix which shows functionality in Eclipse and NetBeans and how to access it in Eclipse and also NetBeans. We will rely on users of Eclipse to help us get this information and category 2 is where they can add their features they would like to know about or have added to NetBeans.
  2. ) A list of features which do not exist in NetBeans or which have not yet been figured out and put into the matrix from category 1.
  3. ) Other documentation in this Wiki which is related to Eclipse. This keeps them from having to look in so many places.

Eclipse and NetBeans Feature Matrix

Feature Eclipse NetBeans
Editor Features
Code Suggestions: Implement all abstract methods Add an interface to a class. A light bulb appears which allows the user to implement the abstract methods Works basically the same. An annotation will appear at the class name. Click where the annotation is. The light bulb appears. If the interface has not yet been imported and the FQN was not used the first suggestion will be to import the class. Once imported the suggestion will be to implement all the abstract methods.
Go to super implementation of a method An up arrow appears next to an overridden method. Clicking on the up arrow takes you to the super implementation. An up arrow appears next to an overridden method. In NB 5.5 and earlier clicking the up arrow has no effect. In NB 6.0 on it will take you to the super implementation. In all versions there is a context menu option Go To/Super Implementation which is linked by default to CTRL-B. The Navigator window's inheritance view can also be used for the same purpose but is hard to use the keyboard to operate.
Reload code during debug Code is reloaded during a debugging session if a class if changed and saved. There are some restrictions (like one can't change the method signature, add new methods, etc) In NetBeans you have to manually select Run->Apply code changes which will compile the currently open file in the editor and will reload the code in the debugger, subject to the same restrictions as Eclipse (method signature, etc)
Show a list of breakpoints from everywhere, and let me enable/disable specific ones without having to open the specific source file and find the line. Use Window/Open Perspective/Debug Use Window/Debugging/Breakpoints
Ability to hover over a class or method and have the javadoc for that class or method be displayed. You can open the Javadoc window, using Window/Show View/Others/Java/@ Javadoc No context menu available, but you can put the cursor on a line and press F4 or click the run to cursor icon in the toolbar

Eclipse Features (which may or may not be in NetBeans)

  • Add arbitrary source folder to project and/or debugging sources window for debugging which is not part of the actual project and will not be compiled
  • To show the javadoc of a class or a method either open the javadoc window (Window->Other->Javadoc) or a small trick: press CTRL+Space before the last character of the class/method.
  • To copy the full qualified name of a class (or even the full path of a file) by selecting the class name, right clicking, and choosing "Copy qualified name".

Other Documentation

Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo