[jira] [Updated] (MESOS-5642) Move include/mesos/v1/master/allocator.proto to its own directory and package
[ https://issues.apache.org/jira/browse/MESOS-5642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhitao Li updated MESOS-5642: - Fix Version/s: 1.0.0 > Move include/mesos/v1/master/allocator.proto to its own directory and package > - > > Key: MESOS-5642 > URL: https://issues.apache.org/jira/browse/MESOS-5642 > Project: Mesos > Issue Type: Bug > Components: HTTP API >Reporter: Zhitao Li >Assignee: Zhitao Li > Fix For: 1.0.0 > > > Right now, all protobuf used in `include/mesos/v1` is in their own directory > and package except for allocator. > We should do the same for it for both consistency, as well as protobuf > compiler friendliness (e.g. golang compiler doesn't work well when two .proto > files generates messages into same package). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5642) Move include/mesos/v1/master/allocator.proto to its own directory and package
[ https://issues.apache.org/jira/browse/MESOS-5642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhitao Li updated MESOS-5642: - Component/s: HTTP API > Move include/mesos/v1/master/allocator.proto to its own directory and package > - > > Key: MESOS-5642 > URL: https://issues.apache.org/jira/browse/MESOS-5642 > Project: Mesos > Issue Type: Bug > Components: HTTP API >Reporter: Zhitao Li >Assignee: Zhitao Li > > Right now, all protobuf used in `include/mesos/v1` is in their own directory > and package except for allocator. > We should do the same for it for both consistency, as well as protobuf > compiler friendliness (e.g. golang compiler doesn't work well when two .proto > files generates messages into same package). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
