ppalaga commented on issue #496: URL: https://github.com/apache/maven-mvnd/issues/496#issuecomment-2277648019
Yeah, the daemon starts in busy state so that the client that initiates its start can grab it by daemonId. I think currently, there is no way to instruct the client on the CLI to connect to a daemon with a specific daemonId. Not sure what is the goal of your experiments? You just want to invoke the client inside the running container so that it connects to the main daemon? If so, you could e.g. try to override the daemon registry after the daemon has started with a static file in which the daemon with your ID has status IDLE. If you want to run the client in a different process, then you may want to implement some new client options for connecting to a remote daemon. -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
