Replace pom.xml sonar.exclusions with @SuppressWarnings
Description
Environment
None
Potential Workaround
None
Checklist
hideTestRail: Results
Activity
Show:
Details
Assignee
UnassignedUnassignedReporter
Julian LadischJulian LadischLabels
NonePriority
TBDTestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Unassigned
UnassignedReporter

Labels
None
Priority
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created October 29, 2024 at 5:15 PM
Updated October 29, 2024 at 5:15 PM
pom.xml contains
<sonar.exclusions> src/main/java/org/folio/edge/EdgeInnReachApplication.java, src/main/java/org/folio/edge/client/**, src/main/java/org/folio/edge/config/**, src/main/java/org/folio/edge/domain/dto/** </sonar.exclusions>
However, some class files are not only setters and getters but also have code that goes beyond.
To get complete code analysis by Sonar the sonar.exclusions should be removed from pom.xml.
https://dev.folio.org/guides/code-analysis/#rule-customization explains what to use instead:
Use @SuppressWarnings with the list of specific warnings to suppress. That way we get all other warnings about potential issues in the code, including security warnings.