Skip to content

Bump the maven-dependencies group with 5 updates#341

Merged
github-actions[bot] merged 1 commit intomasterfrom
dependabot/maven/maven-dependencies-8142d2d95f
May 26, 2025
Merged

Bump the maven-dependencies group with 5 updates#341
github-actions[bot] merged 1 commit intomasterfrom
dependabot/maven/maven-dependencies-8142d2d95f

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github May 26, 2025

Bumps the maven-dependencies group with 5 updates:

Package From To
org.awaitility:awaitility 4.2.0 4.3.0
org.junit:junit-bom 5.10.1 5.12.2
org.jacoco:jacoco-maven-plugin 0.8.11 0.8.13
org.axonframework:axon-messaging 4.10.0 4.11.2
org.axonframework:axon-spring-boot-autoconfigure 4.10.0 4.11.2

Updates org.awaitility:awaitility from 4.2.0 to 4.3.0

Changelog

Sourced from org.awaitility:awaitility's changelog.

Changelog 4.3.0 (2025-02-21)

  • Support for kotlin.time.Duration in Kotlin DSL (thanks to Ivo Šmíd for PR)

  • Upgraded kotlin version in the awaitility-kotlin module to 2.1.10

  • Using a more descriptive error message when using VERY long wait conditions or poll durations (issue 290)

  • Added an overloaded method of untilAsserted(..) that takes a supplier and a consumer. For example, lets say you have a class like this: public class MyClass { public String myFunction() { // Imagine stuff being executed in asynchronously here and the result of this // operation is a string called "my value" return "my value" } }

    // Then in your test you can wait for the "myFunction" to be asserted by a "consumer" that uses // assertj to make sure that "myFunction" returns ""my value" await().untilAsserted(myClass::myFunction, value -> Assertions.assertThat(value).isEqualTo("my value"));

    This has also been implemented for all atomic, adder, and accumulator methods.

Changelog 4.2.2 (2024-08-07)

  • Support JDK EA builds in JavaVersionDetector (thanks to Oleg Estekhin for pull request)

Changelog 4.2.1 (2024-03-15)

  • Upgraded Kotlin to 1.9.22

  • Added extension properties forever, then, and, given to the Kotlin extension. This allows you to do e.g.:

    await.forever until { .. }

  • Added shortcut for enabling logging. Before you had to do e.g.

    await() .with() .conditionEvaluationListener(new ConditionEvaluationLogger(log::info)) .pollInterval(ONE_HUNDRED_MILLISECONDS) .until(logs::size, is(4));

    You can now instead use the "logging" shortcut:

    await() .with() .logging(log::info) .pollInterval(ONE_HUNDRED_MILLISECONDS) .until(logs::size, is(4));

    or simply ".logging()" for "System.out".

    This shortcut has also been added globally:

... (truncated)

Commits
  • e3ff879 [maven-release-plugin] prepare release awaitility-4.3.0
  • d116712 [ci skip] Preparing changelog for release
  • 4e186df Added kotlin source folder explicitly
  • e8d3ab7 Upgraded lots of plugin dependencies
  • a7a167a Added an overloaded method of untilAsserted(..) that takes a supplier and a c...
  • ef8f663 Make ConditionFactory safer to use in java 8
  • 5550079 Using a more descriptive error message when using VERY long wait conditions o...
  • 2a9814b Upgraded kotlin version in the awaitility-kotlin module to 2.1.10
  • 8f22c00 [ci skip] Updated changelog.txt to reflect latest changes
  • 6a35c24 #235 Support for kotlin.time.Duration in Kotlin DSL (#285)
  • Additional commits viewable in compare view

Updates org.junit:junit-bom from 5.10.1 to 5.12.2

Release notes

Sourced from org.junit:junit-bom's releases.

JUnit 5.12.2 = Platform 1.12.2 + Jupiter 5.12.2 + Vintage 5.12.2

See Release Notes.

Full Changelog: junit-team/junit-framework@r5.12.1...r5.12.2

JUnit 5.12.1 = Platform 1.12.1 + Jupiter 5.12.1 + Vintage 5.12.1

See Release Notes.

Full Changelog: junit-team/junit-framework@r5.12.0...r5.12.1

JUnit 5.12.0 = Platform 1.12.0 + Jupiter 5.12.0 + Vintage 5.12.0

See Release Notes.

New Contributors

Full Changelog: junit-team/junit-framework@r5.11.4...r5.12.0

JUnit 5.12.0-RC2 = Platform 1.12.0-RC2 + Jupiter 5.12.0-RC2 + Vintage 5.12.0-RC2

See Release Notes.

Full Changelog: junit-team/junit-framework@r5.12.0-RC1...r5.12.0-RC2

JUnit 5.12.0-RC1 = Platform 1.12.0-RC1 + Jupiter 5.12.0-RC1 + Vintage 5.12.0-RC1

See Release Notes.

Full Changelog: junit-team/junit-framework@r5.12.0-M1...r5.12.0-RC1

JUnit 5.12.0-M1 = Platform 1.12.0-M1 + Jupiter 5.12.0-M1 + Vintage 5.12.0-M1

See Release Notes.

New Contributors

... (truncated)

Commits
  • 0a44659 Release 5.12.2
  • 4c7dfdc Finalize 5.12.2 release notes
  • 561613e Fix handling of CleanupMode.ON_SUCCESS
  • 19d07d2 Add 5.12.2 release notes from template
  • 803cbb6 Add build parameter for enabling dry-run mode for test execution
  • eb43e62 Back to snapshots for further development
  • ba9c9ae Release 5.12.1
  • e28ad4a Finalize 5.12.1 release notes
  • 1044e2c Move entry to 5.12.1 release notes
  • bea821d Fix Javadoc formatting
  • Additional commits viewable in compare view

Updates org.jacoco:jacoco-maven-plugin from 0.8.11 to 0.8.13

Release notes

Sourced from org.jacoco:jacoco-maven-plugin's releases.

0.8.13

New Features

  • JaCoCo now officially supports Java 23 and Java 24 (GitHub #1757, #1631, #1867).
  • Experimental support for Java 25 class files (GitHub #1807).
  • Calculation of line coverage for Kotlin inline functions (GitHub #1670).
  • Calculation of line coverage for Kotlin inline functions with reified type parameter (GitHub #1670, #1700).
  • Calculation of coverage for Kotlin JvmSynthetic functions (GitHub #1700).
  • Part of bytecode generated by the Kotlin Compose compiler plugin is filtered out during generation of report (GitHub #1616).
  • Part of bytecode generated by the Kotlin compiler for inline value classes is filtered out during generation of report (GitHub #1475).
  • Part of bytecode generated by the Kotlin compiler for suspending lambdas without suspension points is filtered out during generation of report (GitHub #1283).
  • Part of bytecode generated by the Kotlin compiler for when expressions and statements with nullable enum subject is filtered out during generation of report (GitHub #1774).
  • Part of bytecode generated by the Kotlin compiler for when expressions and statements with nullable String subject is filtered out during generation of report (GitHub #1769).
  • Part of bytecode generated by the Kotlin compiler for chains of safe call operators is filtered out during generation of report (GitHub #1810, #1818).
  • Method getEntries generated by the Kotlin compiler for enum classes is filtered out during generation of report (GitHub #1625).
  • Methods generated by the Kotlin compiler for constructors and functions with JvmOverloads annotation are filtered out (GitHub #1768).

Fixed bugs

  • Fixed interpretation of Kotlin SMAP (GitHub #1525).
  • File extensions are preserved in HTML report in case of clashes of normalized file names (GitHub #1660).

Non-functional Changes

  • JaCoCo build now uses Maven Wrapper and requires at least Maven 3.9.9 (GitHub #1708, #1707, #1681).
  • JaCoCo now depends on ASM 9.8 (GitHub #1862).
  • More context information when IllegalArgumentException occurs during reading of zip file (GitHub #1833).

0.8.12

New Features

  • JaCoCo now officially supports Java 22 (GitHub #1596).
  • Experimental support for Java 23 class files (GitHub #1553).

Fixed bugs

  • Branches added by the Kotlin compiler for functions with default arguments and having more than 32 parameters are filtered out during generation of report (GitHub #1556).
  • Branch added by the Kotlin compiler version 1.5.0 and above for reading from lateinit property is filtered out during generation of report (GitHub #1568).

Non-functional Changes

  • JaCoCo now depends on ASM 9.7 (GitHub #1600).
Commits

Updates org.axonframework:axon-messaging from 4.10.0 to 4.11.2

Release notes

Sourced from org.axonframework:axon-messaging's releases.

Axon Framework v4.11.2

⭐ Features

  • #3170 Persistent streams - auto configuration #3339
  • #3170 Persistent streams - automatic configuration #3184
  • Persistent streams - automatic configuration #3170

📈 Enhancements

  • Ignore aggregates that have been AggregateLifecycle#markDeleted when using the Create-if-missing policy. #3333
  • Split default Avro schema store creation from the schema scan #3329
  • Separate AvroSchemaScan based detection of schemas and creation of a default Avro SchemaStore #3328
  • Proper handling of attempts to recreate event sourcing aggregates marked as deleted #3323

🪲 Bug fixes

  • #3385 Align interceptor behavior for Aggregate Members #3404
  • CommandHandlerInterceptor on Aggregate Member only called if Aggregate has CommandHandlerInterceptor as well #3385
  • Fix default Snapshotter throwing IndexOutOfBoundsException #3375
  • fix Correlation data table #3370
  • Fixes subscription query update permits issue #3356
  • #3171 Support @CreationPolicy annotated interface methods again #3335
  • Reset the Coordinator's processing gate if the Coordinator was aborted and rescheduled #3307

❤️ Contributors

We'd like to thank all the contributors who worked on this release!

Axon Framework v4.11.1

⚠️ Chance for duplicate interceptor registration

In 4.11.0 of Axon Framework, Spring Boot auto-configuration support for MessageHandlerInterceptors and MessageDispatchInterceptors was introduced. For those curious how this was achieved, we refer to #3203.

Although the feature on it's own shouldn't cause trouble, be aware that if the Axon Framework application you are working on already exposes MessageHandlerInterceptors and MessageDispatchInterceptors beans in the Spring Application Context. When this is the case, in combination with custom code to wire these beans into your infrastructure components, the chance is high they'll be registered twice due to the aforementioned feature.

As such, we recommend to either:

  1. Remove the custom interceptor auto-configuration, to pass along this task to Axon Framework, or
  2. Exclude the InterceptorAutoConfiguration from your Spring Boot auto-configuration.

By following either road, you should be ascertained that interceptors are not registered twice.

... (truncated)

Commits
  • 9bc19de [maven-release-plugin] prepare release axon-4.11.2
  • 618e7b2 Merge pull request #3410 from AxonFramework/documentation/3348/interceptors-f...
  • 01243a8 Add description on how to create a persistent stream message source
  • 1d265b4 Fine tune JavaDoc
  • 2f66522 Fixed the note, as well as added a hierarchy sample
  • 21a6f9b Add note for Intercepting @EventSourcingHandler annotated methods on..
  • f36581a Merge pull request #3405 from AxonFramework/documentation/3374/allocation-size
  • 184c53f Merge pull request #3404 from AxonFramework/bug/3385/interceptor-chain-not-found
  • 397f961 Add allocation-size details
  • 98fe1c5 Merge branch 'axon-4.11.x' into bug/3385/interceptor-chain-not-found
  • Additional commits viewable in compare view

Updates org.axonframework:axon-spring-boot-autoconfigure from 4.10.0 to 4.11.2

Release notes

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

Axon Framework v4.11.2

⭐ Features

  • #3170 Persistent streams - auto configuration #3339
  • #3170 Persistent streams - automatic configuration #3184
  • Persistent streams - automatic configuration #3170

📈 Enhancements

  • Ignore aggregates that have been AggregateLifecycle#markDeleted when using the Create-if-missing policy. #3333
  • Split default Avro schema store creation from the schema scan #3329
  • Separate AvroSchemaScan based detection of schemas and creation of a default Avro SchemaStore #3328
  • Proper handling of attempts to recreate event sourcing aggregates marked as deleted #3323

🪲 Bug fixes

  • #3385 Align interceptor behavior for Aggregate Members #3404
  • CommandHandlerInterceptor on Aggregate Member only called if Aggregate has CommandHandlerInterceptor as well #3385
  • Fix default Snapshotter throwing IndexOutOfBoundsException #3375
  • fix Correlation data table #3370
  • Fixes subscription query update permits issue #3356
  • #3171 Support @CreationPolicy annotated interface methods again #3335
  • Reset the Coordinator's processing gate if the Coordinator was aborted and rescheduled #3307

❤️ Contributors

We'd like to thank all the contributors who worked on this release!

Axon Framework v4.11.1

⚠️ Chance for duplicate interceptor registration

In 4.11.0 of Axon Framework, Spring Boot auto-configuration support for MessageHandlerInterceptors and MessageDispatchInterceptors was introduced. For those curious how this was achieved, we refer to #3203.

Although the feature on it's own shouldn't cause trouble, be aware that if the Axon Framework application you are working on already exposes MessageHandlerInterceptors and MessageDispatchInterceptors beans in the Spring Application Context. When this is the case, in combination with custom code to wire these beans into your infrastructure components, the chance is high they'll be registered twice due to the aforementioned feature.

As such, we recommend to either:

  1. Remove the custom interceptor auto-configuration, to pass along this task to Axon Framework, or
  2. Exclude the InterceptorAutoConfiguration from your Spring Boot auto-configuration.

By following either road, you should be ascertained that interceptors are not registered twice.

... (truncated)

Commits
  • 9bc19de [maven-release-plugin] prepare release axon-4.11.2
  • 618e7b2 Merge pull request #3410 from AxonFramework/documentation/3348/interceptors-f...
  • 01243a8 Add description on how to create a persistent stream message source
  • 1d265b4 Fine tune JavaDoc
  • 2f66522 Fixed the note, as well as added a hierarchy sample
  • 21a6f9b Add note for Intercepting @EventSourcingHandler annotated methods on..
  • f36581a Merge pull request #3405 from AxonFramework/documentation/3374/allocation-size
  • 184c53f Merge pull request #3404 from AxonFramework/bug/3385/interceptor-chain-not-found
  • 397f961 Add allocation-size details
  • 98fe1c5 Merge branch 'axon-4.11.x' into bug/3385/interceptor-chain-not-found
  • Additional commits viewable in compare view

Updates org.axonframework:axon-spring-boot-autoconfigure from 4.10.0 to 4.11.2

Release notes

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

Axon Framework v4.11.2

⭐ Features

  • #3170 Persistent streams - auto configuration #3339
  • #3170 Persistent streams - automatic configuration #3184
  • Persistent streams - automatic configuration #3170

📈 Enhancements

  • Ignore aggregates that have been AggregateLifecycle#markDeleted when using the Create-if-missing policy. #3333
  • Split default Avro schema store creation from the schema scan #3329
  • Separate AvroSchemaScan based detection of schemas and creation of a default Avro SchemaStore #3328
  • Proper handling of attempts to recreate event sourcing aggregates marked as deleted #3323

🪲 Bug fixes

  • #3385 Align interceptor behavior for Aggregate Members #3404
  • CommandHandlerInterceptor on Aggregate Member only called if Aggregate has CommandHandlerInterceptor as well #3385
  • Fix default Snapshotter throwing IndexOutOfBoundsException #3375
  • fix Correlation data table #3370
  • Fixes subscription query update permits issue #3356
  • #3171 Support @CreationPolicy annotated interface methods again #3335
  • Reset the Coordinator's processing gate if the Coordinator was aborted and rescheduled #3307

❤️ Contributors

We'd like to thank all the contributors who worked on this release!

Axon Framework v4.11.1

⚠️ Chance for duplicate interceptor registration

In 4.11.0 of Axon Framework, Spring Boot auto-configuration support for MessageHandlerInterceptors and MessageDispatchInterceptors was introduced. For those curious how this was achieved, we refer to #3203.

Although the feature on it's own shouldn't cause trouble, be aware that if the Axon Framework application you are working on already exposes MessageHandlerInterceptors and MessageDispatchInterceptors beans in the Spring Application Context. When this is the case, in combination with custom code to wire these beans into your infrastructure components, the chance is high they'll be registered twice due to the aforementioned feature.

As such, we recommend to either:

  1. Remove the custom interceptor auto-configuration, to pass along this task to Axon Framework, or
  2. Exclude the InterceptorAutoConfiguration from your Spring Boot auto-configuration.

By following either road, you should be ascertained that interceptors are not registered twice.

... (truncated)

Commits
  • 9bc19de [maven-release-plugin] prepare release axon-4.11.2
  • 618e7b2 Merge pull request #3410 from AxonFramework/documentation/3348/interceptors-f...
  • 01243a8 Add description on how to create a persistent stream message source
  • 1d265b4 Fine tune JavaDoc
  • 2f66522 Fixed the note, as well as added a hierarchy sample
  • 21a6f9b Add note for Intercepting @EventSourcingHandler annotated methods on..
  • f36581a Merge pull request #3405 from AxonFramework/documentation/3374/allocation-size
  • 184c53f Merge pull request #3404 from AxonFramework/bug/3385/interceptor-chain-not-found
  • 397f961 Add allocation-size details
  • 98fe1c5 Merge branch 'axon-4.11.x' into bug/3385/interceptor-chain-not-found
  • 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

@dependabot
Bump the maven-dependencies group with 5 updates
d59d1fd 
Bumps the maven-dependencies group with 5 updates:

| Package | From | To |
| --- | --- | --- |
| [org.awaitility:awaitility](https://github.com/awaitility/awaitility) | `4.2.0` | `4.3.0` |
| [org.junit:junit-bom](https://github.com/junit-team/junit5) | `5.10.1` | `5.12.2` |
| [org.jacoco:jacoco-maven-plugin](https://github.com/jacoco/jacoco) | `0.8.11` | `0.8.13` |
| [org.axonframework:axon-messaging](https://github.com/AxonFramework/AxonFramework) | `4.10.0` | `4.11.2` |
| [org.axonframework:axon-spring-boot-autoconfigure](https://github.com/AxonFramework/AxonFramework) | `4.10.0` | `4.11.2` |


Updates `org.awaitility:awaitility` from 4.2.0 to 4.3.0
- [Changelog](https://github.com/awaitility/awaitility/blob/master/changelog.txt)
- [Commits](awaitility/awaitility@awaitility-4.2.0...awaitility-4.3.0)

Updates `org.junit:junit-bom` from 5.10.1 to 5.12.2
- [Release notes](https://github.com/junit-team/junit5/releases)
- [Commits](junit-team/junit-framework@r5.10.1...r5.12.2)

Updates `org.jacoco:jacoco-maven-plugin` from 0.8.11 to 0.8.13
- [Release notes](https://github.com/jacoco/jacoco/releases)
- [Commits](jacoco/jacoco@v0.8.11...v0.8.13)

Updates `org.axonframework:axon-messaging` from 4.10.0 to 4.11.2
- [Release notes](https://github.com/AxonFramework/AxonFramework/releases)
- [Changelog](https://github.com/AxonFramework/AxonFramework/blob/master/axon-4-api-changes.md)
- [Commits](AxonFramework/AxonFramework@axon-4.10.0...axon-4.11.2)

Updates `org.axonframework:axon-spring-boot-autoconfigure` from 4.10.0 to 4.11.2
- [Release notes](https://github.com/AxonFramework/AxonFramework/releases)
- [Changelog](https://github.com/AxonFramework/AxonFramework/blob/master/axon-4-api-changes.md)
- [Commits](AxonFramework/AxonFramework@axon-4.10.0...axon-4.11.2)

Updates `org.axonframework:axon-spring-boot-autoconfigure` from 4.10.0 to 4.11.2
- [Release notes](https://github.com/AxonFramework/AxonFramework/releases)
- [Changelog](https://github.com/AxonFramework/AxonFramework/blob/master/axon-4-api-changes.md)
- [Commits](AxonFramework/AxonFramework@axon-4.10.0...axon-4.11.2)

---
updated-dependencies:
- dependency-name: org.awaitility:awaitility
  dependency-version: 4.3.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: maven-dependencies
- dependency-name: org.junit:junit-bom
  dependency-version: 5.12.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-dependencies
- dependency-name: org.jacoco:jacoco-maven-plugin
  dependency-version: 0.8.13
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: maven-dependencies
- dependency-name: org.axonframework:axon-messaging
  dependency-version: 4.11.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-dependencies
- dependency-name: org.axonframework:axon-spring-boot-autoconfigure
  dependency-version: 4.11.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-dependencies
- dependency-name: org.axonframework:axon-spring-boot-autoconfigure
  dependency-version: 4.11.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added this to the Release 4.11.1 milestone May 26, 2025
@dependabot dependabot bot requested a review from a team as a code owner May 26, 2025 13:27
@dependabot dependabot bot requested review from CodeDrivenMitch, MateuszNaKodach and smcvb and removed request for a team May 26, 2025 13:27
@github-actions github-actions bot enabled auto-merge May 26, 2025 13:27
@sonarqubecloud
Copy link

sonarqubecloud bot commented May 26, 2025

Quality Gate Passed Quality Gate passed

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 SonarQube Cloud

@github-actions github-actions bot merged commit 23fa468 into master May 26, 2025
9 checks passed
@dependabot dependabot bot deleted the dependabot/maven/maven-dependencies-8142d2d95f branch May 26, 2025 13:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@github-actions github-actions[bot] github-actions[bot] approved these changes

@CodeDrivenMitch CodeDrivenMitch Awaiting requested review from CodeDrivenMitch CodeDrivenMitch was automatically assigned from AxonFramework/framework-developers

@smcvb smcvb Awaiting requested review from smcvb smcvb was automatically assigned from AxonFramework/framework-developers

@MateuszNaKodach MateuszNaKodach Awaiting requested review from MateuszNaKodach MateuszNaKodach was automatically assigned from AxonFramework/framework-developers

Assignees

No one assigned

Labels

Priority 1: Must Type: Dependency Upgrade

Projects

None yet

Milestone

Release 4.12.0

Development

Successfully merging this pull request may close these issues.

0 participants