bazelbuild / migration-tooling

Migration tools for Bazel
Apache License 2.0
44 stars 30 forks source link

"bazel run //generate_workspace" regressed at HEAD (a5e68740) #75

Open erickj opened 6 years ago

erickj commented 6 years ago

previous to the current HEAD the following would run as expected:

bazel run //generate_workspace -- --artifact=io.dropwizard.metrics:metrics-core:3.1.2

producting the expected generate_workspace.bzl

however, as of a5e68740, the same command above prints the following warning and generates an empty bzl file:

WARNING: Could not find any repositories that knew how to resolve io.dropwizard.metrics:metrics-core:3.1.2 (checked )

As of the commit referenced above, there seems to be a new --repositories flag, that when empty yields the rather unhelpful warning above (i.e. "checked [blank]").

However when I try filling in a value for --repositories I see something like:

$ bazel run //generate_workspace -- --artifact=io.dropwizard.metrics:metrics-core:3.1.2 --repositories=https://mvnrepository.com/ .... WARNING: Unable to resolve version

again, creating an empty generate_workspace.bzl file.

Is this expected? If so can the documentation please be updated with new instructions.

JMIsham commented 6 years ago

did you try "http://central.maven.org/maven2/"

erickj commented 6 years ago

But the regression is that I need to specify a repository at all. The code went from working by default to broken by default

jhinrichsen commented 6 years ago

Introducing the --repositories parameter is a wonderful idea, but as of now it is an undocumented feature (on top of the regression)