Anybody using RepositoryHandler extension functions like this in their settings.gradle.kts file? i ...

# gradle

[André Thiele]

Anybody using RepositoryHandler extension functions like this in their settings.gradle.kts file? i can use this extension to clean up my dependencyResolutionManagement block but it does not work when used inside pluginManagement block. i always get unresolved reference errors. any ideas? (it does not matter where i put the extension functions in the file top or bottom)

[Vampire]

The pluginManagement is special like some other blocks. It is extracted and evaluated separately to find out where to resolve plugins (including settings plugins from). Without that knowledge the settings script cannot be compiled as Gradle cannot know where to take the settings plugins from. But because of that you can of course not access anything outside that block from within.

[Vampire]

But this is not true for the opposite. You could configure the dependencyResolutionManagement block from inside the pluginManagement block.
While not being super clean, you could then use the same extension function for both.

[André Thiele]

The thing is I can’t even pass lambdas to it that are then applied in the repositories block. Really weird

[Vampire]

How should that be weird?
I just explained it to you.

[Vampire]

It is extracted before the script is compiled and evaluated separately.
It cannot access anything outside.
Your lambda is outside.

[Vampire]

And it is not even compiled yet.

[Alexey Illarionov]

@André Thiele you can extract this configuration into the gradle settings plugin into build-logic and apply it from the root settings.gradle.kts. This is how I usually do it: repositories.settings.gradle.kts

[Vampire]

That will not help for settings plugins though!
Doing it like that is too late for resolving settings plugins from those repositories.

[Alexey Illarionov]

Yes, that's true. But for building Gradle Settings Plugins we usually don't need any plugins specifically from the Google repository and it's not added here. Of course, some other repositories may require special handling