Calling build-level keys at a subproject resolves to wrong scoping

[eed3si9n]

Ref #2707, #2708, #2469

steps

Using a multi-project build with sbt 0.13.13, navigate to a subproject and call version.

contraband root> project library
[info] Set current project to contraband (in build file:/Users/xxx/work/contraband/)
contraband> version
[info] library/*:version
[info] 	0.3.0-M1
[info] plugin/*:version
[info] 	0.3.0-M1
[info] {.}/*:version
[info] 	0.3.0-M1
contraband> inspect version
[info] Setting: java.lang.String = 0.3.0-M1
[info] Description:
[info] 	The version/revision of the current module.
[info] Provided by:
[info] 	{file:/Users/xxx/work/contraband/}/*:version
[info] Defined at:
[info] 	/Users/xxx/work/contraband/build.sbt:13
[info] Delegates:
[info] 	{.}/*:version
[info] 	*/*:version
[info] Related:
[info] 	*/*:version

problem

The problem is that typing "version" seems to be resolving to some build level scoping, and it ends up aggregating calls to the build level and the subprojects.

expectation

Here's the result using sbt 0.13.11:

contraband root> project library
[info] Set current project to contraband (in build file:/Users/xxx/work/contraband/)
contraband> version
[info] 0.3.0-M1
contraband> inspect version
[info] Setting: java.lang.String = 0.3.0-M1
[info] Description:
[info]  The version/revision of the current module.
[info] Provided by:
[info]  {file:/Users/xxx/work/contraband/}/*:version
[info] Defined at:
[info]  /Users/xxx/work/contraband/build.sbt:13
[info] Reverse dependencies:
[info]  library/*:bintraySyncMavenCentral
[info]  library/*:projectId
[info]  library/*:bintrayRemoteSign
[info]  library/*:isSnapshot
[info]  library/*:bintrayRelease
[info]  library/*:bintrayUnpublish
[info]  library/*:bintray::publishTo
[info] Delegates:
[info]  library/*:version
[info]  {.}/*:version
[info]  */*:version
[info] Related:
[info]  */*:version
[info]  {.}/*:version

notes

This behavior may result to unintended side effect aggregating over the subprojects.