Search Results for "java software .jar"

No configuration, which means no decisions to make, nothing to argue about and no special files to manage. While this might sound extreme, keep in mind that ktlint tries to capture (reflect) official code style from kotlinlang.org and Android Kotlin Style Guide (+ we respect your .editorconfig and support additional ruleset|s). Built-in formatter. So that you wouldn't have to fix all style violations by hand. Customizable output. plain (+ plain?group_by_file), JSON, HTML and check style...

Zally, a minimalistic, simple-to-use API linter. Its standard configuration will check your APIs against the rules defined in Zalando’s RESTful Guidelines, but anyone can use it out of the box. Zally’s easy-to-use CLI uses the server in the background so that you can check your API on the spot. It also features an intuitive Web UI that shows implemented rules and lints external files and (with its online editor) API definitions.

Eclint is a plugin for Eclipse, primarily for use with the Eclipse CDT. It provides a framework for using external C/C++ lint tools within Eclipse.

JCSC is a highly configurable checking tool for your Java source code. It checks the compliance to a defineable coding standard like naming conventions and code structure. Also signs of bad coding, potential bugs are found. JCSC is inspired by lint.

Transmogrify is a code analysis/manipulation tool for Java whose current focus is refactoring. There are also the beginnings of a lint tool and a code twiddler (makes changes to code that aren't refactorings).