Clean up the provisional client-server code with unit tests and proper file-sockets

Seems to work well enough for interactive scala consoles, though still not Ammonite

Also Added ScalaModule#launcher and re-worked our build.sc file to use it

1 files changed, 15 insertions, 15 deletions

diff --git a/readme.md b/readme.md
index 67dd0053..2540c46f 100644
--- a/readme.md
+++ b/readme.md
@@ -31,7 +31,7 @@ Build a standalone executable jar:
 
 ```bash
 sbt bin/test:assembly
-mill devAssembly
+mill dev.assembly
 ```
 
 Now you can re-build this very same project using the build.sc file, e.g. re-run
@@ -41,27 +41,27 @@ e.g.:
 ```bash
 ./target/bin/mill core.compile
 
-./out/devAssembly/dest/mill core.compile
-./out/devAssembly/dest/mill main.test.compile
-./out/devAssembly/dest/mill main.test
-./out/devAssembly/dest/mill scalalib.assembly
+./out/dev/assembly/dest/out.jar core.compile
+./out/dev/assembly/dest/out.jar main.test.compile
+./out/dev/assembly/dest/out.jar main.test
+./out/dev/assembly/dest/out.jar scalalib.assembly
 ```
 
 There is already a `watch` option that looks for changes on files, e.g.:
 
 ```bash
 ./target/bin/mill --watch core.compile
-./out/devAssembly/dest/mill --watch core.compile
+./out/dev/assembly/dest/out.jar --watch core.compile
 ```
 
 You can get Mill to show the JSON-structured output for a particular `Target` or
 `Command` using the `show` flag:
 
 ```bash
-./out/devAssembly/dest/mill show core.scalaVersion
-./out/devAssembly/dest/mill show core.compile
-./out/devAssembly/dest/mill show core.assemblyClasspath
-./out/devAssembly/dest/mill show main.test
+./out/dev/assembly/dest/out.jar show core.scalaVersion
+./out/dev/assembly/dest/out.jar show core.compile
+./out/dev/assembly/dest/out.jar show core.assemblyClasspath
+./out/dev/assembly/dest/out.jar show main.test
 ```
 
 Output will be generated into a the `./out` folder.
@@ -73,15 +73,15 @@ it via:
 ```bash
 sbt "~bin/test:run main.test"
 sbt "~bin/test:run"
-mill --watch dev . main.test
-mill --watch dev .
+mill --watch dev.run . main.test
+mill --watch dev.run .
 ```
 
 You can also test out your current Mill code with one of the hello-world example
 repos via:
 
 ```bash
-mill dev docs/example-1 foo.run
+mill dev.run docs/example-1 foo.run
 ```
 
 Lastly, you can generate IntelliJ Scala project files using Mill via
@@ -332,10 +332,10 @@ git clean -xdf
 sbt bin/test:assembly 
 
 # Build Mill executable using the Mill executable generated by SBT
-target/bin/mill devAssembly 
+target/bin/mill dev.Assembly 
 
 # Build Mill executable using the Mill executable generated by Mill itself
-out/devAssembly/dest/out.jar devAssembly
+out/dev/assembly/dest/out.jar dev.assembly
 ```
 
 Eventually, as Mill stabilizes, we will get rid of the SBT build entirely and