Shade protobuf for SingularityClient/SingularityBase

[ssalinas]

Systems running protobuf 2.5 were having issues since mesos 1.x pulls in protobuf 2.6.1

@stevegutz

[stevie400]

Looks reasonable to me. For things like protobuf its also common to add the version to the package name, eg com.hubspot.singularity.shaded.com.google.protobuf.twosixone or whatever.

Is shading just the client is enough? It doesn't leak into models or anything?

[ssalinas]

Good point, might need it in SingularityBase as well. I can add that

[ssalinas]

Ended up being easier to shade mesos completely here

[baconmania]

🚢

[ssalinas]

There are a few more steps we need to take to solve the protos issues. This is a step in the right direction, so going to merge this and open an additional PR rather than continuing to work off this branch

[stevie400]

I don't think think that this will solve your problem. The issue isn't using an unshaded mesos, it's that mesos is using an unshaded protobuf that conflicts with what we want. So you want to rewrite the protobuf classes inside mesos, not mesos itself.