The Developer Tools documentation indicates that you can specify additional paths outside of the classpath that will be watched for changes here. This does indeed work.

Since the Java-based migrations are Spring Beans themselves, you can inject other beans. If those beans are somehow associated with JPA, the application fails on startup because a circular dependency ...