为什么我的play框架有时会获取oss-parent依赖？

我有一个服务器,可以自动构建一个play framework 2.3.4项目,并且可以成功构建我的开发分支.但是,当我构建不同的分支,在同一台服务器上使用相同的脚本时,我会遇到一些奇怪的行为.

构建由于某种原因获取调用的依赖项[actual dependency]-parent,这在其他分支上不会发生,也不会在我的本地计算机上构建有问题的分支.

例如:

在我当地:

[info] Resolving org.elasticsearch#elasticsearch;1.4.0 ...
[info] Resolving org.apache.lucene#lucene-core;4.10.2 ...
[info] Resolving org.apache.lucene#lucene-analyzers-common;4.10.2 ...
[info] Resolving org.apache.lucene#lucene-queries;4.10.2 ...
[info] Resolving org.apache.lucene#lucene-memory;4.10.2 ...
[info] Resolving org.apache.lucene#lucene-highlighter;4.10.2 ...
...

关于CI构建:

[info] Resolving org.elasticsearch#elasticsearch;1.4.0 ...
[info] Resolving org.sonatype.oss#oss-parent;7 ...
[info] Resolving org.apache.lucene#lucene-core;4.10.2 ...
[info] Resolving org.apache.lucene#lucene-parent;4.10.2 ...
[info] Resolving org.apache.lucene#lucene-solr-grandparent;4.10.2 ...
[info] Resolving org.apache#apache;13 ...
[info] Resolving org.apache.lucene#lucene-analyzers-common;4.10.2 ...
[info] Resolving org.apache.lucene#lucene-parent;4.10.2 ...
[info] Resolving org.apache.lucene#lucene-queries;4.10.2 ...
[info] Resolving org.apache.lucene#lucene-parent;4.10.2 ...
[info] Resolving org.apache.lucene#lucene-memory;4.10.2 ...
[info] Resolving org.apache.lucene#lucene-parent;4.10.2 ...
[info] Resolving org.apache.lucene#lucene-highlighter;4.10.2 ...
[info] Resolving org.apache.lucene#lucene-parent;4.10.2 ...
...

依赖org.sonatype.oss#oss-parent;7是全新的,在工作构建中没有org.sonatype.oss依赖.

然后在无法启动虚假应用程序之后测试失败,我认为这是由于错误的依赖性.

有谁知道是什么原因引起的？

这是我的build.sbt中的解析器的样子:

resolvers := Seq(
  "Sonatype repo" at "https://oss.sonatype.org/content/repositories/releases/",
  "Sonatype snapshots" at "https://oss.sonatype.org/content/repositories/snapshots/",
  "Maven central repo" at "https://oss.sonatype.org/content/repositories/central/",
  "Maven central repo2" at "https://repo1.maven.org/maven2/",
  "Typesafe Repository" at "https://repo.typesafe.com/typesafe/releases/",
  Resolver.url("Objectify Play Repository", url("http://schaloner.github.io/releases/"))(Resolver.ivyStylePatterns),
  Resolver.url("Objectify Play Snapshot Repository", url("http://schaloner.github.io/snapshots/"))(Resolver.ivyStylePatterns),
  Resolver.url("Edulify Repository", url("http://edulify.github.io/modules/releases/"))(Resolver.ivyStylePatterns),
  Resolver.file("Local Repository", file(sys.env.get("PLAY_HOME").map(_ + "/repository/local").getOrElse("")))(Resolver.ivyStylePatterns),
  Resolver.mavenLocal
)

今天上午,2015年2月6日,两个分支机构合并,因此没有差异.但是,一个分支仍然构建但另一个分支失败(在相同的弹性实例上).每个构建都有自己的激活器实例,不共享存储库文件夹,但两个存储库文件夹是相同的.