With the release of Processing 4, we upgraded from JDK 11 to JDK 17 and as a result, our script that parses the JavaDoc comments in the Processing source and creates JSON files in the website repo is broken.

The class that we're using, com.sun.tools.doclets.standard.Standard has been deprecated and replaced with jdk.javadoc.doclet.StandardDoclet which has a whole different API.

We are in need of someone who can evaluate the amount of work required to update the script to use the new class and API and/or make the changes if they are manageable. We understand that this might be a substantial amount of work and we will consider setting a bounty for this task if that is the case.

Please note that this issue is blocking updates to the reference (some examples are linked below) and we would greatly appreciate any help in resolving it, on behalf of the whole Processing community.

Raphaël de Courville
Processing Community Lead Fellow

Edit (20.01.2023): rewrote for clarity and added request for help

As the title says: the sound library maintains argument signatures for some methods in its codebase only for backwards compatibility, however they should best be omitted from the online reference, since they would only confuse new users. These methods are already marked as @deprecated in the codebase, so it would be great if the doclet generation could check for such annotations and omit them from the json output.

I'm currently reorganizing the processing-sound library reference/javadoc and ran into two issues/questions that people more knowledgable than me will hopefully be able to help me with...

1. the relevant code for this one is probably to be found over in the processing-website repo, but I'll ask it here anyway: the default order of the categories (and subcategories) within the reference listing is alphabetic, but ideally I would like a slightly different ordering for the sound library reference. I can see that the core processing reference also uses a custom ordering of categories, but I can't quite see where the order is actually specified in the current codebase? It seems to be somehow controlled by the Shortcuts component, but I can't seem to find where this is actually instantiated. Some ordering code was introduced by @runemadsen with benfry/processing4@a8f9031 but taken out again by benfry/processing4@48b326b, yet the custom ordering on the website is still in place...

2. @fdoflorenzano probably knows more about this: @webref annotated methods that are inherited from superclasses are currently not rendered/written to json for the subclasses. Is there a way to turn on doclet generation of inherited methods, either on a per-case basis, or simply for the entire run of the processing-sound doclet build? I tried using {@inheritDoc} but it doesn't look like the doclet supports automatic expansion for this...

Many thanks!
Kevin