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
Because of the way my protos are structured (in different directories with import statements assuming a specific path in the proto path parameter of the protoc command), I am getting duplicate proto errors when I try to use the plugin to compile my proto files. I believe because it is finding some protos in the directory specified in an import statement and in the local extractedProtosDir that the plugin creates.
Is there a way to tell the plugin to NOT copy the proto files specified in the dependencies into the extractedProtosDir? I've tried disabling the extractedProto task and the compile output shows that the extractedProto task is skipped while the generateProto task is run (shows as UP-TO-DATE), but no java files are actually generated. I'm not sure if this is because generateProto is dependent on extractedProto, but I've tried removing the dependency as well (using generateProto.dependsOn.remove("extractedProto")) with no success.
It would be great that if the extractedProtosDir is not specified that instead of using a default directory, it doesn't actually copy over the proto files at all.
The text was updated successfully, but these errors were encountered:
Because of the way my protos are structured (in different directories with import statements assuming a specific path in the proto path parameter of the protoc command), I am getting duplicate proto errors when I try to use the plugin to compile my proto files. I believe because it is finding some protos in the directory specified in an import statement and in the local extractedProtosDir that the plugin creates.
Is there a way to tell the plugin to NOT copy the proto files specified in the dependencies into the extractedProtosDir? I've tried disabling the extractedProto task and the compile output shows that the extractedProto task is skipped while the generateProto task is run (shows as UP-TO-DATE), but no java files are actually generated. I'm not sure if this is because generateProto is dependent on extractedProto, but I've tried removing the dependency as well (using generateProto.dependsOn.remove("extractedProto")) with no success.
It would be great that if the extractedProtosDir is not specified that instead of using a default directory, it doesn't actually copy over the proto files at all.
The text was updated successfully, but these errors were encountered: