Tim Zöller
As far as I see there is still no solution to the #Liquibase licensing switch with 5.x, is there? Does anybody have insights into the discussions in the #Keycloak project?
Feb 4 at 11:30amWeb
Show threadHeiko DoesFeb 4
@javahippie
Nope. Still curious about what they will do. The GitHub issue looks stale to me.
Show threadjoschiFeb 4

@javahippie I took a brief look into forking the last Liquibase 4.x release before the license switch but everything from build and release tooling over tests was already under a non-free license or so deeply coupled and spread across repositories that I stopped looking into it.

It's not better with Flyway, if anybody would ask. 😅

Show threadStefan PfeifferFeb 4
@joschi @javahippie Time to invent something new!
Show threadTim ZöllerFeb 4

@spfeiffer @joschi I like what @lukaseder did with jOOQ: https://github.com/jOOQ/jOOQ/issues/19353

Not really possible for us with Operaton, because people got used to Camunda / Operaton updating its own schemas upon first deployment... or is it 🤔