You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix javadoc build error + reduce warnings on new classes
The release packaging job (mvn package, release profile) runs
maven-javadoc-plugin's attach-javadocs which treats Javadoc tool
errors as build failures. PR #188 introduced one such error:
TokenLogprob.java had a </p> with no matching <p> (the prose was
already enclosed by an outer <p>...</p>, and the inner </p> was
stray).
Fix the error and bring my new public APIs up to a clean shape:
- TokenLogprob: rebalance the <p>/</p> HTML and add @return / @param
to public getters and constructor.
- Timings, Usage, ServerMetrics, ChatMessage, CancellationToken,
Session, LlamaOutput: add @return / @param tags with a leading
one-line description (the "no main description" warning fires on
bare /** @return ... */ blocks).
- LlamaModel: restore the doc comment for complete(params, token)
that was accidentally stripped during an earlier edit, and add one
for getMetricsTyped(); remove a stray orphan doc block.
Local verification:
mvn clean javadoc:jar -DskipTests=true -Dgpg.skip=true
mvn -P release -Dmaven.test.skip=true -Dgpg.skip=true package
Both: BUILD SUCCESS (was: BUILD FAILURE, 1 error, 100 warnings).
60 warnings remain, all from pre-existing files outside this PR.
Document the verification command and the failure categories
(errors vs warnings) in CLAUDE.md under "Javadoc — must build
cleanly before mvn package".
https://claude.ai/code/session_01R4ZrEy3ptJDLuUgUKuM4Gy
0 commit comments