Publish an empty javadoc JAR instead of building scaladoc - #125
Merged
Conversation
rochala
force-pushed
the
drop-scaladoc-from-release
branch
from
August 19, 2026 11:03
8b2c450 to
e1fceb9
Compare
The v0.1.0 release failed in `publish-maven` with `lib.scalaDocGenerated scaladoc generation failed` — scaladoc errored while reading fs2's `Chunk.scala` TASTy (`undefined: new nowarn213`), not on any cellar source. That is unfixable from here and it aborts the release after the native binaries and JAR have already been built. Cellar is on Maven Central only so coursier can resolve its latest version via `maven-metadata.xml`; nothing consumes these artifacts as a library, so the bundled scaladoc has no readers. Override `docJar` in a shared `CellarPublishModule` to emit an empty JAR — Central still requires the `-javadoc.jar` to exist, but nothing has to compile it. `scalaDocGenerated` remains available for local use. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
rochala
force-pushed
the
drop-scaladoc-from-release
branch
from
August 19, 2026 11:11
e1fceb9 to
37e3237
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The v0.1.0 release run died in
publish-maven:Scaladoc choked reading fs2's TASTy, not any cellar source — nothing we can fix, and it aborts the release after every native binary and the assembly JAR have already been built.
Cellar is on Maven Central for exactly one reason: the coursier apps descriptor reads
maven-metadata.xmlforcellar-lib_3to find the latest version. Nobody depends on these JARs as a library, so the bundled scaladoc has no readers and is not worth a failed release.Change
docJaris overridden in a new sharedCellarPublishModule(mixed intolib,profilingRuntime,cli) to emit an empty JAR. Sonatype Central still requires a-javadoc.jarto exist, so the artifact is still published and still PGP-signed — it just contains nothing and costs nothing to build.scalaDocGeneratedis untouched;./mill lib.scalaDocGeneratedstill works locally for anyone who wants the docs.Verification
./mill lib.docJar→ 1 task, no compilation, JAR contains onlyMETA-INF/MANIFEST.MF./mill show lib.publishArtifacts→ still listscellar-lib_3-<version>-javadoc.jaralongside the pom, jar, and sources jarNo CI job was added: a scaladoc check would go red on dependency bugs we can't act on.
🤖 Generated with Claude Code