왜 sbt가 내 의존성을 찾지 못합니까? 내 리프트 프로젝트에 대한 build.sbt에서

Question

, 내가 빌드 때 페이팔 라이브러리

"net.liftmodules" % "paypal_2.6" % "1.3-SNAPSHOT", 

(예를 들어, SBT 컴파일)에 대한 종속성이 모듈을 찾을 수 없습니다. 무엇 나를 혼란은 내가 sonatype의 REPO에서 확인하면, 예상 의존성이 있다는 것입니다

http://oss.sonatype.org/content/repositories/releases/net/liftmodules/paypal_2.6_2.11/1.3-SNAPSHOT/paypal_2.6_2.11-1.3-SNAPSHOT.pom

내 질문은 왜 SBT 명확>

[info] Resolving net.liftmodules#paypal_2.6_2.11;1.3-SNAPSHOT ... 
[warn] module not found: net.liftmodules#paypal_2.6_2.11;1.3-SNAPSHOT 
[warn] ==== local: tried 
[warn] C:\Users\Andrew Bucknell\.ivy2\local\net.liftmodules\paypal_2.6_2.11\1.3-SNAPSHOT\ivys\ivy.xml 
[warn] ==== public: tried 
[warn] http://repo1.maven.org/maven2/net/liftmodules/paypal_2.6_2.11/1.3-SNAPSHOT/paypal_2.6_2.11-1.3-SNAPSHOT.pom 
[warn] ==== snapshots: tried 
[warn] http://oss.sonatype.org/content/repositories/snapshots/net/liftmodules/paypal_2.6_2.11/1.3-SNAPSHOT/paypal_2.6_ 
2.11-1.3-SNAPSHOT.pom 
[warn] ==== releases: tried 
[warn] http://oss.sonatype.org/content/repositories/releases/net/liftmodules/paypal_2.6_2.11/1.3-SNAPSHOT/paypal_2.6_2 
.11-1.3-SNAPSHOT.pom 
[warn] ==== typesafe-ivy-releases: tried 
[warn] http://repo.typesafe.com/typesafe/ivy-releases/net.liftmodules/paypal_2.6_2.11/1.3-SNAPSHOT/ivys/ivy.xml 
[warn] ==== snapshots: tried 
[warn] http://oss.sonatype.org/content/repositories/snapshots/net/liftmodules/paypal_2.6_2.11/1.3-SNAPSHOT/paypal_2.6_ 
2.11-1.3-SNAPSHOT.pom 
[warn] ==== staging: tried 
[warn] http://oss.sonatype.org/content/repositories/staging/net/liftmodules/paypal_2.6_2.11/1.3-SNAPSHOT/paypal_2.6_2. 
11-1.3-SNAPSHOT.pom 
[warn] ==== releases: tried 
[warn] http://oss.sonatype.org/content/repositories/releases/net/liftmodules/paypal_2.6_2.11/1.3-SNAPSHOT/paypal_2.6_2 
.11-1.3-SNAPSHOT.pom 

Answer 1

I 존재 종속성을 찾기가 없습니다 https를 사용하도록 소셜 형식 해결 프로그램을 업데이트했습니다.

resolvers ++= Seq("snapshots"  at "https://oss.sonatype.org/content/repositories/snapshots", 
       "releases"  at "https://oss.sonatype.org/content/repositories/releases" 
       ) 

문제가 해결되었습니다.