at the end?

No. Sure I'm looking at the latest?

This is the end:

application {
        mainClass = mainClassName
    }
}

If you pulled, yeah.

It's on github, as shown above.

oh looking at

example

ok got it

But as I said, i'm not sold on that way of doing it, it's just the way I do it in Gradle.

*****
***** ERROR Couldn't compile build file: kobalt\src\Build.kt:103:31: error: unresolved reference: getVersion
    project.version = project.getVersion(true)

Is that what you're getting? (because it's normal)

Yeah, but if you change to project.version = "1.0", it doesn't change anything either. As you said it's probably already cached.

Got it to work, I think:

───── example:clean
───── example:release
VERSION BEFORE: 3.1.45+beta
RETURNING VERSION 3.1.46+beta
VERSION : 3.1.46+beta
BUILD SUCCESSFUL (0 seconds)

Looks like it got incremented

Sure does.

Ok so this works. It's still awful but let me run you through it.

First of all, when you do:

val p = project {
  fun f() { ... }

You're not adding a function to the

Project

class, hence the compilation error when you try to access it in your release task.

For that to work, you need to create an extension function on

Project

. Are you familiar with that?

nope

Basically, I simply did:

fun Project.versionFor(isIncrement: Boolean = false): String {
        val propsFile = "version.properties"
        val majorKey = "version.major"

Now this adds a function

versionFor()

on the

Project

class.

okay, makes sense.

Then you can just call

versionFor()

on instances of

Project

and everything works:

@Task(name = "release", dependsOn = arrayOf("clean"), description = "Releases new version.")
fun taskRelease(project: Project): TaskResult {
    project.version = project.versionFor(true)

Note that I renamed your function from

getVersion

to

versionFor

because of an implementation detail in Kobalt you shouldn't worry about right now.

I figured as much. 😉

(I'll fix that)

Now, the whole idea is a bit whacky, incrementing the version halfway through the build

Sounds like this should belong in a pre-build phase

That would be best.

Because right now, the project version is

x

until you hit the

release

task and now it's

x+1

, which is... well, whacky

Even in gradle it's whacky, because if you don't clean before, it might increase the build in the version.properties, but not in the code.

So why not just write a pre-build tool that updates

version.properties

, which is then used throughout the build?

At any rate, I'm glad Kobalt is behaving in a predictible way despite you being crazy