During RHBQ integration we discovered that optaplanner-bom [1] explicitly sets javadoc dependencies in the dependencyManagement section.
This was an issue during RHBQ maven repo generation because those javadoc artifacts would be required/expected just because they are present on the BOM (but they are not built during PNC build - this is an explicit option).

Workaround for RHBOP 8.33 integration would be to explicitly exclude them from maven genearation.

The final solution could be to remove them from usptream BOM, as I cannot see any valid reason to keep them on BOM as users should not depend on javadoc artifacts.

[1] https://github.com/kiegroup/optaplanner/blob/main/build/optaplanner-bom/pom.xml