Some of the new/updated features that I found interesting include:

• Added option to export/import java formatting and indentation for all languages.
• Hint : A new warning that shows places that may cause NullPointException was added:
• Less memory needed to for Maven projects
• Profiler : CPU snapshots can now be compared the same way as memory snapshots.
• JPA : Stand alone jpql editor is added, you can run your jpql from ide directly instead of running your j2se jpa application

The key part is to add the atlassian SDK BIN directory to your path.

After the plugin project is initially created the Maven project comes up as “unloadable” in the NetBeans Projects window. Also, nodes like “Source Packages” do not show up.

Next, the official instructions here say that once you generate a new project, the Maven POM for that project needs to be modified as specified here : https://developer.atlassian.com/display/DOCS/Configuring+NetBeans+to+use+the+Atlassian+Plugin+SDK

It states “In order for NetBeans to pick up the necessary files to recognize this correctly you need to add the following to the project’s pom.xml” like this :

<repositories>
<repository>
<id>atlassian</id>
<name>Atlassian Repository</name>
<url></url>
<snapshots>
<enabled>true</enabled>
</snapshots>
<releases>
<enabled>true</enabled>
</releases>
</repository>
</repositories>

<pluginRepositories>
<pluginRepository>
<id>atlassian-public</id>
<url></url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
</pluginRepository>
</pluginRepositories>

I thought it was odd that the URL tag would be empty.

And in the properties section of the POM I added this :

<maven.local.repo>C:Atlassianatlassian-plugin-sdk-3.2repository</maven.local.repo>

However when both in NetBeans and via the atlas-mvn on command line I run the install goal to build the project it complains that the URL tag is empty and should not be.

Searching Atlassian’s Answers site, I found another person complaining of this issue : https://answers.atlassian.com/questions/22694/netbeans-complains-repositories-repository-atlassian-url-is-missing

There was no answer, so I just decided to enter an arbitrary value for the URL.

<url>foo</url>

Additionally I also realized when they said to use the Atlassian SDK repository in the <maven.local.repo> property they weren’t kidding. I had pointed NetBeans to use that version of Maven (via Tools > Options > Miscellaneous > Maven. I assumed this would work, but apparently not, thus requiring the <maven.local.repo> property to explicitly define the Atlassian-provided repository.

After making these changes the NetBeans project went from being “unloaded” to looking “normal” in the project window.

I could then clean and build it correctly directly in NetBeans without having to use the atlas-mvn on the command line.

There are some interesting planned features such as the ability to import/export projects a zip files, the Maven repositories are getting their own top-level node in the Services window instead of having a separate Maven Repository window, and a very interesting feature for allowing debugger breakpoints to conditionally enable/disable other breakpoints.

So far, the new debugger feature is most interesting and I’ll be testing it out in daily builds as soon as I get a chance.

See here : http://netbeans.org/community/releases/roadmap.html

Check it out here : http://blogs.oracle.com/geertjan/entry/open_source_framework_powers_latest

The patch includes bug fixes in modules for Java, Maven, C/C++, RCP Platform, HTML editor, Java Profiler GUI Builder, and more.

Detailed list of bugs can be found here : https://netbeans.org/bugzilla/buglist.cgi?status_whiteboard=701patch1&status_whiteboard_type=allwordssubstr

Get the patch info here : http://wiki.netbeans.org/NetBeans7.0PatchesInfo

Highlights include:

NetBeans Platform OSGi interoperability
- New Maven project archetypes available
- Easy import of OSGi bundles for use in Ant projects

Java EE
- Support for Contexts and Dependency Injection
- Simplified REST Web Services consumption in NetBeans RCP and Java client applications

Java Web Applications
- Initial support for Spring 3 framework
- Automatic import for Java classes and tag libraries in JSP code completion

PHP
- Zend framework support
- Enhanced code formatting options

Ruby
- Gems indexing

C/C++
- Support for Makefiles: Editor, navigator, run targets
- Virtual functions: Multiple hyperlinks, annotations

Java Editor
- Support for annotation processors
- Over 60 new hints added

Web Languages
- CSS refactoring and enhanced code completion

http://bits.netbeans.org/netbeans/6.9/m1/

View the entire list of patch fixes at the NetBeans Wiki : http://wiki.netbeans.org/NetBeans6.8PatchesInfo

You can read the new and noteworthy report here : http://wiki.netbeans.org/NewAndNoteworthyNB68

It includes features like a new embedded browser, Java EE6 basic support, and a variety of other improvements.

Download NetBeans 6.8 Milestone 1 here : http://bits.netbeans.org/netbeans/6.8/m1/

I was curious what the buzz around NetBeans this year since I’m currently at JavaOne so I thought I’d lookup and mention some of the most searched for (or interesting) terms that people have searched for and hit my site with between January 01, 2009 and today, June 4, 2009.

The session focused on a using Hudson overview, using HUdson in a distributed master/salve manner, and some of the newer use cases (such as with clouds and Kenai).

One of the cool items discussed was the Hudson Amazon EC2 plugin which allows you to automatically provision slaves on EC2 on demand. I haven’t heard it mentioned (yet), but I would imagine in the near future you will be able to do the same in Sun Cloud.

I didn’t hear much about Hudson and NetBeans or Hudson and Kenai. Maybe more later at their BOF.

The concept is to minimize the amount of time the user spends switching between the IDE and external web browser. Hopefully, it will work more like a WYSIWYG preview feature (think Dreamweaver style) and not a thick or heavy web browser. I know I’ve hoped for years to have a web preview option directly in NB. Hopefully this addresses some of that need.

You can follow the plans at the NetBeans Wiki at this location http://wiki.netbeans.org/EmbeddedBrowserPlan68.

In the Options window, select Miscellaneous. A new Java Debugger tab should be listed. Select it and you should see a several settings you can select. Click the Step Filters radio button. You should see a set of options, as pictured below.

The step filters let you specify code blocks to automatically skip while you are stepping through code. You can select a checkbox so that all constructors are skipped, which is a really nice feature for me. There usually isn’t any code of consequence in a constructor and it is annoying to step through when you are in a hurry (and not remembering you have a step over keyboard shortcut). You can also use the ‘filter classes matching’ section to add packages and specific classes to skip as well.

Currently several of the buttons in the Variable Formatters section didn’t seem to work at all, so it seems this feature is not completely ready. Hopefully when Milestone 2 is released next week everything will work as expected. In general I’m glad to see these settings added to the NetBeans debugger.

Kudos Travis.

Read about the second coming of NetBeans.

…Or you can copy and paste this URL in the link above does not work :

http://traviswalt3rs.blogspot.com/2009/02/second-coming-of-netbeans.html

I’m a frequent visitor to the New and Noteworthy page during the Milestone release process… the NB 7 Milestone 2 New & Noteworthy page now reads as : ‘This page has moved to NewAndNoteworthyMilestone2NB67′.

The new page is titled “New and Noteworthy NetBeans IDE 6.7 M2 “. Based on this evidence it seems apparent that NetBeans IDE 6.7 will be the next major release probably due out around JavaOne.

I’v seen more than a few bug reports where someone complains about performance in their project, but cannot send the NB team their code due to proprietary rights issues, intellectual property, export control, etc.

With this feature users can activate the diagnostic tool, perform some action or actions, and then deactivate the diagnostic tool. This will generate a standard NetBeans Profiler snapshot which can then be submitted to the NB team for analysis.

Read about the new feature at the New and Noteworthy page for NetBeans 7 Milestone 2.