Maven artefacts version number will cause collision?

General Discussion
1

Hi -

I am trying to start with liquibase and have a question:

My project is a muliti module project, where every module has its own changeset files in the resources, and thus in the jar -

When I execute a liquibase:update, liquibase picks the files from the jars in the classpath -

What happens if the jars change their version in the future?

Greetings, Ron

2

Which jars are you specifically concerned about?
If it is a multi-module build, then generally all artifacts generated from the modules normally use the same version number, of which you are in full control of.

Do you have a “master” Liquibase changeset file that pulls the various changeset files together that you are running the liquibase:update from?