zmuxuny opened a new pull request, #7173:
URL: https://github.com/apache/rocketmq-dashboard/pull/7173
### Which Issue(s) This PR Fixes
Fixes #7172.
### Brief Description
Make the backend-only contributor quick start runnable with the existing
local `dev` profile. H2 is test-scoped, so the command must also include
`-Dspring-boot.run.useTestClasspath=true`.
Document the backend/readiness URL, the in-memory database's non-persistence
and local-development scope, and the existing full-stack MySQL alternative.
Separate packaging (build only) from starting the backend. No dependencies,
packaging configuration or application behavior change.
AI assistance was used for investigation, editing and verification.
### How Did You Test This Change?
Base: `rocketmq-studio@127c47b06a268cc74224d5f34c56ec7c36ac0d55`, JDK
21.0.12.1 / Maven 3.9.12.
- Negative control: `spring-boot:run -Dspring-boot.run.profiles=dev`,
without the test-classpath property, exits 1 with `Cannot load driver class:
org.h2.Driver`.
- With both documented properties, Studio starts and `GET /readyz` returns
HTTP 200 and `{"status":"UP"}`. Smoke run: 11.92 seconds, peak combined process
RSS 494 MiB. The process was deliberately stopped after the successful
readiness probe (exit 143).
- Smoke isolation: cached official dependencies (`-o`), an isolated
environment, loopback port 18888, a unique in-memory H2 database and bounded
Maven/application heaps. No external MySQL database or RocketMQ cluster was
contacted. These isolation overrides do not change the documented
profile/classpath behavior.
- Both shell blocks pass `bash -n`; `git diff --check` passes. Verified the
runtime configuration/POM are unchanged from the smoke-tested base, and
independently reviewed the final documentation diff and result logs.
This validates startup/readiness for local H2 development, not persistence,
live broker operations or a packaged-JAR deployment. The existing H2 dependency
scope remains unchanged.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
