Where would you define your project's Gradle convention plugin? :one: in buildSrc :two: included bui...

# gradle

[tseisel]

Where would you define your project's Gradle convention plugin?
1️⃣ in buildSrc
2️⃣ included build
3️⃣ Elsewhere

I just discovered from that article that buildSrc and included builds both have performance issues...

[Trevor Stone]

My project has a LOT less than 3500 gradle modules, so buildSrc works well for my team

[ephemient]

~300 modules here, in the process of migrating from buildSrc to multiple included builds instead of a single build-logic included build. it works well

[Chris Lee]

exclusively using build-logic included builds (in fact, added plugin code to prohibit buildSrc). works well.

[mike.holler]

The idea of a project with thousands of modules terrifies me.

[mike.holler]

Are people with that many modules are doing a module-by-feature approach?

[thanksforallthefish]

unfortunately 1 for now

[darkmoon_uk]

~40 modules here; I recently migrated from buildSrc to included build. Do it, it's worth it! Any time you have to edit configuration the feedback cycles are so much faster due to no more cache invalidation. You'll quickly save yourself a day from a few hour's investment.

[K Merle]

@mike.holler sounds like module-by-class 😄