Closed RdeWilde closed 5 years ago
Looking at the example project I think it might be having issues pulling the snapshot from your local kroto branch.
You can try setting the plugin using an absolute path to your local kroto plugin build.
configure<ProtobufConfigurator> {
generatedFilesBaseDir = "$projectDir/src/"
protoc {
artifact = "com.google.protobuf:protoc:3.9.0"
}
plugins {
id("krotoPlus") {
path = "path/to/protoc-gen-kroto-plus/build/libs/protoc-gen-kroto-plus-0.4.1-SNAPSHOT-jvm8.jar"
}
}
...
}
That actualy did work \o/ Thank you very much!
Shouldn't the composite build have replaced it with the local version?
Not entirely sure how composite builds would work with local development. I think the previous config might have worked if the generateProto task depended on publishing to mavenLocal.
I understand, thanks again for helping me out, this is solved for now :+1:
The code generation now works thru Kotlinpoet. Had to apply a few small fixes, but now it's awesome.
I try to extend the
CompilerConfig
with theProtobufMessages
as provided in a PR here (https://github.com/marcoferrer/kroto-plus/pull/13/files).I migrated all the code, but I can't seem to solve this error when I run
generateProto
on my sample projectapp
:I do have this field in my
config.proto
:Also this field is present in
CompilerConfig.java
:And it is also in the CompilerConfig initialization
In krotoPlusConfig.yaml:
Complete error message from the sample project:
I am unsure what else I could be doing wrong?
Hopefully someone can help me out, been stuck on this wayyy too long.