Simon Herter
Simon Herter
We have an internal caching mechanism that is **_more efficient_** than what would be possible with Gradle's inputs/outputs based caching approach. Since we format source files, our inputs and outputs...
Also see https://github.com/sherter/google-java-format-gradle-plugin/issues/18.
That's probably right. This whole distributed build cache thing came after this plugin was conceived. I'll have to look into this...
I understand that some people don't have another choice than forking and adjusting google-java-format to their needs. I can't really 'support' forks of google-java-format though, as I don't have access...
Since this report was labeled with `type:bug` and `priority: p2`, I assume that you really do consider this a bug in jib that should be fixed. Is there an ETA...