Over 60 New Hints in the NetBeans IDE 6.9 Java Editor
The picture on the left shows the list of Java hint categories in NetBeans IDE 6.8, while on the right you see the list that will be part of NetBeans IDE 6.9:
As can be seen, not only has the list been alphabetized, but it has also been extended. I'm told there are over 60 new hints in the Java editor.
Note: All the texts in the categories are currently being reviewed, so all the labels above and below in this article will more than likely be tweaked prior to the final release of NetBeans IDE 6.9.
In case you're not aware what a "hint" is in NetBeans terminology (elsewhere known as "code inspections"), take a look at the screenshot below:
Surely the above, i.e. the usage of "System.out" is a sign of immature code. Hence, the hint suggests that you remove that statement. And when you click the lighbulb or press Enter, the statement is removed for you. Other code immaturity issues that will be handled in 6.9 are as follows:
And what about the "Performance" category in the new list? Here it is:
The documentation of what each of these items means is contained within the same dialog where you specify whether you want to use the hint or not:
Similarly, if you're wondering what "Obsolete Collection" in the "Code Maturity Issues" means, your answer is provided in the description of the hint:
And maybe you're wondering what the "Probable Bugs" category contains? Here it is:
And here's the "Assignment Issues" and "Bitwise Operations" categories:
Clearly NetBeans IDE 6.9 will be a goldmine for those who have been hoping for improvements in the Java editor area. For other enhancements in this area, please feel free to take a look at http://wiki.netbeans.org/NewAndNoteWorthy.





Comments
Ryan De Laplante replied on Sun, 2010/02/28 - 11:18am
These are welcome additions to what I think is already an excellent code editor. Some of these features remind me of what is available in PMD and FindBugs.
What I'd like to see is some investment in the SQE plugin which integrates PMD, FindBugs and CheckStyle into the code editor. I've tried it several times before and although it has improved significantly, I didn't think it felt ready. For example, when I decided having all of its features turned on slowed the editor down too much I tried disabling it but could not. I had to uninstall the plugin. It would also be nice if it made use of any PMD, FindBugs and CheckStyle configuration in Maven POM.
Reto Fabbri replied on Sun, 2010/02/28 - 11:56am
in response to:
Ryan De Laplante
Ryan De Laplante replied on Sun, 2010/02/28 - 12:44pm
in response to:
Reto Fabbri
We have Sonar installed at work. IntelliJ IDEA users have static code analysis built into the code editor so you get live feedback as you are typing. That's what I want to see in NetBeans and SQE aims to do just that
Geertjan Wielenga replied on Mon, 2010/03/01 - 3:56am
Sun Oracle replied on Wed, 2010/03/03 - 12:20pm
Awesome! Will the automatic reminders to avoid System.out be backported to 6.5?
I'm reluctant to upgrade any more, because 6.7 and 6.8 both leave random badges, take long scanning breaks, and can't keep up with my typing. This is my fault, I know; I'm running an old Athlon 64 X2 3800 with only 2 GB. Oddly though, I CAN type quickly in some other applications.
David Yarc replied on Thu, 2010/03/11 - 7:02pm
Matt Coleman replied on Fri, 2012/10/19 - 1:23am
Wow...60 new hits..this is exciting for Java users such as me
present for graphic designer