[ANN] CheckStyle IDEA 0.3

Good evening,

this is a bug-fix and optimisation release of a real-time CheckStyle scanner for IDEA 6.

Limitations:
- No properties can be editing in the CS configuration file.
- No static scanning is supported, only real-time at present (JetStyle fills this gap).
- No IDEA 5 support.

Source code and bug tracking are available at http://code.google.com/p/checkstyle-idea/

Cheers,
James

5 comments

Limitations:
- No properties can be editing in the CS configuration file.

IMHO this would be very important. Even more, some sort of assistance when editing this file would
be very helpful and would increase productivity:
completion for exceptions, links to files, context help(quick help) of the different checks.
I find my self all the time tuning the CS files and switching between config and the CS docs:
in many cases, after running CS, the result is not changing(not only) the source files, but
the CS config files too.

- No static scanning is supported, only real-time at present (JetStyle fills this gap).

IMHO such a function important and it should be in only one plug-in. These checks consume pretty
many resources, so there should be a possibility to turn them off with just a click (and run them
"on demand"(statically), but not from another plug-in like JetStyle), or turn them on again.

- No IDEA 5 support.

Considering that Demetra is already RC2, IMHO it makes no sense to invest in support of IDEA 5.

Ahmed.

0

Well, not all of us are going to upgrade to 6.0.

I will wait and see what comes about in 6.1, but right now, there is nothing in 6.0 that really grabs me as something I need or even want, based on my current work environment.

0

but right now, there is nothing in 6.0 that really grabs me as something I need or even want

But what about supporting JB :) ?
If everyone would follow your strategy there would be no 6.5 :).

So IMHO making plug-ins only 6.0 aware would "convince" more people to upgrade :).

Ahmed.

0

I will support JB when JB supports my needs. I already feel that because I am not mainstream(we don't even have a compatible version control system) and bleeding edge that my opinion is not really welcome/useful/whatever; and that is fine(I know that my needs are not necessarily a priority).

But I check out each EAP and if it excites me enough, I try it out and then go for the upgrade. Right now 6.0 is about as exciting to me as paying income taxes. I know that sounds insulting, and it is not meant to be, but it is how I feel.

I have no problem paying for a product that I like, use, and that I feel makes me productive. I have absolutely zero intrest in buying an upgrade that does not offer me value for my money. What you are suggesting is basically asking me to provide JB with a subsidy.

I truly hope that JB has great success with 6.0; I just won't be a part of it.

However, making plugins only 6.0 aware would convince me to look else where for my Java IDE needs.

0

Hi,

Sorry for the delay - I've been distracted by RealLife(tm) work.

The properties editing is my next priority - hopefully over the next couple of weeks. Editing of the CS config file is somewhat lower on the list (mostly as I don't use it) but certainly there. Static scanning is number two, as I am also vexed by having two plugins. It is, as always, merely a matter of time.

IDEA5 support should be fairly simple. AFAIK the only IDEA6 change I've used is the ability to mark errors as 'end of line'. The downside: it'll need either a seperate build, or some introspection (more likely).This one, I'm afraid, is probably the lowest priority at present, given the limited outcry :)

Thanks for your feedback - it is much appreciated!

Cheers,
James

0

Please sign in to leave a comment.