Here is tasks I can remember - [x] upgrade gradle wrapper - [x] replace removed configration compile runtime testCompile testRuntime - [x] use convention plugin to organize build logic for subprojects

Comment From: bclozel

I've got a draft commit for this, fixing quite a few things in our build. The dokka plugin version we're using is not compatible with Gradle 7 and after checking with the team, we should probably wait for the 1.5.0 version.

I'm moving this back to the backlog and marking it as blocked in the meantime.

Comment From: sbrannen

In the meantime, Gradle 7.1 has been released.

Comment From: bclozel

I've got a draft commit for this issue here.

The build runs fine but the dokka generation takes 10+min on my laptop and the result is quite large (almost 40MB). I'm wondering if I've messed up the configuration or if there's a way to limit the scope here so that the plugin has less things to consider. The new version of the plugin simplifies our setup quite a bit.

@sdeleuze Could you have a look here?

You can locally trigger the generation with: ./gradlew dokkaHtmlMultiModule --no-scan --info.

Comment From: quaff

  1. The Report.destination property has been deprecated. This is scheduled to be removed in Gradle 8.0. Please use the outputLocation property instead. See https://docs.gradle.org/7.2/dsl/org.gradle.api.reporting.Report.html#org.gradle.api.reporting.Report:destination for more details.

  2. The JavaExec.main property has been deprecated. This is scheduled to be removed in Gradle 8.0. Please use the mainClass property instead. See https://docs.gradle.org/7.2/dsl/org.gradle.api.tasks.JavaExec.html#org.gradle.api.tasks.JavaExec:main for more details.

Comment From: sbrannen

Thanks, @quaff.

We've noticed those warnings as well.

Reopening to address those two warnings.

I'll address the first one for spring-test.

Comment From: snicoll

@sbrannen can we please update the title of this issue as I don't think it longer reflects the original intention.