From 08a732be827dd05cf60d375d20e13694c75bdb0e Mon Sep 17 00:00:00 2001
From: leonardo-pilastri-sonarsource
 <115481625+leonardo-pilastri-sonarsource@users.noreply.github.com>
Date: Thu, 24 Oct 2024 16:40:30 +0200
Subject: [PATCH] [NO JIRA] Update targeted SQ and SonarJava plugin versions
 for CustomRules101 (#4841)

---
 docs/CUSTOM_RULES_101.md                             | 12 ++++++------
 .../{pom_SQ_9_9_LTS.xml => pom_SQ_10_6_LATEST.xml}   |  2 +-
 2 files changed, 7 insertions(+), 7 deletions(-)
 rename docs/java-custom-rules-example/{pom_SQ_9_9_LTS.xml => pom_SQ_10_6_LATEST.xml} (99%)

diff --git a/docs/CUSTOM_RULES_101.md b/docs/CUSTOM_RULES_101.md
index 48bd8540baf..3086d0e57c0 100644
--- a/docs/CUSTOM_RULES_101.md
+++ b/docs/CUSTOM_RULES_101.md
@@ -45,19 +45,19 @@ The root of a Maven project is a file named `pom.xml`.
 
 In our case, we have two of them:
 * `pom.xml`: use a snapshot version of the Java Analyzer
-* `pom_SQ_9_9_LTS.xml`: self-contained `pom` file, configured with dependencies matching SonarQube `9.9 LTS` requirements
+* `pom_SQ_10_6_LATEST.xml`: self-contained `pom` file, configured with dependencies matching SonarQube `10.6` requirements
 
 These two `pom`s correspond to different use cases, depending on which instance of SonarQube you will target with your custom-rules plugin. 
 
-In this tutorial, **we will only use the file named `pom_SQ_9_9_LTS.xml`**, as it is entirely independent of the build of the Java Analyzer, is self-contained, and will target the latest release of SonarQube.
+In this tutorial, **we will only use the file named `pom_SQ_10_6_LATEST.xml`**, as it is entirely independent of the build of the Java Analyzer, is self-contained, and will target the latest release of SonarQube.
 
 Let's start by building the custom-plugin template by using the following command:
 
 ```
-mvn clean install -f pom_SQ_9_9_LTS.xml
+mvn clean install -f pom_SQ_10_6_LATEST.xml
 ```
 
-Note that you can also decide to **delete** the original `pom.xml` file (**NOT RECOMMENDED**) and then rename `pom_SQ_9_9_LTS.xml` into `pom.xml`. 
+Note that you can also decide to **delete** the original `pom.xml` file (**NOT RECOMMENDED**) and then rename `pom_SQ_10_6_LATEST.xml` into `pom.xml`. 
 In this case, you would be able to use the very simple command:
 
 ```
@@ -66,13 +66,13 @@ mvn clean install
 
 Looking inside the `pom`, you will see that both SonarQube and the Java Analyzer versions are hard-coded. 
 This is because SonarSource's analyzers are directly embedded in the various SonarQube versions and are shipped together. 
-For instance, SonarQube `8.9` (previous LTS) is shipped with version `6.15.1.26025` of the Java Analyzer, while SonarQube `9.9` (LTS) is shipped with a much more recent version `7.16.0.30901` of the Java Analyzer. 
+For instance, SonarQube `8.9` (previous LTS) is shipped with version `6.15.1.26025` of the Java Analyzer, while the latest SonarQube `10.6` is shipped with a much more recent version `8.0.1.36337` of the Java Analyzer. 
 **These versions can not be changed**.
 
 ```xml
 <properties>
   <sonar.plugin.api.version>9.14.0.375</sonar.plugin.api.version>
-  <sonarjava.version>7.16.0.30901</sonarjava.version>
+  <sonarjava.version>8.0.1.36337</sonarjava.version>
   <!-- [...] -->
 </properties>
 ```
diff --git a/docs/java-custom-rules-example/pom_SQ_9_9_LTS.xml b/docs/java-custom-rules-example/pom_SQ_10_6_LATEST.xml
similarity index 99%
rename from docs/java-custom-rules-example/pom_SQ_9_9_LTS.xml
rename to docs/java-custom-rules-example/pom_SQ_10_6_LATEST.xml
index e9a4bc56a5c..822b46fdf46 100644
--- a/docs/java-custom-rules-example/pom_SQ_9_9_LTS.xml
+++ b/docs/java-custom-rules-example/pom_SQ_10_6_LATEST.xml
@@ -20,7 +20,7 @@
 
   <properties>
     <sonar.plugin.api.version>9.14.0.375</sonar.plugin.api.version>
-    <sonarjava.version>7.28.0.33738</sonarjava.version>
+    <sonarjava.version>8.0.1.36337</sonarjava.version>
     <!-- Don't forget to update this version of JaCoCo -->
     <jacoco.version>0.8.10</jacoco.version>
     <!-- Use UTF-8 for all resources -->