I think selective javadoc enables an anti-pattern that we should not encourage. That said, we previously supported the feature, so we should support it for some transitional period, giving downstream projects notice of our intention to drop it (if we have such an intention), granting them a chance to adjust.
I prefer we continue to support the feature in JDK9+ if possible, but also document a more hygienic approach going forward. I’ve not yet reviewed the provided patch, but my understanding is that it enables the feature, even if using an undesirable method. I think that’s a reasonable compromise, given the situation we have. Thanks, Nick On Thu, Apr 21, 2022 at 18:51 Allen Wittenauer <a...@effectivemachines.com.invalid> wrote: > > Sorry things have been hectic in my personal universe. Just a follow-up to > where this sits today. > > * It doesn’t appear that there was a lot of discussion here so I’m > guessing most people don’t care? > * I missed that the patch that Owen provided does hack the API. I > committed that code change if only to make the source tree build again. > > That said, if the community feels strongly about it, we can obviously > change that. > > >