Closed jtjeferreira closed 3 years ago
Thanks for sharing! I don't have a direct explanation, but I do observe that class was added between protobuf-java 3.11.5 and 2.12.0. Could it be you have some older version of protobuf-java hanging around in your build somehow?
Thanks for sharing! I don't have a direct explanation, but I do observe that class was added between protobuf-java 3.11.5 and 2.12.0.
You meant 3.12.0 right?
Could it be you have some older version of protobuf-java hanging around in your build somehow?
I dont think so:
The above picture was from plugins dependencies. In the actual project I indeed have 3.11.4...
You meant 3.12.0 right?
Oops, yes ;)
I dont think so:
I'm not familiar with that tool but that at least looks good ;).
The above picture was from plugins dependencies. In the actual project I indeed have 3.11.4...
That might make sense, since the code generation is done in the build. It is also 'sandboxed', though I'm not entirely sure how that works exactly.
Unfortunately I don't think I can be of much further help without a reproducer project...
I'm not familiar with that tool but that at least looks good ;).
It is dependencyBrowseGraph
from https://github.com/sbt/sbt-dependency-graph
Unfortunately I don't think I can be of much further help without a reproducer project...
It might take me a while to reduce this to a reproducer, but I will try next week... Meanwhile maybe @thesamet from scalapb you might have an hint?
@jtjeferreira please provide a minimal reproducible example. We can't tell what's in your build is causing it if we don't see your build.
This no longer happens in 2.x...
Versions used
Akka-grpc version: 1.1.1 sbt version: 1.4.7
Expected Behavior
I have a project compiling correctly with akka-grpc 1.0.2. I expected that when upgrading to 1.1.1 the compilation would also succeed
Actual Behavior
Instead I have the exception:
Relevant logs
Reproducible Test Case
I dont have one except my work project