nx-gs-db-migrator-liquibase5
Applies the nx-gs-db-migrations changelog through Liquibase 5. The core
calls it once at start, before any module runs, so no module sees a missing or outdated table.
Coordinates
Section titled “Coordinates”app.l2nx:nx-gs-db-migrator-liquibase5Java 17. Release tag db-migrator-liquibase5/vX.Y.Z. Versions on
maven-oss.
When the host needs it
Section titled “When the host needs it”On every game server: without a SchemaMigrator on the classpath the adapter goes FAILED at start. A login server
does not need it.
What the host provides
Section titled “What the host provides”org.liquibase:liquibase-core5.x on the classpath. The adapter does not bundle Liquibase.- The
JdbcConnectionSourcethe rest of the adapter uses. Its database user needs write and DDL rights on thel2nx_*tables andCREATEin the schema.
What to know
Section titled “What to know”- The migrator keeps its history in its own tables
l2nx_databasechangelogandl2nx_databasechangeloglock, and never reads or writes the host’s own Liquibase history or settings. - A second run on an up-to-date database changes nothing.
- If a previous run died mid-migration and left the lock behind, the start fails and reports the lock holder. Releasing the lock is up to the operator: the adapter does not release a lock it did not take.
Configuration
Section titled “Configuration”No keys of its own.
