Open gmendonca opened 4 years ago
So, the more I think about it, the more this seems like an issue for coursier.
Have you thought of opening an issue there?
Yeah, this was my first thought but then I found this https://github.com/coursier/coursier/issues/164 and decided to do it here. But maybe it wasn't a good call, I'll read more and if that's the case, I'll open an issue there.
About using the original code: It was designed sbt
plugin and it has a different naming pattern, so not sure how resolve this dependency throught bazel: https://stackoverflow.com/a/54585431/4051109
Probably a dead end :(
Not sure if useful, but I had the same problem with
sbt
. When trying to resolve maven artificats from a private s3 path, theCouriserResolver
would fail. Forsbt
this problems was solved by https://github.com/frugalmechanic/fm-sbt-s3-resolverI pretty much hacked its code into
CoursierResolver
to unblock myself into usingbazel-deps
. I decided to share in case anyone bumps into the same problem. I'm not sure if this is the way to go, but I'll be happy to do any modifications if this is useful.