That's great! It was an oversight that *maven.javadoc.skip* [1] was enabled (by accident) all this time. Thanks for catching that. Previously *-javadoc.jar files weren't deployed to Maven Central. e.g. 2.0.0 [2]. Now 2.1.0 does [3]. 👏
ozone-main artifacts don't publish java docs. > I'm not sure ozone-main is supposed to have any? It is the artifactId of the root pom. [1] https://github.com/apache/ozone-site/pull/153/changes [2] https://repo1.maven.org/maven2/org/apache/ozone/ozone-client/2.0.0/ [3] https://repo1.maven.org/maven2/org/apache/ozone/ozone-client/2.1.0/ Thanks, Siyao On Fri, Jan 2, 2026 at 1:55 PM Wei-Chiu Chuang <[email protected]> wrote: > Hi Ozone developers, > > With the latest 2.1.0 release, we finally have javadoc published at > javadoc.io. This is going to help core Ozone developers as well as client > application developers. > > As an example: > > https://javadoc.io/doc/org.apache.ozone/ozone-client/latest/org/apache/hadoop/ozone/client/ObjectStore.html > > Check out more at https://javadoc.io/doc/org.apache.ozone > > Moving forward, let us keep our code tidy. Improve public API javadocs as > needed. > > Note: looks like there's still some snafu. ozone-main artifacts don't > publish java docs. >
