The GitHub Actions job "CI" on grails-core.git/fix/javadoc-jar-disabled-javadoc-output has succeeded. Run started by GitHub user matrei (triggered by matrei).
Head commit for run: e2b6daf70a79ae115261a461b074bcde582c0ab9 / Mattias Reichel <[email protected]> Keep a disabled javadoc task's stale output out of the javadoc jar withJavadocJar() packages whatever sits in the javadoc task's destination directory. The grails-publish plugin disables that task on every module that has a groovydoc task and packages the groovydoc in its place, but a disabled task never cleans its outputs, so a build/docs/javadoc left behind by an earlier build is copied next to the groovydoc and the duplicate help-doc.html fails the jar under DuplicatesStrategy.FAIL. grails-gsp-spring-boot is where this bites: it is Java-only and only started applying the publish conventions in 14da8e4b11, so any build of an older checkout leaves that directory behind and every later `./gradlew build` on the same tree fails until it is cleaned. CompilePlugin now excludes the javadoc destination directory from the jar whenever the task is disabled, reading both lazily since grails-publish disables the task after this plugin has run. An enabled javadoc is packaged exactly as before. Report URL: https://github.com/apache/grails-core/actions/runs/35704423569 With regards, GitHub Actions via GitBox
