Try this in a unix shell:
git clone git#github.com:jsuereth/sbt-in-action-examples.git
cd sbt-in-action-examples/chapter11/scalastyle-plugin/
sbt updateClassifiers
With sbt 0.13.7, I get this:
[warn] [FAILED ] org.scala-sbt#precompiled-2_8_2;0.13.7!precompiled-2_8_2.jar: (0ms)
[warn] ==== typesafe-ivy-releases: tried
[warn] https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/precompiled-2_8_2/0.13.7/jars/precompiled-2_8_2.jar
…
[warn] [FAILED ] org.scala-sbt#precompiled-2_9_2;0.13.7!precompiled-2_9_2.jar: (0ms)
[warn] ==== typesafe-ivy-releases: tried
[warn] https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/precompiled-2_9_2/0.13.7/jars/precompiled-2_9_2.jar
…
[warn] [FAILED ] org.scala-sbt#precompiled-2_9_3;0.13.7!precompiled-2_9_3.jar: (0ms)
[warn] ==== typesafe-ivy-releases: tried
[warn] https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/precompiled-2_9_3/0.13.7/jars/precompiled-2_9_3.jar
…
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: FAILED DOWNLOADS ::
[warn] :: ^ see resolution messages for details ^ ::
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: org.scala-sbt#precompiled-2_8_2;0.13.7!precompiled-2_8_2.jar
[warn] :: org.scala-sbt#precompiled-2_9_2;0.13.7!precompiled-2_9_2.jar
[warn] :: org.scala-sbt#precompiled-2_9_3;0.13.7!precompiled-2_9_3.jar
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[success] Total time: 4 s, completed Apr 13, 2015 9:51:15 AM
Are these warnings normal?
I noticed that the URLs that SBT is trying to look for these artifacts do not match the URLs of the artifacts published.
That is, sbt is looking for these artifacts:
https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/precompiled-2_8_2/0.13.7/jars/precompiled-2_8_2.jar
https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/precompiled-2_9_2/0.13.7/jars/precompiled-2_9_2.jar
https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/precompiled-2_9_3/0.13.7/jars/precompiled-2_9_3.jar
But in fact, the artifacts available are these:
https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/precompiled-2_8_2/0.13.7/jars/compiler-interface-bin.jar
https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/precompiled-2_9_2/0.13.7/jars/compiler-interface-bin.jar
https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/precompiled-2_9_3/0.13.7/jars/compiler-interface-bin.jar
It seems that the above "compiler-interface-bin.jar" artifacts correspond to the "sources" artifacts here:
https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/precompiled-2_8_2/0.13.7/srcs/precompiled-2_8_2-sources.jar
https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/precompiled-2_9_2/0.13.7/srcs/precompiled-2_9_2-sources.jar
https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/precompiled-2_9_3/0.13.7/srcs/precompiled-2_9_3-sources.jar
Nicolas.
I am guessing that these were cause by the instability of either https://repo.typesafe.com/ (redirection proxy) or Bintray. I don't think they are normal.
For what it's worth, I was able to run updateClassifiers fine.
Related
I'm trying to get the spark.sas7bdat package to work so that I can read SAS tables into Spark. For some reason, it seems to make Spark fail.
e.g.
The following code works fine and launches spark:
Sys.setenv(JAVA_HOME = "/Library/Java/JavaVirtualMachines/zulu-8.jdk/Contents/Home")
library(sparklyr)
sc <- spark_connect(master = "local", version = "2.0.1")
However, if I simply load the spark.sas7bdat package, this fails:
Sys.setenv(JAVA_HOME = "/Library/Java/JavaVirtualMachines/zulu-8.jdk/Contents/Home")
library(sparklyr)
library(spark.sas7bdat)
sc <- spark_connect(master = "local", version = "2.0.1")
I get the following error:
Error in spark_connect_gateway(gatewayAddress, gatewayPort, sessionId,
: Gateway in localhost:8880 did not respond. Try running
options(sparklyr.log.console = TRUE) followed by sc <- spark_connect(...) for more debugging info.
I'm running this on an M1 Macbook Air with R 4.2.1. I have maven installed via homebrew.
Any suggestions?
Others seem to have the same issue, see: https://githubmemory.com/repo/bnosac/spark.sas7bdat/issues/9
Running options(sparklyr.log.console = TRUE) gives me the following:
Ivy Default Cache set to: /Users/henrydehe/.ivy2/cache
The jars for the packages stored in: /Users/henrydehe/.ivy2/jars
:: loading settings :: url = jar:file:/Users/henrydehe/spark/spark-2.0.1-bin-hadoop2.7/jars/ivy-2.4.0.jar!/org/apache/ivy/core/settings/ivysettings.xml
saurfang#spark-sas7bdat added as a dependency
:: resolving dependencies :: org.apache.spark#spark-submit-parent;1.0
confs: [default]
:: resolution report :: resolve 460ms :: artifacts dl 1ms
:: modules in use:
---------------------------------------------------------------------
| | modules || artifacts |
| conf | number| search|dwnlded|evicted|| number|dwnlded|
---------------------------------------------------------------------
| default | 1 | 0 | 0 | 0 || 0 | 0 |
---------------------------------------------------------------------
:: problems summary ::
:::: WARNINGS
module not found: saurfang#spark-sas7bdat;2.0.0-s_2.11
==== local-m2-cache: tried
file:/Users/henrydehe/.m2/repository/saurfang/spark-sas7bdat/2.0.0-s_2.11/spark-sas7bdat-2.0.0-s_2.11.pom
-- artifact saurfang#spark-sas7bdat;2.0.0-s_2.11!spark-sas7bdat.jar:
file:/Users/henrydehe/.m2/repository/saurfang/spark-sas7bdat/2.0.0-s_2.11/spark-sas7bdat-2.0.0-s_2.11.jar
==== local-ivy-cache: tried
/Users/henrydehe/.ivy2/local/saurfang/spark-sas7bdat/2.0.0-s_2.11/ivys/ivy.xml
-- artifact saurfang#spark-sas7bdat;2.0.0-s_2.11!spark-sas7bdat.jar:
/Users/henrydehe/.ivy2/local/saurfang/spark-sas7bdat/2.0.0-s_2.11/jars/spark-sas7bdat.jar
==== central: tried
https://repo1.maven.org/maven2/saurfang/spark-sas7bdat/2.0.0-s_2.11/spark-sas7bdat-2.0.0-s_2.11.pom
-- artifact saurfang#spark-sas7bdat;2.0.0-s_2.11!spark-sas7bdat.jar:
https://repo1.maven.org/maven2/saurfang/spark-sas7bdat/2.0.0-s_2.11/spark-sas7bdat-2.0.0-s_2.11.jar
==== spark-packages: tried
http://dl.bintray.com/spark-packages/maven/saurfang/spark-sas7bdat/2.0.0-s_2.11/spark-sas7bdat-2.0.0-s_2.11.pom
-- artifact saurfang#spark-sas7bdat;2.0.0-s_2.11!spark-sas7bdat.jar:
http://dl.bintray.com/spark-packages/maven/saurfang/spark-sas7bdat/2.0.0-s_2.11/spark-sas7bdat-2.0.0-s_2.11.jar
::::::::::::::::::::::::::::::::::::::::::::::
:: UNRESOLVED DEPENDENCIES ::
::::::::::::::::::::::::::::::::::::::::::::::
:: saurfang#spark-sas7bdat;2.0.0-s_2.11: not found
::::::::::::::::::::::::::::::::::::::::::::::
:::: ERRORS
Server access error at url http://dl.bintray.com/spark-packages/maven/saurfang/spark-sas7bdat/2.0.0-s_2.11/spark-sas7bdat-2.0.0-s_2.11.pom (java.net.SocketException: Unexpected end of file from server)
Server access error at url http://dl.bintray.com/spark-packages/maven/saurfang/spark-sas7bdat/2.0.0-s_2.11/spark-sas7bdat-2.0.0-s_2.11.jar (java.net.SocketException: Unexpected end of file from server)
:: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS
Exception in thread "main" java.lang.RuntimeException: [unresolved dependency: saurfang#spark-sas7bdat;2.0.0-s_2.11: not found]
at org.apache.spark.deploy.SparkSubmitUtils$.resolveMavenCoordinates(SparkSubmit.scala:1076)
at org.apache.spark.deploy.SparkSubmit$.prepareSubmitEnvironment(SparkSubmit.scala:294)
at org.apache.spark.deploy.SparkSubmit$.submit(SparkSubmit.scala:158)
at org.apache.spark.deploy.SparkSubmit$.main(SparkSubmit.scala:124)
at org.apache.spark.deploy.SparkSubmit.main(SparkSubmit.scala)
Error in spark_connect_gateway(gatewayAddress, gatewayPort, sessionId, :
Gateway in localhost:8880 did not respond.
`I had a working Ingress controller version 1.0.0 (Bitnami). It stopped working one fine morning, and it appeared that the error was due to the version being depricated. Now I tried to upgrade this version, but started getting errors. I delete ingress and reinstalled it again, and this time from Bitnami repo which pulled the latest image. It is throwing errors. I created a new AKS cluster and installed ingress on it from the same repo, and it seems to work perfectly fine. Can somebody help me understand how this can be fixed please? I have over 120 services running on this cluster, and starting over would mean a lot of effort and time.
E0419 10:57:29.245933 1 queue.go:130] "requeuing" err="\n-------------------------------------------------------------------------------\nError: exit status 1\n2022/04/19 10:57:29 [warn] 25#25: the \"http2_max_field_size\" directive is obsolete, use the \"large_client_header_buffers\" directive instead in /tmp/nginx-cfg2573211911:143\nnginx: [warn] the \"http2_max_field_size\" directive is obsolete, use the \"large_client_header_buffers\" directive instead in /tmp/nginx-cfg2573211911:143\n2022/04/19 10:57:29 [warn] 25#25: the \"http2_max_header_size\" directive is obsolete, use the \"large_client_header_buffers\" directive instead in /tmp/nginx-cfg2573211911:144\nnginx: [warn] the \"http2_max_header_size\" directive is obsolete, use the \"large_client_header_buffers\" directive instead in /tmp/nginx-cfg2573211911:144\n2022/04/19 10:57:29 [warn] 25#25: the \"http2_max_requests\" directive is obsolete, use the \"keepalive_requests\" directive instead in /tmp/nginx-cfg2573211911:145\nnginx: [warn] the \"http2_max_requests\" directive is obsolete, use the \"keepalive_requests\" directive instead in /tmp/nginx-cfg2573211911:145\n2022/04/19 10:57:29 [emerg] 25#25: \"location\" directive is not allowed here in /tmp/nginx-cfg2573211911:783\nnginx: [emerg] \"location\" directive is not allowed here in /tmp/nginx-cfg2573211911:783\nnginx: configuration file /tmp/nginx-cfg2573211911 test failed\n\n-------------------------------------------------------------------------------\n" key="initial-sync"
I0419 10:57:29.246021 1 event.go:282] Event(v1.ObjectReference{Kind:"Pod", Namespace:"nginx-ingress", Name:"nginx-nginx-ingress-controller-5575846679-bjwkp", UID:"9e5641ae-345c-4d3c-a840-83c143f07fd3", APIVersion:"v1", ResourceVersion:"5932936", FieldPath:""}): type: 'Warning' reason: 'RELOAD' Error reloading NGINX:
-------------------------------------------------------------------------------
Error: exit status 1
2022/04/19 10:57:29 [warn] 25#25: the "http2_max_field_size" directive is obsolete, use the "large_client_header_buffers" directive instead in /tmp/nginx-cfg2573211911:143
nginx: [warn] the "http2_max_field_size" directive is obsolete, use the "large_client_header_buffers" directive instead in /tmp/nginx-cfg2573211911:143
2022/04/19 10:57:29 [warn] 25#25: the "http2_max_header_size" directive is obsolete, use the "large_client_header_buffers" directive instead in /tmp/nginx-cfg2573211911:144
nginx: [warn] the "http2_max_header_size" directive is obsolete, use the "large_client_header_buffers" directive instead in /tmp/nginx-cfg2573211911:144
2022/04/19 10:57:29 [warn] 25#25: the "http2_max_requests" directive is obsolete, use the "keepalive_requests" directive instead in /tmp/nginx-cfg2573211911:145
nginx: [warn] the "http2_max_requests" directive is obsolete, use the "keepalive_requests" directive instead in /tmp/nginx-cfg2573211911:145
2022/04/19 10:57:29 [emerg] 25#25: "location" directive is not allowed here in /tmp/nginx-cfg2573211911:783
nginx: [emerg] "location" directive is not allowed here in /tmp/nginx-cfg2573211911:783
nginx: configuration file /tmp/nginx-cfg2573211911 test failed
It turns out the problem was with the ingress class name "nginx". I re-deployed the ingress controller, this time with a values file and ingressclass name as dev-nginx and this seems to resolve the issue. I then had to delete the existing ingressClass and re-deploy ingress to fix the issue.
E0421 07:40:56.183407 7 main.go:122] Unexpected error searching IngressClass: ingressclasses.networking.k8s.io "nginx" is forbidden: User "system:serviceaccount:default:ingress-nginx" cannot get resource "ingressclasses" in API group "networking.k8s.io" at the cluster scope
W0421 07:40:56.183431 7 main.go:125] No IngressClass resource with name nginx found. Only annotation will be us
Weird problem with SBT 0.13.13:
I explicitly add local Maven repository to the build (that's where the last dependency below should come from):
resolvers in ThisBuild += "Local Maven Repository" at "file://"+Path.userHome.absolutePath+"/.m2/repository"
lazy val lostchildDataImpl = project("lostchild-data-impl")
.settings(
//resolvers += Resolver.mavenLocal,
version := "1.0-SNAPSHOT"
, libraryDependencies ++= Seq(
lagomJavadslApi,
lagomJavadslJackson,
lagomJavadslPersistenceCassandra,
lagomJavadslTestKit,
lagomJavadslPubSub
, lagomJavadslKafkaBroker
)
, libraryDependencies += "com.huawei.aspen" % "lagom" % "1.0-SNAPSHOT"
)
I can see it's added correctly:
> show lostchild-data-impl/resolvers
[info] * Local Maven Repository: file:///home/aromanov/.m2/repository
> show lostchild-data-impl/externalResolvers
[info] * FileRepository(local,FileConfiguration(true,None),Patterns(ivyPatterns=List(${ivy.home}/local/[organisation]/[module]/(scala_[scalaVersion]/)(sbt_[sbtVersion]/)[revision]/[type]s/[artifact](-[classifier]).[ext]), artifactPatterns=List(${ivy.home}/local/[organisation]/[module]/(scala_[scalaVersion]/)(sbt_[sbtVersion]/)[revision]/[type]s/[artifact](-[classifier]).[ext]), isMavenCompatible=false, descriptorOptional=false, skipConsistencyCheck=false))
[info] * URLRepository(ivy-proxy,Patterns(ivyPatterns=List(http://10.122.85.159:9081/nexus/content/groups/sbt-plugins/[organization]/[module]/(scala_[scalaVersion]/)(sbt_[sbtVersion]/)[revision]/[type]s/[artifact](-[classifier]).[ext]), artifactPatterns=List(http://10.122.85.159:9081/nexus/content/groups/sbt-plugins/[organization]/[module]/(scala_[scalaVersion]/)(sbt_[sbtVersion]/)[revision]/[type]s/[artifact](-[classifier]).[ext]), isMavenCompatible=false, descriptorOptional=false, skipConsistencyCheck=false))
[info] * maven-proxy: http://10.122.85.159:9081/nexus/content/groups/public
[info] * Local Maven Repository: file:///home/aromanov/.m2/repository
But the repository isn't accessed. On debug level I see:
> lostchild-data-impl/update
... lots of output for other dependencies
[debug] == resolving dependencies com.huawei.cloud#lostchild-data-impl_2.11;1.0-SNAPSHOT->com.huawei.aspen#lagom;1.0-SNAPSHOT [compile->default(compile)]
[debug] dependency descriptor has been mediated: dependency: org.scala-lang#scala-compiler;2.11.8 {scala-tool=[default, optional(default)]} => dependency: org.scala-lang#scala-compiler;2.11.8 {scala-tool=[default, optional(default)]}
[debug] dependency descriptor has been mediated: MergedDescriptors(dependency: org.scala-lang#scala-library;2.11.8 {scala-tool=[default, optional(default)]},dependency: org.scala-lang#scala-library;2.11.8 {compile=[default(compile)]}) => dependency: org.scala-lang#scala-library;2.11.8 {scala-tool=[default, optional(default)], compile=[default(compile)]}
[info] Resolving com.huawei.aspen#lagom;1.0-SNAPSHOT ...
[debug] sbt-chain: Checking cache for: dependency: com.huawei.aspen#lagom;1.0-SNAPSHOT {compile=[default(compile)]}
[debug] don't use cache for com.huawei.aspen#lagom;1.0-SNAPSHOT: changing=true
[info] Resolving com.huawei.aspen#lagom;1.0-SNAPSHOT ...
[debug] sbt-chain-delegate is changing. Checking all resolvers on the chain
[debug] sbt-chain-delegate: Checking cache for: dependency: com.huawei.aspen#lagom;1.0-SNAPSHOT {compile=[default(compile)]}
[debug] don't use cache for com.huawei.aspen#lagom;1.0-SNAPSHOT: changing=true
[debug] don't use cache for com.huawei.aspen#lagom;1.0-SNAPSHOT: changing=true
[debug] tried /home/aromanov/.ivy2/local/com.huawei.aspen/lagom/1.0-SNAPSHOT/ivys/ivy.xml
[debug] local: no ivy file found for com.huawei.aspen#lagom;1.0-SNAPSHOT
[debug] don't use cache for com.huawei.aspen#lagom;1.0-SNAPSHOT: changing=true
[debug] CLIENT ERROR: Not Found url=https://repo1.maven.org/maven2/com/huawei/aspen/lagom/1.0-SNAPSHOT/maven-metadata.xml
[debug] maven-metadata not available: https://repo1.maven.org/maven2/com/huawei/aspen/lagom/1.0-SNAPSHOT/maven-metadata.xml
[debug] tried https://repo1.maven.org/maven2/com/huawei/aspen/lagom/1.0-SNAPSHOT/lagom-1.0-SNAPSHOT.pom
[debug] CLIENT ERROR: Not Found url=https://repo1.maven.org/maven2/com/huawei/aspen/lagom/1.0-SNAPSHOT/lagom-1.0-SNAPSHOT.pom
[debug] public: no ivy file found for com.huawei.aspen#lagom;1.0-SNAPSHOT
[debug] don't use cache for com.huawei.aspen#lagom;1.0-SNAPSHOT: changing=true
[debug] tried https://repo.typesafe.com/typesafe/ivy-releases/com.huawei.aspen/lagom/1.0-SNAPSHOT/ivys/ivy.xml
[debug] CLIENT ERROR: Not Found url=https://repo.typesafe.com/typesafe/ivy-releases/com.huawei.aspen/lagom/1.0-SNAPSHOT/ivys/ivy.xml
[debug] typesafe-ivy-releases: no ivy file found for com.huawei.aspen#lagom;1.0-SNAPSHOT
[debug] don't use cache for com.huawei.aspen#lagom;1.0-SNAPSHOT: changing=true
[debug] tried https://repo.scala-sbt.org/scalasbt/ivy-snapshots/com.huawei.aspen/lagom/1.0-SNAPSHOT/ivys/ivy.xml
[debug] CLIENT ERROR: Not Found url=https://repo.scala-sbt.org/scalasbt/ivy-snapshots/com.huawei.aspen/lagom/1.0-SNAPSHOT/ivys/ivy.xml
[debug] sbt-ivy-snapshots: no ivy file found for com.huawei.aspen#lagom;1.0-SNAPSHOT
[warn] module not found: com.huawei.aspen#lagom;1.0-SNAPSHOT
[warn] ==== local: tried
[warn] /home/aromanov/.ivy2/local/com.huawei.aspen/lagom/1.0-SNAPSHOT/ivys/ivy.xml
[warn] ==== public: tried
[warn] https://repo1.maven.org/maven2/com/huawei/aspen/lagom/1.0-SNAPSHOT/lagom-1.0-SNAPSHOT.pom
[warn] ==== typesafe-ivy-releases: tried
[warn] https://repo.typesafe.com/typesafe/ivy-releases/com.huawei.aspen/lagom/1.0-SNAPSHOT/ivys/ivy.xml
[warn] ==== sbt-ivy-snapshots: tried
[warn] https://repo.scala-sbt.org/scalasbt/ivy-snapshots/com.huawei.aspen/lagom/1.0-SNAPSHOT/ivys/ivy.xml
I've also tried moving resolvers into the project's settings or using Resolver.mavenLocal instead of specifying the path explicitly. In a similar question, adding directly to externalResolvers instead of resolvers worked for someone. Neither helps in my case.
In the build.sbt for my lift project, I have a dependency on the paypal library
"net.liftmodules" % "paypal_2.6" % "1.3-SNAPSHOT",
At build time (e.g. sbt compile), the module cannot be found. What is confusing me is that if I check in the sonatype repo, the expected dependency is there
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
My question is why is sbt not finding a dependency that clearly exists>
[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
I updated my sonatype resolvers to use https
resolvers ++= Seq("snapshots" at "https://oss.sonatype.org/content/repositories/snapshots",
"releases" at "https://oss.sonatype.org/content/repositories/releases"
)
problem solved.
We are suddenly getting failures on the build server (typesafe and maven repos are proxied through our internal Nexus repo) for a project that successfully built with sbt 0.13.5 (tried upgrading to 0.13.6, still not working) Any ideas?
EDIT: note, works fine when run locally
[warn] module not found: com.typesafe.sbt#sbt-pgp;0.8.2
[warn] ==== local: tried
[warn] /home/bisonadm/.ivy2/local/com.typesafe.sbt/sbt-pgp/scala_2.10/sbt_0.13/0.8.2/ivys/ivy.xml
[warn] ==== typesafe-ivy-releases: tried
[warn] https://repo.typesafe.com/typesafe/ivy-releases/com.typesafe.sbt/sbt-pgp/0.8.2/ivys/ivy.xml
[warn] ==== public: tried
[warn] https://repo1.maven.org/maven2/com/typesafe/sbt/sbt-pgp_2.10_0.13/0.8.2/sbt-pgp-0.8.2.pom
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: UNRESOLVED DEPENDENCIES ::
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: com.typesafe.sbt#sbt-pgp;0.8.2: not found
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn]
[warn] Note: Some unresolved dependencies have extra attributes. Check that these dependencies exist with the requested attributes.
[warn] com.typesafe.sbt:sbt-pgp:0.8.2 (sbtVersion=0.13, scalaVersion=2.10)
[warn]
[warn] Note: Unresolved dependencies path:
[warn] com.typesafe.sbt:sbt-pgp:0.8.2 (sbtVersion=0.13, scalaVersion=2.10)
[warn] +- org.scalastyle:scalastyle-sbt-plugin:0.5.0 (sbtVersion=0.13, scalaVersion=2.10) (/ahp_agents/ec/workspace/T_COMMON_master_full_CI_J4350527/common/project/plugins.sbt#L5-6)
[warn] +- default:common-build:0.1-SNAPSHOT (sbtVersion=0.13, scalaVersion=2.10)
sbt.ResolveException: unresolved dependency: com.typesafe.sbt#sbt-pgp;0.8.2: not found
at sbt.IvyActions$.sbt$IvyActions$$resolve(IvyActions.scala:243)
at sbt.IvyActions$$anonfun$updateEither$1.apply(IvyActions.scala:158)
at sbt.IvyActions$$anonfun$updateEither$1.apply(IvyActions.scala:156)
at sbt.IvySbt$Module$$anonfun$withModule$1.apply(Ivy.scala:147)
at sbt.IvySbt$Module$$anonfun$withModule$1.apply(Ivy.scala:147)
at sbt.IvySbt$$anonfun$withIvy$1.apply(Ivy.scala:124)
at sbt.IvySbt.sbt$IvySbt$$action$1(Ivy.scala:56)
at sbt.IvySbt$$anon$3.call(Ivy.scala:64)
at xsbt.boot.Locks$GlobalLock.withChannel$1(Locks.scala:93)
at xsbt.boot.Locks$GlobalLock.xsbt$boot$Locks$GlobalLock$$withChannelRetries$1(Locks.scala:78)
at xsbt.boot.Locks$GlobalLock$$anonfun$withFileLock$1.apply(Locks.scala:97)
at xsbt.boot.Using$.withResource(Using.scala:10)
at xsbt.boot.Using$.apply(Using.scala:9)
at xsbt.boot.Locks$GlobalLock.ignoringDeadlockAvoided(Locks.scala:58)
at xsbt.boot.Locks$GlobalLock.withLock(Locks.scala:48)
at xsbt.boot.Locks$.apply0(Locks.scala:31)
at xsbt.boot.Locks$.apply(Locks.scala:28)
at sbt.IvySbt.withDefaultLogger(Ivy.scala:64)
at sbt.IvySbt.withIvy(Ivy.scala:119)
at sbt.IvySbt.withIvy(Ivy.scala:116)
at sbt.IvySbt$Module.withModule(Ivy.scala:147)
at sbt.IvyActions$.updateEither(IvyActions.scala:156)
at sbt.Classpaths$$anonfun$sbt$Classpaths$$work$1$1.apply(Defaults.scala:1282)
at sbt.Classpaths$$anonfun$sbt$Classpaths$$work$1$1.apply(Defaults.scala:1279)
at sbt.Classpaths$$anonfun$doWork$1$1$$anonfun$84.apply(Defaults.scala:1309)
at sbt.Classpaths$$anonfun$doWork$1$1$$anonfun$84.apply(Defaults.scala:1307)
at sbt.Tracked$$anonfun$lastOutput$1.apply(Tracked.scala:35)
at sbt.Classpaths$$anonfun$doWork$1$1.apply(Defaults.scala:1312)
at sbt.Classpaths$$anonfun$doWork$1$1.apply(Defaults.scala:1306)
at sbt.Tracked$$anonfun$inputChanged$1.apply(Tracked.scala:45)
at sbt.Classpaths$.cachedUpdate(Defaults.scala:1324)
at sbt.Classpaths$$anonfun$updateTask$1.apply(Defaults.scala:1264)
at sbt.Classpaths$$anonfun$updateTask$1.apply(Defaults.scala:1242)
at scala.Function1$$anonfun$compose$1.apply(Function1.scala:47)
at sbt.$tilde$greater$$anonfun$$u2219$1.apply(TypeFunctions.scala:40)
at sbt.std.Transform$$anon$4.work(System.scala:63)
at sbt.Execute$$anonfun$submit$1$$anonfun$apply$1.apply(Execute.scala:226)
at sbt.Execute$$anonfun$submit$1$$anonfun$apply$1.apply(Execute.scala:226)
at sbt.ErrorHandling$.wideConvert(ErrorHandling.scala:17)
at sbt.Execute.work(Execute.scala:235)
at sbt.Execute$$anonfun$submit$1.apply(Execute.scala:226)
at sbt.Execute$$anonfun$submit$1.apply(Execute.scala:226)
at sbt.ConcurrentRestrictions$$anon$4$$anonfun$1.apply(ConcurrentRestrictions.scala:159)
at sbt.CompletionService$$anon$2.call(CompletionService.scala:28)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
[error] (*:update) sbt.ResolveException: unresolved dependency: com.typesafe.sbt#sbt-pgp;0.8.2: not found
It appears they've moved to Bintray recently (and perhaps cleaning up other locations?).
With the recent release of sbt-pgp 1.0-M1 I can find the plugin's binaries at https://bintray.com/sbt/sbt-plugin-releases/sbt-pgp/1.0-M1/view.
As you can read in Improvements in 0.13.6 Release Notes:
Adds Resolver.jcenterRepo and Resolver.bintrayRepo(owner, repo) to add Bintray easier.
With all that said, the following worked for me (mind I haven't worked with the plugin before):
project/sbt-pgp.sbt
resolvers += Resolver.jcenterRepo
addSbtPlugin("com.typesafe.sbt" % "sbt-pgp" % "1.0-M1")
project/build.properties
sbt.version=0.13.6
No other files were needed to boot sbt shell (with sbt) and query for available plugins:
> plugins
In file:/Users/jacek/sandbox/sbt-pgp/
sbt.plugins.IvyPlugin: enabled in sbt-pgp
sbt.plugins.JvmPlugin: enabled in sbt-pgp
sbt.plugins.CorePlugin: enabled in sbt-pgp
sbt.plugins.JUnitXmlReportPlugin: enabled in sbt-pgp
com.typesafe.sbt.SbtPgp: enabled in sbt-pgp