Re : Replacement for missing liquibase classes moving from liquibase 2.0.3 to 3.3.0

So it looks like your class is mainly an alternative to the normal Liquibase class-finding logic to better fit in your environment? You aren't necessarily using the missing classes, but you need to make sure all the standard liquibase classes are being loaded so that it works as it should. Is that correct? Or are there extension classes of your own that are not compiling?