specific order of the jars on classpath should not be important

[Peter Butkovic]

having the restriction that liquibase-sqlfire needs to be on classpath prior to liquibase-core itself seems like a bad practice to me. this might very tricky.

I believe the implementation needs to be adopted in a way we can get rid of it.

┆Issue is synchronized with this Jira Bug by Unito

[Nathan Voxland]

The order should not matter. Can you list the error you are getting?

[Peter Butkovic]

I'm not getting error. This was rather based on what README.md says:

To enable this plugin it needs to be added to the classpath prior to the liquibase.jar. This is due to having to override a couple of datatypes with in liquibase-core project. Therefore it is required that this module be picked up first from the classpath.

...

The simplest way is to add this to the Liquibase distribution's "lib" folder and adjust the shell script to add jars from the lib folder before the liquibase*.jar.

If that's not the case, feel free to close this one and remove the sections from the referred file.
Thanks.

[Nathan Voxland]

I see. I haven't really done anything with this extension to notice that part of the readme. I'll look into it more. Thanks for the follow up.