-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Empty Project Dashboard in SQ7.7 & other issues with 3.0.0-beta-3 #44
Comments
No. Under the tab "Licenses" you can define which licenses are globally allowed in your organisation (e.g. Apache-2.0 and MIT). The default is to forbid all licenses - that's why you get those issues. The Maven Dependencies and Maven Licences tabs are here because Maven has no structured approach to licenses (npm does with SPDX). With Maven Dependencies setting you can map Maven groupId:artifactId matching regex to a license - e.g. "org.apache..*" -> Apache-2.0. With the Maven Licenses setting you can map the string in the license name of the pom.xml to a license - e.g. "Apache.2." -> Apache-2.0. |
Just tried that with 7.7 and I also get an empty dashboard. I will have a look into this. |
Seems like SonarQube changed some API semantics with 7.7 - measures on modules are not stored anymore. This breaks the storing of licenses/dependencies. Not a good practice do break APIs in minor versions See also SonarOpenCommunity/sonar-cxx#1695 |
This means the License Check project dashboard only works for single module projects in SQ 7.7+. |
- SQ 7.7 does not store measures on modules anymore. A workaround is implemented that stores the module's data in a static variable.
Hi @derkoe , If it re-enables support, do you see any chance to release a new "beta" for v3 including this commit so we can try it out (cause we already are seing the issue also on our end) |
#46 addresses this |
@derkoe Thanks for the quick help and bug fixing, we will test the release soon. |
- SQ 7.7 does not store measures on modules anymore. A workaround is implemented that stores the module's data in a static variable.
Hello,
we use SonarQube 7.7 and SonarQube License Check Plugin 3.0.0-beta-3 to check java licenses und dependencies. "License is not allowed", "Dependency has unknown license" is enabled.
The first problem is, that license check don't use the global license list settings and analyze only for the specific project license specification.
Do we have to update the "License Check - Maven Dependencies" for each license?
Because we only find the dependencies which are registered in "License Check - Maven Dependencies":
Project Dashboard Issue:
We always have an empty project dashboard, but for the same project we get dependencies issue (upperimage).
Thank for your support
The text was updated successfully, but these errors were encountered: