I assumed that and can definitely understand that this would imply major changes.
So we will discuss the mentioned alternatives in developer team. As I see the default generated envers scheme uses an auto incremented column for revision ID (REVINFO.REV). I assume it would also be possible to use database sequences for that field right? This would ease the integration with liquibase generated scripts.