Check if it is feasible to integrate ktlint as a rule set

[arturbosch]

pro:

• get fixes asap from ktlint
• more rules?

neg:

• different kotlinc versions
• two engines -> same work twice? -> shortcuts? invoke ktlint
• detekt additional formatting rules split

[arturbosch]

ktlint-standard-ruleset is not published to maven central as standalone artifact. Formatting rules were fixed and cleaned up for M11.

[shyiko]

@arturbosch fyi: http://search.maven.org/#search%7Cga%7C1%7Ca%3A%22ktlint-ruleset-standard%22

[arturbosch]

@shyiko nice thx. Did not find it on my own :)

[arturbosch]

KtLint uses the embeddable kotlin compiler, detekt not.
The new recommend way for formatting is to use the detektIdeaFormat task starting from M11.

[arturbosch]

Detekt now uses the embeddable compiler. A KtLint rule set is now feasible.

Idea:

• Create new rule set with wrappers around all KtLint rules
• Delete spacing, indentation and newline rules from detekt-formatting, just keep the extra rules which feature ast manipulation
• Users have now the choice between formatting with detektIdeaFormat and detektKtLintFormat