You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After doing a lot of debugging due to sbt/sbt#2209, I am fairly confident that there is an issue with ivy resolution for the http://rubygems-proxy.torquebox.org/releases repo
A lot of investigation has been done, using both ivyLoggingLevel := UpdateLogging.Full and logLevel in update := Level.Debug (in sbt), and it appears that ivy is just spitting out a FAILURE, without providing any reason, i.e.
This fork may have changed how ivy does resolution in some cases (I doubt its an issue with the mainline ivy, else a lot more people would have complained about it, and the resolution works fine with mainline maven)
After doing a lot of debugging due to sbt/sbt#2209, I am fairly confident that there is an issue with ivy resolution for the
http://rubygems-proxy.torquebox.org/releases
repoA lot of investigation has been done, using both
ivyLoggingLevel := UpdateLogging.Full
andlogLevel in update := Level.Debug
(in sbt), and it appears that ivy is just spitting out aFAILURE
, without providing any reason, i.e.This fork may have changed how
ivy
does resolution in some cases (I doubt its an issue with the mainlineivy
, else a lot more people would have complained about it, and the resolution works fine with mainlinemaven
)For quick reference, here is a trivial
build.sbt
you can use to debug the issue https://gist.github.com/mdedetrich/ea95947c9b8e35a4d849The text was updated successfully, but these errors were encountered: