I had asked about this same problem back in December, but I don’t think I ever found a solution. Now, I’m facing the same problem again, but I don’t think I can so easily step around it as last time.
I have a CustomTaskChange that loads a Spring context configuration. This context contains the various beans I need to perform the migration tasks at hand, without re-writing a lot of code in more traditional JDBC style. I can make this configuration work in a test mode, but when I run “mvn liquibase:update” it fails to find my Spring context file on the classpath. I can see that the context file is in target/classes, though. Currently, my plugin is configured as follows: