At https://github.com/markiewb/idea-create-from-template-plugin you will find an IDEA plugin, which shows you some APIs in action:
- How to add an action to the context menu
- How to create a context sensitive action. The action is only activated for Maven-based module nodes.
- How to add an option panel – see
projectConfigurable in the
- How to register and use a project based settings service. See
projectService in the
- How to register a file template. See
Do you use a Nightly-/Dev-Build of NetBeans or even a release candidate of 8.2 within the NetCAT-program and you are missing some of your favorite plugins?
First there is no plugin center for Dev-Builds. Also most plugins from the 8.1 plugin center are not verified for the new 8.2 build yet – including my plugins.
Nevertheless in the meantime you can still use the plugins and give the plugin authors feedback of the compatiblity to 8.2. Some plugins won’t work, because of using non-public API, but that is the point to find out!
How to do that?
Tools|Plugins|Settings add the plugin center URL for 8.1  and then at
Tools|Plugins|Available Plugins click at “
Check for Newest”
If you are interested in testing non-verified plugins see the article 
As you already know, I provide a NetBeans plugin to format your Java code using the Eclipse formatter engine. Currently the 4.5.x engine is embedded.
But there were several complaints that this version does not format the same way as it does using the previous version. There is a reason for that: The Eclipse formatter has been changed in an incompatible way . Other formatter plugins like the one for Intellj Idea are also affected 
But here is a good news for all the brave NetBeans Java developers, who are still in such an environment of 4.4.x Eclipse installations: Now I provide a 4.4-fork of my own plugin. It has the same features and issues like the 4.5 plugin, but it uses the other engine and the plugin has been updated to be installed side by side to the original plugin.
The plugin is already available from the update center from within your NetBeans IDE. Or you can download it from the plugin page  or from github .
In the last days and weeks I was busy enhancing the Eclipse Code Formatter plugin. The main focus was the support of the Workspace Mechanic  configuration file to be in compliance with my coworkers.
Offtopic: Workspace Mechanic is a plugin for Eclipse IDE itsself, which makes sure that shared Eclipse configurations are applied to your local installation. Have a look. It’s useful in a team of several developers.
Workspace Mechnanic also synchronizes the configuration of the formatter. Luckily its file format is quite simple and thus supportable by my plugin. So next to the standard XML-formatter file you can now use Workspace Mechanic EPF-files too.
I also added some other useful features you may like. That was the reason, why the release of this version took so long. For example now the “format on save”-action can optionally format the changed lines only. You can use formatter settings from
.settings, you can configure the Java source level and the line feed. And the download size of the plugin has been massively decreased.
The full changelog can be found at 
In a few days it will be available as an update from within your NetBeans IDE. If you are curious and you don’t want to wait for it, then you can install it manually from  or .
Feel free to file issues and even better, provide pull-requests! We see us at NetBeans Day Germany in Munich on the 31st of March 2016. Get your ticket at !
 Workspace Mechanic
 NetBeans Day Germany in Munich
When you develop a NetBeans module using the Maven-approach, every time you “Clean & build” your module the userdir, which is placed in the target-directory by default, will be deleted. “Clean & Build” is necessary if you’re altering the layer.xml directly or indirectly by using annotations like @ActionReferences. So after that you have to reconfigure your target platform again, f.e. by opening the same projects and files to restore the previous state. That is annoying, but easy to fix.
Add a profile to your settings.xml
After that you can choose the profile from the profile-dropdown or in the context-menu of the project node.
This way the configured userdir is used for running/debugging your NetBeans module. It won’t get deleted automatically.
Advanced tips: Of course you can also configure an absolute path or even make the profile default by applying activeByDefault
As you might already read in the NetBeans weekly newsletter, I also updated the Code outline plugin this week. This plugin shows the document content in miniature at the right gutter of the editor. Some of you know that feature from “Sublime Text” editor. This implementation is a bit simpler.
A highly requested feature was the support of dark themes. And now it’s supported. The basic text color and the background color of the editor is used. You can also check the “Darkening” option, which lowers the brightness of the code outside of the viewport. Try it!
Other improvements: You can define the font-size, but I propose to use single-digit font-sizes. The display quality has also been improved by applying anti-aliasing.
The plugin is already available from the plugin dialog within your NetBeans IDE 8+. Or it can by downloaded manually from the plugin page at  and github .
Please file issues/enhancement at . I also like to merge your pull-requests for further improvements! Happy coding with NetBeans!
Within the last days I had time to update the formatter plugin, which allows you to format java source code using the formatter engine of Eclipse JDT. In a few days it will be available as an update from within your NetBeans IDE. If you are curious and you don’t want to wait for it, then you can install it manually from  or .
The major change is that the jars for the formatter engine are now taken from Eclipse 4.5.1 Mars.1.
As you might know, the plugin already provided support for @format:off before – if it was enabled in the formatter file. But now it provides some code templates, so that it easier to use. See the documentation at 
Feel free to file issues and provide pull-requests to see your enhancement in the next release! Happy coding and a happy new year!