New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Builds relying on Scala 2.10.2 artifact in Maven are failing #8772
Comments
Imported From: https://issues.scala-lang.org/browse/SI-8772?orig=1 |
@gourlaysama said (edited on Aug 4, 2014 12:01:31 PM UTC): As a workaround, you can have it download from Sonatype with (in build.sbt): resolvers += Resolver.sonatypeRepo("releases") |
@milessabin said: |
@gourlaysama said (edited on Aug 2, 2014 12:22:16 PM UTC): |
@milessabin said: |
fred aalbue (faalbue) said: Thanks, |
Pradeep Jain (pradeep.jain-at-gmail.com) said: |
Tobias Svensson (svensson.s.t) said: |
fred aalbue (faalbue) said: |
fred aalbue (faalbue) said: However, I just ran my build and got passed the previous 2.10.2 issue and got it deployed to heroku. I still get a 404 at maven repo, so I don't really think it is fixed, but I just got lucky this time and found a mirror where the repo is available. |
@gourlaysama said (edited on Aug 4, 2014 6:17:01 PM UTC): |
Pradeep Jain (pradeep.jain-at-gmail.com) said: |
Patrick Wendell (pwendell) said: |
@jsuereth said: I'd recommend a few things:
Let us know if you're still seeing the original issue or if we can do anything else to help alleviate problems. |
Mark Hibberd (markhibberd) said (edited on Aug 7, 2014 1:39:05 AM UTC): We still see this on all our internal intermittently (approx 1 in 4 fail). I can't share internal builds details easily but as examples of what happens here are some of my argonaut builds that fail intermittently:
The exact scenario that we have is that the projects do not depend on 2.10.2 directly, but are using sbt versions/plugins that do. On travis, reducing the number of platforms helped a fair bit (i.e. just the parallel builds clashing with themselves seems to be enough to trigger it more regularly). If there is anything we can do to help test changes / fixes let me know. This is particularly painful for open source projects who are largely at the mercy of maven central in terms of making it easy for people to clone and build. |
@milessabin said: |
@paulp said: def plugin(m: ModuleID) = Defaults.sbtPluginExtra(m, "0.13", "2.10") excludeAll ExclusionRule("org.scala-lang")
libraryDependencies ++= Seq(
plugin("me.lessis" % "bintray-sbt" % "0.1.2"),
plugin("com.typesafe" % "sbt-mima-plugin" % "0.1.6")
) |
Mark Hibberd (markhibberd) said: |
@paulp said:
Josh - is that a purely theoretical suggestion? I don't see any sign this is possible. |
@jsuereth said: (a) can you post that code to sbt? I'll talk with Eugene at possibly just having that be the default for all sbt plugin dependencies in 0.13.6. Details here: http://docs.travis-ci.com/user/caching/ |
@paulp said: I did post that code in the comments to sbt/sbt#1439 , not sure what you mean by "to sbt" but that's in the neighborhood. |
@jsuereth said: |
@paulp said: |
@milessabin said: |
Samuel Halliday (fommil) said: |
Several Spark users reported this today and it's breaking our build. I narrowed this down to the following: a trivial project build on Scala 2.10.2 can not resolve artifacts correctly:
The same code works for 2.10.1 and 2.10.3. The issue seems to be that maven is returning 404 errors for the entire 2.10.2 directory.
The error message from sbt seems to imply the artifact or POM can not be downloaded, but from what I can tell, the most likely issue is that the parent directory containing them cannot be listed. I can download the pom and jar easily without any issue.
As a workaround, if you have access to the machine where the build is running, you can manually populate your ivy cache with the needed jars:
The text was updated successfully, but these errors were encountered: