[
https://issues.apache.org/jira/browse/MESOS-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14711710#comment-14711710
]
Bo Shi commented on MESOS-3309:
-------------------------------
Hi Vinod,
We'd like to persist our framework data along with associated mesos messages.
As an example, our Java-based framework (built using maven) has some protocol
buffer schemas that look like:
{noformat}
import "mesos/mesos.proto"
message StrawManWork {
required StrawManWorkMetadata metadata;
repeated mesos.TaskStatus task_update;
}
{noformat}
The only way to do is to vendor the mesos.proto file. It turns out that the
maven protobuf compiler plugins can detect .proto files in the resources of
dependency artifacts so the duplication from the vendoring approach wouldn't be
necessary if mesos.proto was included in the maven artifact. Is using Mesos
protobuf message schemas in client projects ill-advised?
> Include protobuf .proto files as a resource in the Java artifact
> ----------------------------------------------------------------
>
> Key: MESOS-3309
> URL: https://issues.apache.org/jira/browse/MESOS-3309
> Project: Mesos
> Issue Type: Improvement
> Components: java api
> Affects Versions: 0.23.0, 0.24.0
> Reporter: Bo Shi
>
> As far as I can see (or google), Java framework authors that would like to
> re-use Mesos protocol buffer messages need to vendor
> {{include/mesos/mesos.proto}}. If the protobuf schemas were included in the
> artifact as resources, maven protobuf plugin users would not need to vendor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
