On 24/01/2022 13:16, Andy Seaborne wrote:
2/ Java11.
That might have been an upstream fix. The offending search.js seems to
be a different size. But this is fragile as to which tools generated
the javadoc,
For now
1: remove the breaking fix.
2: see what happens
3: if no better approach comes along, release and fixup the website
javadoc directly.
There's a fix for javadoc production so we need customization of the
javadoc production for JDK11 only (the necessary setting has ben removed
in later JDKs.
How is that done? A profile would need to replicate the whole of the
modules settings which is doable but extreme.
Or activate by property "apache-release" which I think then means
multiple profiles are active. (Never done it myself)
We can hack it by producing duff javadoc and fixing it like the current
javadoc is fixed. Nuisance for javadoc artifact.
There is a script the website.
https://github.com/apache/jena-site/tree/javadoc
Andy
