From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

no, a task should not mutate project state

it's unfortunate that `version` isn't a `Property` like more modern APIs are, but you can work around that with
```version = object {
    override fun toString(): String =
        computeVersion().getArtifactVersionString()
}```
during build configuration, which will be stringified to the expected value by everything using `version`, such as the `Jar` tasks and publishing

Hm, thing is that computeVersion() also reads the current project version setting before appending "-SNAPSHOT" to it. That wouldn't work there, right? Or does the above code *only* override the toString method of the version object?

it creates a whole new version. if you need to read the existing version, you need to read it before setting this object