Exclude Gradle samples from SCA analysis to avoid FPs

[leveretka]

No description provided.

[sonarqube-next]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0 Dependency risks
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[sonar-review-alpha]

Summary

This PR adds **/samples/** to SonarQube's Software Composition Analysis (SCA) exclusions in build.gradle.kts. This prevents the SCA scanner from analyzing Gradle sample/example code, which can generate false positives since samples are not part of the production codebase and often deliberately use simplified or outdated patterns for educational purposes.

What reviewers should know

Where to look: Single line change in build.gradle.kts (line 241) in the sonarqube configuration block, specifically the sonar.sca.exclusions property.

Context: The change aligns with the existing exclusion pattern for other non-production code (**/its/** for integration tests and **/kotlin-checks-test-sources/** for test sources). This is a common practice to focus SCA scanning on actual dependencies used in production.

What to verify: Confirm that **/samples/** correctly captures all sample/example directories in the Gradle project structure that should be excluded from SCA analysis.

---

• Generate Walkthrough
• Generate Diagram

🗣️ Give feedback

[sonarqube-next]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0 Dependency risks
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube