Details
Description
The scope of this ticket is the following:
- be able to analyze a project that has a mix of several languages (for the moment, 1 file = 1 language at most)
- be able to configure the relevant quality profiles for each language
- be able to create issues on each file based on the rules activated on the quality profile for the language of the file
- be able to compute measures on each file based on its language
Starting with 4.2, projects won't be "tagged" with languages any more. As a consequence, this means that:
- the language information won't be displayed any more in the "Description" widget
- language-based measure filters won't be work any more (and the "Language" criterium will be removed in the Measures Page)
What's not in the scope of this ticket:
- be able to give the distribution of metrics per language (for instance: the number of lines of code per language)
Attachments
Issue Links
- depends upon
-
SONAR-3024 Allow files and directories with same relative path from source/test dirs
-
- Closed
-
- is depended upon by
-
SONAR-4828 Make it possible to display full distribution of files/classes/functions by complexity
-
- Closed
-
- is duplicated by
-
SONAR-419 Analysis of projects containing both java and sql technologies
-
- Closed
-
- is related to
-
SONAR-2602 Make it possible to analyse a multi-modules project whose some modules have different language (sonar.language)
-
- Closed
-
-
SONAR-5130 Show distribution of LOC by language
-
- Closed
-
-
SONARJAVA-438 Compatibility with SonarQube 4.2
-
- Closed
-
-
SONAR-2322 Filter unit tests files listed in surefire reports
-
- Closed
-
-
SONAR-5118 Add new criteria in the "Issues" page to search for issues by language
-
- Closed
-