The GitHub Actions job "Release - Drafter" on grails-gradle-publish.git/fix/issue36-stale-javadoc-output has succeeded. Run started by GitHub user jdaugherty (triggered by jdaugherty).
Head commit for run: e54351eccfdeceefe4ec69ec1a3ca16516f6387c / James Daugherty <[email protected]> Keep a disabled javadoc task's stale output out of the javadoc jar `withJavadocJar()` registers `javadocJar` with `from(javadoc)`, and the plugin then disables `javadoc` and adds the groovydoc directory to the same jar. The standard tasks are kept in place deliberately, so that the rest of Gradle can depend on them, and only the jar's content is meant to be swapped - but the `from(javadoc)` was never taken away, and a disabled task does not clean its outputs. Anything an earlier build left in `build/docs/javadoc` was therefore still packaged next to the groovydoc: stale pages shipped silently, and the jar failed outright for consumers that set `DuplicatesStrategy.FAIL`. A javadoc task that does not run has nothing to contribute, so its destination directory is now excluded from the jar whenever it is disabled. Both the flag and the directory are read lazily, since the task is disabled after the jar has been configured. An enabled javadoc is packaged exactly as before. The javadoc jar is now groovydoc-only in practice as well as in intent, so the README no longer promises both. Fixes #36 Fixes #23 Report URL: https://github.com/apache/grails-gradle-publish/actions/runs/35743934011 With regards, GitHub Actions via GitBox
