Bump the maven-dependencies group with 6 updates

Bumps the maven-dependencies group with 6 updates:

Package	From	To
org.springframework:spring-test	`5.3.39`	`6.0.0`
org.springframework.boot:spring-boot-autoconfigure	`2.7.18`	`3.0.0`
org.springframework.boot:spring-boot-test	`2.7.18`	`3.0.0`
org.mockito:mockito-core	`4.11.0`	`5.0.0`
org.mockito:mockito-junit-jupiter	`4.11.0`	`5.0.0`
org.apache.maven.plugins:maven-javadoc-plugin	`3.10.0`	`3.10.1`

Updates org.springframework:spring-test from 5.3.39 to 6.0.0

Release notes

Sourced from org.springframework:spring-test's releases.

v6.0.0

See What's New in Spring Framework 6.x and Upgrading to Spring Framework 6.x for upgrade instructions and details of new features.

:star: New Features

Avoid direct URL construction and URL equality checks #29486

Simplify creating RFC 7807 responses from functional endpoints #29462

Allow test classes to provide runtime hints via declarative mechanisms #29455

:notebook_with_decorative_cover: Documentation

Align javadoc of DefaultParameterNameDiscoverer with its behavior #29494

Document AOT support in the TestContext framework #29482

Document Ahead of Time processing in the reference guide #29350

:hammer: Dependency Upgrades

Upgrade to Reactor 2022.0.0 #29465

:heart: Contributors

Thank you to all the contributors who worked on this release:

@ophiuhus and @wilkinsona

v6.0.0-RC4

:star: New Features

Introduce DataFieldMaxValueIncrementer for SQL Server sequences #29447

Introduce findAllAnnotationsOnBean variant on ListableBeanFactory #29446

Introduce support for Jakarta WebSocket 2.1 #29436

Allow @ControllerAdvice in WebFlux to handle exceptions before a handler is selected #22991

:lady_beetle: Bug Fixes

Bean with unresolved generics do not use fallback algorithms with AOT #29454

TomcatRequestUpgradeStrategy is not compatible with Tomcat 10.1 #29434

Autowiring of a generic type produced by a factory bean fails after AOT processing #29385

:notebook_with_decorative_cover: Documentation

Reference PDF containing full docs not available #28451

:hammer: Dependency Upgrades

Revisit Servlet API baseline: Servlet 6.0 in the build, Servlet 5.0 compatibility at runtime #29435

Upgrade to Context Propagation 1.0.0 #29442

Upgrade to Jackson 2.14.0 #29351

Upgrade to Micrometer 1.10.0 #29441

... (truncated)

Commits

5a30a43 Release v6.0.0
42856ba Add milestone repo for optional Netty 5 support
9be6cea Polishing deprecated methods
37b4391 Align javadoc of DefaultParameterNameDiscoverer with its behavior
09a58a5 Polish
10f4ad1 Assert fixed in DefaultErrorResponseBuilder
9457ed3 Document AOT support in the TestContext framework
074ec97 Fix section formatting in the testing chapter
9ede4af Revert "Ignore HttpComponents Javadoc"
bfc1251 Merge branch '5.3.x'
Additional commits viewable in compare view

Updates org.springframework.boot:spring-boot-autoconfigure from 2.7.18 to 3.0.0

Release notes

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

v3.0.0

See the Release notes for 3.0 for upgrade instructions and details of new features.

:star: New Features

Provide a configuration property for the observation patterns of Spring Integration components #33099

:lady_beetle: Bug Fixes

io.micrometer.tracing.Tracer on the classpath breaks AOT processing for tests #33298

Tracer library HTTP instrumentation is auto-configured unnecessarily #33287

Auto-configuration ignores user-provided ObservationConventions #33285

ScheduledBeanLazyInitializationExcludeFilter is auto-configured even when annotation-based scheduled has not been enabled #33284

SpringBootContextLoader prints banner twice when using a @ContextHierarchy #33263

Properties migrator causes an application to fail to start if it tries to map a property whose metadata data entry contains an invalid configuration property name #33250

Wavefront MeterRegistryCustomizer is not applying application tags from application.properties #33244

Actuator responses no longer format timestamps as ISO-8601 #33236

Configuration property is not bound in a native image when property has get, set, and is methods #33232

Configuration property binding does not deal with bridge methods #33212

Contribute missing resource hints for GraphQL schema files and GraphiQL HTML page #33208

Hints for ClientHttpRequestFactory should only be generated for matching methods #33203

Native profile should configure execution in pluginManagement #33184

Configuring management.server.port via a config tree results in a ConverterNotFoundException when the management context is refreshed #33169

JBoss logging does not route directly to SLF4J when using Logback #33155

Test with UseMainMethod.Always do not work with Kotlin main functions #33114

Maven process-aot does not specify source and target release when compiling generated sources #33112

Some Actuator beans are ineligible for post-processing #33110

AOT-generated source fails to compile when Actuator is enabled on a WebFlux project #33106

@ContextHierarchy should never be used with main method #33078

Maven process-aot fails when compiler plugin has been configured with --enable-preview #33012

Wavefront application tags differ from those used in a Spring Boot 2.x application #32844

Maven goal spring-boot:build-image runs package phase twice #26455

:notebook_with_decorative_cover: Documentation

Document observation for R2DBC #33335

Align Tomcat multiple connectors example with recommendation to configure SSL declaratively #33333

Actuator document is misleading about k8s startup probe #33327

Update documented for @Timed to reflect narrower support #33282

Update reference documentation to replace mentions of tags providers and contributors with their Observation-based equivalents #33281

Link to Micrometer's @Timed documentation #33266

Clarify use of the spring.cache.type property with Hazelcast #33258

Example git.commit.time in the Actuator API documentation is thousands of years in the future #33256

Update Spring Security filter dispatcher types docs to reflect change in default value #33252

Documentation for nested configuration properties in a native image uses @NestedConfigurationProperty too widely #33239

Document that the jar task should not be disabled when building a native image #33238

Document nesting configuration properties using records or Kotlin data classes and how and when to use @NestedConfigurationProperty #33235

Links to Features describes sections that have moved elsewhere #33214

Fix broken links in docs #33209

Document the need for compilation with -parameters when targeting a native image #33182

... (truncated)

Commits

c9c359f Release v3.0.0
fb2cc73 Work around Thymeleaf's dependency on spring-security-bom:6.0.0-RC2
355b428 Merge branch '2.7.x'
7ea5881 Update LATEST_GA to false to prepare for 3.0.0's release
1de09f4 Merge branch '2.6.x' into 2.7.x
e922650 Upgrade to Spring Framework 6.0.2
4b8a28a Next development version (v2.7.7-SNAPSHOT)
14ba9b1 Start building against Spring Framework 6.0.2 snapshots
d4a9100 Next development version (v2.6.15-SNAPSHOT)
28cb225 Merge branch '2.7.x'
Additional commits viewable in compare view

Updates org.springframework.boot:spring-boot-test from 2.7.18 to 3.0.0

Release notes

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

v3.0.0

See the Release notes for 3.0 for upgrade instructions and details of new features.

:star: New Features

Provide a configuration property for the observation patterns of Spring Integration components #33099

:lady_beetle: Bug Fixes

io.micrometer.tracing.Tracer on the classpath breaks AOT processing for tests #33298

Tracer library HTTP instrumentation is auto-configured unnecessarily #33287

Auto-configuration ignores user-provided ObservationConventions #33285

ScheduledBeanLazyInitializationExcludeFilter is auto-configured even when annotation-based scheduled has not been enabled #33284

SpringBootContextLoader prints banner twice when using a @ContextHierarchy #33263

Properties migrator causes an application to fail to start if it tries to map a property whose metadata data entry contains an invalid configuration property name #33250

Wavefront MeterRegistryCustomizer is not applying application tags from application.properties #33244

Actuator responses no longer format timestamps as ISO-8601 #33236

Configuration property is not bound in a native image when property has get, set, and is methods #33232

Configuration property binding does not deal with bridge methods #33212

Contribute missing resource hints for GraphQL schema files and GraphiQL HTML page #33208

Hints for ClientHttpRequestFactory should only be generated for matching methods #33203

Native profile should configure execution in pluginManagement #33184

Configuring management.server.port via a config tree results in a ConverterNotFoundException when the management context is refreshed #33169

JBoss logging does not route directly to SLF4J when using Logback #33155

Test with UseMainMethod.Always do not work with Kotlin main functions #33114

Maven process-aot does not specify source and target release when compiling generated sources #33112

Some Actuator beans are ineligible for post-processing #33110

AOT-generated source fails to compile when Actuator is enabled on a WebFlux project #33106

@ContextHierarchy should never be used with main method #33078

Maven process-aot fails when compiler plugin has been configured with --enable-preview #33012

Wavefront application tags differ from those used in a Spring Boot 2.x application #32844

Maven goal spring-boot:build-image runs package phase twice #26455

:notebook_with_decorative_cover: Documentation

Document observation for R2DBC #33335

Align Tomcat multiple connectors example with recommendation to configure SSL declaratively #33333

Actuator document is misleading about k8s startup probe #33327

Update documented for @Timed to reflect narrower support #33282

Update reference documentation to replace mentions of tags providers and contributors with their Observation-based equivalents #33281

Link to Micrometer's @Timed documentation #33266

Clarify use of the spring.cache.type property with Hazelcast #33258

Example git.commit.time in the Actuator API documentation is thousands of years in the future #33256

Update Spring Security filter dispatcher types docs to reflect change in default value #33252

Documentation for nested configuration properties in a native image uses @NestedConfigurationProperty too widely #33239

Document that the jar task should not be disabled when building a native image #33238

Document nesting configuration properties using records or Kotlin data classes and how and when to use @NestedConfigurationProperty #33235

Links to Features describes sections that have moved elsewhere #33214

Fix broken links in docs #33209

Document the need for compilation with -parameters when targeting a native image #33182

... (truncated)

Commits

c9c359f Release v3.0.0
fb2cc73 Work around Thymeleaf's dependency on spring-security-bom:6.0.0-RC2
355b428 Merge branch '2.7.x'
7ea5881 Update LATEST_GA to false to prepare for 3.0.0's release
1de09f4 Merge branch '2.6.x' into 2.7.x
e922650 Upgrade to Spring Framework 6.0.2
4b8a28a Next development version (v2.7.7-SNAPSHOT)
14ba9b1 Start building against Spring Framework 6.0.2 snapshots
d4a9100 Next development version (v2.6.15-SNAPSHOT)
28cb225 Merge branch '2.7.x'
Additional commits viewable in compare view

Updates org.springframework.boot:spring-boot-test from 2.7.18 to 3.0.0

Release notes

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

v3.0.0

See the Release notes for 3.0 for upgrade instructions and details of new features.

:star: New Features

Provide a configuration property for the observation patterns of Spring Integration components #33099

:lady_beetle: Bug Fixes

io.micrometer.tracing.Tracer on the classpath breaks AOT processing for tests #33298

Tracer library HTTP instrumentation is auto-configured unnecessarily #33287

Auto-configuration ignores user-provided ObservationConventions #33285

ScheduledBeanLazyInitializationExcludeFilter is auto-configured even when annotation-based scheduled has not been enabled #33284

SpringBootContextLoader prints banner twice when using a @ContextHierarchy #33263

Properties migrator causes an application to fail to start if it tries to map a property whose metadata data entry contains an invalid configuration property name #33250

Wavefront MeterRegistryCustomizer is not applying application tags from application.properties #33244

Actuator responses no longer format timestamps as ISO-8601 #33236

