The elasticsearch module is not included in the javadoc generation. It would not have caused that much harm if an error in the javadoc hadn't made the build fail only when the separate javadocs are also built (eg in release mode).
The main difference between the CI build and the release build is that the release build also generate individual javadocs so an error in an individual javadoc which is not included in the aggregate javadoc will fail the release build while CI is still green. On Validator, the individual javadocs are not generated at all (same as ORM) thus we don't have this issue.
We can either:
disable individual javadoc generation for all the modules and only enable the aggregated one
disable individual javadoc for the modules not being included in the aggregated one (and hope we don't forget to add them in the future)
also generate the individual javadocs in the CI build
what's your take on this?
The linked javadocs could also be updated.