arturobernalg commented on PR #1888: URL: https://github.com/apache/maven-mvnd/pull/1888#issuecomment-6518390080
Makes sense as a follow-up, but it's not as simple as it sounds today: `DaemonInfo`/`DaemonRegistry` don't track a version at all right now -- the daemon never sends one when it registers itself (`Server.java`), and the registry is a positional binary format (`writeUTF`/`writeInt` in fixed order, no schema versioning), so adding a field there is an on-disk format change that affects compatibility with daemons already running from older mvnd builds. I'd rather not fold that into this PR, which is a narrow, already-tested fix. Happy to open a follow-up issue for "surface the running daemon's version (e.g. as a column in `--status`)" if that's the right place for it -- let me know and I'll file it. -- 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]
