Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Seems as though addCommandAlias confuses sbt-client #5
dir=$(mktemp -d) cd "$dir" mkdir -p src/test/scala project cat >project/build.properties<<! sbt.version=1.2.8 ! cat >build.sbt <<! addCommandAlias("foo", "test") ! cat >src/test/scala/Test.scala <<! bogus !
I wonder if this is actually an sbt issue, emitting
too soon, as there's no followup
Yes, it looks like sbt is returning the responses in a strange order. It returns the "result" response before the log messages.
While that's totally fine in terms of LSP, sbt-client doesn't like it. sbt-client needs some way to decide that it's finished communicating with sbt and it's time to exit the process. It uses the "result" response for this, with the implicit assumption that this is the final message it will receive.
I'm not really sure what to do about this. sbt-client can't hang around forever on the off chance sbt might want to send it some more messages.
Might be worth opening an sbt issue? This behaviour does seem strange to me.