Wednesday, December 31, 2008

SQE - New Year's Eve and 2009

Again - after a long quiet period here some news from SQE - the last one for 2008.

Still, the actual main goal of SQE is to provide a stable release for NetBeans 6.5 .

Here is a list what we have already achieved and what will be part of the next binary drop. It will take a few more days before we can upload it - to allow us to ensure everything is working as expected after the major rewrite we did during Devoxx 2008.

Bug fixes:
  • Fixes for numerous NPE, CCE
  • use NetBeans 6.5 features where possible (Option Panel...)
New features
  • codedefect history is now working
  • further UI enhancements
    • windowgroup for codedefect results
    • move codedefect history to control center
  • select checkstyle.xml to use
  • even better sorting capability for PMD and Checkstyle results
  • Update FindBugs to 1.3.6
  • Update PMD to 4.2.4
Upcoming (new things or things already planned)
  • Support for configuration of FindBugs and PMD based on Maven pom's
  • Refresh on save/compile (especially useful for tasklist)
  • NetBeans 7.0?
  • PMD 5.0
Any other ideas, comments, wishes? Just leave your comment here or send an e-mail to the user list at

... and don't forget we will be going full OpenSource at in 2009 (promised) using Maven as build tool. This possibly allows us to provide different binary drops (e.g. PMD 4.x / PMD 5.x series) and many other exciting things.

Happy New Year 2009 to all of you - and see you in 2009!


hantsy said...

Many features is lack in SQE.
I need an alternative product to CodePro( for eclipse).
Firstly , the checkstyle basic configuration is need.There are some different checkstyle module in Plugin Portal, why not work together to make this feature better.
Checkstyle rule definition is need for adv users. The same problem in PMD.
Secondly , give an option in project properties panel to user determine wheather use it . By default, do not load the modules ,for example, the icon in editor toolbar.
The last, do not forgot providing fix Suggestion via Code Completion for fatal defect.

Sven said...

Better support for configuration is on the roadmap although a lot of the developers already have working configurations from the continous build process. The main focus is to support this first.

The configuration if a tool is enabled can be done in Quality Control Center (can be found in Window Menu), but you are right - would be nice to have this in project properties dialog as well (maybe I can squeeze this in for the next binary drop)

Anonymous said...

Wow you did a rewrite? I'm looking forward to trying it out and for a stable release. This is one area NetBeans has lagged behind other IDEs (until SQE is fully released).

I think there should be code-coverage built in as well that integrates with the editor. i think there might be a code coverage plugin for java already, for 6.0? I haven't tried it yet. It seems like something that should integrate with SQE somehow.

Maybe a visual editor (like the visual web.xml editor) for checkstyle, findbugs and pmd config files?

Sven said...

Codecoverage support using Cobertura is currently under consideration - although I am not sure if it will be part of SQE or just another module on the Plugin Portal. If you would like such a feature to be part of NetBeans standard builds for Java create an issue or vote for one ;-)

Better configuration support is on the roadmap, but we want to get the basics correct first. So maybe after the first real OpenSource release.

christian said...

So when do you finally plan to upload the mentioned SQE version that can handle checkstyle config files?

daveh said...

There are buttons in the Editor Toolbar to toggle the display of the warnings. I don't normally have the Editor Toolbar visible. Would it be possible to add menu items that do the same thing?