jsuereth
commented
10 years ago This is where the sbt-launcher resolves dbuild artifacts themselves into ~/.ivy2. It shouldn't be an issue because dbuild is published as legitimate ivy2 artifacts. The reason we split dbuild's ivy2 caches into different directories is because when we are rewiring versions, we're creating artifacts that may conflict with existing public artifacts.
I don't think this is an issue.
Dsbt-build should, in theory, confine all of the artifacts loaded during its operation to the directory containing the project. However, at present some artifacts may be loaded into the ~/.ivy2 cache directory, and specifically during the loading stages of the nested sbt invocations. Although not a major issue, it should be easy to fix that by changing the ivy.root used while starting sbt.