diff options
| author | Robby <robby@santoslab.org> | 2018-04-07 08:23:42 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-04-07 08:23:42 -0500 |
| commit | ccb67db3759a16e95a75920d87281185310ccd81 (patch) | |
| tree | b901d0173eaf48489583c9a905914baaaf3486ab /docs | |
| parent | e628c84be7cf0b7bb00ba2141635d29503203fc4 (diff) | |
| download | mill-ccb67db3759a16e95a75920d87281185310ccd81.tar.gz mill-ccb67db3759a16e95a75920d87281185310ccd81.tar.bz2 mill-ccb67db3759a16e95a75920d87281185310ccd81.zip | |
Merge April 1 - 4, 2018 changes on master (#283)
* fix build
* Detect sh/batch launcher, dev.assembly, and release filename.
* Updated appveyor cache.
* Added some entries for master in readme.md changelog.
* Updated readme.md changelog.
* fixes #173; use default(compile) configuration for deps as default (#270)
* revert #254 to fix bootstrapping https://github.com/lihaoyi/mill/issues/268
* Updated ci tests.
* Reverted Ammonite caching workaround (a796f0a) now that it's fixed
* Changed ci/test-mill-0.sh to use interactive mode due to intermittent client failures to connect to server in travis
* Added ci/test-mill-bootstrap.sh (ci/test-mill-0.sh with bootstrapping) and use it on oraclejdk9 instead of ci/test-mill-0.sh
* Upgraded mill used for ci to 0.1.7-29-f5097f
* revive #254 and fix #268 (#274)
* Test mill batch (.bat) in AppVeyor
* fix minor typos in docs
* Sync Ammonite in ScalaModule (with build.sc).
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/pages/1 - Intro to Mill.md | 8 |
1 files changed, 3 insertions, 5 deletions
diff --git a/docs/pages/1 - Intro to Mill.md b/docs/pages/1 - Intro to Mill.md index d0ce29c7..305721d4 100644 --- a/docs/pages/1 - Intro to Mill.md +++ b/docs/pages/1 - Intro to Mill.md @@ -453,13 +453,12 @@ res2: mill.scalalib.CompilationResult = CompilationResult( ) ``` -You can run `mill` alone to open a build REPL; this is a Scala console with your +You can run `mill -i` to open a build REPL; this is a Scala console with your `build.sc` loaded, which lets you run tasks interactively. The task-running syntax is slightly different from the command-line, but more in-line with how you would depend on tasks from within your build file. -You can use this REPL to run build commands quicker, due to keeping the JVM warm -between runs, or to interactively explore your build to see what is available. +You can use this REPL to interactively explore your build to see what is available. ## Deploying your code @@ -543,6 +542,5 @@ You also need to specify `release` as `true` or `false`, depending on whether you just want to stage your module on `oss.sonatype.org` or you want Mill to complete the release process to Maven Central. -If you are publishing multiple artifacts, you can also use `target/bin/mill -mill.scalalib.PublishModule/publishAll1 as described +If you are publishing multiple artifacts, you can also use `mill mill.scalalib.PublishModule/publishAll` as described [here](http://www.lihaoyi.com/mill/page/common-project-layouts.html#publishing) |