Also, make sure you do not use --classpath liquibase argument to pass in your custom extension jar. It seems to only load the database driver.
Below however, did work and added my custom jar to the classpath so it got loaded when the parser loaded the helloWorld change.
So for instance the below did not work ---> (liquibase-custom.jar would not be loaded only the jsqlconnect jar would be loaded and it wouldn't find my custom hello world extension)
java -jar liquibase-core-3.5.3.jar --changeLogFile=test-update.xml --username=username --password=password
--driver=com.jnetdirect.jsql.JSQLDriver --url="jdbc:JSQLConnect://localhost:1433;databaseName=dbname"
--classpath=liquibase-custom.jar;jsqlconnect-5.5.32.jar update
--driver=com.jnetdirect.jsql.JSQLDriver --url="jdbc:JSQLConnect://localhost:1433;databaseName=dbname"
--classpath=liquibase-custom.jar;jsqlconnect-5.5.32.jar update
Below however, did work and added my custom jar to the classpath so it got loaded when the parser loaded the helloWorld change.
java -cp jsqlconnect-5.5.32.jar;liquibase-custom.jar;liquibase-core-3.5.3.jar
liquibase.integration.commandline.Main --changeLogFile=test-update.xml
--username=username --password=password
--driver=com.jnetdirect.jsql.JSQLDriver --url="jdbc:JSQLConnect://localhost:1433;databaseName=dbname"
--classpath=jsqlconnect-5.5.32.jar update
--driver=com.jnetdirect.jsql.JSQLDriver --url="jdbc:JSQLConnect://localhost:1433;databaseName=dbname"
--classpath=jsqlconnect-5.5.32.jar update
(This wasn't apparent to me and I was confused why classpath didn't work as I thought it should .....)