Enhance run.sh to support extra Maven properties per version

support-version.list now supports format: version[,key=value[,key=value...]]
Extra properties are passed as -D flags to Maven. This allows different
framework versions to use different dependency versions (e.g., Spring Boot).

Example: 2.7.14,spring.boot.version=2.7.18

Use this to extend Spring Kafka test coverage:
- 2.3.x scenario: 2.3-2.6 (default Spring Boot 2.3), 2.7-2.9 (Spring Boot 2.7)
- 3.x scenario: 3.0 (Spring Boot 3.0), 3.1-3.3 (matching Spring Boot 3.1-3.3)

Author: wu-sheng

CHANGES.md

@@ -16,6 +16,7 @@ Release Notes.
 * Extend Undertow plugin to support Undertow 2.1.x, 2.2.x, 2.3.x.
 * Extend GraphQL plugin to support graphql-java 18 -> 24 (20+ requires JDK 17).
 * Extend Spring Kafka plugin to support Spring Kafka 2.4 -> 2.9 and 3.0 -> 3.3.
+* Enhance test/plugin/run.sh to support extra Maven properties per version in support-version.list (format: version,key=value).
 
 All issues and pull requests are [here](https://github.com/apache/skywalking/milestone/249?closed=1)
 

test/plugin/run.sh

@@ -231,8 +231,21 @@ ls "${jacoco_home}"/jacocoagent.jar || curl -Lso "${jacoco_home}"/jacocoagent.ja
 ls "${jacoco_home}"/jacococli.jar || curl -Lso "${jacoco_home}"/jacococli.jar https://repo1.maven.org/maven2/org/jacoco/org.jacoco.cli/${jacoco_version}/org.jacoco.cli-${jacoco_version}-nodeps.jar
 
 supported_versions=`grep -v -E "^$|^#" ${supported_version_file}`
-for version in ${supported_versions}
+for version_line in ${supported_versions}
 do
+    # Support format: version[,key=value[,key=value...]]
+    # e.g., "2.7.14,spring.boot.version=2.7.19"
+    # First token is test.framework.version, rest are extra Maven properties.
+    version=$(echo "${version_line}" | cut -d',' -f1)
+    extra_props=""
+    remaining=$(echo "${version_line}" | cut -d',' -f2- -s)
+    if [[ -n "${remaining}" ]]; then
+        IFS=',' read -ra props <<< "${remaining}"
+        for prop in "${props[@]}"; do
+            extra_props="${extra_props} -D${prop}"
+        done
+    fi
+
     testcase_name="${scenario_name}-${version}"
 
     # testcase working directory, there are logs, data and packages.
@@ -245,7 +258,7 @@ do
     cp ./config/expectedData.yaml ${case_work_base}/data
 
     # echo "build ${testcase_name}"
-    ${mvnw} -q --batch-mode clean package -Dtest.framework.version=${version} && \
+    ${mvnw} -q --batch-mode clean package -Dtest.framework.version=${version} ${extra_props} && \
         mv ./target/${scenario_name}.* ${case_work_base}
 
     java -jar \

test/plugin/scenarios/spring-kafka-2.3.x-scenario/support-version.list

@@ -14,10 +14,13 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 
+# Format: spring-kafka-version[,key=value] — extra properties passed to Maven.
+# spring-kafka 2.7+ requires Spring Framework 5.3+ (ApplicationStartup class),
+# so those versions override spring.boot.version to match.
 2.3.10.RELEASE
 2.4.13.RELEASE
 2.5.17.RELEASE
 2.6.13
-2.7.14
-2.8.11
-2.9.13
+2.7.14,spring.boot.version=2.7.18
+2.8.11,spring.boot.version=2.7.18
+2.9.13,spring.boot.version=2.7.18

test/plugin/scenarios/spring-kafka-3.x-scenario/support-version.list

@@ -15,6 +15,8 @@
 # limitations under the License.
 
 # Spring Kafka 3.x requires Spring Boot 3.x / JDK 17+
-# This scenario uses Spring Boot 3.0.13, so only 3.0.x is compatible.
-# 3.1+ requires Spring Boot 3.1+ (Spring Framework 6.1).
+# 3.1+ requires Spring Framework 6.1, so override spring.boot.version.
 3.0.17
+3.1.4,spring.boot.version=3.1.12
+3.2.10,spring.boot.version=3.2.12
+3.3.7,spring.boot.version=3.3.8