| User: outside | Rating: 9 | 2009-07-02 00:37:46 |
| |
It is very usefull to find out and eliminate the coding standard violations and other errors in the beginning itself.
|
| User: outside | Rating: 10 | 2009-07-01 13:04:48 |
| |
Really cool.
|
| User: Anonymous | Rating: 10 | 2009-06-15 18:10:52 |
| |
Fabulous ! Nothing to tell more :)
|
| User: outside | Rating: 10 | 2009-06-10 17:15:15 |
| |
I just started using the plugin.
I was thinking it would be great if the plugin could suggest and make changes in the formatter (code style). For example now I am getting this message:
method def throws at indentation level 12 not at correct indentation, 8
Checkstyle could suggest to automatically change the formatter configuration to enforce this.
|
| User: outside | Rating: 9 | 2009-06-09 11:10:02 |
| |
it would be good to be able to configure checkstyle globally and then to be able to switch it off per source directory
|
| User: outside | Rating: 9 | 2009-06-08 10:43:52 |
| |
The checkstyle plugin is very nice however there are a few small improvements that might make it more usable:
- the "Multiple String Literals" rule needs a way of ignoring BigDecimal constructor literals
- it would be nice to have an "all" summary view to show all the rules that you have selected (similar to the way you can see all the rules added under each "Known module" when you select it
- the Configuration UI could use an "expand all" button instead of expanding each "Known Module" section individually
- the Configuration UI should be resizable for the bottom "Description" area since descriptions often max out this space
- it would be nice to have the classic selection box output for the "Known modules" area so one knows if none, some, or all of the items under that module are selected. Similar to installers which have the (emtpy box = none, shaded box = some, checked box = all) idiom
- this may be a bit esoteric but in our company we have a set of Eclipse Java "Clean Up" and "Formatter" rules. We are looking to translate these rules into a Checkstyle configuration so that we can enforce the rules at build time. It would be nice to have a Checkstyle to Eclipse Formattter/CleanUp converter so that we wouldn't have to go rule by rule to conver the two. The Eclipse definition is nice becuase it translates well into the "Save Actions" which autoformat your code upon saving the file so developers don't have to think about it
|
| User: outside | Rating: 7 | 2009-06-03 13:08:04 |
| |
Love checkstyle, love the tool, but IT NEEDS TO AUTO-REFRESH.
It's a pain to clear, and regenerate the messages after addressing some.
|
| User: outside | Rating: 7 | 2009-06-01 01:27:16 |
| |
too complicated
|
| User: outside | Rating: 10 | 2009-05-27 22:09:54 |
| |
excellent!!
|
| User: outside | Rating: 10 | 2009-05-25 17:12:06 |
| |
great ass plugin
|
