-
-
Notifications
You must be signed in to change notification settings - Fork 52
Detekt start analyze java and kotlin file in build/.gradle dir #145
Comments
@cortinico could you see this problem? |
Don't you mind sending a PR? |
I try, but I've never done this before in open source projects. |
No problem. Just try and if you get stuck let us know :) |
I create commit, but can't push on branch feature/145. I need correct permission?
|
You would need to create a fork first. And push your branch to your fork. |
Well, I think this is a very strange way, but I did it) |
Hi, what i must do, for merge PR? Because of this problem, we have many builds which throw OutOfMemory:metaspce. I would like to quickly deliver these changes to our infrastructure |
There seems to be failures on the CI. |
|
Yup now it's merged 👍 |
Can You explain, how i can add my custom release to my sonar instance? Some instruction? or guide? |
The instructions are basically the one listed here https://github.com/detekt/sonar-kotlin#building-from-source |
sonarqube.gradle.plugin - 3.3
Sonar server Community Edition Version 8.5.1 (build 38104)
gradle - 7.1.1
run in gitlab 14.1.0
I think that problem in function:
then evaluate inputPaths field
I have one-module project. If i apply sonar plugin, baseDir = rootDir. In root dir gradle create very many cache/tmp file. This base dir map to property pathsToAnalyze in function createCompilerConfiguration . Because of this javaFiles contains all file(include cache/tmp file)
Full log for this situation
I suggest change
this improvement allows you to configure detekt only for sources file
The text was updated successfully, but these errors were encountered: