Fix spelling error.

waywardmonkeys 2011-12-01 07:22:26 -08:00
parent 2b2fd748b4
commit bccf4c2166
1 changed files with 2 additions and 2 deletions

@ -68,7 +68,7 @@ artifactName := { (config: String, module: ModuleID, artifact: Artifact) =>
(Note that in practice you rarely want to drop the classifier.)
Finally, you can get the `(Artifact, File)` pair for the artifact by mapping the `packaged-artifact` task. Note that if you don't need the `Artifact`, you can get just the File from the package task (`package`, `package-doc`, or `package-src`). In both cases, mapping the task to get the file ensures that the artifact is generated first and so the file is guaranteed to be uptodate.
Finally, you can get the `(Artifact, File)` pair for the artifact by mapping the `packaged-artifact` task. Note that if you don't need the `Artifact`, you can get just the File from the package task (`package`, `package-doc`, or `package-src`). In both cases, mapping the task to get the file ensures that the artifact is generated first and so the file is guaranteed to be up-to-date.
For example:
@ -83,7 +83,7 @@ where `val myTask = TaskKey[Unit]`.
# Defining custom artifacts
In addition to configuring the builtin artifacts, you can declare other artifacts to publish. Multiple artifacts are allowed when using Ivy metadata, but a Maven POM file only supports distinguishing artifacts based on classifiers and these are not recorded in the POM.
In addition to configuring the built-in artifacts, you can declare other artifacts to publish. Multiple artifacts are allowed when using Ivy metadata, but a Maven POM file only supports distinguishing artifacts based on classifiers and these are not recorded in the POM.
Basic `Artifact` construction look like: