Bump the maven-dependencies group with 2 updates

[dependabot]

Bumps the maven-dependencies group with 2 updates: org.springframework.boot:spring-boot-starter-parent and org.jetbrains.dokka:dokka-maven-plugin.

Updates org.springframework.boot:spring-boot-starter-parent from 3.4.0 to 3.4.1

Release notes

Sourced from org.springframework.boot:spring-boot-starter-parent's releases.

v3.4.1

🐞 Bug Fixes

• KafkaProperties fail to build SSL properties when the bundle name is an empty string #43563
• Diagnostics are poor when property resolution throws a ConversionFailedException #43559
• SpringApplicationShutdownHandlers do not run in deterministic order #43536
• Unable to find a @SpringBootConfiguration results in misleading error message #43507
• With multiple ResourceHandlerRegistrationCustomizer beans in the context, only one of them is used #43497
• Unable to use Docker Compose support when mixing dedicated and shared services #43472
• Kafka dependency management does not include the kafka-server module #43454
• Docker API version is incorrectly reported when '/_ping` calls fail and version should be fixed #43452
• Methods to build producer / consumer properties from KafkaProperties are inconvienenent to use without an SSL bundle #43448
• Failures in -Djarmode=tools do not consistently return a non-zero exit #43436
• HttpComponentsClientHttpRequestFactoryBuilder replaces the existing defaultRequestConfigCustomizer rather than adding to it #43429
• spring-boot-maven-plugin sets imagePlatform even if it's empty #43424
• OnBeanCondition fails to match on annotations when using Scoped Proxies #43423
• Failure analysis for InvalidConfigurationPropertyValueException doesn't correctly handle fuzzy matching of environment variables #43382
• H2ConsoleAutoConfiguration causes early initialization of DataSource beans #43359
• Accept progress on numbers >2GB #43356
• Servlet-based UserDetailsServiceAutoConfiguration is active in a reactive app #43334
• StructuredLoggingJsonMembersCustomizer implementations declared in spring.factories with a generic type more specific than Object are not called #43312
• Overriding log level with an environment variable does not work when using an environment prefix #43307
• Management endpoint access and enabled properties are ignored unless the endpoint ID is an exact match #43302
• UnsupportedOperationException when starting a Maven shaded application on Java 21 with virtual threads enabled #43291
• JmsListener failing with Narayana (pooled ConnectionFactory) since 3.4.0 #43277
• SslBundle can no longer open store file locations without using a 'file:' prefix #43274
• TestRestTemplate does not allow redirects to be customized #43258
• Testcontainers start() methods may be started multiple times #43253

📔 Documentation

• Fix typo in documentation #43558
• Document that server.ssl.cipher and server.ssl.enabled-protocols are not fallbacks used with SSL bundles #43552
• Use <annotationProcessorPaths> in Maven examples for configuring an annotation processor #43544
• Fix typo #43519
• Links to logback javadoc are incorrect #43456
• Fix JUnit javadoc links #43428
• Reference documentation incorrectly uses 'disabled' rather than 'none' for access restrictions #43351
• Restore System property in Logging section of the reference documentation #43342
• Fix link to proxyBeanMethods in @AutoConfiguration javadoc #43325
• Fix links to Servlet and JPA javadoc #43324
• Link to @EnableMethodSecurity instead of the deprecated @EnableGlobalMethodSecurity #43315
• Document that StructuredLoggingJsonMembersCustomizer implementations may optionally take constructor parameters #43314
• Update javadoc of StructuredLoggingJsonMembersCustomizer to note that implementations can registered through spring.factories #43313
• Fix Javadoc link for Hikari #43311
• Document how to use structured logging with custom log configuration #43301
• Update Javadoc since for OtlpMetricsProperties and OtlpTracingProperties #43249

🔨 Dependency Upgrades

... (truncated)

Commits

• 1832852 Release v3.4.1
• c9e8174 Merge branch '3.3.x'
• 316fe52 Next development version (v3.3.8-SNAPSHOT)
• 4300ee9 Merge branch '3.3.x'
• da59380 Upgrade to Spring Batch 5.2.1
• a085a01 Upgrade to Spring Batch 5.1.3
• fcc569e Upgrade to Hibernate 6.6.4.Final
• 1b8fcb6 Merge pull request #43560 from arefbehboudi
• dbc1fc2 Polish
• ef43160 Merge branch '3.3.x'
• Additional commits viewable in compare view

Updates org.jetbrains.dokka:dokka-maven-plugin from 1.9.20 to 2.0.0

Release notes

Sourced from org.jetbrains.dokka:dokka-maven-plugin's releases.

2.0.0

Dokka 2.0.0 focuses on simplifying configuration and preparing for support of future Kotlin language features. Key highlights include:

• Dokka Gradle Plugin v2: revamped Gradle plugin based on Dokkatoo.
• Experimental K2 Analysis: support for K2 compiler frontend.
• HTML Improvements: better accessibility and easier customization.

More details about each of the changes below. See Dokka 2.0.0 milestone for the list of all changes.

Dokka's Gradle plugin v2 based on Dokkatoo

Please check the migration guide for the update procedure and give feedback!

Dokka 2.0.0 introduces significant improvements to Dokka Gradle plugin, aligning more closely with Gradle best practices:

• Adopts Gradle types, which leads to better performance.
• Uses an intuitive top-level DSL configuration instead of a low-level task-based setup, which simplifies the build scripts and their readability.
• Takes a more declarative approach to documentation aggregation, which makes multi-project documentation easier to manage.
• Uses a type-safe plugin configuration, which improves the reliability and maintainability of your build scripts.
• Fully supports Gradle configuration cache and build cache, which improves performance and simplifies build work.

Changes from Dokka 2.0.0-Beta

• Forward Dokka Generator messages to Gradle logger (Kotlin/dokka#3833)
• Add deprecated property to help migrate from JSON Dokka plugin configuration (Kotlin/dokka#3877)
• Rename dokkaPublicationDirectory to basePublicationsDirectory (Kotlin/dokka#3876)
• Rename dokkaModuleDirectory, and mark as internal (Kotlin/dokka#3880)
• Update and add KDoc for DGPv2 (Kotlin/dokka#3842)
• Remove DokkaPluginParametersBuilder (Kotlin/dokka#3872)
• Increase default max heap of Worker to 2G (Kotlin/dokka#3913)
• Remove the dependency of dokkaGenerate on dokkaGenerateModule* (Kotlin/dokka#3920)
• KT-71784 Fix classpath for KMP shared source sets (Kotlin/dokka#3942)
• Fix DGP/KMP integration, so Dokka can 'see' code from shared source sets in target source sets (Kotlin/dokka#3814)

Dokka's K2 analysis

Dokka 2.0.0 introduces K2 analysis, which is currently in an experimental stage. Dokka's K2 analysis leverages Kotlin's K2 compiler frontend for analysing code and uses the same shared Analysis API, which is used in IntelliJ IDEA’s K2 mode. The output with K2 analysis should mostly match that of K1 analysis, but there may be minor differences. We are actively working towards stabilizing K2 analysis and are planning to enable K2 analysis by default in future.

To opt in to Dokka's K2 analysis, add the following flag to your project's gradle.properties file:

org.jetbrains.dokka.experimental.tryK2=true

Known limitations:

• Intersecting source roots (#3701) and intersecting sample roots (#3373) may cause issues.
• Kotlin/JS libraries compiled with the legacy Kotlin/JS compiler are not supported (#3751).

We would greatly value your feedback if you encounter any of these limitations.

... (truncated)

Commits

• 3be1aa6 Update Kotlin/Dokka version references to 2.0.0 (#3957)
• 47ee7fb Update the version to the 2.0.0 release
• a2fe934 Avoid configuration resolution error for v2 migration helper task (#3950)
• a6e5b03 Update DGPv2 examples to use Kotlin 2.1.0 (#3949)
• 94eec02 Run integration tests with Kotlin 2.1.0 (#3865)
• 2b63314 KT-71784 Fix classpath for KMP shared source sets (#3942)
• 17871a0 Add new tests for KDoc links (#3947)
• f728e3a feat: implemented new UI for Navbar and Table of Contents (#3917)
• 9577dc7 Edit some tests to check the stability of the order (#3943)
• ae68eee Add a test for #3702 (#3941)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[smcvb]

Looks good to me 👍