As a follow up on HSEARCH-2774: we want to have javadocs validated by default, while currently this requires activating the "dist" profile.
We want to enable this only after having cleaned up most of the other warnings a failure would produce, so that occasional contributors don't get overwhelmed with a too long error message in case a failure is detected.
UPDATE: While working on this, we changed the purpose of this ticket a bit. We still require the -Pdist profile to be enabled, but if we add a new module and forget to include it in the aggregated javadoc, we now validate the javadoc for this new module regardless. The goal is to have a javadoc validation in CI that is in par with the validation when releasing. |
|
