-
-
Notifications
You must be signed in to change notification settings - Fork 678
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
Uber's gomock 0.5.0 is incompatible with rules_go's gomock.bzl #4153
Comments
We are not planning to support Uber's gomock in rules_go. The plan is to move it to the same repo as Uber's gomock so they can co-evolve easily. The maintainers of Uber's gomock agreed with the plan. It's in my backlog, but any helping hand will be welcomed. |
@linzhp, to clarify, is the plan to move gomock.bzl to the Uber gomock repo? Is this just as simple as creating a PR in the Uber gomock repo copying it over? |
Yes, the first PR would be just that and maybe update the mockgen tool used by the rule to be Uber's mockgen. As followups, we should also
|
FYI: uber-go/mock#231 |
What version of rules_go/gazelle/bazel/gomock are you using?
What happened?
reflect
mode got dropped, and so the latest release no longer generates a source file that then gets compiled into a binary, which rules_go expects it to do. Instead, a newpackage
mode was added, which calls thego
binary, which is unavailable in the Bazel sandbox.I tried to modify rules_go to support the new mode but my bazel-fu isn't quite at the level needed for that 😄
Error
The text was updated successfully, but these errors were encountered: