Today I like to blog about some new plugins from another very productive plugin author. All of them were created by junichi11, who created more than 15 plugins, which all are freely available at the NetBeans plugin portal. Many of them are PHP-related, so if you are a PHP developer you are certainly using one of his plugins already.
a) Github issues plugin
This plugin integrates issues from your github repositories into the tasks view of NetBeans. From within NB you can view, edit and create issues. And much more…
BTW if you are using Backlog for tracking your issues, then you can also use https://github.com/junichi11/netbeans-backlog-plugin
b) Color preview plugin
This plugin shows color for hexadecimal encoded colors (f.e. #FF0045) in the left sidebar of the editor. This feature is not new to IDEs, but it is now finally available for NetBeans. Enable this feature via “View->Show Colors” and the colors in CSS files will be visualized. It is configurable and thus not limited to CSS.
The plugins are signed and this way they can be installed directly from your IDE (Tools->Plugins->Available Plugins). You can also download them from their github pages or from http://plugins.netbeans.org and install them manually
Do not hesitate to post feedback or file issues at the respective github pages of the plugins. junichi11 is a friendly one and very responsive! Thank you for the good work junichi11!
I am sure you already noticed that there was an update to the JRebel for NetBeans plugin.
Regarding to http://plugins.netbeans.org/plugin/22254/jrebel-netbeans-plugin version 6.1.0 contains the following changes:
- Added support for launching Grails applications with JRebel.
- Added JRebel startup tab to JRebel Configuration. Added setup instructions for three startup scenarios (IDE, CLI and remoting).
- Added support for enabling/disabling JRebel agent per server and standalone project via the JRebel Configuration. Removed the global on/off JRebel toolbar button.
- Fixed an issue with setting VPN IPs for remoting/cloud.
One highly visible and very useful new feature is the configuration wizard in the options. This way you can configure your app server/application to use JRebel without any external documenation. Good Job ZT!
When you develop a NetBeans platform application sometimes you like to refer to existing resource files like images.
Therefor you have to hard-code the path into your sources in a string literal. Normally you would notice a wrong path at runtime because of a FileNotFoundException – not very professional.
But wait! Use the
org.netbeans.api.annotations.common.StaticResource-annotation from the Common Annotations module (/
org.netbeans.api:org-netbeans-api-annotations-common) instead. Backed by an annotation processor NetBeans will check whether the path is correct at compile-time. This is pretty cool.
What do you get? NetBeans shows missing resources in the editor, in the “Action Items”-view and even the build will fail.
Today I released the version 1.3.1 of the “Open File At Cursor” plugin. There are some new minor features, which proofed to be useful for myself and may be also useful for other Java developers.
Updates in 1.3.1:
- [Issue 18]: NPE when pressing CTRL in the diff dialog
Updates in 1.3.0:
- [Feature 12]: Support fully qualified classnames
- [Feature 14]: Search for classname in dependencies too (only works for dependencies with sources)
- [Feature 10]: Find files in same package but different source root
- [Issue 16]: Make the hyperlinking faster / use less IO
You can download it from http://plugins.netbeans.org/plugin/52349/open-file-at-cursor. The plugin is currently scheduled for verification for NB 8.0 and NB 7.4 and will be available from the plugin dialog within your NetBeans IDE within the next days (after verification).
As always please file issues and enhancements at https://github.com/markiewb/nb-resource-hyperlink-at-cursor/issues . Pull request are also appreciated. Thank you
In large Maven-based projects consisting of several high-level frameworks sooner or later there will come the time, when there are two versions of the same dependency in the classpath. For example: two versions of the same logging framework.
One approach to solve such ambiguity is to choose one of the versions (which is hopefully compatible) and to use it as an explicit dependency. Nevertheless other dependencies may still introduce other version as transitive dependencies. This may be caused by different groupIds, which will result in two similar named jar.
Once you got a candidate you can start finding all the possible sources of the dependency.
mvn dependency:tree -Dverbose -Dincludes=log4j:log4j
will show you the dependency-tree, but only the relevant excerpt. Using this information you can now add your exclusions to the affected pom.xml files.
Exclusions are configured via the exclusion-tag , which excludes specific transitive dependencies. For example:
By the way: Java IDEs can help you doing this.
After that you can make sure the faulty dependency versions will never ever be included again. This can be done using the maven-enforcer-plugin 
<!-- exclude all versions lower than 1.2.17-->
Breakpoints will now be preserved – that is the major change. Unfortunately linebreakpoints are not supported, but better than nothing and better than the previous state. I also updated the embedded eclipse formatter engine to 4.4.
Here the full list of changes.
- [Feature 47]: Preserve Class/Method/Field breakpoints (experimental, can be disabled in options)
- [Bugfix 53]: Fixed: Do not remove linebreakpoint, if line is not included in selection
- [Bugfix 52]: Fixed: Cannot assign shortcut for “Format with Eclipse Formatter” action
- [Task 46]: Update to use eclipse formatter libs from eclipse 4.4
- [Task 48]: Support only NetBeans 7.4 and above
- [Task 49]: Add donation button
- [Task 50]: Add link to github/homepage
Downlad it from the plugin center http://plugins.netbeans.org/plugin/50877/ or install it directly from your IDE (Tools/Plugins).
You can file issues at https://github.com/markiewb/eclipsecodeformatter_for_netbeans/issues
I am looking forward for your feedback.
Recently a guitar-playing developer asked me if I can help him to build his favorite guitar tab program TuxGuitar from the sources. So here is a small step-by-step guide using NetBeans.
- Checkout the sources via the NetBeans SVN Client (Team->Subversion->Checkout…) from
(At http://sourceforge.net/p/tuxguitar/code/HEAD/tree/trunk/ you will find the SCM URL)
- Open the maven project at
- Right click on the project, choose “
Clean and Build” and wait for the assembly to finish.
- After that in
trunk\build-scripts\tuxguitar-windows-x86\target\tuxguitar-1.3-SNAPSHOT-windows-x86 there is a executable version of TuxGuitar
- Start TuxGuitar *g*
The setup was easy because NetBeans provides a SVN Client and a Maven installation out-of-the-box. Tested with NetBeans 8.0.1 (running using JDK8) and Windows 7 64bit.
If you use a x64-Windows and a x64-JDK TuxGuitar won’t run because of native 32bit-SWT libraries. You will see the following exception.
Exception in thread "main" java.lang.UnsatisfiedLinkError: Cannot load 32-bit SWT libraries on 64-bit JVM
Solution: In the
tuxguitar.bat set the path to the java executable of a 32 bit JDK.
SET JAVA="C:/Program Files (x86)/Java/jre7/bin/java"