This message was deleted.

The only viable way I found is to create an extension which reacts to configuration. It could be just a bunch methods or a

NamedDomainObjectContainer

which modify

dependencyResolutionManagement

when relevant part of the settings script is executed. Also there's

gradle#settingsEvaluated

to create defer callback to the point when the settings script has been evaluated. I use both approaches since eager methods like `container#all`/`container#whenObjectAdded` are fired before configuration callback is executed, so I just use

myExt.container.all { gradle.settingsEvaluated(MyConfigAction(name)) }

and use that

name

to get configured element from container in my action.