Gradle: add support for dependencies in buildSrc

[Tapchicoma]

Gradle has a concept of buildSrc (https://docs.gradle.org/current/userguide/organizing_gradle_projects.html#sec:build_sources) that provides logic for the project build files.

Also it is possible to define there a dependencies (even using common Kotlin files): https://github.com/JLLeitschuh/ktlint-gradle/blob/master/plugin/buildSrc/src/main/kotlin/PluginDependencies.kt

Please add support to updating dependencies defined in buildSrc folder in Groovy, Java or Kotlin file (please also keep in mind closed dependabot/feedback#392)

[JavierSegoviaCordoba]

Gradle 6.8 will include a new official dependencies management.

Source: gradle/gradle#14896

[sindrenm]

Apologies for bumping this thread, but I felt it was worth mentioning that the new dependencies management moved over to the 7.0 RC1 milestone on December 8. In case you're already on 6.8 and want to try this out, as I was. Further progress is tracked in gradle/gradle#15352.

[JavierSegoviaCordoba]

Gradle 7.0 milestone1 is available and the stable version should be available before February ends.

[savvisingh]

What happened to the support for buildSrc?

[JavierSegoviaCordoba]

What happened to the support for buildSrc?

You should stop using buildSrc and move to catalogs, it is not recommend by Gradle.

[sindrenm]

Version catalogs is what was introduced in 7.0. It's still in preview, however.

https://docs.gradle.org/current/userguide/platforms.html

[TSRBerry]

What happened to the support for buildSrc?

You should stop using buildSrc and move to catalogs, it is not recommend by Gradle.

How is it not recommended by Gradle? I have been following their guide to setup my multi-project build and was told to use buildSrc for that.
See here:
https://docs.gradle.org/current/userguide/sharing_build_logic_between_subprojects.html#sec:convention_plugins

They even mention project dependencies specifically and declare a dependency on junit:junit:4.13 in their example:
https://docs.gradle.org/current/userguide/declaring_dependencies_between_subprojects.html#sec:project_jar_dependencies

It would be pretty nice if dependabot was able to scan the files under buildSrc as well, since Gradle in my eyes still wants people to use buildSrc to share build logic in multi-project builds.

[JavierSegoviaCordoba]

Because it breaks some caches. There is multiple workaround to use catalogs inside precompiled plugins.

[TSRBerry]

Are you saying that Gradle wants me to use some workarounds to use catalogs with buildSrc? Why would they still recommend precompiled plugins over catalogs for multi-project builds then?

I thought this was a bug of dependabot which is how I got here and am a bit confused about the state of this issue. Since according to my understanding Gradle still wants people to use buildSrc.

Even if workarounds exist to make it work I don't want to put in extra effort to reconfigure the project and potentially mess something up.

If dependabot is not going to support this case that's fine with me. I'll need to monitor the dependencies myself then, so some kind of heads up about that would be appreciated.

Edit: reworded my initial question, since it sounded quite rude and I think I misunderstood the comment above.

[JavierSegoviaCordoba]

@jeliebig, I didn't say you should use one or another, using catalogs doesn't imply not using precompiled catalogs.

I am using precompiled plugins AND catalogs every single day, for single or multi-project builds.

I was using precompiled plugins + dependency management in buildSrc since 2019 and I still use precompiled plugins but without having the dependency management in buildSrc, moving it to Version Catalogs.

Why do you have to hardcode the strings + versions directly in the precompiled plugins and/or buildSrc object/classes instead of getting the catalog INSIDE buildSrc precompiled plugins and get the deps from there, and adding them to the dependencies block in your precompiled plugin?

You should use Version Catalogs for dependency management, something completely unrelated to precompiled plugin feature. You can get the deps from the Version Catalogs and apply them inside buildSrc precompiled plugins.

That means if you update your deps, you have to change nothing in buildSrc, avoiding breaking cache.

[TSRBerry]

Oh that doesn't sound that hard to do!
I thought workarounds means that I would have to follow some kind of complicated process to get something to work that isn't supposed to work.

But what you just described sounds pretty easy to me. I guess I'll give it another try and see if it works.

Although it doesn't solve this issue, this might be acceptable to just get it working at the moment.

Thank you for your patience with me!

[Goooler]

Complex build logics still need buildSrc, any plan to support this feature?

[wartingep]

did this just got released? I see a lot of PR:s in my buildsrc today :)

[mwierzchowski]

Same here. Looks like "something" was released. Where can we find any details?

[mwierzchowski]

Alright, found minute after asking a question (so typical...). See: #5028

[deivid-rodriguez]

So.. this can be closed now?? 😮 🎉

[deivid-rodriguez]

I'll do a reaction-driven issue close then! :)