Hey Tim, that's the the thing, the aot jar shouldn't be required at all so it's not bundled. I did manage to get past this issue when I upgraded the spring parent version in the web app relying on the mybatis project, so that's good, however it *did* seem to be working without having to do that, so not sure what changed. Forcing that upgrade to the webapp using the newer mybatis project, seems is going to force a lot more upgrades to the project, which is ok just curious what happened to all of a sudden have the project complaining about not finding AotDetector.
My mybatis services jar (not an uber jar) is a mybatis project using spring-boot-starter-parent 3.4.1and mybatis spring boot starter 3.0.4.
The webapp using this jar is using spring-boot-starter-parent 2.7.9, which I believe "used" to be working - but something I added/changed caused the error I initially posted about. If I upgrade the web app to a newer version of Spring (3.x versions) which requires changing to jakarta packages etc, I could get things working so I can end up managing. Still would be curious what caused things to start throwing the error about mybatis' mapper scanner needing to find AotDetector:
Caused by: java.lang.NoClassDefFoundError: org/springframework/aot/AotDetector
at org.mybatis.spring.mapper.ClassPathMapperScanner.<init>(ClassPathMapperScanner.java:95)