From cdd45ba48f6bc5da6aac58f56b525a4c35bedf40 Mon Sep 17 00:00:00 2001 From: harrah Date: Sun, 5 Jun 2011 17:42:01 -0700 Subject: [PATCH] Updated Full Configuration (Draft) (markdown) --- Full-Configuration.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/Full-Configuration.md b/Full-Configuration.md index 718fa0f..3f308dd 100644 --- a/Full-Configuration.md +++ b/Full-Configuration.md @@ -1,3 +1,5 @@ +[#35]: https://github.com/harrah/xsbt/issues/35 + # Full Configuration (Draft) 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. 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 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.