[ebarboni]

This is a PR out of 5 (I hope) where I execute the apidoc not using codesnippet-doclet.

<arg value="--allow-script-in-comments" if:true="${javadoc23.or.later}" `/>`
<arg value="--snippet-path ${javadoc.base}/test/unit/src:${javadoc.base}/src" if:true="${javadoc23.or.later}" />
<arg value="-Xdoclint:all" />
<arg value="-Xdoclint:-missing" />

javadoc 23 is checking hard for correct header sequence, removed attribute and element, and if an error is detected it break generation for the current module.

I would like to anticipate and having apidoc base clean to this aspect so I could focus on xslt management to get jdk23 looking docs later.

As header sequence changed I added more header to the link checker.

With default apidoc pages like https://bits.netbeans.org/dev/javadoc/org-netbeans-api-visual/org/netbeans/api/visual/widget/doc-files/documentation.html that render out of structure looks a bit better integrated:

[mbien]

This is a PR out of 5 (I hope)

can you update commit and PR title to indicate what clusters/modules this covers if this is a multi-part PR?

[ebarboni]

it's 25 out of approx 140 modules in the javadoc build order (on master branch). It goes to ide folder and back to platform. Not sure how to present that.

[mbien]

well. give it a number at least, e.g: apidoc html compliance part 1

[ebarboni]

roger