Describe the enhancement requested

Arrow uses protobuf-maven-plugin in several modules but not in the recommended way. There are multiple issues like:

• use of compile/compile-custom instead of test-compile/test-compile-custom for test protobufs (causing test classes to be added to the main artifact)
• forcing the output location which causes different execution to overwrite each other (each execution should have their own output directory). When done properly, setting clearOutputDirectory property to false is not necessary anymore
• adding test-compile goal when no test protobufs are present.

The protobuf-maven-plugin is also declared multiple times instead of it managed at the top level

Component(s)

Java