This message was deleted.

task execution time is likely too late to set a version, as many other tasks require the version at configuration time. Agree that having version as a

Provider<String>

is a great first step to untangle all this.

Good point, I was mislead by the existing broken implementation I am looking at. Basically the only way is to directly take care of it in the plugin. 🤔

yea. it’s not pretty, no clean solutions in current model. Providing your own Object as the version with a toString() method that resolves the version is the only known solution (though be careful around performance vis-a-vis multiple calls to resolve version). Effectively a “budget”

Provider

.