This message was deleted.

if it’s in a single project, create a

starter

module and expose all the dependencies on the api scope; in each module (perhaps via a convention plugin) add a dependency on the starter. For example, have a

testing-starter

that defines all kinds of test dependencies (kotest, junit, mockk, etc). If the intention is to share these dependencies across projects, a separate

starter

project could be created that does the same thing. Alternately, one could create a bundle in a version catalog (and optionally publish that catalog) to accomplish something similar.

It’s multiple projects with multiple modules :) (company wide projects). Regarding the kind of the module (we have modules with only http clients, modules with only apis, …), I want to add the right set of dependencies in the easiest way for devs. • I’m not going with catalogs because developers would have to use a bundle for implementation dependencies, another one for api dependencies, …. • I thought about creating a kind of meta dependency (or starter dependency). Like what you proposed. With a plugin adding it as dependency in the projet. But I dont know if it’s the best way to achieve what I want.

agreed, bundles aren’t a great fit for this. Seems like publishing a starter lib would work.

Thanks for your feedback 🙂