adityamparikh opened a new pull request, #230: URL: https://github.com/apache/solr-mcp/pull/230
## Summary - `dev-docs/DEVELOPMENT.md` told developers to run `docker compose up -d` before `./gradlew bootRun`, then a few lines later contradicted itself by saying Spring Boot Docker Compose starts the services automatically. - `AGENTS.md` had the same stale "requires `docker compose up -d`" comment above the `bootRun` commands. - The old text also claimed LGTM starts automatically, which is incorrect — `compose.yaml` marks it `org.springframework.boot.ignore: "true"`, explicitly opting it out of Spring Boot's compose lifecycle management. ## What changed - Clarified that `./gradlew bootRun` genuinely auto-starts (and stops) `compose.yaml`'s `solr`/`zoo` services via the `developmentOnly` `spring-boot-docker-compose` / `spring-ai-spring-boot-docker-compose` starters — no manual step needed there. - Kept the manual `docker compose up -d` step only where it's actually required: running the packaged JAR, Docker image, or native image directly, since `developmentOnly` dependencies are excluded from those artifacts' runtime classpath. - Added a short "Observability (optional)" note explaining LGTM must always be started by hand (`docker compose up -d lgtm`) since it's boot-ignored, regardless of run mode. - README.md, docs/observability.md, dev-docs/TROUBLESHOOTING.md, the client docs, the hackathon table card, and the CoC 2026 Glasgow slides were checked and are already accurate (their flows either run the built JAR/Docker image, or use a plain `docker run` quickstart unrelated to `compose.yaml`), so no changes were needed there. ## Test plan - [x] Docs-only change; no build-affecting files touched. - [x] Verified `spring-boot-docker-compose` / `spring-ai-spring-boot-docker-compose` are declared `developmentOnly` in `build.gradle.kts` / `gradle/libs.versions.toml`. - [x] Verified `lgtm` carries `org.springframework.boot.ignore: "true"` in `compose.yaml`. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
