When using ByteBuddy classpath discovery, the Axon plugin of our ByteBuddy integration currently relies on Spring's @Component to be available on the compile classpath. We should defensively only apply the mapping if Spring libraries are really available.
The same applies to very fundamental functionality in PluginUtils with references to Spring's ClassUtils.
When using ByteBuddy classpath discovery, the Axon plugin of our ByteBuddy integration currently relies on Spring's
@Componentto be available on the compile classpath. We should defensively only apply the mapping if Spring libraries are really available.The same applies to very fundamental functionality in
PluginUtilswith references to Spring'sClassUtils.