axon-tracing-opentelemetry with Spring Devtools crashes on start

[tiger-seo]

Basic information

• Axon Framework version: 4.6
• JDK version: 17
• Complete executable reproducer if available (e.g. GitHub Repo):

Steps to reproduce

-add axon-tracing-opentelemetry to dependencies
-start application

Expected behaviour

application running successfully

Actual behaviour

application failed to run because of exception

Caused by: java.lang.ClassCastException: class org.axonframework.tracing.opentelemetry.OpenTelemetrySpanFactory cannot be cast to class org.axonframework.tracing.SpanFactory (org.axonframework.tracing.opentelemetry.OpenTelemetrySpanFactory is in unnamed module of loader 'app'; org.axonframework.tracing.SpanFactory is in unnamed module of loader org.springframework.boot.devtools.restart.classloader.RestartClassLoader @6084846e)

[tiger-seo]

i believe this can be fixed in the same way as in kafka - add the file https://github.com/AxonFramework/extension-kafka/blob/master/kafka/src/main/resources/META-INF/spring-devtools.properties

[smcvb]

We've only recently noticed that the Spring configuration redesign we did in 4.6.0 of Axon Framework leads to the referred-to file no longer being required.
To be more exact, we actually dropped the entire spring-devtools.properties file from Axon Framework in this pull request.

As you can read from the referred-to PR, it will be included in the 4.8.2 release of Axon Framework, which we're planning to release today.
If you're not able to move to 4.8.2 yet, @tiger-seo, know that you can add the spring-devtools.properties file in your application too to achieve the same.
In doing so, you essentially take up the role that Axon Framework took in the past, which should let you move forward.
By the way, if you add the file, you need to define the axon-tracing-opentelemetry module to be included in restarted (just as with the Kafka version you're sharing).

Since the issue is resolved in a more recent version you can utilize soon, and the workaround easy, we've decided to close this issue as resolved.
Feel free to keep commenting here if necessary!