diff options
| author | Li Haoyi <haoyi.sg@gmail.com> | 2018-03-26 19:39:12 -0700 |
|---|---|---|
| committer | Li Haoyi <haoyi.sg@gmail.com> | 2018-03-26 19:39:12 -0700 |
| commit | ae1e499cbb5b710a5a4e7dd8536a42c22631e84d (patch) | |
| tree | da2ed1ad195886ad44984b2a20b7e78557c36948 /docs | |
| parent | 25c26d00146c1dee15099cb9ebd332e96a788c66 (diff) | |
| download | mill-ae1e499cbb5b710a5a4e7dd8536a42c22631e84d.tar.gz mill-ae1e499cbb5b710a5a4e7dd8536a42c22631e84d.tar.bz2 mill-ae1e499cbb5b710a5a4e7dd8536a42c22631e84d.zip | |
remove /target/bin prefix from mill examples in Common Project Layouts
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/pages/3 - Common Project Layouts.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/pages/3 - Common Project Layouts.md b/docs/pages/3 - Common Project Layouts.md index 3af47a45..a0e3afbe 100644 --- a/docs/pages/3 - Common Project Layouts.md +++ b/docs/pages/3 - Common Project Layouts.md @@ -148,7 +148,7 @@ Once you've mixed in `PublishModule`, you can publish your libraries to maven central via: ```bash -target/bin/mill mill.scalalib.PublishModule/publishAll \ +mill mill.scalalib.PublishModule/publishAll \ lihaoyi:$SONATYPE_PASSWORD \ $GPG_PASSWORD \ foo.publishArtifacts @@ -159,7 +159,7 @@ them manually. You can also pass in the `--release true` flag to perform the staging/release automatically: ```bash -target/bin/mill mill.scalalib.PublishModule/publishAll \ +mill mill.scalalib.PublishModule/publishAll \ lihaoyi:$SONATYPE_PASSWORD \ $GPG_PASSWORD \ foo.publishArtifacts \ @@ -170,7 +170,7 @@ If you want to publish/release multiple modules, you can use the `_` or `__` wildcard syntax: ```bash -target/bin/mill mill.scalalib.PublishModule/publishAll \ +mill mill.scalalib.PublishModule/publishAll \ lihaoyi:$SONATYPE_PASSWORD \ $GPG_PASSWORD \ __.publishArtifacts \ @@ -223,4 +223,4 @@ A relatively complex build with numerous submodules, some cross-built across Scala major versions while others are cross-built against Scala minor versions. Also demonstrates how to pass one module's compiled artifacts to the -`run`/`test` commands of another, via their `forkEnv`.
\ No newline at end of file +`run`/`test` commands of another, via their `forkEnv`. |