can you create a task, that configures another at runtime? if I wanted to change publishing settings later...

you would have to write the config to a file and have the task that needs it read it from said file

eww

guess it also depends on if that config needs to be considered as a task input for caching. something else I've done is put things is a build service map that tasks can read from later. roughly: launchWebSocketConnectionTask -> doExpensiveRemoteThingWithWebSocketTask -> closeWebsocketTask the build service just holds the websocket connection object through them all.

yeah... I mean, the desire was to have a task that doesn't configure the publish plugin until right before publish (or whatever step) is called

If you do not intend to use configuration cache, one task can configure another task that is going to run after that. But it is bad practice and discouraged, especially because of incompatibility with configuration cache.

so that it's not run during

build

publish${Publication}To${Repository}

shouldn't be a dependency of

build

.

it's not but the whole F-ing configuration is always done, and I was trying to think of a way to make it lazier so pom's aren't generated and configuration of pom isn't done

Yea, lazy configuration for publishing is still on the todo list IIRC

Hopefully we get it with the great

Property

-ization with Gradle 9

Was going to link an issue but looks like you're aware of it 😄 https://github.com/gradle/gradle/issues/29342

yeah, I was retooling my convention plugin, tried to make an extension and it blew up