Configuration property is not bound in a native image when property has get, set, and is methods #33232

Configuration property binding does not deal with bridge methods #33212

Contribute missing resource hints for GraphQL schema files and GraphiQL HTML page #33208

Hints for ClientHttpRequestFactory should only be generated for matching methods #33203

Native profile should configure execution in pluginManagement #33184

Configuring management.server.port via a config tree results in a ConverterNotFoundException when the management context is refreshed #33169

JBoss logging does not route directly to SLF4J when using Logback #33155

Test with UseMainMethod.Always do not work with Kotlin main functions #33114

Maven process-aot does not specify source and target release when compiling generated sources #33112

Some Actuator beans are ineligible for post-processing #33110

AOT-generated source fails to compile when Actuator is enabled on a WebFlux project #33106

@ContextHierarchy should never be used with main method #33078

Maven process-aot fails when compiler plugin has been configured with --enable-preview #33012

Wavefront application tags differ from those used in a Spring Boot 2.x application #32844

Maven goal spring-boot:build-image runs package phase twice #26455

:notebook_with_decorative_cover: Documentation

Document observation for R2DBC #33335

Align Tomcat multiple connectors example with recommendation to configure SSL declaratively #33333

Actuator document is misleading about k8s startup probe #33327

Update documented for @Timed to reflect narrower support #33282

Update reference documentation to replace mentions of tags providers and contributors with their Observation-based equivalents #33281

Link to Micrometer's @Timed documentation #33266

Clarify use of the spring.cache.type property with Hazelcast #33258

Example git.commit.time in the Actuator API documentation is thousands of years in the future #33256

Update Spring Security filter dispatcher types docs to reflect change in default value #33252

Documentation for nested configuration properties in a native image uses @NestedConfigurationProperty too widely #33239

Document that the jar task should not be disabled when building a native image #33238

Document nesting configuration properties using records or Kotlin data classes and how and when to use @NestedConfigurationProperty #33235

Links to Features describes sections that have moved elsewhere #33214

Fix broken links in docs #33209

Document the need for compilation with -parameters when targeting a native image #33182

... (truncated)

Commits

c9c359f Release v3.0.0
fb2cc73 Work around Thymeleaf's dependency on spring-security-bom:6.0.0-RC2
355b428 Merge branch '2.7.x'
7ea5881 Update LATEST_GA to false to prepare for 3.0.0's release
1de09f4 Merge branch '2.6.x' into 2.7.x
e922650 Upgrade to Spring Framework 6.0.2
4b8a28a Next development version (v2.7.7-SNAPSHOT)
14ba9b1 Start building against Spring Framework 6.0.2 snapshots
d4a9100 Next development version (v2.6.15-SNAPSHOT)
28cb225 Merge branch '2.7.x'
Additional commits viewable in compare view

Updates org.mockito:mockito-core from 4.11.0 to 5.0.0

Release notes

Sourced from org.mockito:mockito-core's releases.

v5.0.0

Mockito 5: prepare for future JDK versions

For a while now, we have seen an increase in problems/incompatibilities with recent versions of the JDK due to our usage of JVM-internal API. Most notably, JDK 17 made some changes which are incompatible with the current subclass mockmaker. Therefore, to prepare for the future of JDK, we are making some core changes to ensure Mockito keeps on working.

Switch the default mockmaker to mockito-inline

Back in Mockito 2.7.6, we published a new mockmaker based on the "inline bytecode" principle. This mockmaker creates mocks manipulating bytecode equivalent within the original class such that its method implementations hook into the normal Mockito machinery. As a comparison, the subclass mockmaker generates "real" subclasses for mocks, to mimic the same behavior. While the approaches are similar, the inline mockmaker avoids certain restrictions that the JDK imposes. For example, it does not violate module boundaries (introduced in JDK 9, but more heavily used in JDK 17) and avoids the leaking of the creation of the subclass.

Massive thanks to community member @reta who implemented this change.

Note: this does not affect mockito-android nor testing on Android.

