Development: Update server dependencies and improve server test output

[krusche]

• All relevant checks pass
• Deployment on test server and clicking through the application works fine

[coderabbitai]

Walkthrough

The recent update primarily focused on upgrading various plugins and dependencies in the build.gradle file to their latest versions. Additionally, an enhancement was made to the test results output to track and display failed tests. The gradle.properties file also saw a minor update with the version bump of the Mockito library.

Changes

File	Change Summary
build.gradle	Updated versions for org.owasp.dependencycheck, io.micrometer:micrometer-registry-prometheus, org.springframework.data:spring-data-ldap, io.projectreactor.netty:reactor-netty, org.springframework:spring-messaging, org.springframework.retry:spring-retry, com.nimbusds:nimbus-jose-jwt, org.apache.maven.shared:maven-invoker. Added logic to track and display failed tests in the test results output.
gradle.properties	Updated mockito_version from 5.11.0 to 5.12.0.

---

Recent Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between d9143b9 and 17096f6.

Files selected for processing (2)

• build.gradle (7 hunks)
• gradle.properties (1 hunks)

Files skipped from review due to trivial changes (1)

• gradle.properties

Additional comments not posted (9)

build.gradle (9)

30-30: Update to org.owasp.dependencycheck version 9.2.0 is noted.

Ensure that this version is compatible with other plugins and does not introduce any breaking changes.

---

326-326: Update to io.micrometer:micrometer-registry-prometheus version 1.13.0 is noted.

Verify that this version integrates well with the existing metrics collection and reporting setup.

---

368-368: Update to org.springframework.data:spring-data-ldap version 3.3.0 is noted.

Ensure that this version is compatible with other Spring dependencies and does not introduce any breaking changes.

---

380-380: Update to io.projectreactor.netty:reactor-netty version 1.1.19 is noted.

Verify that this version is compatible with the existing reactive programming setup and does not introduce any performance regressions.

---

381-381: Update to org.springframework:spring-messaging version 6.1.7 is noted.

Ensure that this version is compatible with other Spring dependencies and does not introduce any breaking changes.

---

382-382: Update to org.springframework.retry:spring-retry version 2.0.6 is noted.

Verify that this version integrates well with the existing retry mechanisms and does not introduce any breaking changes.

---

390-390: Update to com.nimbusds:nimbus-jose-jwt version 9.39.1 is noted.

Ensure that this version is compatible with the existing security configurations and does not introduce any vulnerabilities.

---

467-467: Update to org.apache.maven.shared:maven-invoker version 3.3.0 is noted.

Verify that this version is compatible with the existing Maven configurations and does not introduce any breaking changes.

---

Line range hint 504-541: Enhancements to test logging to track and display failed tests are noted.

This change should help in better tracking of test failures and improve the debugging process. Ensure that the logging does not expose any sensitive information.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.