Code cleanup in netbeans

Question

Is there something similar to the Eclipse cleanup rules (Preferences > Java > Code Style > Clean Up) in NetBeans?

The cleanup rules in eclipse will allow you to clean things up like organizing imports, removing unnecessary casts, adding missing override annotations etc.

Also can you do that on a whole set of classes/packages instead of individual classes?

Solution 1

Refactor > Inspect and Transform

Is there something similar to the Eclipse cleanup rules ((Preferences > Java > Code Style > Clean Up) in NetBeans?

In NetBeans 8.0, the powerful batch tool is Refactor > Inspect and Transform. See the tutorial page, Refactoring with Inspect and Transform in the NetBeans IDE Java Editor.

Individual tools are also available:

• Fixing imports
  For a single file, namespace, or project (depending on what's selected in Project window or has the focus): Source > Organize Imports (to sort and remove unused imports) or Source > Fix Imports (to sort, remove unused imports, and add missing imports). Or during every save: Tools > Options > Editor > On Save > Organize Imports.

• Removal of trailing spaces
  For a single file (place the carret in the code file): Source > Remove Trailing Spaces. Or during every save: Tools > Options > Editor > On Save > Remove Trailing Whitespace.

• Code Format
  For a single file, namespace, or project: Source > Format. (Customize the rules in Tools > Editor > Formatting). There is also a plugin called Jindent you can install (I have not used it myself). Or during every save: Tools > Options > Editor > On Save > Reformat.

By default, Netbeans will display hint icons next to problematic lines of code and in the scrollbar, allowing you to perform an automatic fix if desired. These can be configured via Tools > Options > Editor > Hints. Netbeans can search all problems in the project using Source > Inspect. Or, to reiterate, many of these problems can be batch fixed with Refactor > Inspect and Transform.

Solution 2

The equivalent of Eclipse's "Code Cleanup" in NetBeans is "Format". It's under Source > Format, and the keyboard shortcut is Alt+Shift+F (on Windows). Unfortunately, unlike Eclipse, it doesn't seem like this can be configured in NetBeans.

Solution 3

NetBeans 7.2 has Inspect & Transform refactoring to do this:

http://netbeans.org/kb/docs/java/editor-inspect-transform.html

Solution 4

For Netbeans use Ctrl+Shift+I to remove unused import from the file.

Solution 5

tools -> options -> Tab "Editor" -> Tab "Hints" -> select Java (talking about) in JComboBox

and then you'd see yellow ocean ..., great and quick from ver 6.9

View more solutions

Comments

[Ben Hocking]

I've added a bounty, and I'm hoping someone will know of a plugin or some other manner of doing this. I really miss my Eclipse clean up options.

[Daniel]

As answered below, there are ways to clean up certain aspects of a single source code file. I doubt that NetBeans would introduce a "fix all of my files" feature because changes to each file could be dependent upon changes to the previous file(s), so NetBeans would need to prioritize which files to fix first and compile files as it fixes them.

[Ben Hocking]

@Daniel: The nature of these "fixes" are usually minor: stripping whitespace, adding @Override tags, organizing imports, removing unnecessary casts, removing unused variables, etc. I.e., they're fixes that should have no functional impact, and hence it shouldn't matter what order they're applied in.

[ssakl]

Version 6.5 displays a little light bulb icon inline, which if you click on will suggest fixes (such as add Override annotation, remove unused imports, etc.).

[Martin]

Eclipse has two separate functions: Code-Format and Code-Cleanup. NetBeans Source-Format is only the equivalent from Code-Format - and even there it is not as powerful. In no way it can be compared to Eclipse Code-Cleanup. Don't know how you got to up votes for this faulty answer.

[Ravi Parekh]

In netbeans for Code-formate alt + shift + f and imports ctrl + shift + i. and this works for individual file. For all files there is no functionality.

[Ravi Parekh]

and even with format-code u cannot set column width upto what you want your line of code extend. i mean if u have 200 column width netbean will set as a single line until you manually Enter.

[Ben Hocking]

That notifies you about possible problems in your code (and is very useful), but what we're looking for is an option to automatically fix issues such as these, either with a single command to fix all problems in a file (or better yet a set of files), or automatically on save. Eclipse has both of these options. I use it frequently to automatically fill in missing @Override statements, to organize imports, and to eliminate trailing whitespace.

[mKorbel]

@Ben Hocking :-) I don't want to something ... and automatically, because in (majories) some cases there are more than one options coming from the Hints, and you can select "better" from Items, how some automat can choose and knows better option ..., loook like that I started FlameWar ...

[Ben Hocking]

@mKorbel: Which items are fixed automatically are not the same as the warnings, and as you point out you wouldn't want them to be. Typically, the "automatic" things are trivial things, such as organizing imports and eliminating trailing whitespace, as well as slightly bigger things such as adding missing @Override (which could break code if other people compile with Java 1.5). The point is, it's separately configurable from your hints and you can do as much or as little as you like. The "code cleanup on save" is also more dangerous than doing it on request.

[mKorbel]

@Ben Hocking but I've never drawn a distinction between whether wrote better or more comfortable in Eclipse or Netbeans

[Ben Hocking]

There are plenty of distinctions that can be made, but users of both IDEs would benefit from learning tricks from the other IDE. For example, I really love how easy it is to use cobertura from Netbeans. Although it's possible to do it from Eclipse as well, it requires many more steps. There are also more significant differences, of course.

[mKorbel]

@Ben Hocking yes, that was anser to your Bounty, agreed my coworker three or more times switch between Intellij IDEA and Eclipse, for same reason/depends of plugins supports

[mKorbel]

@Ben Hocking I think that you already answered by yourself your bounty, each of IDE's is designated for different areas of users(Teams Coding in Eclipse), approach, plugins, custom Compilator, support and sponsors too, then to your Bounty (maybe) isn't possible to find out rellevant answer

[Ben Hocking]

It might not be, but I'm hoping that someone is aware of a plugin that implements this behavior.

[Jérôme Verstrynge]

Cool. Thanks. Over time, NetBeans tends to include new tools and utilities accelerating and facilitating coding into core distributions. Good plugins are often integrated into core. New plugins are offered at each release. I believe fully automated functionalities will be made available sooner or later...

[TheLQ]

As an update to this answer, recursive formatting is implemented in Netbeans natively (yay!). Just select "Source Packages" in the package viewer, then go to Source > Format. The only thing it doesn't do is cleanup imports

[Aleksandr Dubinsky]

@RaviParekh The options in Tools > Options > Editor > Formatting > Line Wrap are there, but I see that it's not taking effect. Bug?

[Basil Bourque]

The question is about doing this for many classes/files rather than just one.

[shareef]

Is there a shortcut for inspect and transform and how to set it

[Pere]

It took me a bit to realize that, after selecting Inspect and Transform (in my 8.2 Netbeans it appears directly as an option after right-clicking over the project; no Refactor previous menu) I had to choose Use: Configuration: Organize Imports (click on the Manage... button if it doesn't appear directly in the dropdown. There are dozens of "inspections" available there to apply to your code!