I would like to discuss a little bit about organization of Axon source base.
My main concern is axon-core module which contains in fact all things starting from JPA, quartz scheduling and spring namespace handlers. This causes a freak pom.xml with optional dependencies which are, in fact, non optional if you want to use JPA store. My proposal in this case is to extract all interfaces to axon-api module. Keep quartz support separate from core and depend only on the API, same for JPA stores which are mainly linked to spring-orm.
Is there any particular reason why all these things are keept in core? This few modules will clean up a structure and modularize Axon.