[ES-2914] build action failure in sun bird plugin due to inclusion/exclusion str…#192
[ES-2914] build action failure in sun bird plugin due to inclusion/exclusion str…#192Md-Humair-KK wants to merge 1 commit intomosip:developfrom
Conversation
…ategies Signed-off-by: Md-Humair-KK <mdhumair.kankudti@gmail.com>
WalkthroughAdds SonarQube integration to the Maven build configuration by introducing a sonar profile with plugin properties and code analysis exclusion rules. This enables automated code quality scanning during the verify phase when the profile is activated. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment Tip CodeRabbit can suggest fixes for GitHub Check annotations.Configure the |
There was a problem hiding this comment.
🧹 Nitpick comments (1)
sunbird-rc-plugin/pom.xml (1)
350-354: Decouple analysis exclusions from coverage exclusions.At Line 353,
sonar.exclusionsis bound to${sonar.coverage.exclusions}. That makes the dedicatedsonar.exclusionsdeclared at Line 85 effectively unused and couples two strategies that are usually tuned independently.Suggested cleanup
<properties> <sonar.sources>.</sonar.sources> <sonar.inclusions>src/main/java/**,src/main/resources/**</sonar.inclusions> - <sonar.exclusions>${sonar.coverage.exclusions}</sonar.exclusions> <sonar.host.url>https://sonarcloud.io</sonar.host.url> </properties>🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@sunbird-rc-plugin/pom.xml` around lines 350 - 354, The sonar.exclusions property is incorrectly set to ${sonar.coverage.exclusions}, coupling general analysis exclusions with coverage-specific exclusions; change the sonar.exclusions declaration so it uses its own explicit value or references the intended property (remove the link to sonar.coverage.exclusions) so the separate sonar.exclusions defined elsewhere is honored—update the <properties> block where sonar.exclusions is assigned and ensure sonar.coverage.exclusions remains a distinct property.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@sunbird-rc-plugin/pom.xml`:
- Around line 350-354: The sonar.exclusions property is incorrectly set to
${sonar.coverage.exclusions}, coupling general analysis exclusions with
coverage-specific exclusions; change the sonar.exclusions declaration so it uses
its own explicit value or references the intended property (remove the link to
sonar.coverage.exclusions) so the separate sonar.exclusions defined elsewhere is
honored—update the <properties> block where sonar.exclusions is assigned and
ensure sonar.coverage.exclusions remains a distinct property.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: 53f6ff21-34b8-47b1-a4a0-3f241a062716
📒 Files selected for processing (1)
sunbird-rc-plugin/pom.xml
…ategies
Summary by CodeRabbit