What’s the best practice for creating a library with all the dependencies necessary for implementation in the consumer project? e.g.: I’m generating gPRC service classes via

protobuf

plugin and packaging into a jar, then in the consumer project I want to add this library(jar file) as a dependency in the gradle file and be ready to create a blocking stub, which requires the

io.grpc

library to be present? 🤔

is there something wrong with just depending on it?

I’d be uploading this jar to a repo, so if I bundle these dependencies together with the compiled classes, the file could get bigger(~13MB)

is there something wrong with using transitive dependencies?

Just publish it as a maven dependency, the build tools (Gradle, Maven) will ensure the correct transitive dependencies are downloaded alongside your library. https://docs.gradle.org/current/userguide/publishing_maven.html. Gradle is smart enough to bundle the generated classes with the library (may need some additional Gradle configuration, depending on how those classes are being generated)

Oh nice! I’ll check it out! Thanks @Casey Brooks and @octylFractal