diff options
author | Li Haoyi <haoyi.sg@gmail.com> | 2018-02-21 21:05:37 -0800 |
---|---|---|
committer | Li Haoyi <haoyi.sg@gmail.com> | 2018-02-24 17:13:03 -0800 |
commit | c98408adf2d96928fe227a740631a8efd8e0c339 (patch) | |
tree | 5a36d9ee7d8ee6e1f7f9247cd7ddd31b194df5df /readme.md | |
parent | 51db54d4f1deefb34b9d7f6581611ae166652493 (diff) | |
download | mill-c98408adf2d96928fe227a740631a8efd8e0c339.tar.gz mill-c98408adf2d96928fe227a740631a8efd8e0c339.tar.bz2 mill-c98408adf2d96928fe227a740631a8efd8e0c339.zip |
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
Diffstat (limited to 'readme.md')
-rw-r--r-- | readme.md | 30 |
1 files changed, 15 insertions, 15 deletions
@@ -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 |