Is there a sensible way to use ProGuard with multi-project builds?

Ah, I see, so you did it by some simple filtering based on filename; thanks for sharing! We have a ton of subprojects and they don’t produce jars that start with a common prefix so that probably wouldn’t be very viable in our case. We ended up splitting library dependencies and project dependencies into separate gradle configurations per-project (and configuring the built-in api configuration to extend from both of them) so they could be accessed/referenced independently in places like the proguard task.