It can be useful for projects using this jetcd project to be able to start etcd server in their respective tests. And not just for tests, but possibly also to simplify at least development (but probably never production) set ups - think "embedded database" (à la Derby, h2, MariaDB4j & Co.).

The tests in this project use Testcontainers. Projects using jetcd could also use Testcontainers for above. For simple Windows users, or even Linux noobs without Docker installed, this could sometimes be a PITA.

An alternative is to just start jetcd via exec. I'm doing this over in my EtcdLauncher. (That as-is currently just assumes that one has done e.g. sudo dnf install etcd ... it's also imaginable to make native binaries available as dependencies, such as how e.g. MariaDB4j and similar projects for other databases do it.)

Would a contribution with such a Launcher, or perhaps even some work for a simple etcd launch API which can start it either via Testcontainers or via exec, be of interest to this project?

If so, would using (and having a dependency from a jetcd:launcher artifact to) https://github.com/vorburger/ch.vorburger.exec for such a feature be acceptable, or do you have any preference for another similar launcher utility?