Did we just completely deprecate this article? https://medium.com/@acerezoluna/detekt-in-2018-5f9b898c12d8 (with the new gradle plugin re-write)

I’ll try to get things moving ASAP on the Novoda static analysis plugin side too

@Artur Bosch re: https://kotlinlang.slack.com/archives/C88E12QH4/p1536417537000100 This breaks the compatibility with projects running still on Gradle < 4.9. Have you considered to have a simple check there and use

create

for older version of Gradle?

Where are the contributing guidelines?

@pavlospt What is the error you are seeing?

Is there a migration guide to Rc09 that I missed to locate? I feel like searching through the PRs is totally wrong 😝 but I couldn't spot anything more obvious 🤣 can someone please confirm that I did not Search well enough?

Also is there no way to define 2 input dirs? previously i was doing:

input = "${rootProject.projectDir}/app/","${rootProject.projectDir}/modules/"

and it worked perfectly. But now it even though i am using

files()

it tries to do a weird concatenation between those paths and fails to run.

@Artur Bosch Should we go for another RC with this fix and some of the other fixes currently going on?

There are still way too many things that should be fixed I think

what is proper way to fix this?

is anyone having issues with RC8? did something changed when RC9 was released that could affect RC8?

detektCheck

is always crashing now, both locally and on CI. thread with more info

Did a bit of searching regarding this https://github.com/arturbosch/detekt/issues/1122 and i am seeing that even though any test we would write, will work correctly, when run with Gradle, it’s like it ignores the given value and executes the Rules with the default ones (e.g.:

ObjectPropertyNaming

->

privatePropertyPattern: '[A-Za-z][_A-Za-z0-9]*'

)

So I think that there is a broader issue here not just regarding

ObjectPropertyNaming

. I have tried changing almost every regex in the config and still get specific issues reported, which is wrong. That leads me to think that custom values are not picked up. I am worried that I might have broken something when added

LazyRegex

in the sense of a

Config

picking up custom values and instantiating those Regexes instantly, but later on these fields being mutated and essentially nullified, leading to

LazyRegex

picking up the default value when it’s time to execute for the first time. I am not sure if my thoughts are towards the correct direction, but it seems urgent enough to resolve this before going for v1.0.0.

This message was deleted.

With Gradle 4.9 I get error about using defaultProfile, is there documentation about new config in RC9 ?

can we modify rule?

Any ideas for my problem

> Task :detekt FAILED
Error: Could not find or load main class io.gitlab.arturbosch.detekt.cli.Main

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':detekt'.
> Process 'command 'C:\java\jdk1.8.0_131\bin\java.exe'' finished with non-zero exit value 1

Regarding https://github.com/arturbosch/detekt/issues/1143 is there a task that should run before executing

detekt

that would add

Main

class in classpath?

Since i understand there is availability by most of the contributors this weekend, should we try debugging the Rules patterns issue? I consider it one of the biggest before 1.0.0 😕

Basically you want package-private back? Seems going against the language…

@mairanosimone Unfortunately we do not publish the cli-all, feel free to open an issue for this

Anyone is using SonarLint plugin?

I've installed detekt plugin into IDEA, how to use it?

It would be great to have this part as a separate video to be able to replay some moments. While it's still possible with this one, rewinding is not quite precise

For tests in particular you can use `testPattern`: https://github.com/arturbosch/detekt/blob/master/detekt-cli/src/main/resources/default-detekt-config.yml#L4

hm... probably I was not writing it clearly enough. I don't want to suppress rules. I want to configure them differently for different src

Hello. I wonder, wihch is the correct way to resolve symbols? Get fully-qualified names and modifiers from call expressions? For example, this code relies on a fact that

java.lang.*

is implicitly imported and nothing interferes with

System

and `Runtime`: https://github.com/arturbosch/detekt/blob/249822360b88d57ea75a212bd6a811f3c7678d8e/detekt-rules/src/main/kotlin/io/gitlab/arturbosch/detekt/rules/bugs/ExplicitGarbageCollectionCall.kt#L49

is there a way to do a

try-catch

on the

detekt

task in order to continue the execution of other tasks?