DependencyCheck reports uploaded to SonarQube has the "suppress" button disabled
perostman opened this issue · 10 comments
Describe the bug
When uploading the dependency check report to, when accessing the report, the "suppress" button in the report is disabled
To Reproduce
Steps to reproduce the behavior:
- Sonarqube 10.0.0 with Dependency-Check plugin 4.0.0
- Produce a dependencycheck report and upload it to SonarQube
- Access the dependency check report in SonarQube
- Observe that the "Suppress" buttons are disabled
Current behavior
The "Suppress" buttons are disabled.
Expected behavior
The "Suppress" buttons are enabled.
Screenshots
Error:
Expected:
Versions (please complete the following information):
- dependency-check 8.2.1
- sonarqube 10.0.0
- dependency-check-sonar-plugin 4.0.0
Additional context
Add any other context about the problem here.
This could be a problem of the IFrame.
See if the following PR fixes your problem.
#765
@Reamer I am not sure how I would apply this patch - could you please point me to how to do this?
- check out the plugin on your local computer
- Apply the patch
- Compile the plugin
- Add the plugin to your SonarQube
Tried (compiled using mvn clean package -Dlicense.skip since I got errors on license check).
Getting compilation error;
[INFO] [webpack-cli] ModuleNotFoundError: Module not found: Error: Can't resolve 'sonar-helpers' in '/home/postman/github/depcheck/dependency-check-sonar-plugin/sonar-dependency-check-plugin/src/main/js/report_page/components'
Maybe something is missing from the instructions on how to setup for compilation?
I think you have not applied the patch correctly. Do you have a GitHub repo where I can look over it?
Hi,
same issue here...
I've built the plugin using current master and changes from #765.
Now, the dependency check report opens nicely in a new browser tab, but the "suppress" button still does not work.
The error message in the browser console is
Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). report_page.js:1:8126
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days.
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days.
This issue was closed because it has been stalled for 14 days with no activity.