Seitenhistorie
...
<settings>[...] <profiles> [...] <profile> <id>sonar</id> <properties> <sonar.host.url>http://****:9000</sonar.host.url> <sonar.login>****</sonar.login> <sonar.password>****</sonar.password> <sonar.jdbc.username>****</sonar.jdbc.username> <sonar.jdbc.password>****</sonar.jdbc.password> </properties> </profile> </profiles> <!-- activeProfiles | List of profiles that are active for all builds. | --> <activeProfiles> <activeProfile>sonar</activeProfile> </activeProfiles></settings> |
Details auch im internen Wiki.
Wichtige Artikel und Hilfen zur Konfiguration
- Creating Code Coverage Reports
- Separating Code Coverage With Maven, Sonar and Jacoco
- Tracking Integration Test Coverage with Maven and SonarQube
- Sonar Unit and Integration Test Coverage with Maven
- Integration Testing with Maven
- Separating Integration and Unit Tests with Maven, Sonar, Failsafe, and JaCoCo
- Sonar: Code Coverage by Integration/Unit Tests
Weitere Artikel zur Konfiguration
- Configure jacoco agent
- sonar-maven-plugin database configuration
- Mvn lifecyles
- Dokumentation jacoco-maven-plugin
- Dokumentation maven-failsafe-plugin
- Dokumentation JaCoCo agent
- Dokumentation Sonar Plugin für Jenkins (auch hier)
- Code Coverage Tools für Sonar
- Sonar Code Coverage by Unit Tests for Java Project
- Sonar Code Coverage by Integration Tests for Java Project
- Sonar JaCoCo Plugin
- Sonar für Java
- Sonar FAQ
- Sonar Default Links
- Sonar: excluding files
- Sonar Jacoco excludes
Spezielle
ProblemProbleme mit Mvn (sub) Modulen
- Test Ergebnis Aggregation in Mvn
- Multi-module Konfiguration für Mvn/JaCoCo/SonarQube
- TestRunner and Mvn
Überblick
Inhalte