Incompatibility with new grgit version

Hi. We have encountered the following problem:

* What went wrong:
An exception occurred applying plugin request [id: 'org.ajoberstar.reckon', version: '0.13.0']
> Failed to apply plugin [class 'org.ajoberstar.grgit.gradle.GrgitServicePlugin']
   > Could not create plugin of type 'GrgitServicePlugin'.
      > Could not generate a decorated class for class org.ajoberstar.grgit.gradle.GrgitServicePlugin.
         > org/gradle/api/services/BuildServiceSpec

It seems like the 0.13 versions of reckon are not compatible with the new 5.0.0-rc1 version of grgit and the newly introduced grgit service-plugin (https://github.com/ajoberstar/grgit/pull/354). Our guess is that the missing version number at https://github.com/ajoberstar/reckon/blob/main/build.gradle.kts#L2 causes loading always the latest grgit version… in this case a release candidate.

Our workaround

buildscript {
  repositories {
    ...
  }
  dependencies {
    classpath ('org.ajoberstar.grgit:grgit-gradle:4.1.1') {
      force = true
    }
  }
}

Expected behavior/solution: Maybe it might a solution to use a fixed version of grgit inside of reckon… something like this:

plugins {
  id 'org.ajoberstar.grgit' version '4.1.1'
  ...
}

[ajoberstar]

Ugh 😫, 0.13.1 fixed the POM files on Maven Central, but for some reason Gradles publish plugin ignores the way maven-publish was configured and puts the ranges in the POM on the plugin portal. Will look into a fix later today.

[ajoberstar]

This should be fixed now in 0.13.2. It was caused by some interplay with com.gradle.plugin-publish, java-gradle-plugin, and dependency locking. I believe I’ve got a solution that’s more reliable now (which includes not publishing directly to the Gradle plugin portal anymore, and making use of the fact that the portal proxies Maven Central).

It may take up to an hour for the version to show up in Central (due to their syncing process), but it should resolve the issue you all encountered.