Help with `Fail to resolve 159 file(s)`

[Colin]

Ah I think I know what’s going on.

If you’re using the Scanner for Gradle, exclusions or not, the backend folder probably isn’t being indexed properly. You need to add it as a proper sourceset, at which point the files will get indexed, and you can attach external issues. If this seems a bit convoluted, we know, and our first stop was the Maven scanner to improve the default behavior.

You can confirm right now if the backend folder is being indexed by just checking the Code tab of your project (following an analysis where you’ve removed the backend folder from your exclusions).

All of this mostly unnecessary if you aren’t actually using any JVM-based languages, and can switch to the SonarScanner CLI.

@Colin

Are there proper JVM based languages in this project (Java, Kotlin)? Just want to make sure there’s a valid reason for using the SonarScanner for Gradle as opposed to the SonarScanner CLI.