This message was deleted.

registerIfAbsent() returns a provider for your service, and I guess you want to register your service as an Project extension so it's accessible in the build scripts?

yeah, I guess so? I'm really not confident this is designed right, since I'm mostly just trying to add accessible methods to the build scripts

you probably want to use a ValueSource to contain the git version logic, because otherwise Gradle will complain about Configuration Cache compliance

I believe I have removed the problems with configuration cache

A build service is useful if you want to wrap some sort of resource, like a connection to a HTTP service, so you can re-use the resource across the build. It's also useful if you want to share a build service with multiple tasks, across the build. So maybe it would be useful in your case, because the version would be accessible in multiple projects..

I doubt it's significant either way, I'm sure that the IO for reading .git/refs is pretty negligible

true

@Vampire suggested the build service 😉

and because Project.version hasn't been updated to use the Provider API, I created a wrapper for the version: https://github.com/adamko-dev/kotlin-binary-compatibility-validator-mu/blob/b0509394692942934150cf37fc75e4bbc38d7580/build.gradle.kts#L9-L12

so your extension is just a provider?

so your extension is just a provider?

yup

looks like java 21 is kind of unhappy with some of (what is I think are suggested access patterns of a build service), this is now a warning and I turn warnings into build errors

@Inject
  public GitVersionProvider() {
    this.builder =
      new FileRepositoryBuilder()
        .readEnvironment(SystemReader.getInstance())
        .setMustExist(true)
        .findGitDir(this.getParameters().getProjectDirectory().get().getAsFile());
  }

@Adam btw, now working with --configuration-cache, no value source