feat(jans-scim): fix javadocs generation

[yurem]

closes #9348

• I confirm that there is no impact on the docs due to the code changes in this PR.

[dryrunsecurity]

DryRun Security Summary

The provided code change updates the pom.xml file in the jans-scim project, primarily by updating the maven-site-plugin version and adding a specific version for the maven-javadoc-plugin, which are build-related changes that do not appear to have any significant security implications.

Expand for full summary

Summary:

The provided code change is an update to the pom.xml file in the jans-scim project. The primary changes are updating the maven-site-plugin version from 4.0.0-M12 to 4.0.0-M16 and adding a specific version for the maven-javadoc-plugin to 3.8.0. From an application security perspective, these changes do not appear to have any significant security implications, as they are related to the build process and project management, and do not involve any changes to the application's source code or functionality.

However, it's important to review any changes, even in build-related files, to ensure that there are no unintended consequences or potential security risks. For example, if the new versions of the plugins introduce known vulnerabilities or issues, that could be a concern. Additionally, any changes to the project's dependencies or configuration settings should be carefully reviewed. Overall, this pull request seems to be a routine update to the project's build and configuration management, and does not raise any immediate security concerns. As an application security engineer, I would recommend approving the changes, but continuing to monitor the project's security posture and staying vigilant for any future updates that may require a more thorough security review.

Files Changed:

• jans-scim/pom.xml: This file has been updated to change the version of the maven-site-plugin from 4.0.0-M12 to 4.0.0-M16 and to add a specific version for the maven-javadoc-plugin to 3.8.0. These changes are related to the build process and project management, and do not appear to have any significant security implications.

Code Analysis

We ran 9 analyzers against 1 file and 1 analyzer had findings. 8 analyzers had no findings.

Analyzer	Findings
Sensitive Files Analyzer	1 finding

Riskiness

🟢 Risk threshold not exceeded.

View PR in the DryRun Dashboard.

[sonarqubecloud]

Quality Gate passed for 'SCIM API'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud