From b017c732b07fd8a33080f646da4fa5a3c3218319 Mon Sep 17 00:00:00 2001 From: cynthiabethea <108268296+cynthiabethea@users.noreply.github.com> Date: Mon, 3 Oct 2022 13:44:00 +0100 Subject: [PATCH] DOC-141 updating to the correct required version of Gradle (#6761) --- .../src/pages/analysis/scan/sonarscanner-for-gradle.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/server/sonar-docs/src/pages/analysis/scan/sonarscanner-for-gradle.md b/server/sonar-docs/src/pages/analysis/scan/sonarscanner-for-gradle.md index df67881f741..73d736c159e 100644 --- a/server/sonar-docs/src/pages/analysis/scan/sonarscanner-for-gradle.md +++ b/server/sonar-docs/src/pages/analysis/scan/sonarscanner-for-gradle.md @@ -16,7 +16,7 @@ The SonarScanner for Gradle provides an easy way to start SonarQube analysis of The ability to execute the SonarQube analysis via a regular Gradle task makes it available anywhere Gradle is available (developer build, CI server, etc.), without the need to manually download, setup, and maintain a SonarQube Runner installation. The Gradle build already has much of the information needed for SonarQube to successfully analyze a project. By preconfiguring the analysis based on that information, the need for manual configuration is reduced significantly. ## Prerequisites -* Gradle versions 3+ +* Gradle versions 5+ * At least the minimal version of Java supported by your SonarQube server is in use Bytecode created by javac compilation is required for Java analysis, including Android projects. -- 2.39.5