Skip to content
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

Use a jar-packaged protoc instead requiring pre installed #28653

Open
johanandren opened this issue Feb 27, 2020 · 0 comments
Open

Use a jar-packaged protoc instead requiring pre installed #28653

johanandren opened this issue Feb 27, 2020 · 0 comments
Labels
discuss Tickets that need some discussion before proceeding. Not decided if it's a good idea. t:build

Comments

@johanandren
Copy link
Member

I've just stumbled on having the wrong protoc version installed for the Nth time. It would be nice if we could get rid of that as an external dependency of the build (when changing the files) and instead use a jar-packaged set version like how Akka gRPC does it.

I wouldn't want to change the way we do it with generating explicitly and then checking in the generated sources, only that we'd automagically have the right protoc version pulled in by the build.

@johanandren johanandren added t:build discuss Tickets that need some discussion before proceeding. Not decided if it's a good idea. labels Feb 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss Tickets that need some discussion before proceeding. Not decided if it's a good idea. t:build
Projects
None yet
Development

No branches or pull requests

1 participant