It all seems like it should be working for you. The fact that it is MacOS shouldn't matter
Liquibase looks for extensions by the packages listed in Liquibase-Package fields of MANIFEST.MF files. The standard liquibase jar ships with "liquibase.ext" as a package as well as "liquibase.database" and so either of your packages should have worked.
The current DefaultPackageScanClassResolver looks for files ending with .class to find classes. Is your extension packaged with ".groovy" extensions?
Nathan
Liquibase looks for extensions by the packages listed in Liquibase-Package fields of MANIFEST.MF files. The standard liquibase jar ships with "liquibase.ext" as a package as well as "liquibase.database" and so either of your packages should have worked.
The current DefaultPackageScanClassResolver looks for files ending with .class to find classes. Is your extension packaged with ".groovy" extensions?
Nathan
