I'm +1 to remove the Javadoc functionality. I'm not a fan of hacking the API. It's not a long-term solution. In addition, personally I don't want selective javadocs. I want to look at even @Private javadoc to develop Hadoop and its related projects.
-Akira On Sun, Apr 10, 2022 at 11:46 AM Allen Wittenauer <a...@apache.org> wrote: > > Thanks to Owen, pretty much determined the only way to have > feature parity under JDK9+ is to extend an internal Java object > (specifically DocEnvImpl from jdk.javadoc.internal.tool.DocEnvImpl) . From > what we can tell, the new javadoc APIs do not provide a way (easy or > otherwise) to remove content from the document tree. We as a community > need to decide how we want to go forward. > > We’re not the only ones to hit this issue but from what we can > tell, the Java team isn’t interested in fixing it. > > Some options off the top of my head: > > - Go ahead and do the hack. We wouldn’t be the first to do it (see > https://github.com/rnc/hiderdoclet/blob/main/doclet/src/main/java/org/goots/hiderdoclet/doclet/DocletEnvironmentProcessor.java > which is also ASL 2.0 so we could effectively just lift and modify this > code) > > - Remove the Javadoc functionality entirely…. but I’m not sure how > useful these annotations become without it. > > - Throw in the towel and just remove the annotations functionality > entirely. > > I’m sure there are others. > > > Thoughts? > > Thanks! > >
