detekt's ./gradlew detektGenerateConfig task copies the default configuration file to the location specified by the config property.

detekt's reporting mechanism relies on implementations of ConsoleReport's. The cli module and therefore the Gradle plugin implement a bunch of this reports.

Today we are announcing the 1.0 release of detekt, a static code analysis tool for Kotlin. It operates on the abstract syntax tree provided by the Kotlin compiler and finds common programming flaws like unused or too complex constructs. Think of it as pmd or checkstyle but for Kotlin.

detekt uses bintray for releases and artifactory for snapshots.

Starting with RC15 the test-pattern is obsolete. This post shows how to leverage rule path excludes to achieve the same functionality.

A common use case of detekt users was to build upon the default config file and use a second config file to override some defaults.

When configuring detekt for your Gradle based project, you basically have two options:

• for each sub module a new gradle task should be created
• or one uber-task analyzes your whole project

As of today the website was launched!