Closed gmendonca closed 4 years ago
This tool does not consult the local ivy or maven cache. Since bazel is focused on reproducibility that is out of scope here.
You can use replacements and a custom scala_import although we don’t have a documentation of that kind of set up. rules_scala has documentation on scala_import and replacements is documented in the readme of this project.
This tool does not consult the local ivy or maven cache. Since bazel is focused on reproducibility that is out of scope here.
So, I was indeed missing something. Thanks for the explanation. I'll see if I can still test without the need to publish it.
Closing as not really an issue.
I did a simple project with
sbt
and abuild.sbt
as follows:The
sbt
version I'm using is 1.3.7After publishing it locally with
sbt +publishLocal
, when I runbazel run //:parse generate -- --repo-root "$MY_PROJ_DIR" --sha-file 3rdparty/workspace.bzl --deps dependencies.yaml
withdependencies.yaml
importing it, I get a:However, when I check with
coursier
CLI, works just fine:coursier resolve com.some.organization:some-project_2.11:0.0.1
Maybe I'm missing something, but I decided to report as I couldn't make it work yet.