Gradle-Plugin: Are Tasks with TypeResolution not using the same compiler options as configured for the project? #3629
mervyn-mccreight
started this conversation in
General
Replies: 2 comments 2 replies
-
Good point. It's a pity that we can't move a discussion to an issue because I think that this is an issue. I'm not sure if we could do something about it but we could, at least, write something in our documentation to how to solve this problem. Probably this issue is gone with https://github.com/detekt/detekt-compiler-plugin |
Beta Was this translation helpful? Give feedback.
2 replies
-
It's possible to create a new issue and delete the discussion afterwards. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi folks :-)
When using tasks like e.g.
detektMain
I figured out that it displays a lot of compiler warnings.E.g. I have opted-in kotlin.time by passing a compiler-flag like the following in my
build.gradle.kts
so I do not have to opt-in it all over the source-code.
detektMain
does not seem to pick this up and is constantly complaining about it with messages like this:which does not look very nice. Is the validation even working for these files?
The task itself "passes" if no source-file violates any rules, but in my perception it is misleading that the terminal is full of red text containing the term "error" if everything is fine.
Is it intended that detekt is not using the same compiler flag as the project uses to check against rules using type-resolution?
Or am I missing some configuration so that detekt does this?
Beta Was this translation helpful? Give feedback.
All reactions