6.5 RC1 out of the oven.. time to get ready for 7.0!
By Erno Mononen on Oct 21, 2008
NetBeans 6.5 RC1 was just released, meaning that the final release is well on its way. Although not all work is done for 6.5, we've had some time to work on the next release already. We haven't gotten to any major features yet, but some little enhancements here and there. I'll list here are a couple of things implemented so far, starting with one that is not really going to directly help our users in their daily work, but should make reporting bugs a bit more convenient: Ruby IDE Logging options: In the past, when somebody reported an issue, we often had to ask the reporter to turn on detailed logging in order to be able to track down the problem. To do this, he/she had to edit the netbeans.conf file and restart the IDE, as described here. We always felt that this is a bit stupid and might frustrate the reporter (for a reason), so I finally got around to implement an option for this in the IDE. So the next time you report an issue and we ask for a log file with detailed logging turned on, it is enough to check the check boxes above, no restart is needed. For normal use it is however best to keep detailed logging off (for performance reasons). Folks using Shoulda should be happy to hear that NetBeans now has at least some rudimentary support for it: I didn't know the plugin myself, learned about it thanks to the user who reported an issue about it. It seems interesting and since it builds on top of Test/Unit, basic support for it was straightforward to add (in fact some things worked already before fixing the issue). Some things are still missing, such as jump to source for Shoulda test methods, and I'm sure there are things that I haven't yet discovered. Another testing related enhancement are the new context menu actions in the test runner: For individual methods: And for suites: I think this is kinda nice, but unfortunately it didn't make it into 6.5. Of course, you can still run individual test methods in 6.5 (as in 6.1 already) by hitting Alt-Shift-F6 (or Alt-Shift-F5 for debugging) when you're within a test method in the editor. Also, some may have noticed from the above screenshots that failed test methods node in the test runner display now have the error message inlined, thanks to Tor's patch. I think that's about it for now -- Martin has also been working on new things; I'm sure he will blog about those at some point. As mentioned, these enhancements are only available in trunk (i.e. the next release) nightly builds, downloadable here, and of course in continous builds.