This message was deleted.

Sure, you can use

buildSrc

to centralize things and for example have a dependencies class with constants there. It is just not the standard and idiomatic way, and has various drawbacks. For example if you change one single version, that changes the classpath of all build scripts and thus makes all tasks in all projects out-of-date. With a version catalog only the specific tasks that somehow use that version will need to re-run. And also tools that might support parsing the standard version catalog files to do something with the information might not support custom

buildSrc

solutions. ...

I see, thank you so much. I think I have a better understanding on it now. Appreciated 👍