2016-01-06 51 views
0

我有一個基於SBT,我發佈到Maven倉庫Scala庫:爲什麼沒有檢測到傳遞依賴關係?

organization := "com.mycompany" 
name := "mylib" 
version := "0.0.1" 
scalaVersion := "2.10.6" 
crossScalaVersions := Seq("2.10.6", "2.11.7") 
scalacOptions ++= Seq("-feature", "-unchecked", "-deprecation") 

libraryDependencies ++= Seq(
    "org.scalaj" %% "scalaj-http" % "2.2.0", 
    "org.json4s" %% "json4s-jackson" % "3.3.0", 
    "org.slf4j" % "slf4j-api" % "1.7.13", 
    "org.slf4j" % "slf4j-simple" % "1.7.13" 
) 

isSnapshot := true 
publishMavenStyle := true 
publishTo := { 
    Some(s3resolver.value("My Repo", s3("mybucket")).withMavenPatterns) 
} 

我有這個庫到另一個項目:

libraryDependencies ++= Seq(
    "com.mycompany" %% "mylib" % "0.0.1" 
) 

運行sbt sbt-dependency dependencyTree只能說明:

[info] Done updating. 
[info] default:another-project_2.10:1.2 [S] 
[info] +-com.mycompany:mylib_2.10:0.0.1 
[info]  

我無法看到所有第三方依賴項:org.scalajorg.json4s等。

編輯:此外,構建組件時,這些依賴關係是從uberjar缺失爲好。

部署到Maven倉庫不包含上述所有依賴的.pom文件,而~/.ivy2/cache/com.mycompany/mylib_2.10/ivy-0.0.1.xml沒有。

運行在MYLIB /節目sbt about

[info] Loading global plugins from /home/michael/.sbt/0.13/plugins 
[info] Loading project definition from /home/michael/Dev/projects/mylib/project 
[info] Set current project to mylib (in build file:/home/michael/Dev/projects/mylib/) 
[info] This is sbt 0.13.9 
[info] The current project is {file:/home/michael/Dev/projects/mylib/}mylib 0.0.1 
[info] The current project is built against Scala 2.10.6 
[info] Available Plugins: sbt.plugins.IvyPlugin, sbt.plugins.JvmPlugin, sbt.plugins.CorePlugin, sbt.plugins.JUnitXmlReportPlugin, com.typesafe.sbteclipse.plugin.EclipsePlugin, ohnosequences.sbt.SbtS3Resolver 
[info] sbt, sbt plugins, and build definitions are using Scala 2.10.5 

在otherproject /運行sbt about顯示:

[info] Loading global plugins from /home/michael/.sbt/0.13/plugins 
[info] Loading project definition from /home/michael/Dev/projects/otherproject/project 
[info] Set current project to otherproject (in build file:/home/michael/Dev/projects/otherproject/) 
[info] Updating {file:/home/michael/Dev/projects/otherproject/}otherproject... 
[info] Resolving org.fusesource.jansi#jansi;1.4 ... 
[info] Done updating. 
[info] This is sbt 0.13.9 
[info] The current project is {file:/home/michael/Dev/projects/otherproject/}otherproject 1.2 
[info] The current project is built against Scala 2.10.6 
[info] Available Plugins: sbt.plugins.IvyPlugin, sbt.plugins.JvmPlugin, sbt.plugins.CorePlugin, sbt.plugins.JUnitXmlReportPlugin, com.typesafe.sbteclipse.plugin.EclipsePlugin, ohnosequences.sbt.SbtS3Resolver, net.virtualvoid.sbt.graph.DependencyGraphPlugin, sbtassembly.AssemblyPlugin 
[info] sbt, sbt plugins, and build definitions are using Scala 2.10.5 

下面是從發佈到本地目錄輸出:

[info] Loading global plugins from /home/michael/.sbt/0.13/plugins 
[info] Loading project definition from /home/michael/Dev/projects/mylib/project 
[info] Set current project to mylib (in build file:/home/michael/Dev/projects/mylib/) 
[info] Updating {file:/home/michael/Dev/projects/mylib/}mylib... 
[info] Packaging /home/michael/Dev/projects/mylib/target/scala-2.10/mylib_2.10-0.0.1-sources.jar ... 
[info] Done packaging. 
[info] Wrote /home/michael/Dev/projects/mylib/target/scala-2.10/mylib_2.10-0.0.1.pom 
[info] Resolving org.fusesource.jansi#jansi;1.4 ... 
[info] Done updating. 
[info] :: delivering :: com.mycompany#mylib_2.10;0.0.1 :: 0.0.1 :: integration :: Sat Jan 09 16:10:20 IST 2016 
[info] delivering ivy file to /home/michael/Dev/projects/mylib/target/scala-2.10/ivy-0.0.1.xml 
[info] Main Scala API documentation to /home/michael/Dev/projects/mylib/target/scala-2.10/api... 
[info] Packaging /home/michael/Dev/projects/mylib/target/scala-2.10/mylib_2.10-0.0.1.jar ... 
[info] Done packaging. 
model contains 9 documentable templates 
[info] Main Scala API documentation successful. 
[info] Packaging /home/michael/Dev/projects/mylib/target/scala-2.10/mylib_2.10-0.0.1-javadoc.jar ... 
[info] Done packaging. 
[info] published mylib_2.10 to /home/michael/Dev/projects/mylib/releases/com/mycompany/mylib_2.10/0.0.1/mylib_2.10-0.0.1.pom 
[info] published mylib_2.10 to /home/michael/Dev/projects/mylib/releases/com/mycompany/mylib_2.10/0.0.1/mylib_2.10-0.0.1.jar 
[info] published mylib_2.10 to /home/michael/Dev/projects/mylib/releases/com/mycompany/mylib_2.10/0.0.1/mylib_2.10-0.0.1-sources.jar 
[info] published mylib_2.10 to /home/michael/Dev/projects/mylib/releases/com/mycompany/mylib_2.10/0.0.1/mylib_2.10-0.0.1-javadoc.jar 
[success] Total time: 4 s, completed Jan 9, 2016 4:10:23 PM 

什麼我做錯了嗎?

+0

爲什麼'isSnapshot:= TRUE;因爲' 「0.0.1」'是穩定的,即非快照版本? –

+0

這僅用於測試目的,以便啓用發佈者覆蓋工件。我嘗試禁用它,但沒有運氣 – spektom

+0

你可以在兩個項目中做'關於'嗎?你使用什麼版本的sbt-dependency-graph?你可以使用'publishTo:= Some(Resolver.file(「file」,new File(「releases」)))'而不是s3?請包括問題的輸出。 (擾流板:它爲我的作品) –

回答

0

build.sbt文件包含行

publishMavenStyle := true 

根據the documentation

由makePom作用產生的POM併發布到 存儲庫,而不是ivy文件

我可以假設ivy.xml只是沒有生成和o你看到的是前一次運行的殘差,當時publishMavenStyle還沒有設置。

由於您的工件被髮布到Maven倉庫,你試圖從~/.ivy2/cache/com.mycompany/mylib_2.10取出一個,並檢查依賴關係樹上市的結果呢?

+0

是的,我試着刪除'〜/ .ivy /緩存/ com.mycompany'以及'〜/ .m2目錄/庫/ COM/mycompany'(以防萬一),並重新檢查依賴關係樹。 'ivy-0.0.1.xml'文件仍然是在沒有依賴關係的情況下重新創建的。 – spektom