The Axon 3 documentation recommends putting @EnableAxon on a Spring configuration class to automatically locate components and set up reasonable defaults. But the Javadoc for @EnableAxon recommends against using it and warns that it will probably be removed. Which advice should I believe?
One twist is that although my application uses Spring, it isn't built on top of Spring Boot. The @EnableAxon Javadoc seems to imply that Spring Boot is going to be a requirement for automatic configuration at some point (at least that's how I interpret the fact that it recommends using a Spring-Boot-specific module). Is that the case? If so, is my best bet to ignore all the autoconfiguration stuff entirely and instead directly call the configuration API to explicitly set everything up?