This message was deleted.

Why do you actually want to do that? Just publish each of the jars individually and any build tool will pull them in automatically. (btw. the

doNotCacheIf

is useless, as

Jar

tasks are not cacheable anyway)

I ended up publishing individually. I just thought it was convenient for the user to only have to depend on a single dependency

you can publish a single "all" module which will transitively include all the rest; your users only need to include that one.

how?

Just make a new project that depends on the other projects and has no jar