Improving the example using the same approach for load testing

.cursor/rules/112-java-maven-documentation.mdc

@@ -28,7 +28,10 @@ When creating a README-DEV.md file for a Maven project, include ONLY the followi
 ./mvnw dependency:resolve
 
 ./mvnw clean validate -U
+./mvnw buildplan:list-plugin
 ./mvnw buildplan:list-phase
+./mvnw help:all-profiles
+./mvnw help:active-profiles
 ./mvnw license:third-party-report
 
 # Clean the project

.cursor/rules/templates/java-checklist-template.md

@@ -48,7 +48,7 @@ Use the following process to improve the java development in some areas if requi
 
 | Activity | Description | Prompt | Notes |
 |----------|------|--------|-------|
-| [151-java-performance-jmeter](.cursor/rules/151-java-performance-jmeter.mdc) | Run a peformance test with Jmeter | `Add JMeter performance testing to this project using @151-java-performance-jmeter.mdc` | You could ask the model to create a JMeter based on a RestController/Resource |
+| [151-java-performance-jmeter](.cursor/rules/151-java-performance-jmeter.mdc) | Run a peformance test with Jmeter | `Add JMeter performance testing to this project using @151-java-performance-jmeter.mdc` | You could ask the model to create a JMeter based on a RestController/Resource. Example: `Can you create a Jmeter file based on the restcontroller in the path src/test/resources/jmeter/load-test.jmx?` |
 
 ### Step 7: Profiling (Async profiler)
 

.gitattributes

@@ -0,0 +1 @@
+*.java linguist-detectable=true

.github/workflows/maven.yaml

@@ -18,17 +18,6 @@ jobs:
         run: cd examples/maven-demo && ./mvnw --batch-mode --no-transfer-progress verify --file pom.xml
       - name: Spring Boot build
         run: cd examples/spring-boot-demo/implementation && ./mvnw --batch-mode --no-transfer-progress verify -Pjacoco --file pom.xml
-      - name: Spring Boot startup and API test
-        run: |
-          cd examples/spring-boot-demo/implementation
-
-          # Make sure the test script is executable
-          chmod +x test-api.sh
-
-          # Run the comprehensive API test script
-          # Uses 'local' profile and default port 8080
-          # Set CLEANUP_LOGS=true to remove log files after execution
-          CLEANUP_LOGS=true ./test-api.sh local 8080
       - name: AWS Lambda build
         run: cd examples/aws-lambda-hello-world && ./mvnw --batch-mode --no-transfer-progress package --file pom.xml
       - name: Azure Function build

README.md

@@ -61,7 +61,7 @@ Using the Cursor rules is straightforward: simply `drag and drop` the cursor rul
 
 | Activity | Description | Prompt | Notes |
 |----------|------|--------|-------|
-| [151-java-performance-jmeter](.cursor/rules/151-java-performance-jmeter.mdc) | Run a peformance test with Jmeter | `Add JMeter performance testing to this project using @151-java-performance-jmeter.mdc` | You could ask the model to create a JMeter based on a RestController/Resource |
+| [151-java-performance-jmeter](.cursor/rules/151-java-performance-jmeter.mdc) | Run a peformance test with Jmeter | `Add JMeter performance testing to this project using @151-java-performance-jmeter.mdc` | You could ask the model to create a JMeter based on a RestController/Resource. Example: `Can you create a Jmeter file based on the restcontroller in the path src/test/resources/jmeter/load-test.jmx?` |
 
 ### Profiling rules (Async profiler)