When should I still be using the subclass mockmaker?

There are legitimate remaining use cases for the subclass mockmaker. For example, on the Graal VM's native image, the inline mockmaker will not work and the subclass mockmaker is the appropriate choice. Additionally, if you would like to avoid mocking final classes, using the subclass mockmaker is a possibibility. Note however that if you solely want to use the subclass mockmaker to avoid mocking final, you will run into the above mentioned issues on JDK 17+. We want to leave this choice up to our users, which is why we will keep on supporting the subclass mockmaker.

If you want to use the subclass mockmaker instead, you can use the new mockito-subclass artifact (published on Maven Central along with all our other artifacts).

Update the minimum supported Java version to 11

Mockito 4 supports Java 8 and above. Similar to other open source projects, we are moving away from JDK 8 and to newer versions. The primary reason for moving away from JDK 8 is the increasing maintenance costs with keeping our own infrastructure working. Lately we have been running into more and more JDK 8 breakages. Additionally, while we want to support the newest JDK API's, our current solution to support both JDK 8 and newer versions causes issues with the SecurityManager. Since we want Mockito to work on the newest version and more and more businesses adopting JDK 11, we have decided to make the switch as well.

Massive thanks to community member @reta who implemented this change.

What should I do if I still run JDK 8?

For JDK 8 and below, you can keep on using Mockito 4. This is similar to if you are using JDK 6, for which you can keep on using Mockito 2. The changes in Mockito 5 (for now) are primarily focused on the latest JDK versions, which means the API differences between Mockito 4 and 5 are minimal. However, over time this will most likely widen, so we do recommend adopting JDK 11 in the future.

New type() method on ArgumentMatcher

One of our most used public API's for customizing Mockito is the ArgumentMatcher interface.

... (truncated)

Commits

adf528d Bump versions.bytebuddy from 1.12.21 to 1.12.22 (#2864)
2418419 Bump versions.junitJupiter from 5.9.1 to 5.9.2 (#2858)
3d40cd5 Bump junit-platform-launcher from 1.9.1 to 1.9.2 (#2859)
9bec8e3 Bump versions.errorprone from 2.17.0 to 2.18.0 (#2857)
a9595f5 Switch the default mockmaker to the inline mockmaker on JDK 17+ (#2834)
c5d7fbc Bump assertj-core from 3.23.1 to 3.24.1 (#2854)
dbd7f2f Bump versions.bytebuddy from 1.12.20 to 1.12.21 (#2852)
4d62fa7 Bump junit from 1.1.4 to 1.1.5 (#2850)
b1b6d6a Bump espresso-core from 3.5.0 to 3.5.1 (#2849)
7b5b8dd Remove use case for non-existent method VerificationWithTimeout#never (#2848)
Additional commits viewable in compare view

Updates org.mockito:mockito-junit-jupiter from 4.11.0 to 5.0.0

Release notes

Sourced from org.mockito:mockito-junit-jupiter's releases.

v5.0.0

Mockito 5: prepare for future JDK versions

For a while now, we have seen an increase in problems/incompatibilities with recent versions of the JDK due to our usage of JVM-internal API. Most notably, JDK 17 made some changes which are incompatible with the current subclass mockmaker. Therefore, to prepare for the future of JDK, we are making some core changes to ensure Mockito keeps on working.

Switch the default mockmaker to mockito-inline

Back in Mockito 2.7.6, we published a new mockmaker based on the "inline bytecode" principle. This mockmaker creates mocks manipulating bytecode equivalent within the original class such that its method implementations hook into the normal Mockito machinery. As a comparison, the subclass mockmaker generates "real" subclasses for mocks, to mimic the same behavior. While the approaches are similar, the inline mockmaker avoids certain restrictions that the JDK imposes. For example, it does not violate module boundaries (introduced in JDK 9, but more heavily used in JDK 17) and avoids the leaking of the creation of the subclass.

Massive thanks to community member @reta who implemented this change.

Note: this does not affect mockito-android nor testing on Android.

When should I still be using the subclass mockmaker?

There are legitimate remaining use cases for the subclass mockmaker. For example, on the Graal VM's native image, the inline mockmaker will not work and the subclass mockmaker is the appropriate choice. Additionally, if you would like to avoid mocking final classes, using the subclass mockmaker is a possibibility. Note however that if you solely want to use the subclass mockmaker to avoid mocking final, you will run into the above mentioned issues on JDK 17+. We want to leave this choice up to our users, which is why we will keep on supporting the subclass mockmaker.

If you want to use the subclass mockmaker instead, you can use the new mockito-subclass artifact (published on Maven Central along with all our other artifacts).

Update the minimum supported Java version to 11

Mockito 4 supports Java 8 and above. Similar to other open source projects, we are moving away from JDK 8 and to newer versions. The primary reason for moving away from JDK 8 is the increasing maintenance costs with keeping our own infrastructure working. Lately we have been running into more and more JDK 8 breakages. Additionally, while we want to support the newest JDK API's, our current solution to support both JDK 8 and newer versions causes issues with the SecurityManager. Since we want Mockito to work on the newest version and more and more businesses adopting JDK 11, we have decided to make the switch as well.

Massive thanks to community member @reta who implemented this change.

What should I do if I still run JDK 8?

For JDK 8 and below, you can keep on using Mockito 4. This is similar to if you are using JDK 6, for which you can keep on using Mockito 2. The changes in Mockito 5 (for now) are primarily focused on the latest JDK versions, which means the API differences between Mockito 4 and 5 are minimal. However, over time this will most likely widen, so we do recommend adopting JDK 11 in the future.

New type() method on ArgumentMatcher

One of our most used public API's for customizing Mockito is the ArgumentMatcher interface.

... (truncated)

Commits

adf528d Bump versions.bytebuddy from 1.12.21 to 1.12.22 (#2864)
2418419 Bump versions.junitJupiter from 5.9.1 to 5.9.2 (#2858)
3d40cd5 Bump junit-platform-launcher from 1.9.1 to 1.9.2 (#2859)
9bec8e3 Bump versions.errorprone from 2.17.0 to 2.18.0 (#2857)
a9595f5 Switch the default mockmaker to the inline mockmaker on JDK 17+ (#2834)
c5d7fbc Bump assertj-core from 3.23.1 to 3.24.1 (#2854)
dbd7f2f Bump versions.bytebuddy from 1.12.20 to 1.12.21 (#2852)
4d62fa7 Bump junit from 1.1.4 to 1.1.5 (#2850)
b1b6d6a Bump espresso-core from 3.5.0 to 3.5.1 (#2849)
7b5b8dd Remove use case for non-existent method VerificationWithTimeout#never (#2848)
Additional commits viewable in compare view

Updates org.mockito:mockito-junit-jupiter from 4.11.0 to 5.0.0

Release notes

Sourced from org.mockito:mockito-junit-jupiter's releases.

v5.0.0

Mockito 5: prepare for future JDK versions

For a while now, we have seen an increase in problems/incompatibilities with recent versions of the JDK due to our usage of JVM-internal API. Most notably, JDK 17 made some changes which are incompatible with the current subclass mockmaker. Therefore, to prepare for the future of JDK, we are making some core changes to ensure Mockito keeps on working.

Switch the default mockmaker to mockito-inline

Back in Mockito 2.7.6, we published a new mockmaker based on the "inline bytecode" principle. This mockmaker creates mocks manipulating bytecode equivalent within the original class such that its method implementations hook into the normal Mockito machinery. As a comparison, the subclass mockmaker generates "real" subclasses for mocks, to mimic the same behavior. While the approaches are similar, the inline mockmaker avoids certain restrictions that the JDK imposes. For example, it does not violate module boundaries (introduced in JDK 9, but more heavily used in JDK 17) and avoids the leaking of the creation of the subclass.

Massive thanks to community member @reta who implemented this change.

Note: this does not affect mockito-android nor testing on Android.

When should I still be using the subclass mockmaker?

There are legitimate remaining use cases for the subclass mockmaker. For example, on the Graal VM's native image, the inline mockmaker will not work and the subclass mockmaker is the appropriate choice. Additionally, if you would like to avoid mocking final classes, using the subclass mockmaker is a possibibility. Note however that if you solely want to use the subclass mockmaker to avoid mocking final, you will run into the above mentioned issues on JDK 17+. We want to leave this choice up to our users, which is why we will keep on supporting the subclass mockmaker.

If you want to use the subclass mockmaker instead, you can use the new mockito-subclass artifact (published on Maven Central along with all our other artifacts).

Update the minimum supported Java version to 11

Mockito 4 supports Java 8 and above. Similar to other open source projects, we are moving away from JDK 8 and to newer versions. The primary reason for moving away from JDK 8 is the increasing maintenance costs with keeping our own infrastructure working. Lately we have been running into more and more JDK 8 breakages. Additionally, while we want to support the newest JDK API's, our current solution to support both JDK 8 and newer versions causes issues with the SecurityManager. Since we want Mockito to work on the newest version and more and more businesses adopting JDK 11, we have decided to make the switch as well.

Massive thanks to community member @reta who implemented this change.

What should I do if I still run JDK 8?

For JDK 8 and below, you can keep on using Mockito 4. This is similar to if you are using JDK 6, for which you can keep on using Mockito 2. The changes in Mockito 5 (for now) are primarily focused on the latest JDK versions, which means the API differences between Mockito 4 and 5 are minimal. However, over time this will most likely widen, so we do recommend adopting JDK 11 in the future.

New type() method on ArgumentMatcher

One of our most used public API's for customizing Mockito is the ArgumentMatcher interface.

... (truncated)

Commits

adf528d Bump versions.bytebuddy from 1.12.21 to 1.12.22 (#2864)
2418419 Bump versions.junitJupiter from 5.9.1 to 5.9.2 (#2858)
3d40cd5 Bump junit-platform-launcher from 1.9.1 to 1.9.2 (#2859)
9bec8e3 Bump versions.errorprone from 2.17.0 to 2.18.0 (#2857)
a9595f5 Switch the default mockmaker to the inline mockmaker on JDK 17+ (#2834)
c5d7fbc Bump assertj-core from 3.23.1 to 3.24.1 (#2854)
dbd7f2f Bump versions.bytebuddy from 1.12.20 to 1.12.21 (#2852)
4d62fa7 Bump junit from 1.1.4 to 1.1.5 (#2850)
b1b6d6a Bump espresso-core from 3.5.0 to 3.5.1 (#2849)
7b5b8dd Remove use case for non-existent method VerificationWithTimeout#never (#2848)
Additional commits viewable in compare view

Updates org.apache.maven.plugins:maven-javadoc-plugin from 3.10.0 to 3.10.1

Release notes

Sourced from org.apache.maven.plugins:maven-javadoc-plugin's releases.

maven-javadoc-plugin-3.10.1

What's Changed

[MJAVADOC-810] [REGRESSION] MJAVADOC-791 causes forked Maven execution fail if any toolchains or settings file isn't present by @cstamas in apache/maven-javadoc-plugin#313

Bump org.apache.commons:commons-lang3 from 3.16.0 to 3.17.0 by @dependabot in apache/maven-javadoc-plugin#314

Bump org.codehaus.plexus:plexus-io from 3.5.0 to 3.5.1 by @dependabot in apache/maven-javadoc-plugin#315

Bump commons-io:commons-io from 2.16.1 to 2.17.0 by @dependabot in apache/maven-javadoc-plugin#319

[MJAVADOC-812] [REGRESSION] maven-javadoc-plugin 3.10.0 creates empty… by @michael-o in apache/maven-javadoc-plugin#320

Full Changelog: https://github.com/apache/maven-javadoc-plugin/compare/maven-javadoc-plugin-3.10.0...maven-javadoc-plugin-3.10.1

Commits

091785b [maven-release-plugin] prepare release maven-javadoc-plugin-3.10.1
cde7c56 [MJAVADOC-812] [REGRESSION] maven-javadoc-plugin 3.10.0 creates empty JARs
db6d7f6 [MJAVADOC-811] javadoc.bat fails to execute on Windows when project is not on...
a737e16 Bump commons-io:commons-io from 2.16.1 to 2.17.0
577c204 Bump org.codehaus.plexus:plexus-io from 3.5.0 to 3.5.1
ff52cff Bump org.apache.commons:commons-lang3 from 3.16.0 to 3.17.0
54a7651 Add goal prefix
a424c6b [MJAVADOC-810] [REGRESSION] MJAVADOC-791 causes forked Maven execution fail i...
d9c0002 [maven-release-plugin] prepare for next development iteration
See full diff in compare view

Most Recent Ignore Conditions Applied to This Pull Request

| Dependency Name | Ignore Conditions | | --- | --- | | org.mockito:mockito-core | [>= 5.a, < 6] | | org.mockito:mockito-junit-jupiter | [>= 5.a, < 6] | | org.springframework:spring-test | [>= 6.a, < 7] | | org.springframework.boot:spring-boot-autoconfigure | [>= 3.a, < 4] | | org.springframework.boot:spring-boot-test | [>= 3.a, < 4] | | org.springframework:spring-test | [>= 6.0.a, < 6.1] | | org.springframework.boot:spring-boot-autoconfigure | [>= 3.0.a, < 3.1] | | org.springframework.boot:spring-boot-test | [>= 3.0.a, < 3.1] | | org.mockito:mockito-core | [>= 5.0.a, < 5.1] | | org.mockito:mockito-junit-jupiter | [>= 5.0.a, < 5.1] |

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 ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore 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 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 ` 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 ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions

AxonFramework / extension-reactor

Bump the maven-dependencies group with 6 updates #288

v6.0.0

:star: New Features

:notebook_with_decorative_cover: Documentation

:hammer: Dependency Upgrades

:heart: Contributors

v6.0.0-RC4

:star: New Features

:lady_beetle: Bug Fixes

:notebook_with_decorative_cover: Documentation

:hammer: Dependency Upgrades

v3.0.0

:star: New Features

:lady_beetle: Bug Fixes

:notebook_with_decorative_cover: Documentation

v3.0.0

:star: New Features

:lady_beetle: Bug Fixes

:notebook_with_decorative_cover: Documentation

v3.0.0

:star: New Features

:lady_beetle: Bug Fixes

:notebook_with_decorative_cover: Documentation

v5.0.0

Mockito 5: prepare for future JDK versions

Switch the default mockmaker to mockito-inline

When should I still be using the subclass mockmaker?

Update the minimum supported Java version to 11

What should I do if I still run JDK 8?

New type() method on ArgumentMatcher

v5.0.0

Mockito 5: prepare for future JDK versions

Switch the default mockmaker to mockito-inline

When should I still be using the subclass mockmaker?

Update the minimum supported Java version to 11

What should I do if I still run JDK 8?

New type() method on ArgumentMatcher

v5.0.0

Mockito 5: prepare for future JDK versions

Switch the default mockmaker to mockito-inline

When should I still be using the subclass mockmaker?

Update the minimum supported Java version to 11

What should I do if I still run JDK 8?

New type() method on ArgumentMatcher

maven-javadoc-plugin-3.10.1

What's Changed

Quality Gate passed

Switch the default mockmaker to `mockito-inline`

New `type()` method on `ArgumentMatcher`

Switch the default mockmaker to `mockito-inline`

New `type()` method on `ArgumentMatcher`

Switch the default mockmaker to `mockito-inline`

New `type()` method on `ArgumentMatcher`