-
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
Help for run License Check for NPM modules #69
Comments
When the sonar scanner (via Maven or the standalone version) detects a package.json in the root of your module it is scanned automatically. The dependency files (pom.xml, package.json) are not uploaded to SonarQube |
Thank you very much for your answer. We had a bug in the Sonar Qube Task configuration (Azure Devops) and had to explicitly set the ProjectBaseDir as property and for the NPM project the wrong Java Quality profile was used. It would be very good if, as already suggested, there were still separate rules for it. We are scanning a pure NPM project without Java/Maven dependencies, the following exception is thrown:
How can you bypass the error or exclude the required Maven analysis infos? |
Hello,
we already use License Check for Java from bug #44 and now want to use LicenseCheck for our NPM projects as well.
How is Sonar Qube configured to have all the necessary information for LicenseCheck and run the analysis?
Currently, no package.json is uploaded to the code files with Sonar Qube.
Thank you very much for your help.
The text was updated successfully, but these errors were encountered: