diff options
Diffstat (limited to 'sonar-core')
| -rw-r--r-- | sonar-core/src/main/resources/org/sonar/l10n/core.properties | 40 |
1 files changed, 40 insertions, 0 deletions
diff --git a/sonar-core/src/main/resources/org/sonar/l10n/core.properties b/sonar-core/src/main/resources/org/sonar/l10n/core.properties index aa7985abb6b..7126eeb049c 100644 --- a/sonar-core/src/main/resources/org/sonar/l10n/core.properties +++ b/sonar-core/src/main/resources/org/sonar/l10n/core.properties @@ -2685,3 +2685,43 @@ component_measures.legend.color_x=Color: {0} component_measures.legend.size_x=Size: {0} component_measures.x_of_y={0} of {1} component_measures.no_history=There is no historical data. + + +#------------------------------------------------------------------------------ +# +# ABOUT PAGE +# +#------------------------------------------------------------------------------ +about_page.projects_analyzed=Projects Analyzed +about_page.issues_found=Issues Found +about_page.read_more=Read More + +about_page.clean_code=Keep your code clean by fixing the leak +about_page.clean_code.text=By fixing new issues as they appear in code, you create and maintain a clean code base. Even on legacy projects, focusing on keeping new code clean will eventually yield a code base you can be proud of. + +about_page.leak_period=Understanding the Leak Period +about_page.leak_period.text=The leak metaphor and the default Quality Gate are based on the leak period - the recent period against which you're tracking issues. For some previous_version makes the most sense, for others the last 30 days is a good option. + +about_page.quality_model=SonarQube Quality Model +about_page.quality_model.bugs=Bugs track code that is demonstrably wrong or highly likely to yield unexpected behavior. +about_page.quality_model.vulnerabilities=Vulnerabilities are raised on code that is potentially vulnerable to exploitation by hackers. +about_page.quality_model.code_smells=Code Smells will confuse maintainers or give them pause. They are measured primarily in terms of the time they will take to fix. + +about_page.quality_gates=Understanding Quality Gates +about_page.quality_gates.text=Your project's quality gate is the set of conditions the project must meet before it can be released into production. The quality gate is designed to ensure that the next version's quality will be better than the last. + +about_page.standards=Conform to recognized standards +about_page.standards.text=SonarAnalyzers offer rules that support industry standards. Configure your Quality Profile with standard-related rules to ensure adherence. + +about_page.scanners.sonarqube=SonarQube Scanner +about_page.scanners.sonarqube.text=The SonarQube Scanner is a Java-based command-line tool that can analyze any language SonarQube supports. +about_page.scanners.msbuild=SonarQube Scanner for MSBuild +about_page.scanners.msbuild.text=Built in collaboration with Microsoft, the SonarQube Scanner for MSBuild is the recommended way to launch a SonarQube analysis on MSBuild projects and solutions. +about_page.scanners.maven=SonarQube Scanner for Maven +about_page.scanners.maven.text=Using the SonarQube Scanner for Maven is as simple as running mvn sonar:sonar on your Maven project. +about_page.scanners.gradle=SonarQube Scanner for Gradle +about_page.scanners.gradle.text=The SonarQube Scanner for Gradle provides an easy way to start analysis of a Gradle project. +about_page.scanners.jenkins=SonarQube Scanner for Jenkins +about_page.scanners.jenkins.text=The SonarQube Scanner for Jenkins lets you integrate analysis seamlessly into a job or a pipeline. +about_page.scanners.ant=SonarQube Scanner for Ant" +about_page.scanners.ant.text=The SonarQube Scanner for Ant lets you start an analysis directly from an Apache Ant script. |