Simplify manual testing using SBT

2 files changed, 15 insertions, 6 deletions

diff --git a/build.sbt b/build.sbt
index bc393aa3..c021dd38 100644
--- a/build.sbt
+++ b/build.sbt
@@ -125,15 +125,16 @@ lazy val scalaplugin = project
     sharedSettings,
     pluginSettings,
     name := "mill-scalaplugin",
-    fork in Test := true,
+    fork := true,
     baseDirectory in Test := (baseDirectory in Test).value / "..",
-    javaOptions in Test := bridgeProps.value.toSeq
+    javaOptions := bridgeProps.value.toSeq
   )
 
 lazy val bin = project
   .dependsOn(scalaplugin)
   .settings(
     sharedSettings,
+    mainClass in (Compile, run) := Some("mill.Main"),
     assemblyOption in assembly := {
       (assemblyOption in assembly).value.copy(
         prependShellScript = Some(
diff --git a/readme.md b/readme.md
index 2640d6b0..bed0f7f0 100644
--- a/readme.md
+++ b/readme.md
@@ -28,13 +28,21 @@ e.g.:
 ./bin/target/mill run ScalaPlugin.assembly
 ```
 
-there is already a `watch` option that looks for changes on files, e.g.:
+There is already a `watch` option that looks for changes on files, e.g.:
 
 ```bash
 ./bin/target/mill --watch run Core.compile
 ```
 
-output will be generated into a the `./out` folder.
+Output will be generated into a the `./out` folder.
+
+If you are repeatedly testing Mill manually by running it against the `build.sc`
+file in the repository root, you can skip the assembly process and directly run
+it via:
+
+```bash
+sbt "~bin/run Core.test"
+```
 
 Lastly, you can generate IntelliJ Scala project files using Mill via
 
@@ -123,10 +131,10 @@ git clean -xdf
 sbt bin/test:assembly 
 
 # Build Mill executable using the Mill executable generated by SBT
-bin/target/mill run assembly 
+bin/target/mill devAssembly 
 
 # Build Mill executable using the Mill executable generated by Mill itself
-out/assembly run assembly
+out/devAssembly devAssembly
 ```
 
 Eventually, as Mill stabilizes, we will get rid of the SBT build entirely and