Closed tmulle closed 1 year ago
Ok, turns out it was my fault and misread the docs for the protobuf-maven-plugin
.
I was using includes
when I should've been using:
<additionalProtoPathElements>
<additionProtoPathElement>${project.build.directory}/protos/protobuf</additionProtoPathElement>
</additionalProtoPathElements>
I found it by cloning the repo for the plugin and stepping through the debugger and realized the error.
I know this project isn't maintained any more but hoping someone might have an idea.
Using the configuration below the plugin finds my source protos in
src/main/proto
but it doesn't find my base protos to import which we use for compilation.As soon as I try to use the includes param to specify the location of our expanded dependency, the plugin says "No protos to compile" which isn't true.
Any ideas?