First of all, I would like to congratulate you on this awesome piece of software, I have successfully used it for the last 3 years.
Then, let me explain the use-case justifying this issue.
My client runs some Oracle synonym drop/create/grant scripts, executed by SYSTEM user. However, 1 server hosts multiple environments and they would really like to avoid the creation of Liquibase tables in this shared schema.
As a quickfix/workaround, I dynamically prefixed my changesets by environment in order to avoid clashes between changelog entries. But that does not solve the fundamental problem that LQB tables are created in SYSTEM schema.
I was thinking about introducing a new parameter, allowing to override the LQB table destination schema (in my case, the schema where synonyms are created). This would maintain the current behaviour by default (thus remaining backwards-compatible) and solve my problem.
What are your thoughts on this?