This message was deleted.

You need to use the type-unsafe API: https://docs.gradle.org/current/userguide/platforms.html#sub:type-unsafe-access-to-catalog

You can it only use like that with a hack-around. Alternatively you could use the type-unsafe string-based API to access the catalog. See here for more information including my hack-around: https://github.com/gradle/gradle/issues/15383 For the stringly api, get the

VersionCatalogsExtension

extension and use that. https://docs.gradle.org/current/userguide/platforms.html#sub:type-unsafe-access-to-catalog

I think the hack-around only works for precompiled script plugins, of which

buildSrc/src/main/kotlin/DoSomethingWithVersions.kt

would not be one

Thanks guys. If I try to dig into it, do you think a newbie like me could create a PR to fix it or it needs a lot of changes so not anytime soon it's happening?

If you're asking specifically about precompiled script plugins, I think it is not a newbie-friendly change, as mentioned in the issue it really needs some design work put into it, not just making code changes. Your specific question, which is for what we call "binary" plugins, is something that I don't think is really ever going to be fixed. Binary plugins have never had generated accessors available, and I don't think there's plans to change that.

I think the hack-around only works for precompiled script plugins

I think it should work alike in a normal Kotlin file, as long as you have access to the

project

to get the

LibrariesForLibs

extension or supply it in.

Thanks everyone 🙂 you gave me good points to start.