@jer @manishearth you might want to look at Bazel or equivalent, so you can have the build system download all of the dependencies for Diplomat contributors.

Here's what I did for the tweet parser: https://sayrer.com/blog/whats-in-a-tweet/#bazel

@sayrer @jer I'm a bit confused about this suggestion, diplomat is a rust project, if you have rust installed you can hack on it, you don't need dependency management beyond cargo.

Running tests for individual backend may need more deps but it's mostly like "if you're working on Dart you need a standard Dart environment" which like...fair. It's explicitly designed so that you don't need to care about backends you don't work on

@sayrer @jer I think you are trying to tell me to use a tool to solve a problem I do not have.

diplomat-java is a special case and not a general issue. you're extrapolating from a years-old README

@sayrer @jer diplomat-java is experimental, we're not sure about the approach, and it relies on *weird* java tooling, not regular stuff. putting that together, I wanted it prototyped outside.

"use bazel" is a strictly worse solution: people like me doing cross-language diplomat dev still have to set up a new tool, except now the people who were working on just their language *also* need to do that

@sayrer @jer like, I work at Google, I use Blaze, I love it, and I also think it is a very poor fit for Diplomat.

Right now we are a rust tool where the only additional dep is your language *if you want to run integration tests*, and cargo-make (not mandatory, just makes it easier). This is a desired state.