We now write the output of the JavaDoc generation to ${project.root}/target/generated-sources/delombok so that it will always end up in the top level target folder so that the aggregation of JavaDoc for multiple projects can actually find the generated source.
Upgraded the JavaDoc plugin to 3.0.0 and switched to use the additionalJOptions parameter to disable the doclint. Delayed documentation generation to the prepare-package phase. This is due to javadoc:aggregate triggering the compile phase before running which then caused the reference docs to be created twice slowing down the build significantly (mostly due to the PDF generation taking quite a while).
We now refrain from creating any JavaDoc during the standard build run and rather explicitly create it when wither the ci or distribution profiles are active. Generating JavaDoc now follows the delombok step to make sure that the code generated by Lombok appears in JavaDoc.
Moved version declaration of the Lombok Maven plugin into plugin managament section, only declare the configuration globally and explicitly declare executions in the aforementioned build profiles. Tie the Lombok Maven plugin version to 1.16.18.1 in preparation of the coming upgrade to Lombok 1.16.20.
Added Delombok plugin to produce a delomboked version of the sources to then let the JavaDoc plugin use that to render JavaDoc. Without that in place, methods generated via Lombok are completely missing from the Javadoc.
Updated reference links for JavaSE and Spring Framework references in the JavaDoc to the currently used versions.
