Updated Full Configuration (Draft) (markdown)

harrah 2011-06-05 17:42:01 -07:00
parent bbe14af89a
commit cdd45ba48f
1 changed files with 4 additions and 0 deletions

@ -1,3 +1,5 @@
[#35]: https://github.com/harrah/xsbt/issues/35
# Full Configuration (Draft) # Full Configuration (Draft)
A full configuration consists of one or more Scala source files that define concrete Builds. A full configuration consists of one or more Scala source files that define concrete Builds.
@ -161,6 +163,8 @@ Additionally, there are implicit conversions `URI => RootProject` and `File => R
External, remote builds are retrieved or checked out to a staging directory in the user's `.ivy2` directory so that they can be manipulated like local builds. External, remote builds are retrieved or checked out to a staging directory in the user's `.ivy2` directory so that they can be manipulated like local builds.
Examples of using project references follow in the next sections. Examples of using project references follow in the next sections.
When using external projects, the `sbt.boot.directory` should be set (see [[Setup]]) so that unnecessary recompilations do not occur (see [#35]).
### Execution Dependency ### Execution Dependency
If project A has an execution dependency on project B, then when you execute a task on project A, it will also be run on project B. No ordering of these tasks is implied. If project A has an execution dependency on project B, then when you execute a task on project A, it will also be run on project B. No ordering of these tasks is implied.