Ah. The Maven build already long since points at https:// for resolution for security. I tried just overriding the resolver for the SBT build, but it doesn't seem to work. I don't understand the SBT build well enough to debug right now. I think it's possible to override resolvers with local config files as a workaround.
On Thu, Jan 16, 2020 at 4:33 PM Dongjoon Hyun <dongjoon.h...@gmail.com> wrote: > > Hi, All. > > As of now, Apache Spark sbt build is broken by the Maven Central repository > policy. > > - > https://stackoverflow.com/questions/59764749/requests-to-http-repo1-maven-org-maven2-return-a-501-https-required-status-an > > > Effective January 15, 2020, The Central Maven Repository no longer supports > > insecure > > communication over plain HTTP and requires that all requests to the > > repository are > > encrypted over HTTPS. > > You can reproduce this locally by the following. > > $ rm -rf ~/.m2/repository/org/apache/apache/18/ > $ build/sbt clean > > The usual suspects are the following two. > > - SBT: sbt 0.13.18 > - Plugin: addSbtPlugin("org.spark-project" % "sbt-pom-reader" % > "1.0.0-spark") > > Bests, > Dongjoon. --------------------------------------------------------------------- To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
