leizhiyuan opened a new issue, #1470: URL: https://github.com/apache/rocketmq-dashboard/issues/1470
**FEATURE REQUEST** 1. Please describe the feature you are requesting. Allow the Studio local deployment script (`deploy/deploy.sh`) to reuse the host Maven cache when building the backend in a container. Today the script invokes `docker build` for `server/`, and Maven runs only inside the Docker build stage. The container build cannot reuse the developer's existing `~/.m2` repository. When the Maven layer is invalidated, dependencies have to be downloaded again, making repeated local deployments unnecessarily slow, especially on limited or high-latency networks. 2. Provide any additional detail on your proposed use case for this feature. The proposed deployment path is: - run Maven in a temporary Maven container, so Maven/JDK are still not required on the host; - mount the host Maven directory into that container; - set `maven.repo.local` explicitly to the mounted repository; - reuse the host `settings.xml` when present; - build the runtime image from the prebuilt JAR; - keep the existing default Dockerfile target for CI and `docker compose build` compatibility. The cache directory and Maven image should be configurable, with `~/.m2` and `maven:3.9.9-eclipse-temurin-21` as defaults. 3. Indicate the importance of this issue to you. Should-have. The current behavior does not block deployment, but repeated backend deployments spend significant time downloading the same Maven artifacts. The workaround is to build the JAR manually on the host or maintain a separate local deployment flow, which defeats the purpose of the one-command containerized deployment script. -- 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]
