Command line too long

[kevinstembridge]

Hi,
We have a large number of proto files to be compiled. We're getting an error about the command line being too long. Is it possible for the plugin to invoke protoc for one file at a time?

[sergei-ivanov]

Hello Kevin,

I must admit we have never hit this limitation before in our environment. The plugin by default hashes paths for dependencies to make command line more compact, but it does not do anything about proto files from the current project.

Invoking protoc separately on each proto file will only work well if those files are not dependent on each other. I can probably add the source proto folder itself into the list of import paths, but I am not sure if it's not going to create some sort of circular reference. Let me experiment with that.

There is a workaround available if you need to address the problem right now. If you can split your proto files into a number of independent groups, you can set up several plugin executions using inclusion/exclusion patterns. The only gotcha is that the plugin clears out the output directory on each run, so each separate execution will need to have its own output directory configured. Clearing out the output directory is more of a nuisance than help and I am going to make it optional in the next release.

Kind regards,
Sergei

[kevinstembridge]

Hi Sergei,
Thanks for looking at this.
We ended up using the maven-exec-plugin to invoke protoc directly and use a wildcard pattern to pick up the proto files. Maybe your plugin could optionally accept a wildcard pattern as well.