Custom Task Change "teardown"?

Quick question.  We are using liquibase to do some migrations, however they don’t hit the database directly.  In our case, we are boostraping the Spring configuration we have in our application and calling some common services that we have to handle administration of this data.  So to do this we created a migration that implements the CustomTaskChange interface.  In this interface there is a setUp method that we use to load the ApplicationContext and inject the services as needed.  However, we’ve discovered a small issue.  There doesn’t seem to be a tearDown or other way to clean up after a migration is complete.  Because of this, there is no way for us to nicely clean up the spring container by closing our app context. 

Am I missing something?  If not, I’d definitely be interested in getting this feature added (I’m assuming this wouldn’t be a huge architectural shift).  Any insight anyone can provide is appreciated.  Thanks in advance!

Michael Minella

No, it is not currently implemented, but would be good to add if you wanted to take a look at it. 

Let me know if you have questions on how to get started