axonframework/axon-bom

Axon Bill of Materials (BOM) - provides managed dependencies for all Axon artifacts

axon-bom's Issues

Add Project Reactor version

Enhancement Description

Add dependencies for reactor as there are issues when using incorrect version of reactor.

Current Behaviour

User has to specify the version of reactor in their own pom file, potentially leading to issues when upgrading from older Axon version.

Wanted Behaviour

Possible Workarounds

add axon-server-plugin-api

Feature Description

I would like to have the latest version of the server plugin api in this BOM as well

<!-- https://mvnrepository.com/artifact/io.axoniq/axonserver-plugin-api -->
<dependency>
    <groupId>io.axoniq</groupId>
    <artifactId>axonserver-plugin-api</artifactId>
    <version>4.5</version>
</dependency>

Bom versioning question

1st: cool that there is a BOM now

2nd: Question: what is your versioning idea? coupling the extension versions to the axon-framework release versions seems a bit strange to me ... when 4.5 main release is out and we adopt for example extension-kotlin to support new features of 4.5 this will result in a new version of extension-kotlin and thus will require a new bom release ...

Possible Solutions:

• provide two boms: one just containing the "main" axon-framework components released under 4.5 (or 4.4.7, ...) and one that is released more frequently, referring to the first one and updating extension versions
• a versioning scheme that contains the main framework version but supports an additional version counter to reflect intermediate changes extensions, which could either be a four digit version (4.4.6.1) or a suffixed version (1.2.3-A4.4.6) where the part after the "-" is the main framework version and the part before the continuing version of the bom artifact.

Did you consider this? What is the plan, what's your opinion?

Provide Bill of Materials Artifact

@joshiste commented on Wed Aug 21 2019

Imho it would be great if you'd provide a maven bill of materials artifact for axon. So you can import it into the dependencyManagement and have all versions defined in one place.

---

@smcvb commented on Wed Aug 21 2019

Fair suggestion @joshiste, we'll look into this.

---

@smcvb commented on Fri Jan 08 2021

This issue is currently in progress, and can be spotted as a dedicated repository here.

axon-kotlin-test is missing from BOM

Enhancement Description

Add axon-kotlin-test definition i BOM

Current Behaviour

No dependency defined

Wanted Behaviour

<dependency>
    <groupId>org.axonframework.extensions.kotlin</groupId>
    <artifactId>axon-kotlin-test</artifactId>
    <version>...</version>
</dependency>

Possible Workarounds

Support Axon 4.7

Feature Description

Hello, Looks like all dependencies related to this bom are already updated to axon 4.7, when will it be available to be used?

Thanks.

Current Behaviour

Just released til version 4.6.3

Wanted Behaviour

Release support to version 4.7.x

Possible Workarounds

Put the versions directly in dependencies without bom to auto-fill the versions.

Upgrade Tracing Extension version from 4.6.0 to 4.6.1.

Upgrade Tracing Extension version from 4.6.0 to 4.6.1.