The GitHub Actions job "Groovy Snapshot Canary Build" on grails-core.git/fix/docs-out-of-gradle-daemon has succeeded. Run started by GitHub user jdaugherty (triggered by jdaugherty).
Head commit for run: dfede9d49d662f047a7b0f9bd6cdade5230f06cd / James Daugherty <[email protected]> build: address second review round on the documentation fork - Groovydoc resolves referenced types with Class.forName, which runs their static initialisers; any that reach LoggerFactory made slf4j-api warn that it found no provider, three lines per module. Inside the daemon the Ant class loader's parent supplied Gradle's binding - a forked JVM has no such parent - so slf4j-nop joins the documentation configuration, the same way cliCompileOnly already handles it for compilation. - The two heap overrides used two mechanisms; both now go through providers.gradleProperty, which is also the form that survives the configuration cache if gradle/gradle#15497 is ever closed. - The gradle-developer skill listed groovydocMaxHeapSize among the root gradle.properties flags, where it deliberately is not. Says so instead, for both override properties. Report URL: https://github.com/apache/grails-core/actions/runs/35746718711 With regards, GitHub Actions via GitBox
