![]() ![]() Wildcards ( *, **, and ?) are not allowed. The entries in the list are simple paths.When explicitly set, both sonar.sources and sonar.tests take a comma-delimited list of directories or files. If the defaults are not suitable (for example, if you do have test code) you must set the parameters explicitly in the scanner invocation or in the appropriate configuration file (see Analysis parameters). By default, sonar.sources is set to the current working directory (the path.If you do explicitly set the parameters (for example in your pom.xml, in the case of Maven), this will override the automatically determined values. You do not have to explicitly set the parameters. NET, the sonar.sources and sonar.tests parameters are automatically determined based on information in your project configuration. If you are analyzing code using SonarScanner for Maven, SonarScanner for Gradle, or SonarScanner for. Test code does not count towards coverage (you don't have to test your test code)Īutomatic setting for Maven, Gradle, and.Test code does not count toward lines-of-code limits defined by your license.The two categories have different metrics.Different analysis rules are applied to the two categories.Test and non-test code are distinguished because Pattern matching with wildcards is not supported. set explicitly and both accept a comma-delimited list of paths.There are no UI settings for these parameters. either set automatically by your SonarScanner, set explicitly in the sonar-project.properties configuration file, or set on the command line that invokes the scanner.There are no global, server-level equivalents for these parameters. Files within the scope defined by these parameters will be analyzed unless excluded by further adjustments (exclusions, inclusions, etc.Files outside the scope defined by these parameters will not be analyzed at all. ![]() These parameters define the starting point for analysis scope adjustment: sonar.tests define the initial scope of analysis for test code in your project.sonar.sources define the initial scope of analysis for non-test code in your project.The initial scope of analysis is controlled by the following parameters: Other parameters must be set explicitly in the scanner invocation or in the appropriate configuration file as we describe in more detail below see the Analysis parameters page for more detail. Most of the properties that define your analysis scope can be defined in the SonarQube UI. To help narrow the focus, SonarQube gives you several options to precisely configure what will be analyzed and how. In such cases, it makes sense to skip some or all aspects of analysis for these files, thus removing noise and narrowing the focus to issues that really matter. For example, your project may contain generated code, source code from libraries, or intentionally duplicated code. There are many cases where you do not want to analyze every aspect of every source file in your project.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |