There are several issues with this plug-in.
I tested it with NB 6.9 (a daily build I downloaded just yesterday).
It causes a ClassNotFoundException on start-up.It overwrites the [ctrl]+[s] hot-key.Selecting a different Coding standard requires a restart of NetBeans IDE.
I guess this plugIn is not yet ready for prime time.
I tried to track down the ClassNotFound-issue. I found this CodeSniffer plug-in is not compatible with the current version (1.13.4) of the "scan on demand" plug-in.
Installing both will cause the ClassNotFoundException mentioned above and keep the IDE from loading further plug-ins, causing several problems.
So which version of NetBeans do you recommend ?
Tom mentioned on the blog that it mostly works with 6.8. Hopefully the amount of feedback to Mr Eberlei from the people on this blog will lead to improvements in the NBM.
Actually it works with NetBeans 6.8. However: the current functionality is limited.
It only scans 1 file at a time (no directories or projects). It doesn't scan automatically. You need to right-click the file and manually trigger it.
You need to open the task list and switch to "file mode" or violations won't show up. Also the violations just raise hints, but have no colors in the sidebar to get a quick overview. So you either must use the task list or manually scroll through the file while keeping your eyes open for hint icons.
For now it is nice for playing around a bit, but not really useful if you want to get productive.
this is very gooooood
Nice plugin, as others have pointed out, only works for nb 6.7. It would be great to be able to configure the standard to sniff. I've been tinkering with properties files under config/Preferences with no luck :-S Anyone?
I tried another implementation, based on the NteBeans task list api.
Module works in nb 6.7.1 - 6.9.1.
As I wrote in my last few posts, we are working on the new
branch to the...
This week I'm going to visit
PHP Conference that will
take place from the 28th to the 29th of October in Barcelona. I
will have there one...
Many of you were asking about editor support for changed
delimiters policy which happened in Smarty 3.0. I'm glad that I can