Globalyzer Dashboard FAQ
Mapping of Rule Set Rules to Dashboard Rules
Rules in Globalyzer Rule Sets have both an associated category, and an associated priority. Issue detection categories include:
- Embedded Strings
- Locale Sensitive Methods
- General Patterns
- Static File References.
Rules for all categories may have priorities of 1-5. Additionally, Embedded String detections may be set to priority 0, which indicates a concatenation issue.
The Lingoport Dashboard's rules include the same categories as above. However, the priorities only go from 1-3. The mapping between these priorities is as follows:
| Globalyzer Priority | Dashboard Priority |
|---|---|
| 0 (Embedded String) | Concatenation |
| 1 | 1 |
| 2 | 2 |
| 3-5 | 3 |
Determining the number of issues created/fixed in a given time period
It is possible to view detailed information about the number of issues created or fixed during a given time period. This can be done using the Dashboard's inbuilt api. See the REST API#Issue_tracking section on this wiki for more information.
Limit files uploaded to the Dashboard to be files scanned by Globalyzer
A project is made up of one or more scans, and each scan processes source files with configured file extensions. The issues found via scanning are reflected on the Dashboard. By default, all files found within the project's base path are uploaded to the Dashboard, even ones that aren't scanned. To limit what is uploaded, you can configure the sonar.inclusions property in the sonar-project.properties file for your project.
If your project contains a Java scan, JavaScript scan, and HTML scan, then you would set your sonar-project.properties to include the extensions for all three languages.
For example, if your project contained only a Java scan, you would add the following line to your sonar-project.properties file:
sonar.inclusions=**/*.java,**/*.jsp,**/*.jspf,**/*.jspx
If your project contained a Java scan and a JavaScript scan, you would add the following line to your sonar-project.properties file:
sonar.inclusions=**/*.as,**/*.asax,**/*.ascx,**/*.asp,**/*.aspx,**/*.cshtml,**/*.ejs,**/*.htm,**/*.html,**/*.java,**/*.js,**/*.jsp,**/*.jspf,**/*.jspx,**/*.mas,**/*.mi,**/*.php,**/*.xhtml
Below is the list of languages and the sonar.inclusions property set to their default file extensions. It is important to note that source file extensions are configurable in rule sets, so if extensions are added or removed in the rule set, they should be added or removed in the sonar-project.properties; that is, they should match.
| Rule Set Language | sonar.inclusions= |
|---|---|
| Actionscript | **/*.as,**/*.mxml |
| C# | **/*.asax,**/*.ascx,**/*.ashx,**/*.aspx,**/*.cs,**/*.cshtml |
| C++ | **/*.c,**/*.cc,**/*.cpp,**/*.cxx,**/*.h,**/*.hpp,**/*.hxx,**/*.qml |
| Delphi | **/*.dfm,**/*.dpk,**/*.dpr,**/*.pas |
| HTML | **/*.asa,**/*.asax,**/*.ascx,**/*.cxx,**/*.ashx,**/*.asmx,**/*.asp,**/*.aspx,**/*.axd,**/*.cshtml,**/*.ejs,**/*.htm,**/*.html,**/*.inc,**/*.jsp,**/*.jspf,**/*.jspx,**/*.mas,**/*.master,**/*.mi,**/*.php,**/*.shtml,**/*.skin,**/*.svg,**/*.tag,**/*.vm,**/*.xhtml |
| Java | **/*.java,**/*.jsp,**/*.jspf,**/*.jspx |
| JavaScript | **/*.as,**/*.asax,**/*.ascx,**/*.asp,**/*.aspx,**/*.cshtml,**/*.ejs,**/*.htm,**/*.html,**/*.js,**/*.jsp,**/*.jspf,**/*.jspx,**/*.mas,**/*.mi,**/*.php,**/*.xhtml |
| Objective-C | **/*.h,**/*.m,**/*.mm |
| Perl | **/*.mas,**/*.mi,**/*.perl,**/*.pl,**/*.plx,**/*.pm |
| PHP | **/*.inc,**/*.php |
| SQL | **/*.sqc,**/*.sql,**/*.sqx |
| Swift2 | **/*.swift |
| VB | **/*.ascx,**/*.asp,**/*.aspx,**/*.bas,**/*.cls,**/*.ctl,**/*.dob,**/*.dsr,**/*.frm,**/*.pag,**/*.vb |
| VBscript | **/*.asax,**/*.ascx,**/*.asp,**/*.aspx,**/*.htm,**/*.html,**/*.vbs,**/*.xhtml |
| XML | **/*.jspx,**/*.mxml,**/*.storyboard,**/*.tld,**/*.vcxproj,**/*.wsdd,**/*.wsdl,**/*.xaml,**/*.xhtml,**/*.xib,**/*.xlf,**/*.xml,**/*.xsd,**/*.xsl,**/*.xslt,**/*.xul |
