You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I have a project https://github.com/bitemyapp/revise which depends on this library. I recently separated the compiled protocol buffers from the project into a separate jar (and dependency). And I also removed the plugin "lein-protobuf" from my project.clj (none of these changes are live yet) and then I deleted all of my .proto files.
My problem is that this still downloads protoc, compiles it and then downloads - a seemingly outdated 2.4.1 - protobuf jar. And in the end it does nothing because there are no .proto files to compile.
My understanding is that lein-protobuf should do the compilation while clojure-protobuf should just use the actual compiled protocol buffers. So what I want is that the user should be able to use them separately.
Also the automatic compilation of the protoc sources probably makes this project explode on windows.
Thanks.
The text was updated successfully, but these errors were encountered:
Hello, I have a project https://github.com/bitemyapp/revise which depends on this library. I recently separated the compiled protocol buffers from the project into a separate jar (and dependency). And I also removed the plugin "lein-protobuf" from my project.clj (none of these changes are live yet) and then I deleted all of my .proto files.
My problem is that this still downloads protoc, compiles it and then downloads - a seemingly outdated 2.4.1 - protobuf jar. And in the end it does nothing because there are no .proto files to compile.
My understanding is that lein-protobuf should do the compilation while clojure-protobuf should just use the actual compiled protocol buffers. So what I want is that the user should be able to use them separately.
Also the automatic compilation of the protoc sources probably makes this project explode on windows.
Thanks.
The text was updated successfully, but these errors were encountered: