[
https://issues.apache.org/jira/browse/HBASE-16263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15386926#comment-15386926
]
stack commented on HBASE-16263:
-------------------------------
nvm. Its a PITA. The hadoop plugin that runs the protoc is primitive. It allows
multiple imports but not output dirs or multiple executions. We could make a
test profile. Would have to have one profile for usual proto files and another
for tests. You'd have to invoke them distinctly. Then would have to doc it. I
think it too much of a PITA. [~eclark]?
> Move all to do w/ protobuf -- *.proto files and generated classes -- under
> hbase-protocol
> -----------------------------------------------------------------------------------------
>
> Key: HBASE-16263
> URL: https://issues.apache.org/jira/browse/HBASE-16263
> Project: HBase
> Issue Type: Sub-task
> Components: Protobufs
> Reporter: stack
> Assignee: stack
> Attachments: HBASE-16263.master.001.patch
>
>
> To better contain our protobuf exposure, keep all to do w/ protobuffing
> inside the hbase-protocol module.
> This task moves rest, examples, and server proto files that do testing and CP
> endpoints etc., under hbase-protocol. The patch is big but it is all just
> moving files.
> interesting to see the copy-paste being done everywhere of proto generation.
> For this reason alone, it is better to have all the protos in the one place
> beside doc on how-to, etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
