Dream dc90f160df [2.x] feat: Support --autostart=false and --no-server in sbtn client (#8895) ... **Problem** When sbtn (native thin client) can't find a running sbt server, it prompts to start one. There was no way to opt out of server auto-start from the client side, which is needed for CI environments and scripting (sbt/sbt#7079). **Solution** Reuse the existing sbt.server.autostart system property in NetworkClient to control whether sbtn should attempt to start a server. When no server is running and sbt.server.autostart=false, sbtn exits with an error instead of prompting. Support setting this property via: - sbtn --no-server compile (sets sbt.server.autostart=false) - sbtn --autostart=false compile (new flag following sbt conventions) - sbtn -Dsbt.server.autostart=false compile (direct system property) - sbt --autostart=false compile (bash runner and sbtw) This follows sbt's naming conventions for properties/options: positive property names with =false opt-out (like --color=false, --supershell=false). Fixes sbt/sbt#7079 Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>		2026-03-12 20:51:07 -04:00
..
src	[2.x] feat: Support --autostart=false and --no-server in sbtn client (#8895)	2026-03-12 20:51:07 -04:00
build.sbt	[2.x] feat: sbtw launcher (#8742)	2026-02-16 16:21:30 -05:00