SONARJAVA-6212 Document and rename sonarRules property for ruling tests (#5534)

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: asya-vorobeva

README.md

@@ -120,14 +120,18 @@ Failing to do so will produce inconsistencies with the expected results.
 
 From the `its/ruling` folder, launch the ruling tests:
 
-    mvn clean install -Pit-ruling -DcommunityEditionTestsOnly=true 
+    mvn clean install -Pit-ruling -DcommunityEditionTestsOnly=true
     # Alternatively
     JAVA_HOME=/my/local/java21/jdk/ mvn clean install -Pit-ruling -DcommunityEditionTestsOnly=true
 
-Note for internal contributors: in order to also execute the tests that depend on the SonarQube Server Enterprise Edition, use: 
+Note for internal contributors: in order to also execute the tests that depend on the SonarQube Server Enterprise Edition, use:
 
     mvn clean install -Pit-ruling
 
+To run the ruling tests for only a subset of rules, use the `sonarRules` property with a comma-separated list of rule keys:
+
+    mvn clean install -Pit-ruling -DsonarRules=S100,S101
+
 This test gives you the opportunity to examine the issues created by each rule and make sure they're what you expect. Any implemented rule is highly likely to raise issues on the multiple projects we use as ruling code base.
 
 * For a newly implemented rule, it means that a first build will most probably fail, caused by differences between expected results (without any values for the new rule) and the new results. You can inspect these new issues by searching for files named after your rule (`squid-SXXXX.json`) in the following folder:

its/ruling/pom.xml

@@ -114,6 +114,20 @@
         </plugins>
       </build>
     </profile>
+    <profile>
+      <id>only-jboss-project</id>
+      <build>
+        <plugins>
+          <plugin>
+            <groupId>org.apache.maven.plugins</groupId>
+            <artifactId>maven-surefire-plugin</artifactId>
+            <configuration>
+              <test>org.sonar.java.it.JavaRulingTest#jboss_ejb3_tutorial</test>
+            </configuration>
+          </plugin>
+        </plugins>
+      </build>
+    </profile>
     <profile>
       <id>only-sonarqube-project</id>
       <build>

its/ruling/src/test/java/org/sonar/java/it/JavaRulingTest.java

@@ -71,11 +71,17 @@ public class JavaRulingTest {
   private static final String INCREMENTAL_ANALYSIS_KEY = "sonar.java.skipUnchanged";
   private static final String SONAR_CACHING_ENABLED_KEY = "sonar.analysisCache.enabled";
 
-  // by default all rules are enabled, if you want to enable just a subset of rules you can specify the list of
-  // rule keys from the command line using "rules" property, i.e. mvn test -Drules=S100,S101
+  /**
+   * By default, all rules are enabled.
+   * If you want to enable just a subset of rules, you can specify the list of rule keys from the command line
+   * using the "sonarRules" property, i.e.
+   * <pre>{@code
+   * mvn test -DsonarRules=S100,S101
+   * }</pre>
+   */
   private static final ImmutableSet<String> SUBSET_OF_ENABLED_RULES = ImmutableSet.copyOf(
       Splitter.on(',').trimResults().omitEmptyStrings().splitToList(
-          System.getProperty("rules", "")
+          System.getProperty("sonarRules", "")
       )
   );